
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.
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/postingguidelinesList address:
squirrelmail-devel@...
List archives:
http://news.gmane.org/gmane.mail.squirrelmail.develList info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel