- ... If you have Postfix reject mail to invalid users you won t have to deal with SMTPTracker or any other downstream server doing it. When Postfix acts as aMessage 1 of 4 , Dec 30, 2005View Source
>I have postfix running on a mail gateway, going to an exchange server withIf you have Postfix reject mail to invalid users you won't have to deal with
>some third party software. The third party software is using 552 to reject
>invalid recipients, and postfix defers mail instead of permanently failing.
>Is there any way to correct this behaviour on the postfix side, since my
>understanding is that all 500 codes are supposed to be permanent errors?
>(I'm using postfix 2.2.5)
>Dec 30 21:38:25 mail-gw01 postfix/qmgr: AD84511DF1: to=<foo@...>,
>relay=none, delay=105889, status=deferred (delivery temporarily suspended:
>lost connection with 172.16.0.2[172.16.0.2] while sending DATA command)
>This is what the third party software is issuing (before closing the
>552 5.7.1 SMTPTracker (www.smtptracker.com). Message rejected! User
>foo@... does not exist.
>I'd like to avoid taking this up with the other vendor if at all possible.
SMTPTracker or any other downstream server doing it. When Postfix acts as a
relay (gateway) server this is typically the right thing to do at any rate.
Use relay_recipient_maps to have Postfix reject mail addressed to invalid
Here are links geared toward automating the population of
Don�t just search. Find. Check out the new MSN Search!