Thus spake Jason R. Mastaler: > How should we set SENDER then? Is there a header in your messages > which accurately reflects the envelope sender address? Usually this is > ``Return-Path'', but I don't know if this munged in a dialup > environment.
This depends on the setup. But a local mta is required anyway for a tmda setup. Thus, if the user forwards mail to a local account, the return-path won't be munged. > Perhaps that's a second TMDA configuration variable---the > header which contains the envelope sender address. > > So, your .tmda/config might have the following variables set: > > ENVELOPE_RECIPIENT_HEADER = 'x-original-to' > ENVELOPE_SENDER_HEADER = 'return-path' nice :) > > Of course one still needs to inject that header on retrieval of the > > message into the message but it could avoid all those fiddling with > > local mda's again and again. > Wouldn't the MTA on the host that first receives > your messages have to add this header, since only it is privy to the > true envelope recipient address? Yes, but not all isps make in a uniq way. For example, when I receive mail from the tmda-users list, I get something like this: .. Delivered-To: [EMAIL PROTECTED] .. Delivered-To: [EMAIL PROTECTED] .. The recipe to figure out to whoom the mail was orignally sent to is: 1. If the mail was delivered directly to my primay mail account at my provider it has only one delivered-to line or more precisely the top most (first) Delivered-To: header contains the address to whoom this mail was intended to. 2. If the mail was delivered to the catch-all account at my provider (which has the same name as my primary inbox there) it has a additional Delivered-To: header: The first will be [EMAIL PROTECTED] and the second will be the orginal address where this mail was intended to (e.g. [EMAIL PROTECTED]). Marcus -- .signature: No such file or directory _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
