From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: Lyndon Nerenberg <lyndon@messagingdirect.com>
Message-ID: <861ywv62rs.fsf@gollum.esys.ca>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
References: <024501c04064$a14477a0$0ab9c6d4@cybercable.fr>, <001401c043a8$00a2a640$0ab9c6d4@cybercable.fr>
Subject: Re: [9fans] smtpfs
Date: Wed,  1 Nov 2000 17:09:16 +0000
Topicbox-Message-UUID: 1fcec124-eac9-11e9-9e20-41e7f4b1d025

>>>>> "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