Squirrelmail header folding

[George Barwood-2]

Some parts of this message have been removed. Learn more about Nabble's security policy.

I have encountered an email from Squirelmail where the content type header has been split at a non-whitespace point,

due to an unusually long content type.

 

Example:

 

Content-Type:
     application/vnd.openxmlformats-officedocument.wordprocessingml.documen
     t; name="News.docx"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="News.docx"

 

As far as I can see, this is incorrect according to the standard, e.g.

 

http://tools.ietf.org/html/rfc5322#section-2.2.3

 

Is this intentional?

It may be possible for parsers to work around this particular case, but adherence to standards is generally a good idea.

George Barwood

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-devel@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel

[Paul Lesniewski]

On Wed, Feb 18, 2009 at 3:17 AM, George Barwood <george@...> wrote:

> I have encountered an email from Squirelmail where the content type header
> has been split at a non-whitespace point,
> due to an unusually long content type.
>
> Example:
>
> Content-Type:
>      application/vnd.openxmlformats-officedocument.wordprocessingml.documen
>      t; name="News.docx"
> Content-Transfer-Encoding: base64
> Content-Disposition: attachment; filename="News.docx"
>
> As far as I can see, this is incorrect according to the standard, e.g.
>
> http://tools.ietf.org/html/rfc5322#section-2.2.3
>
>
> Is this intentional?

Only the author of the original folding code can tell you that, but I
think it's wrong.  I have re-written the folding code and it is in
1.5.2SVN now and pending feedback to see if we can port it back to
1.4.x.  If you want to try the new code in 1.4.x, there is a file you
can use attached to the following tracker:

https://sourceforge.net/tracker/?func=detail&atid=100311&aid=1951776&group_id=311

------------------------------------------------------------------------------
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-devel@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel