On Thursday 20 January 2011 14:21:15 Paul J Stevens wrote: > > But when I get message from dbmail and see it in MUA, the message > > contains > > > > this in header: > >> Content-Transfer-Encoding: base64 > >> Content-Type: application/octet-stream; > >> > >> name*0*=iso-8859-1''ABC_1234_1AB-1234567890-1234567890-123456789_e6b3f1 > >> 32b; name*1*=75c479f9d97d7ae0f019136136_07_01_01.zip > >> > >> Content-Disposition: attachment; > >> > >> filename*0*=iso-8859-1''ABC_1234_1AB-1234567890-1234567890-123456789_e6 > >> b3f; filename*1*=132b75c479f9d97d7ae0f019136136_07_01_01.zip > > There is no difference between dbmail-lmtp and dbmail-smtp with regards > to message insertion that I'm aware of - except from handling \r\n > differently. > > The message is read as a raw string, this string is parsed through > gmime, gmime's string-representation of the parsed message is inserted > into the database.
So, gmime can modify header (or the hole message) ??? But I whant to see message in original view, without midifications. > First question is: what is in the messageblks table. There is modified header in dbmail_messageblks in case of using dbmail-lmtp and original header in case of dbmail-smtp > Next question is: what could possibly explain the difference between > lmtp and smtp? I don't know. I prepare raw test message and use it in both cases. > Final question: does 3.0-rc1 suffer from this problem? I don't try 3.0-rc1 yet, I'l try if it would be some time... I'l try to do some debuging with code. Thanks. __ wbw Lapshin Oleg _______________________________________________ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev