If you set the CONFIRM_ADDRESS variable in your .tmda/config file to [EMAIL PROTECTED] then TMDA will correctly generate confirmation responses using [EMAIL PROTECTED] as the base address. This is also a very handy variable to use to get around mail forwarders that leave the original to address alone. E.g. I've got a bigfoot address that forwards to my TMDA protected address. I use the CONFIRM_ADDRESS to prevent the confirmations from having [EMAIL PROTECTED] used as base address since bigfoot will just reject anything like [EMAIL PROTECTED] (unless someone other than me is unlucky enough to have such an address).
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Becz Tam�s > Sent: Tuesday, June 07, 2005 12:27 AM > To: Stephen Warren > Cc: [email protected] > Subject: Re: Problems with cc'd mails and tagging. > > On Monday 06 June 2005 17:50, Stephen Warren wrote: > > This sounds like the expected behaviour. > > > > Typically, TMDA is setup to handle a specific recipient's > (i.e. yours) > > email messages. > > > > If a message is sent to multiple recipients, even if those multiple > > recipients are all "handled" by the same detination mail > server, then > > TMDA is run one per each recipient (assuming all those > recipients have > > TMDA setup) and TMDA is not aware that other recipients of > the message > > may also be generating challenges via TMDA. > > > > Hence, TMDA must generate challenge messages from your > address, even if > > you only received the email due to CC or BCC. Actually, to > be precise, > > TMDA doesn't care about the To/CC headers (or the non-existent BCC > > header), since it performs its processing based on the SMTP envelope > > sender, which may technically be something completely > different again. > > > Yes, this would be excepted. But it looks like I was not > clear. Suppose, my > address is [EMAIL PROTECTED] Then suppose someone sends a mail that has: > To: [EMAIL PROTECTED] > cc: [EMAIL PROTECTED] > > Then my tmda sends a confirmation request like > From: [EMAIL PROTECTED] > Confirm address: [EMAIL PROTECTED] > > > > I use postfix, and before handing to tmda I'm checking > the X-original-to: > > > header, and set the RECIPIENT env var to it if it exists, > because I had > > > problems otherwise. (Trough I have to look at my docs for > the concrete > > > reason :) ) > > > > > > It is done like this: > > > > > > XTO=`echo -e "$MAIL" |formail -x X-Original-To` > > > if [ "$XTO" != "" ]; then > > > export RECIPIENT="$XTO" > > > fi > > > > I'm not quite sure why you need to do this - are you > forwarding email > > between multiple servers, or using address rewriting or aliasing? > > > As far as I remember, Postfix used to mess up that variable, > and put wrong > things in there. But all my test mails has the correct > address in it before > handing them over to tmda. > > Thanks, > > Becz Tam�s > _____________________________________________ > tmda-users mailing list ([email protected]) > http://tmda.net/lists/listinfo/tmda-users > _____________________________________________ tmda-users mailing list ([email protected]) http://tmda.net/lists/listinfo/tmda-users
