9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lyndon Nerenberg <lyndon@messagingdirect.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] smtpfs
Date: Wed,  1 Nov 2000 17:09:16 +0000	[thread overview]
Message-ID: <861ywv62rs.fsf@gollum.esys.ca> (raw)
In-Reply-To: <001401c043a8$00a2a640$0ab9c6d4@cybercable.fr>

>>>>> "Boyd" == Boyd Roberts <boyd@planete.net> writes:

    >> How do you handle the case where the RCPT TO address doesn't
    >> match the To: header address? They don't have to be the same.

    Boyd> this is ridiculous.  read the RFC's.

I have. (I've been doing MTA development for 15 years.)

    Boyd> how do think delivery works?

By issuing a RCPT TO command via SMTP. The SMTP protocol has no
knowledge of the To: header in the message body. While it is very
often the case that the address(es) in the To: header match those
in the RCPT TO command(s), there is no requirement that this be
the case.

The behaviour you described seems to match that of "sendmail -t"
submission, in which case the RCPT TO recipients are derived from
the To:, Cc:, and Bcc: headers. This works in most cases, but
doesn't provide complete functionality in that you cannot have
SMTP envelope recipient addresses that are distinct from the RFC822
header recipient list.

And then there is the issue of MAIL FROM vs From:. It's much more
common for these to be different from each other (e.g. mailing lists).

And you still haven't explained how this will handle DSNs. Or message
tracking. Or SMTP AUTH.

--lyndon


      reply	other threads:[~2000-11-01 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-27 22:23 Boyd Roberts
2000-10-31  9:27 ` Lyndon Nerenberg
2000-11-01  2:04   ` Boyd Roberts
2000-11-01 17:09     ` Lyndon Nerenberg [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=861ywv62rs.fsf@gollum.esys.ca \
    --to=lyndon@messagingdirect.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).