[moving this to tmda-workers since I see Marcus is subscribed there] Marcus Geiger <[EMAIL PROTECTED]> writes:
>> RECIPIENT_HEADER only affects $RECIPIENT. You'll have to manually >> fudge with $EXT if you want extension addresses to work. > > ok, thanks on this. Maybe I diged a little to deep in all this an > overlooked this detail. > > Just a suggestion: What about a feature 'like' RECIPIENT_HEADER that > would simplfy using tmda in a dialup-environment such that tmda > would figure out the orignal envelope recipient based on this header This sounds reasonable, but help me out as I don't use TMDA in a dialup environment. So basically, you specify a header, say ``X-Original-To'', which is added to your incoming messages by your MTA. It might look like: X-Original-To: [EMAIL PROTECTED] TMDA then parses the address in this header and sets RECIPIENT and EXT for you in the environment. [EMAIL PROTECTED] EXT=dated-1037484885.7112e0 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. 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' > 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. What do you mean by ``inject that header on retrieval of the message into the message''? 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? _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
