From: Robert Raschke <rrplan9@tombob.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] how to deal with mail delivery problems
Date: Mon, 22 Nov 2004 08:55:43 +0000 [thread overview]
Message-ID: <29a2a049442d6be3b50aa8c395da3128@tombob.com> (raw)
In-Reply-To: <ee9e417a0411190747566fd1d9@mail.gmail.com>
Hi,
Russ wrote:
> If you change the last part of the line in your /mail/lib/rewrite to
>
> | "/mail/lib/qmail '\s' 'net!\1'" "'\1!\2'"
>
> and then change the last line of /mail/lib/remotemail to say:
>
> if(upas/smtp -h $fd $addr $sender $*)
> exit 0
> exec upas/smtp -h $fd net!your.gate.way $sender $*
>
> then I think you'll get the behavior you describe.
> Whether it's useful is of course another matter altogether.
C Forsyth also recommended setting up SPF for my domain
(spf.pobox.com). I did that first, but that did not solve all my
problems. Sending mail to web.de just won't work unless I go via my
ISP's smtp server.
With the solution by Russ above, I now have a setup where I fall back
onto my ISP's smtp server if direct delivery did not work. I also add
a line to a log file that I can check when I send "important" mail:
today=`{date}
if (upas/smtp -h $fd $addr $sender $*) {
exit 0
}
echo $today : upas/smtp -h $fd net!smtp.blueyonder.co.uk $sender $* >>/sys/log/remotemail
exec upas/smtp -h $fd net!smtp.blueyonder.co.uk $sender $*
I think it's useful for me at the moment. This way I can at least
check and instantly see if a mail went via a potentially very slow
route. I know that I can't really be sure either way, but it gives me
a workaround for otherwise unreachable addresses.
I will have to keep watching this space for a while to see if I can't
find a better way.
Thank you for your help,
Robby
prev parent reply other threads:[~2004-11-22 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 15:20 Robert Raschke
2004-11-19 15:47 ` Russ Cox
2004-11-22 8:55 ` Robert Raschke [this message]
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=29a2a049442d6be3b50aa8c395da3128@tombob.com \
--to=rrplan9@tombob.com \
--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).