-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter Rabbitson wrote: > John Fawcett wrote: >> I think that it would be a good idea to add a guard to dbmail to remove >> existing Return-Path headers so that this problem does not occur. > > Errrr probably not add anything if a duplicate is detected. I definitely > do not want my headers tampered with unless necessary.
There should only be one Return-Path header and that should be written by the final delivery agent, so there isn't much alternative here. > >> In the meantime it is probably best to configure the MTA not to add the >> Return-Path header. >> > > Email often passes through dbmail twice, so the MTA will not solve > anything. I have a number of dbmail forwards like: > > [EMAIL PROTECTED]: [EMAIL PROTECTED] > > so the email loops through the MTA and comes back to the correct > mailbox. This is to work against stupid forms/systems that do not > support '+' it would be a workaround to the current situation where dbmail freaks out on existing Return-Path headers (and because of that potentially does not store other headers - like the subject header not being stored as in bug 685). Return-Path headers should only be used for final delivery, so should not be added to forwarded messages. However MTAs should remove existing Return-Path headers, so I doubt this will be a problem. John > > _______________________________________________ > DBmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHzS/jd4I3jTtt9EIRAotQAKDgYckCVF5iPfIg24MreRMsaF4sCwCfdn2L 8tK3AdaFOX3ZCMO+qc/4U08= =VQJx -----END PGP SIGNATURE----- _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
