Re: New line character after Content-type: causing SquirrelMail to display messages incorrectly
Adrian Hada <adrian.hada <at> gmail.com>
2013-02-17 19:53:36 GMT
I finally managed to connect the problem to HMail's IMAP responses. I
posted the problem there.
Thanks for the help and for the excellent piece of software. I've only
used Squirrelmail for the past four years but I still haven't
encountered any serious problems - I guess this HMail issue is just
another example of how reliable SM is!
On Sat, Nov 10, 2012 at 11:53 AM, Adrian Hada <adrian.hada <at> gmail.com> wrote:
> Thank you for your answer. I forgot to add some details to the last message
> so here's some additional info.
>
> The e-mail I had sent was HTML plus a txt file attachment (a readme.txt I
> added trying to debug). I wasn't able to reproduce the problem using plain
> text e-mails (actually, most people in my organization still choose to send
> plain text and only a few go for HTML - this is why I was very slow in
> finding out there was a problem). Yesterday I found out that sending message
> receipts fails with the same problem - the text does not appear, but a .dat
> attachment gets added to the e-mail with the message contents from the new
> boundary.
>
> The reason I pointed out the newline was that I was messing around with the
> original messages' contents (as stored by HMail) and removing the newline
> character solved the problem. Adding it broke the display again. Using a
> logfile which posted headers as they were processed, I was able to track the
> newline being added by the foldline function.
>
>
> On Sat, Nov 10, 2012 at 8:41 AM, Tomas Kuliavas
> <tokul <at> users.sourceforge.net> wrote:
>>
>> Adrian Hada wrote
>> > I encountered a problem using SquirrelMail which I wasn't able to solve
>> > using regular means or find in the mailing lists so far. The problem
>> > goes
>> > like this - some HTML e-mails are missing contents with the relevant
>> > parts
>> > appearing as ATT-n.dat attachments.
>> >
>> > I was able to track the problem to the MIME header of the e-mail, namely
>> > to
>> > there being a new line character after Content-Type for
>> > multipart/alternative. For example, this e-mail header (I removed the
>> > domain info):
>> >
>> > ....
>> > I was able to track this issue to the foldline function in the deliver
>> > class - namely, the long Content-type line causes foldline to do a fold
>> > before the soft limit and sends the rest of the line to the new one.
>> > From
>> > there on, I guess the boundary is not correctly interpreted. As a
>> > workaround, I added a preg_match test so that foldLine is not called for
>> > Content-Type lines.
>> >
>> > My knowledge of MIME is limited so I can't figure out if the problem is
>> > in
>> > the message creation (the newline shouldn't be there) or reception
>> > (newline
>> > should be ignored) and I'd prefer to rely on something better than my
>> > quick-fix skills to solve the issue.
>> >
>> > Further info:
>> >
>> > - SquirrelMail version - *1.4.23 [SVN] (config file is 1.4.20)*
>> > - PHP version 5.3.18
>> > - Web server IIS 6.0
>> > - HMail Server 5.3.3
>> > - Windows 2003
>> > - Installed Manually
>> > - Browsers - tried multiple
>> >
>> > Thanks for your help.
>>
>> email has two content-type headers. if it is reply, check headers in
>> original email. check, if you can reproduce it without html_mail plugin
>> messing with message structure.
>>
>>
>> newline after header tag is allowed, if header value+header tag does not
>> fit
>> into recommended header line length.
>> --
>> Tomas
>>
>>
>>
>> --
>> View this message in context:
>> http://squirrelmail.5843.n7.nabble.com/New-line-character-after-Content-type-causing-SquirrelMail-to-display-messages-incorrectly-tp25122p25123.html
>> Sent from the squirrelmail-devel mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_d2d_nov
>> -----
>> squirrelmail-devel mailing list
>> Posting guidelines: http://squirrelmail.org/postingguidelines
>> List address: squirrelmail-devel <at> lists.sourceforge.net
>> List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
>> List info (subscribe/unsubscribe/change options):
>> https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
>
>
>
>
> --
>
> Adrian Hada
--
--
Adrian Hada
------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-devel <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel
I am also a FreeBSD committer, and the
maintainer of the FreeBSD squirrelmail port.
I know that this is a question that OSS development teams hate getting
pestered with, but I was wondering if you could give me an idea of when
1.4.23 may see the light of day? If momentum has stalled and there is no
projected plans for a release coming, that's totally okay and I'll work
on collecting patches to update our port.
The main thing that I'd like to backport if 1.4.23 is on an indefinite
delay would be fixes for php-5.4 compatibility. Due to the mechanics of
our ports system (which encourages building from source), I get a lot
of confused emails due to us erroring out at php > 5.3.
I've identified and backported r14343 (plugins/message_details
session_unregister->sqsession_unregister), and r14276
(plugins/mail_fetch hex2bin clobbering). Are there other patches
that I should be including as php-5.4 fixes? What is your level of
confidence regarding 5.4 compatibility in 1.4.23-devel?
I really appreciate you taking the time to help me clear up the status
and the 5.4 fixes. Thanks, and have a great weekend!
# Adam
--
Adam Weinberger
adamw <at> adamw.org
RSS Feed