> However, when we start adding a From_ header > to it during delivery, some (recent) versions of gmime will decode > them internally (ok, fine), but then recode them as latin5 is > something like that before giving them back like when we need a > string representatation of a parsed message.
That reminds me of something: Could dbmail add a header saying which alias/user the e-mail arrived at? Sometimes it's hard to impossible to tell when I received a Spam which address it arrived at. Especially if there are several recipients that are BCCed. I know it could be done in postfix, but that would need another instance that makes a single-user delivery then, and that hurts performance, and if 10 aliases arrive in the same final folder I have 10 mails then. DBmail would be a good place to add X-DBmail-arrived-at: [email protected], [email protected] upon delivery to the final address(es). So for each real delivery list all those aliases that fit to this user. I know there was once an X-dbmail* header so you might not want it, it could be configurable if needed. But that header would be good for the bayes db from SpamAssassin, it loves such clear spam signs and leads to more accurate spam processing :-) 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 [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
