JAMES has always enforced RFC compliance. In the case of JAMES-642 (a request
to drop the RFC 2821 requirement that MAIL and RCPT addresses have brackets),
when this has come up on rare occasions, we have repeatedly and deliberately
rejected such requests. Now Norman, Stefano and Joachim are in favor of
permitting the behavior.
I am against supporting specification violations, even as an option, except
*maybe* in the case that there is such a widespread issue that everyone's
transport capabilities are compromised. Postal's Law doesn't mean to ignore
mandated behavior. RFC 2821 is quite clear that the brackets must always be
present for MAIL and RCPT. Are we as a community changing to say that
specification compliance is no longer important?
As for a possible solution, the "fast fail" chain is really about in-protocol
plug-ins, not just fast fail. If someone wants to write a command handler to
repair defective addresses for MAIL and RCPT, that's their option. JAMES is
open source. If someone wants to violate the specification, they can manage
their own changes.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
