From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <825ab1b11c6efdfedc86a4826906ef65@quintile.net> From: "Steve Simon" Date: Mon, 15 Jan 2007 23:35:48 +0000 To: 9fans@cse.psu.edu Subject: Re: [9fans] $smtp dns failure In-Reply-To: <88a477560701151202x7491769dwd738d2284ebccbe2@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 03e18600-ead2-11e9-9d60-3106f5b1d025 re smtp dns problems: Hi, Debugging smtp: check the exact way upas/smtp is being envoked. Look at the end of /sys/mail/runq, here is an example from mine: felix Jan 12 19:33:36 steve/C.095795: execing '/mail/lib/remotemail' 'smtp' 'steve' 'net!$smtp' '9fans@cse.psu.edu' Then you can try running the remotemail script with rc -x to see what it is doing, in my example: rc -x '/mail/lib/remotemail' 'smtp' 'steve' 'net!$smtp' '9fans@cse.psu.edu' ... exec /bin/upas/smtp -g 'net!$smtp' -h quintile.net 'net!$smtp' steve 9fans@cse.psu.edu Finally you can exec smtp with the -d option (debug) to see the SMTP conversation, and perhaps more importantly the DNS lookups (and failures) that occur. ---------------------- I used to put this in my /mail/lib/remotemail: exec /bin/upas/smtp -h $fd $addr $sender $* But due to a weird bug in the DNS cache (that I couldn't find even after several attempts) mail would fail, so I changed (at Russ's advice) to exec /bin/upas/smtp -g $addr -h $fd $addr $sender $* and email has worked fine since. -Steve