On Thu, Apr 16, 2009 at 06:47:58PM -0700, Seth Mattinen wrote: > I apologize in advance if I'm being horribly dense, but I'm seeing > something that doesn't feel right. In the event that a transport map > lookup fails with a "host not found" error, Postfix is bouncing the > message rather than treating it as a temporary error.
The transport map lookup did not fail. > For my test, I have the transport map: > > 50lightyears.com smtp:[badrecord.mattinen.org]:1234 > > Where "badrecord.mattinen.org" intentionally does not exist. So I send a > test message and I see this in the logs: > > postfix/smtp[5361]: 773FA3E442: to=<[email protected]>, relay=none, > delay=0.25, delays=0.21/0.04/0/0, dsn=5.4.4, status=bounced (Host or > domain name not found. Name service error for > name=badrecord.mattinen.org type=A: Host not found) The destination nexthop does not exist, this is not a transient condition. > So, my question is, why is that fatal instead of temporary? Shouldn't it > be temporary? Observed on 2.5.5 and 2.4.5. It should not be temporary. All lookups succeed and establish that the destination is non-existent. Postfix correctly bounces the message. If you really want sub-optimal behaviour and a queue full of junk, try: smtp_defer_if_no_mx_address_found = yes -- Viktor. Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the "Reply-To" header. To unsubscribe from the postfix-users list, visit http://www.postfix.org/lists.html or click the link below: <mailto:[email protected]?body=unsubscribe%20postfix-users> If my response solves your problem, the best way to thank me is to not send an "it worked, thanks" follow-up. If you must respond, please put "It worked, thanks" in the "Subject" so I can delete these quickly.
