OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Transport map lookup failures are fatal?

From: Seth Mattinen (sethmrollernet.us)
Date: Thu Apr 16 2009 - 20:47:58 CDT


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.

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=<test50lightyears.com>, 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)

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.

~Seth