I'm having problems with the last CRLF in plain mime parts.
...
Are there mailers running arround that do not append this 'spacer' CRLF?
Mozilla Thunderbird behaves the same, here is an example:
Message text: "1.Line<crlf>"
Encoded:
[..]
--------------010609020500050508040002
Content-Type: text/plain; charset=ISO-8859-1;
Content-Transfer-Encoding: 7bit
1.Line
--------------010609020500050508040002
[..]
MimeDec decodes it to "1.Line<crlf><crlf>"
I would like to know if it is save to replace the trailing <crlf><crlf>
by <crlf>.
(First time posting to the list, so go easy on me :) )
To the best of my knowledge, the RFC says that its <CRLF>--(identifier)
to start a section and <CRLF>--(identifier)-- to end a section.. To me,
MimeDec should swallow that <CRLF> and not append it to the content of
the section.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
