David Banning <[EMAIL PROTECTED]> writes: > I have a couple of kinks when I was testing it. I used two different > outside html mail applications to send me mail. One is my address > [EMAIL PROTECTED] the problem here is that the address is identified > as [EMAIL PROTECTED] which is the address the confirmation request > is sent to.
Why is this happening? Are you using Sendmail aliases, or the virtusertable? TMDA doesn't decide that 'davey' maps to 'www-data'; some other piece of software is changing the envelope recipient before TMDA sees it. > The address is read in procmail as the Return-Path header on the email. > I used a small script to have SENDER set to the actual address it's from > but then I get this problem; When the sender confirms, somewhere in the > TDMA process the Return-Path header is read again, but -not- from the > procmail file. So it sends -another- request to the sender to confirm once > again. The only time TMDA looks at the original mail's Return-Path: is when it writes that address into your CONFIRM_APPEND file. A different Return-Path: on the confirmation email will not cause TMDA to send another confirmation request. Perhaps there's a different problem? > On the second test site I sent from yahoo, which works fine but on the > confirmation request yahoo brands the confirmation request as > as -bulk- or spam. I imagine this is because of the elaborate encoded return > email address. Is there anyway around this? It's probably because TMDA sets the 'Precedence: bulk' header field. We may need to re-consider the use of this field, either removing it entirely or using a different value (not 'bulk'). Jason will have to make the decision on that. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
