In the normal run of things, the moment I want a host’s involvment with mail to be anything more complicated than just sending it I replace sendmail with exim.
Today’s struggle revealed that even setting a ‘smarthost’ (what everyone else calls ‘relays’) can be too complicated. Not entirely sendmail’s fault though, a Win2k server is serving duff AAAA records. Sendmail likes to make loads of name service lookups, and just one of these duff records will result in it sulking:
Nov 3 07:00:37 dave sm-mta[33084]: j9T7biPo056996: to=admin@zzz.co.uk, delay=4+23:22:52, xdelay=00:00:00, mailer=relay, pri=22441893, relay=budd.xxx.yyy.co.uk., dsn=4.0.0, stat=Deferred: Name server: budd.xxx.yyy.co.uk.: host name lookup failure
Now, there isn’t an AAAA record for this machine; but when sendmail queries for it, it reports SERVFAIL, whereas if I dig(1) for it, i get the correct null reply with NOERROR. Even setting WorkAroundBrokenAAAA doesn’t change this.
This seems to be the same problem as here.
I spent about an hour of this. Gah. Seems I’ll be installing exim every time from now on…
Anyway – debug sendmail name resolution over a queue run with
sendmail -d8.20 -qf
Leave a Reply
Recent articles
- Getting paranoid about ssh-agent
(Wednesday, 09. 1. 2010 – 1 Comment) - cron
(Wednesday, 02. 24. 2010 – 6 Comments) - SOAP in unexpected “actually, quite easy” incident.
(Wednesday, 09. 30. 2009 – No Comments) - ipmitool for OSX
(Tuesday, 09. 29. 2009 – No Comments)
Archives
- September 2010
- February 2010
- September 2009
- August 2009
- January 2009
- September 2008
- August 2008
- July 2008
- May 2008
- April 2008
- February 2008
- January 2008
- November 2007
- October 2007
- September 2007
- August 2007
- December 2006
- November 2006
- August 2006
- June 2006
- May 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005