Seriously Dated Interface
Solid Iron <[email protected]> Thu, 2 Feb 2017 22:52:02 -0500
| Newsgroups | gmane.mail.squirrelmail.devel |
|---|---|
| Message-ID | <CABCb=YGqfwjeRhgit-tBxZa7FGotkgHu-dh07yqixcxWFGapZA@mail.gmail.com> |
--===============7164553516257562614== Content-Type: multipart/alternative; boundary=001a113521de66a02e05479834db --001a113521de66a02e05479834db Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi everyone, I will prefix this by saying that this is my first time posting to this list and that I have never contributed to SquirrelMail development so feel free to ignore my question. However I own a software development firm. We write mostly web-based business software on .NET framework with an MS-SQL backend. We have been doing this since the days of =E2=80=9Cclassic=E2=80=9D ASP in the late 1990= =E2=80=99s. So while I haven=E2=80=99t contributed specifically to SquirrelMail I do nevertheless = have a pretty good idea of what it takes to develop a robust modern web-based application that people use every day. I also have a good grasp of what users expect when it comes to web-based applications. Nevertheless, as I said before, feel free to ignore my question. Has the issue of the *seriously dated* user experience of SquirrelMail got anyone=E2=80=99s attention? With the explosion of web-based email apps (Gma= il, Outlook.com, Microsoft Exchange, RoundCube, etc) users expect a radically different experience then what they are getting from SquirrelMail. Any IT administrator deploying SquirrelMail today is likely to be perceived by their user base as having deployed an archaic solution. Web-based apps in general (Office 365, Google Docs, Facebook, etc) are pushing the limits of what=E2=80=99s possible and redefining what users exp= ect. Let=E2=80=99s ask the hard question: is SquirrelMail even close?!?? Are the= re any plans to get it there? It seems to me (if the screenshots on the squirrelmail.org website are any indication) that all serious development on SquirrelMail stalled in 2002 or thereabouts. Sorry if this sounds harsh... Today if I was looking for an open source web-based IMAP client I would be looking at RoundCube =E2=80=93 no question= . SquirrelMail was the pioneer. Why aren=E2=80=99t we there? Best, Solid Iron On Sun, Dec 4, 2016 at 9:10 PM, Kevin Buckley <[email protected]> wrote: > OS NetBSD 7.0_STABLE > Software Stack PkgSrc > SquirrelMail 1.4.23pre14605 > Apache 2 Apache/2.2.31 (Unix) mod_ssl/2.2.31 OpenSSL/1.0.1u DAV/2 > PHP/7.0.13 > PHP 7.0.135.6.28-1 > > > Before I start, a bit of info on the SquirrelMail version, because I > was told that we are reasonably up-to-date, in that the PkgSrc commit > says: > > ---------------------------- > revision 1.131 > date: 2016-11-18 04:10:07 +1300; author: taca; state: Exp; lines: +2 > -3; commitid: TckPzUpbAFssFuuz; > Update squirrelmail to 1.4.23pre14605, latest snapshot. > PHP 7.0 support should be improved, too. > > - Added new "smtp_helo_override" hook; allows plugins to override > the HELO host sent to the SMTP server when sending messages > - Added STARTTLS support for both IMAP and SMTP connections > - Added PDO support for database connections, so no external > database module needs to be installed > ---------------------------- > > furthermore, I also note that this issue echoes that described in > this (Dec 2016) devel list posting > > - https://sourceforge.net/p/squirrelmail/mailman/message/35527151/ > > except that ours > > 1) is only using a secure (https) connection > 2) exhibits the "blank page" but DOESN'T send a message. > 3) is using PHP7, not the PHP5. > > but here we go with the actual issue. > > Our School's webservers updated to PHP7 over the weekend and one of the > issues in the wake of that has been that SquirrelMail works to a degree > (we're a Uni, but no pun intended) but no longer seems to be able to > send out mail, either when doing a "Compose" or a reply to. > > The webserver logs tell us that, following a click on the "Send" button > we're falling foul of these four routines > > squirrelmail/class/html.class.php > squirrelmail/class/mime/Disposition.class.php > squirrelmail/class/mime/Language.class.php > squirrelmail/class/mime/ContentType.class.php > > which give error (not warning) messages akin to > > PHP Deprecated: Methods with the same name as their class will not be > constructors in a future version of PHP; > > although that might not be the whole story as some parts of SquirrelMail > clearly still work. > > I tried adding in "proper" __constructor functions, in the manner of the > fix described here > > - https://cweiske.de/tagebuch/php4-constructors-php7.htm > > to those four files, however that just moves the same issue down into > (or possibly across) the SquirrelMail stack, and we see some other > webserver error logs, three indicating similar "deprecated constructor" > stuff from different fucntions: > > squirrelmail/functions/addressbook.php > squirrelmail/functions/abook_local_file.php > squirrelmail/functions/abook_ldap_server.php > > however, two more exhibit different errors > > PHP Deprecated: Non-static method Message::parseStructure() should not > be called statically in > > squirrelmail/functions/mime.php on line 36, > squirrelmail/class/mime/Message.class.php on line 296, > > both with the same referrer > > referer: > https://our.host/squirrelmail/src/right_main.php?PG_SHOWALL=3D > 0&sort=3D0&startMessage=3D1&mailbox=3DINBOX > > > Reading around the interweb thing, especially this posting in the > squirrelmail-devel list > > - https://sourceforge.net/p/squirrelmail/mailman/message/35457393/ > > suggests that there's a snapshot version out there in which all this may > have been > fixed ? > > What I'd like to know is whether there is an identifiable set of patches > that I could use, so to to patch the PkgSrc version of SquirrelMail, rath= er > than go straight to a /newer/the most recent/ snapshot version that will > have extra (or even reduced) functionality, which the PkgSrc folk clearly > decided wasn't the way forwards for them. > > I suppose what I am asking is, did you do the PHP7 updates in an SVN bran= ch > that I could take the top off, rather than taking the most recent branch > and > extracting out only the "solution" to the "deprecated" errors ? > > I also suppose that the errors we're seeing could be something else > altogether! > > Either way, and it pretty much covers most "ways", any insight would be > useful, > > Kevin Buckley > eScience Consultant > School of Engineering and Computer Science > Victoria University of Wellington > New Zealand > > ------------------------------------------------------------ > ------------------ > ----- > squirrelmail-devel mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > List address: [email protected] > List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel > List info (subscribe/unsubscribe/change options): > https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel > --001a113521de66a02e05479834db Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi everyone,<br><br>I will prefix this by saying that this= is my first time posting to this list and that I have never contributed to= SquirrelMail development so feel free to ignore my question.<br><br>Howeve= r I own a software development firm. We write mostly web-based business sof= tware on .NET framework with an MS-SQL backend. We have been doing this sin= ce the days of =E2=80=9Cclassic=E2=80=9D ASP in the late 1990=E2=80=99s. So= while I haven=E2=80=99t contributed specifically to SquirrelMail I do neve= rtheless have a pretty good idea of what it takes to develop a robust moder= n web-based application that people use every day. I also have a good grasp= of what users expect when it comes to web-based applications. Nevertheless= , as I said before, feel free to ignore my question.<br><br>Has the issue o= f the <u><b>seriously dated</b></u> user experience of SquirrelMail got any= one=E2=80=99s attention? With the explosion of web-based email apps (Gmail,= Outlook.com, Microsoft Exchange, RoundCube, etc) users expect a radically = different experience then what they are getting from SquirrelMail. Any IT a= dministrator deploying SquirrelMail today is likely to be perceived by thei= r user base as having deployed an archaic solution.<br><br>Web-based apps i= n general (Office 365, Google Docs, Facebook, etc) are pushing the limits o= f what=E2=80=99s possible and redefining what users expect. Let=E2=80=99s a= sk the hard question: is SquirrelMail even close?!?? Are there any plans to= get it there?<br><br>It seems to me (if the screenshots on the <a href=3D"= http://squirrelmail.org">squirrelmail.org</a> website are any indication) t= hat all serious development on SquirrelMail stalled in 2002 or thereabouts.= <br><br>Sorry if this sounds harsh...=C2=A0 Today if I was looking for an o= pen source web-based IMAP client I would be looking at RoundCube =E2=80=93 = no question. SquirrelMail was the pioneer. Why aren=E2=80=99t we there?<br>= <br>Best,<br>Solid Iron<br><div class=3D"gmail_extra"><br><div class=3D"gma= il_quote">On Sun, Dec 4, 2016 at 9:10 PM, Kevin Buckley <span dir=3D"ltr">&= lt;<a href=3D"mailto:[email protected]" target=3D"_blank">Kevin.B= [email protected]</a>></span> wrote:<br><blockquote class=3D"gmail_qu= ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20= 4);padding-left:1ex">OS=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Net= BSD 7.0_STABLE<br> Software Stack=C2=A0 PkgSrc<br> SquirrelMail=C2=A0 =C2=A0 1.4.23pre14605<br> Apache 2=C2=A0 =C2=A0 =C2=A0 =C2=A0 Apache/2.2.31 (Unix) mod_ssl/2.2.31 Ope= nSSL/1.0.1u DAV/2<br> PHP/7.0.13<br> PHP=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A07.0.135.6.28-1<br> <br> <br> Before I start, a bit of info on the SquirrelMail version, because I<br> was told that we are reasonably up-to-date, in that the PkgSrc commit<br> says:<br> <br> ----------------------------<br> revision 1.131<br> date: 2016-11-18 04:10:07 +1300;=C2=A0 author: taca;=C2=A0 state: Exp;=C2= =A0 lines: +2<br> -3;=C2=A0 commitid: TckPzUpbAFssFuuz;<br> Update squirrelmail to 1.4.23pre14605, latest snapshot.<br> PHP 7.0 support should be improved, too.<br> <br> =C2=A0 =C2=A0- Added new "smtp_helo_override" hook; allows plugin= s to override<br> =C2=A0 =C2=A0 =C2=A0the HELO host sent to the SMTP server when sending mess= ages<br> =C2=A0 =C2=A0- Added STARTTLS support for both IMAP and SMTP connections<br= > =C2=A0 =C2=A0- Added PDO support for database connections, so no external<b= r> =C2=A0 =C2=A0 =C2=A0database module needs to be installed<br> ----------------------------<br> <br> furthermore, I also note that this issue echoes that described in<br> this (Dec 2016) devel list posting<br> <br> =C2=A0 =C2=A0 - <a href=3D"https://sourceforge.net/p/squirrelmail/mailman/m= essage/35527151/" rel=3D"noreferrer" target=3D"_blank">https://sourceforge.= net/p/squi<wbr>rrelmail/mailman/message/35527<wbr>151/</a><br> <br> except that ours<br> <br> 1) is only using a secure (https) connection<br> 2) exhibits the "blank page" but DOESN'T send a message.<br> 3) is using PHP7, not the PHP5.<br> <br> but here we go with the actual issue.<br> <br> Our School's webservers updated to PHP7 over the weekend and one of the= <br> issues in the wake of that has been that SquirrelMail works to a degree<br> (we're a Uni, but no pun intended) but no longer seems to be able to<br= > send out mail, either when doing a "Compose" or a reply to.<br> <br> The webserver logs tell us that, following a click on the "Send" = button<br> we're falling foul of these four routines<br> <br> squirrelmail/class/html.class.<wbr>php<br> squirrelmail/class/mime/Dispos<wbr>ition.class.php<br> squirrelmail/class/mime/Langua<wbr>ge.class.php<br> squirrelmail/class/mime/Conten<wbr>tType.class.php<br> <br> which give error (not warning) messages akin to<br> <br> PHP Deprecated:=C2=A0 Methods with the same name as their class will not be= <br> =C2=A0 constructors in a future version of PHP;<br> <br> although that might not be the whole story as some parts of SquirrelMail<br= > clearly still work.<br> <br> I tried adding in "proper" __constructor functions, in the manner= of the<br> fix described here<br> <br> =C2=A0 =C2=A0 - <a href=3D"https://cweiske.de/tagebuch/php4-constructors-ph= p7.htm" rel=3D"noreferrer" target=3D"_blank">https://cweiske.de/tagebuch/ph= <wbr>p4-constructors-php7.htm</a><br> <br> to those four files, however that just moves the same issue down into<br> (or possibly across) the SquirrelMail stack, and we see some other<br> webserver error logs, three indicating similar "deprecated constructor= "<br> stuff from different fucntions:<br> <br> squirrelmail/functions/address<wbr>book.php<br> squirrelmail/functions/abook_l<wbr>ocal_file.php<br> squirrelmail/functions/abook_l<wbr>dap_server.php<br> <br> however, two more exhibit different errors<br> <br> PHP Deprecated:=C2=A0 Non-static method Message::parseStructure() should no= t<br> be called statically in<br> <br> squirrelmail/functions/<a href=3D"http://mime.ph">mime.ph</a><wbr>p=C2=A0 o= n line 36,<br> squirrelmail/class/mime/Messag<wbr>e.class.php on line 296,<br> <br> both with the same referrer<br> <br> referer:<br> <a href=3D"https://our.host/squirrelmail/src/right_main.php?PG_SHOWALL=3D0&= amp;sort=3D0&startMessage=3D1&mailbox=3DINBOX" rel=3D"noreferrer" t= arget=3D"_blank">https://our.host/squirrelmail/<wbr>src/right_main.php?PG_S= HOWALL=3D<wbr>0&sort=3D0&startMessage=3D1&mailbo<wbr>x=3DINBOX<= /a><br> <br> <br> Reading around the interweb thing, especially this posting in the<br> squirrelmail-devel list<br> <br> =C2=A0 =C2=A0 - <a href=3D"https://sourceforge.net/p/squirrelmail/mailman/m= essage/35457393/" rel=3D"noreferrer" target=3D"_blank">https://sourceforge.= net/p/squi<wbr>rrelmail/mailman/message/35457<wbr>393/</a><br> <br> suggests that there's a snapshot version out there in which all this ma= y<br> have been<br> fixed ?<br> <br> What I'd like to know is whether there is an identifiable set of patche= s<br> that I could use, so to to patch the PkgSrc version of SquirrelMail, rather= <br> than go straight to a /newer/the most recent/ snapshot version that will<br= > have extra (or even reduced) functionality, which the PkgSrc folk clearly<b= r> decided wasn't the way forwards for them.<br> <br> I suppose what I am asking is, did you do the PHP7 updates in an SVN branch= <br> that I could take the top off, rather than taking the most recent branch an= d<br> extracting out only the "solution" to the "deprecated" = errors ?<br> <br> I also suppose that the errors we're seeing could be something else<br> altogether!<br> <br> Either way, and it pretty much covers most "ways", any insight wo= uld be<br> useful,<br> <br> Kevin Buckley<br> eScience Consultant<br> School of Engineering and Computer Science<br> Victoria University of Wellington<br> New Zealand<br> <br> ------------------------------<wbr>------------------------------<wbr>-----= -------------<br> -----<br> squirrelmail-devel mailing list<br> Posting guidelines: <a href=3D"http://squirrelmail.org/postingguidelines" r= el=3D"noreferrer" target=3D"_blank">http://squirrelmail.org/postin<wbr>ggui= delines</a><br> List address: <a href=3D"mailto:[email protected]" t= arget=3D"_blank">[email protected]<wbr>eforge.net</a><br> List archives: <a href=3D"http://news.gmane.org/gmane.mail.squirrelmail.dev= el" rel=3D"noreferrer" target=3D"_blank">http://news.gmane.org/gmane.ma<wbr= >il.squirrelmail.devel</a><br> List info (subscribe/unsubscribe/change options): <a href=3D"https://lists.= sourceforge.net/lists/listinfo/squirrelmail-devel" rel=3D"noreferrer" targe= t=3D"_blank">https://lists.sourceforge.net/<wbr>lists/listinfo/squirrelmail= -de<wbr>vel</a><br> </blockquote></div><br></div></div> --001a113521de66a02e05479834db-- --===============7164553516257562614== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot --===============7164553516257562614== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ----- squirrelmail-devel mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: [email protected] List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel --===============7164553516257562614==--