--
On Mon, Sep 23, 2002 at 04:14:38PM +0100, Mike Meredith wrote:
> RFC2505 2.6.1 specifically says that you MUST NOT block "<>" with
> multiple recipients because there are sometimes occasions when a bounce
> should go to multiple recipients (it mentions list aliases).
>
> As I'm pretty sure I don't have senders with multiple recipients, it's
> tempting to ignore that bit of the RFC (did I really say that?) and go
> ahead.
Just for reference, when I wrote my patch to do SMTP callbacks on the sender
*and* postmaster@remotedomain, I noticed problems within the first day. Some
mail servers were refusing the second callback because they refused more
than one receipient for the null envelope.
I quickly modified my callback code to issue a RSET and a second FROM/RCPT
TO to avoid that problem.
Whether it's legal or not, it's something that's done quite commonly
already, and I can't say that the people who do this are that wrong.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@??? for PGP key
--
[ Content of type application/pgp-signature deleted ]
--
