> Mimemess decoding message always correctly. Enclosure is not mime part! > What you mean by "logicaly existing bodypart"?
You obviously didn't understand suggestion. Suggested was new class which decode all messages - universal solution. In that case, no additional coding is necessary to manipulate with UU/XXencoded attachment in non-MIME messages. > Blah! First mime part is decoded correctly. What is incorrect? > Or at least read mimepart documentation about prepart and postpart > properties? This is exactly what is suggested to be simplified. Usually it is not necessary to have parent of nested subparts, but actual parts and simple navigation. Currently this require a lot of extra code. > Please, do not release rumors about Synapse! I sincerely hope this is a really bad choice of words. Please explain about what rumours releasing you are talking about?! Sasa -- www.szutils.net ------------------------------------------------------------------------- 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
