From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] $smtp dns failure
Date: Mon, 15 Jan 2007 23:35:48 +0000 [thread overview]
Message-ID: <825ab1b11c6efdfedc86a4826906ef65@quintile.net> (raw)
In-Reply-To: <88a477560701151202x7491769dwd738d2284ebccbe2@mail.gmail.com>
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
next prev parent reply other threads:[~2007-01-15 23:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 16:55 Matthias Teege
2007-01-15 18:05 ` Federico Benavento
2007-01-15 19:22 ` Russ Cox
2007-01-15 18:10 ` geoff
2007-01-15 20:02 ` Matthias Teege
2007-01-15 23:35 ` Steve Simon [this message]
2007-01-16 16:46 ` Matthias Teege
2007-01-16 18:21 ` Steve Simon
2007-01-16 18:31 ` erik quanstrom
2007-01-16 18:44 ` Russ Cox
2007-01-16 18:52 ` lucio
2007-01-16 19:05 ` erik quanstrom
2007-01-16 19:30 ` Russ Cox
2007-01-15 19:28 erik quanstrom
2007-01-15 19:42 ` Paul Lalonde
2007-01-16 17:01 erik quanstrom
2007-01-16 20:31 erik quanstrom
2007-01-16 20:50 ` geoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=825ab1b11c6efdfedc86a4826906ef65@quintile.net \
--to=steve@quintile.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).