On Montag 16 Februar 2009 Mantis Bug Tracker wrote: > For instance, one of them, write_addrspec function (which is used for > From, To, and similar headers), parses header value, converts it to > UTF-8, and then converts it back to the charset gmime thinks is best > for this header (see internet-address.c and gmime-utils.c).
Why? Mail comes via SMTP, and that headers are clearly ASCII. There are no 8bit headers allowed. This makes problems with postfix. I discussed that with Wietse Venema and Victor Duchovni (the 2 main devs), they clearly stated that only ASCII is allowed (this was on the context that I sometimes get errors when postfix connects to dbmail via an SQL query). > The philosophical question: should dbmail treat the input message as > something precious (and the only permitted action is inserting of > additional message headers)? The alternative is to permit modifying > the message form (for instance, header charset), but not the message > value (meaning). I'd say never ever modify the mail (headers). That would be very bad with SpamAssassin for example. I absolutely need the original mail in order to feed it back to SA, to learn it. Exactly such spelling/coding errors are generally a good sign for the difference of SPAM or HAM, so it's really needed. If needed, add some only internally used headers, but always return the original mail to the outside world. mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0660 / 415 65 31 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
