From: forsyth@minster.york.ac.uk forsyth@minster.york.ac.uk
Subject: From addresses and upas
Date: Fri, 22 Oct 1993 08:41:05 -0400 [thread overview]
Message-ID: <19931022124105.Zmw71sqydjJsdj7GeeFhDpbd9CCPqOE2u-H8a6dh_uY@z> (raw)
there might be a compromise.
we went through this here some time ago with an implementation of
the smtp part of upas as mangled by System V.4 and
somewhat unmangled by me. it seems to be sufficient
to have the smtpd pick the right name to put in the Unix
`From ' header. since it has already cracked the header and knows RFC822,
it's a fairly simple change. it takes the `From ' address from the first of
Reply-to:, From:, Sender: and SMTP FROM:. errors go to the SMTP FROM:.
(there should never be a Sender: without a From: but we get junk mail
from some machines.)
the Reply command in the mail reader just uses the `From ' address,
and needn't mess with the Wilt . (the Stilt) crud unless it wants to.
i didn't understand the recent discussion
until i realised that my From lines were being built as described by
our Unix machine before being sent to me on Plan 9,
and that's why my replies were going to the right address.
it also makes the seemail face list more interesting.
reply other threads:[~1993-10-22 12:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19931022124105.Zmw71sqydjJsdj7GeeFhDpbd9CCPqOE2u-H8a6dh_uY@z \
--to=forsyth@minster.york.ac.uk \
/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).