From: Periko S. <phe...@gm...> - 2013-04-25 04:31:23
|
I have squirrelmail-1.4.2, freebsd 8.x and php 5.4. I had read that exist a patch to fix the issue with php5.4 because squirrelmail complaint about php5.4, I had seen the patches, download them, but could some point how to apply them? I did this: cd /usr/local/www/squirrelmail/plugins/administrator download my patches patch -p1 < patch-1 It start asking what file to patch. I did something wrong? Thanks!!! |
From: Paul L. <pa...@sq...> - 2013-04-25 14:36:21
|
On Wed, Apr 24, 2013 at 9:31 PM, Periko Support <phe...@gm...> wrote: > I have squirrelmail-1.4.2, freebsd 8.x and php 5.4. > > I had read that exist a patch to fix the issue with php5.4 because > squirrelmail complaint about php5.4, I had seen the patches, download them, > but could some point how to apply them? Just use a snapshot of version 1.4.23 from the downloads page. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Periko S. <phe...@gm...> - 2013-04-25 17:47:50
|
I will do it, thanks!!! On Thu, Apr 25, 2013 at 7:35 AM, Paul Lesniewski <pa...@sq...>wrote: > On Wed, Apr 24, 2013 at 9:31 PM, Periko Support > <phe...@gm...> wrote: > > I have squirrelmail-1.4.2, freebsd 8.x and php 5.4. > > > > I had read that exist a patch to fix the issue with php5.4 because > > squirrelmail complaint about php5.4, I had seen the patches, download > them, > > but could some point how to apply them? > > Just use a snapshot of version 1.4.23 from the downloads page. > > -- > Paul Lesniewski > SquirrelMail Team > Please support Open Source Software by donating to SquirrelMail! > http://squirrelmail.org/donate_paul_lesniewski.php > > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > ----- > squirrelmail-users mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > List address: squ...@li... > List archives: http://news.gmane.org/gmane.mail.squirrelmail.user > List info (subscribe/unsubscribe/change options): > https://lists.sourceforge.net/lists/listinfo/squirrelmail-users > |
From: Tóth A. <at...@at...> - 2013-06-16 18:13:46
|
Dear Paul, The new bug tracker interface placed my reply under your original post, not at the end of the thread. I continued browsing and found this: http://nikic.github.io/2012/01/28/htmlspecialchars-improvements-in-PHP-5-4.html - justifying the changes of htmlspecialchars from PHP 5.3 to 5.4 I've also checked out the manual page again: http://php.net/manual/en/function.htmlspecialchars.php And no shit: iso-8859-2 is not supported. I don't know PHP developers keep pissing on this charset over and over again. I'd also like to make it clear: all my system and my databases are on utf-8 (including squirrelmail). I'm not generating iso-8859-2 content at all. It's hotmail (see my sample images in the previous mail), yahoo or sometimes even gmail is guilty of sending quoted printable iso-8859-2 contents. What can be done? Some kind of double conversion? First convert it to utf-8? If there's anything I must test, please let me know... I keep thinking an may try out something on my own. Thx: Dw. -- dr Tóth Attila, Radiológus, 06-20-825-8057 Attila Toth MD, Radiologist, +36-20-825-8057 2013.Április 25.(Cs) 16:35 időpontban Paul Lesniewski ezt írta: > On Wed, Apr 24, 2013 at 9:31 PM, Periko Support > <phe...@gm...> wrote: >> I have squirrelmail-1.4.2, freebsd 8.x and php 5.4. >> >> I had read that exist a patch to fix the issue with php5.4 because >> squirrelmail complaint about php5.4, I had seen the patches, download >> them, >> but could some point how to apply them? > > Just use a snapshot of version 1.4.23 from the downloads page. > > -- > Paul Lesniewski > SquirrelMail Team > Please support Open Source Software by donating to SquirrelMail! > http://squirrelmail.org/donate_paul_lesniewski.php > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring > service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > ----- > squirrelmail-users mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > List address: squ...@li... > List archives: http://news.gmane.org/gmane.mail.squirrelmail.user > List info (subscribe/unsubscribe/change options): > https://lists.sourceforge.net/lists/listinfo/squirrelmail-users > |
From: Tóth A. <at...@at...> - 2013-06-16 18:23:04
|
Dear Paul, I've updated the quoted printable bug in the tracker system after I tried your quoted printable patch. I attach some sample screen save images just to let you have a clue on what's happening. Thx: Dw. -- dr Tóth Attila, Radiológus, 06-20-825-8057 Attila Toth MD, Radiologist, +36-20-825-8057 2013.Április 25.(Cs) 16:35 időpontban Paul Lesniewski ezt írta: > On Wed, Apr 24, 2013 at 9:31 PM, Periko Support > <phe...@gm...> wrote: >> I have squirrelmail-1.4.2, freebsd 8.x and php 5.4. >> >> I had read that exist a patch to fix the issue with php5.4 because >> squirrelmail complaint about php5.4, I had seen the patches, download >> them, >> but could some point how to apply them? > > Just use a snapshot of version 1.4.23 from the downloads page. > > -- > Paul Lesniewski > SquirrelMail Team > Please support Open Source Software by donating to SquirrelMail! > http://squirrelmail.org/donate_paul_lesniewski.php > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring > service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > ----- > squirrelmail-users mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > List address: squ...@li... > List archives: http://news.gmane.org/gmane.mail.squirrelmail.user > List info (subscribe/unsubscribe/change options): > https://lists.sourceforge.net/lists/listinfo/squirrelmail-users > |
From: Tóth A. <at...@at...> - 2014-04-05 00:10:26
|
Dear Paul, I've been using a reasonably new pull of 1.4.23 SVN squirrelmail. The quoted printable problems seems to be OK using a prior patch in the tree. Recently I received an email, for which the subject appears empty. Therefore I cannot open it in squirrelmail. Android email application and alpine shows the subject and can open it. It is an utf-8 subject. I'm not sure what the problem is. But I attach the message in an mbox format. Please let me know what else you need to deal with the problem. Is it reproducible after all? Thanks: Dw. -- dr Tóth Attila, Radiológus, 06-20-825-8057 Attila Toth MD, Radiologist, +36-20-825-8057 2013.Április 25.(Cs) 16:35 időpontban Paul Lesniewski ezt írta: > On Wed, Apr 24, 2013 at 9:31 PM, Periko Support > <phe...@gm...> wrote: >> I have squirrelmail-1.4.2, freebsd 8.x and php 5.4. >> >> I had read that exist a patch to fix the issue with php5.4 because >> squirrelmail complaint about php5.4, I had seen the patches, download >> them, >> but could some point how to apply them? > > Just use a snapshot of version 1.4.23 from the downloads page. > > -- > Paul Lesniewski > SquirrelMail Team > Please support Open Source Software by donating to SquirrelMail! > http://squirrelmail.org/donate_paul_lesniewski.php > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring > service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > ----- > squirrelmail-users mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > List address: squ...@li... > List archives: http://news.gmane.org/gmane.mail.squirrelmail.user > List info (subscribe/unsubscribe/change options): > https://lists.sourceforge.net/lists/listinfo/squirrelmail-users > |
From: Paul L. <pa...@sq...> - 2014-05-14 06:29:09
|
On Fri, Apr 4, 2014 at 5:10 PM, "Tóth Attila" <at...@at...> wrote: > Dear Paul, > > I've been using a reasonably new pull of 1.4.23 SVN squirrelmail. The > quoted printable problems seems to be OK using a prior patch in the tree. This one's unrelated > Recently I received an email, for which the subject appears empty. > Therefore I cannot open it in squirrelmail. Android email application and > alpine shows the subject and can open it. It is an utf-8 subject. > I'm not sure what the problem is. But I attach the message in an mbox format. The subject is malformed. =w6 is not valid quoted printable. Looks like other clients might be substituting + for = as a fix, which you can do by hand to see the subject get displayed. The right fix is to address it at the source. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Tóth A. <at...@at...> - 2014-05-14 09:13:19
|
Dear Paul, I'm sorry for bothering you. You are right that it's unrelated. The subject header is not a printed quotable, but it is base64 encoded (?UTF-8?B?): =?UTF-8?B?VsOhOiBSZTogVMOhasOpa296dGF0w7MgUEFDUy1vdCDDqXJpbnTFkQ==IMOhcmFtc3rDvG5ldHLFkWw=?= If I try to use a base64 decoder, it gives back gibberish. The from header is also base64 encoded. Using a decoder I can correctly decode that. Squirrelmail also shows the sender like it should. Somehow other clients manage to decode it. So there might be some problem with the encoding for base64, not just for quoted printable. I don't know how I can help you to figure it out. But it would be good to implement some workaround to display at least something for the subject to be able to open it. I would do whatever you ask to help studying this issue. Many thanks: Attila -- dr Tóth Attila, Radiológus, 06-20-825-8057 Attila Toth MD, Radiologist, +36-20-825-8057 2014.Május 14.(Sze) 08:28 időpontban Paul Lesniewski ezt írta: > On Fri, Apr 4, 2014 at 5:10 PM, "Tóth Attila" <at...@at...> wrote: >> Dear Paul, >> >> I've been using a reasonably new pull of 1.4.23 SVN squirrelmail. The >> quoted printable problems seems to be OK using a prior patch in the >> tree. > > This one's unrelated > >> Recently I received an email, for which the subject appears empty. >> Therefore I cannot open it in squirrelmail. Android email application >> and >> alpine shows the subject and can open it. It is an utf-8 subject. >> I'm not sure what the problem is. But I attach the message in an mbox >> format. > > The subject is malformed. =w6 is not valid quoted printable. Looks > like other clients might be substituting + for = as a fix, which you > can do by hand to see the subject get displayed. The right fix is to > address it at the source. > > -- > Paul Lesniewski > SquirrelMail Team > Please support Open Source Software by donating to SquirrelMail! > http://squirrelmail.org/donate_paul_lesniewski.php > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform > available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > ----- > squirrelmail-users mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > List address: squ...@li... > List archives: http://news.gmane.org/gmane.mail.squirrelmail.user > List info (subscribe/unsubscribe/change options): > https://lists.sourceforge.net/lists/listinfo/squirrelmail-users > |
From: Paul L. <pa...@sq...> - 2014-05-14 15:52:12
|
On Wed, May 14, 2014 at 2:12 AM, "Tóth Attila" <at...@at...> wrote: > Dear Paul, > > I'm sorry for bothering you. You are right that it's unrelated. > The subject header is not a printed quotable, but it is base64 encoded > (?UTF-8?B?): > =?UTF-8?B?VsOhOiBSZTogVMOhasOpa296dGF0w7MgUEFDUy1vdCDDqXJpbnTFkQ==IMOhcmFtc3rDvG5ldHLFkWw=?= > If I try to use a base64 decoder, it gives back gibberish. Correct. As I already told you, the header is malformed. So then why do you suggest there is a bug in SquirrelMail? > The from header > is also base64 encoded. Using a decoder I can correctly decode that. > Squirrelmail also shows the sender like it should. > Somehow other clients manage to decode it. So there might be some problem > with the encoding for base64, not just for quoted printable. I don't know > how I can help you to figure it out. > But it would be good to implement some workaround to display at least > something for the subject to be able to open it. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Tóth A. <at...@at...> - 2014-05-14 18:42:40
|
Dear Paul, I don't blame squirrelmail. Agreed, that the header is malformed. While I'm trying to suggest a workaround I don't mean the bug is in squirrelmail. However some sort of workaround (for a bug in another application) might be considered, because such messages cannot be opened. It wouldn't represent a proper way to deal with the issue. But I hate to switch to another client just to figure out the malformed subject and the contents of the message. Some other clients decode the malformed header anyways somehow. Thanks: Dw. -- dr Tóth Attila, Radiológus, 06-20-825-8057 Attila Toth MD, Radiologist, +36-20-825-8057 2014.Május 14.(Sze) 17:51 időpontban Paul Lesniewski ezt írta: > On Wed, May 14, 2014 at 2:12 AM, "Tóth Attila" <at...@at...> > wrote: >> Dear Paul, >> >> I'm sorry for bothering you. You are right that it's unrelated. >> The subject header is not a printed quotable, but it is base64 encoded >> (?UTF-8?B?): >> =?UTF-8?B?VsOhOiBSZTogVMOhasOpa296dGF0w7MgUEFDUy1vdCDDqXJpbnTFkQ==IMOhcmFtc3rDvG5ldHLFkWw=?= >> If I try to use a base64 decoder, it gives back gibberish. > > Correct. As I already told you, the header is malformed. So then why > do you suggest there is a bug in SquirrelMail? > >> The from header >> is also base64 encoded. Using a decoder I can correctly decode that. >> Squirrelmail also shows the sender like it should. >> Somehow other clients manage to decode it. So there might be some >> problem >> with the encoding for base64, not just for quoted printable. I don't >> know >> how I can help you to figure it out. >> But it would be good to implement some workaround to display at least >> something for the subject to be able to open it. > > -- > Paul Lesniewski > SquirrelMail Team > Please support Open Source Software by donating to SquirrelMail! > http://squirrelmail.org/donate_paul_lesniewski.php > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform > available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > ----- > squirrelmail-users mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > List address: squ...@li... > List archives: http://news.gmane.org/gmane.mail.squirrelmail.user > List info (subscribe/unsubscribe/change options): > https://lists.sourceforge.net/lists/listinfo/squirrelmail-users > |
From: Paul L. <pa...@sq...> - 2014-05-15 19:33:02
Attachments:
fix_broken_base64-squirrelmail_1.4.x.diff
|
Please do not top-post, thanks. >>> I'm sorry for bothering you. You are right that it's unrelated. >>> The subject header is not a printed quotable, but it is base64 encoded >>> (?UTF-8?B?): >>> =?UTF-8?B?VsOhOiBSZTogVMOhasOpa296dGF0w7MgUEFDUy1vdCDDqXJpbnTFkQ==IMOhcmFtc3rDvG5ldHLFkWw=?= >>> If I try to use a base64 decoder, it gives back gibberish. >> >> Correct. As I already told you, the header is malformed. So then why >> do you suggest there is a bug in SquirrelMail? >> >>> The from header >>> is also base64 encoded. Using a decoder I can correctly decode that. >>> Squirrelmail also shows the sender like it should. >>> Somehow other clients manage to decode it. So there might be some >>> problem >>> with the encoding for base64, not just for quoted printable. I don't >>> know >>> how I can help you to figure it out. >>> But it would be good to implement some workaround to display at least >>> something for the subject to be able to open it. > > I don't blame squirrelmail. Agreed, that the header is malformed. Then you shouldn't have suggested there was a problem in SquirrelMail. It's always better to ask instead of suggest someone's code is buggy. > While > I'm trying to suggest a workaround I don't mean the bug is in > squirrelmail. However some sort of workaround (for a bug in another > application) might be considered, because such messages cannot be opened. > It wouldn't represent a proper way to deal with the issue. So have you made an effort to report the bug to the proper place? Without anyone taking steps to get the problem fixed at its source while plenty of complaints pour in to those who work on software that consumes non-compliant data, the result is that you get bloated, difficult-to-maintain and inefficient code on the wrong end of the problem. > But I hate to > switch to another client just to figure out the malformed subject and the > contents of the message. Some other clients decode the malformed header > anyways somehow. You can try to pull the newest 1.4.23-svn within the next 24 hours. Please test this FIRST and confirm, if you will, that you can now open such messages. Only after you do that, you can try the attached patch, which is a hack that should display the original string(?). -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Tóth A. <at...@at...> - 2014-05-16 16:03:42
|
2014.Május 15.(Cs) 21:32 időpontban Paul Lesniewski ezt írta: > You can try to pull the newest 1.4.23-svn within the next 24 hours. > Please test this FIRST and confirm, if you will, that you can now open > such messages. Only after you do that, you can try the attached > patch, which is a hack that should display the original string(?). Dear Paul, Here is my feedback. I've downloaded and installed the current SVN today. An "(unknown)" message displayed for the malformed subjects, which can be a good solution. "(unknown)" is also displayed for a message with a missing From header. Although I still find your hack more useful, because unfortunately some malformed subjects contain important information. One example in my practice is ICON Medical Imaging. ICON is large company. They use MS Exchange. And that system repeatedly generates malformed subjects. What can we expect from an ordinary player if large companies probably paying a lot for the IT services are sending out malformed headers? Thank you for your efforts: Attila -- dr Tóth Attila, Radiológus, 06-20-825-8057 Attila Toth MD, Radiologist, +36-20-825-8057 > > -- > Paul Lesniewski > SquirrelMail Team > Please support Open Source Software by donating to SquirrelMail! > http://squirrelmail.org/donate_paul_lesniewski.php |
From: Paul L. <pa...@sq...> - 2014-05-16 16:10:02
|
On Fri, May 16, 2014 at 9:03 AM, "Tóth Attila" <at...@at...> wrote: > 2014.Május 15.(Cs) 21:32 időpontban Paul Lesniewski ezt írta: >> You can try to pull the newest 1.4.23-svn within the next 24 hours. >> Please test this FIRST and confirm, if you will, that you can now open >> such messages. Only after you do that, you can try the attached >> patch, which is a hack that should display the original string(?). > > Dear Paul, > > Here is my feedback. > I've downloaded and installed the current SVN today. > An "(unknown)" message displayed for the malformed subjects, which can be > a good solution. "(unknown)" is also displayed for a message with a > missing From header. > > Although I still find your hack more useful, Please confirm that it helps you view the broken subject. Thanks. > because unfortunately some > malformed subjects contain important information. > One example in my practice is ICON Medical Imaging. ICON is large company. > They use MS Exchange. And that system repeatedly generates malformed > subjects. > > What can we expect from an ordinary player if large companies probably > paying a lot for the IT services are sending out malformed headers? I expect that if they have a large IT budget that they have the resources to address the problem. And if it's a problem with the software from Microsoft, they have enough pull to have Microsoft notice it. Have you told them they are sending messages with broken headers? -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |