Aaron,
> *Interoperability Rule Number One:* Be strict in what you send and
> lenient in what you accept.
The problem with that rule is that it encourages and facilitates bad
clients. One way to deal with that situation is to let bad clients know
that they ARE bad.
I am not saying that we might not be lenient. It is not Jame's job, but it
is the admin's job. If someone wants to contribute code that allowed a
"strict|lenient" RFC interpretation, I would not object IFF that code was
clean. But I am more concerned with the DOS aspects of Serge's report than
in supporting broken mail clients.
I say this from the perspective of a mail admin supporting paying accounts
who also has to deal with the fact that Yahoo's mail client uses an obsolete
POP3 command that is specifically suggested to NOT be implemented.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
