Stefano Bagnara wrote:
> I don't agree that JAMES-642 is a request to drop RFC2821 requirement
> that MAIL and RCPT address have brackets: IMO is clear that this is a
> requirement for clients, not for servers!
RFC 2821 is a protocol for message transfer. Where this is different behavior
allowed for clients and servers, it so indicates, as you noted elsewhere.
> My interpretation of Postal's Law applied to this issue is quite different:
> An SMTP client MUST use the brackets.
> An SMTP server COULD accept also addresses without brackets.
Section 3.3 makes clear in several places that the "<" and ">" are necessary
delimiters, mentioning (for example): "a mailbox and domain, always surrounded
by "<" and ">" brackets". Furthermore, section 4.1.2 allows no
misinterpretation. Those are REQUIRED characters. There is no ambiguity in
the specification.
> It is not so clear that accepting a MAIL FROM or an RCPT TO without
> brackets is a violation to the RFC.
I disagree.
> So I think that I never changed my mind on specification compliance: we
> seem to have a different Idea on what does it mean to be specification
> compliant.
Well, that's a good thing. We're agreeing that spec compliance is still
mandatory.
As for an acceptable change, I suggested twice:
> we have a place in the code path where a plug-in could repair invalid
> addresses.
> We should not pollute our code with specification violations. If [we] want to
> help the user, [let's write] a sample command handler for MAIL and RCPT that
> repairs the addresses before the real handlers are called.
As previously, noted, that would be a worthwhile exercise on our part to make
sure that our implementation of the protocol handler mechanism and
configuration is flexible enough to support the notion, even if the plug-in,
itself, is rather bogus. I am opposed to polluting the main handlers to logic
to deal with spec violations.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
