> That is the case here (as well as for UUencoded attachments) - encoded > part is practically part of the message body. Instead of Synapse Mimemess > I always use my own classes to encode/decode any raw message which decode > that case correctly. As such this is irelevant for me, however may be of > interest for other Synapse users.
Mimemess decoding message always correctly. Enclosure is not mime part! > This is also a part of general decoding problem with Synapse in some > specific cases, since ecplicit distinguish of MIME bodyparts and logicaly > existed bodyparts. I personally use logicaly bodyparts decoding, which > conveniency avoid different treading with all kinds of multipart messages. What you mean by "logicaly existing bodypart"? > Also there is a problem in some multipart/alternate/mixed messages created > by MS Outlook Express, which always unhappy add extra lines. This causing > that Synapse cannot correctly decode first body part. Unfortunately, I > have had no time to look into code carefuly and this may be solved > differently. However, suggestion is to tread body parts logicaly, not > explicitly. Blah! First mime part is decoded correctly. What is incorrect? Did you understand MIME standard, their mime part definition, and suggestions about handling of text before and after mime boundaries outside mime parts? Or at least read mimepart documentation about prepart and postpart properties? Please, do not release rumors about Synapse! -- Lukas Gebauer. E-mail: [EMAIL PROTECTED] WEB: http://www.ararat.cz/synapse - Synapse Delphi and Kylix TCP/IP Library ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
