[9fans] smtpfs

[9fans] smtpfs

[Boyd Roberts]

looking at inferno's smtp module i thought why not an smtpfs?

all you do is write the 822 message into /n/smtp and it parses
the message and delivers it.

it's trivial.

a minimal 822 message is:

    Date:
    From:
    To:

or:

    Date:
    From:
    Bcc:

ok, we can toss the Date: 'cos the server can add that.  we can
toss the From: 'cos the Tattach has the uid.  parsing To:/Cc:/Bcc:
is trivial 'cos i have a yacc grammar that does that.

so MH style 'comp' is just:

    cat <<'!'
    To:
    Cc:
    Bcc:
    Subject:

    !

sourced into say acme, then name the file /n/smtp and Put sends it.

Re: [9fans] smtpfs

[Lyndon Nerenberg]

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

    Boyd> looking at inferno's smtp module i thought why not an
    Boyd> smtpfs?  all you do is write the 822 message into /n/smtp
    Boyd> and it parses the message and delivers it.

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.

What about DSN? AUTH?

    Boyd> it's trivial.

I don't think so.

--lyndon

Re: [9fans] smtpfs

[Boyd Roberts]

----- Original Message -----
From: Lyndon Nerenberg <lyndon@messagingdirect.com>
To: <9fans@cse.psu.edu>

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

this is ridiculous.  read the RFC's.

how do think delivery works?

    BCC TO

i think not.

Re: [9fans] smtpfs

[Lyndon Nerenberg]

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