From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] how to deal with mail delivery problems
Date: Fri, 19 Nov 2004 10:47:16 -0500 [thread overview]
Message-ID: <ee9e417a0411190747566fd1d9@mail.gmail.com> (raw)
In-Reply-To: <7a1e45b3731ba65d720e75192cec523b@tombob.com>
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.
Russ
next prev parent reply other threads:[~2004-11-19 15:47 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 [this message]
2004-11-22 8:55 ` Robert Raschke
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=ee9e417a0411190747566fd1d9@mail.gmail.com \
--to=russcox@gmail.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).