Yes, I'm using sendmail and the end recipient address wasn't correctly assumed. (don't go there, i don't like sendmail's lack of this info)

However, my DELIVERY method is procmail, why would tmda be calling sendmail for final delivery?

DELIVERY = os.path.expanduser("|/usr/bin/procmail ~/.procmailrc-tmda-delivery")

David

Tim Legant wrote:

David Ford <[EMAIL PROTECTED]> writes:



If X-TMDA-Recipient somehow gets the wrong address, then it will never
deliver the email. It'll sit in queue. When manually released, it
sits there for a while, then goes back to being a "new" email.



If X-TMDA-Recipient contains the wrong address it is because your MTA provided TMDA with the wrong address. The only way TMDA knows who a message is really for is by examining the RECIPIENT environment variable set by your MTA (unless you are using Sendmail, in which case it's a little more complicated. I don't think you're using Sendmail, though...).



Now that I've figured that out, I'll find a way to avoid this
situation, but I think TMDA should always attempt to deliver an email
that has been released regardless of the headers. The headers are no
longer relevant.



TMDA *does* always attempt to deliver the mail. TMDA attempts to deliver the message to the address to which the message was originally sent. If a particular configuration of your MTA has caused it to claim that the recipient is "[EMAIL PROTECTED]" when, in fact, that is not the case, then you need to fix your MTA's configuration. TMDA is acting on the only information it has and it has, essentially, been lied to!


Tim


_____________________________________________
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

Reply via email to