From: Daniel Quinlan
Sent: Wednesday, June 09, 2004 1:51 PM
"Stuart D. Gathman" <stuart(_at_)bmsi(_dot_)com> writes:
The current macros cover all information available before DATA.
Additional macros may be required to take advantage of proposals to
copy certain 2822 fields to 2821 ESMTP parameters. In that case, yes,
you have the same problem unless there is a 'N/A' behaviour for
unrecognized macros. (Currently an unrecognized macro must generate
ERROR.)
So, let's say you can add some 2822 fields into macros. How, then,
would you implement my proposal with exists?
I'm still confused about what you originally proposed. If I understood you
right, it was that a domain owner would be able to forbid any relaying of
their mail. How can a domain owner know whether the addresses they send to
are end-user accounts or forwarding accounts? Let's say that AOL's user set
up a forwarding account, dignified-user(_at_)pobox(_dot_)com, that forwards to
their
home address flatus(_at_)bozoISP(_dot_)com, for obvious reasons. In this case,
billing.aol.com sends a billing message to dignified-user(_at_)pobox(_dot_)com,
but
pobox.com rejects the message because billing.aol.com prohibits relaying.
Poor Mr. Flatus never gets his bill and AOL doesn't get their money. If
I've misunderstood what you are proposing, please correct me.
--
Seth Goodman