It's quite clear about it: "--fooblah" is fine, as long as fooblah does not match any of the actual multipart mime boundary delimiter strings. And my parser does exactly that. Literally. If the parser recognizes a delimiter string, it's going to close that MIME section. But, anything else that looks like a boundary delimiter string is going to get ignored.Sam wrote:Alessandro Vesely writes:In that case it does, because the last attachment was absolutely
I doubt that the output from reformime includes all the attachments, unmolested. Count the boundaries in the reformatted mail.My filter complains it cannot understand such MIME structure, it dumps a copy of the message and blocks it. So I have to manually look at it, run reformime -r and send it over again. Reformime returns a valid MIME structure.
(i.e. without even a blank line) empty. In general yes, a boundary
may live as text in the body of another entity. Will some "smart"
client recognize it and decode the attachment?
When MIME came out it standardized and enhanced the practice of
hand writing boundaries, typically like the following:
--8<--- cut here ----
The standard says the boundary value should never appear in the
body, but it is not clear how to handle a message when that
prescription is not observed.
--
Sam
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
