I like your suggestion: I've not thought at it enough to understand
wether this will make us to duplicate all of our code or not, but
generally speaking your proposal make sense.
The problem with the specific issue of missing brackets is that I don't
consider that supporting them (when acting as server) is not a
specification violation.
As an example this change already involve the MAIL and the RCPT
handlers. You would start having 2 MAIL Handlers and 2 RCPT handlers,
for only this specific support... not sure that this will be good, but
as I said I don't know enought the current handlerchain architecture
(maybe noone does, because it is in branch since 2 months and not
completed yet).
Stefano
Jürgen Hoffmann wrote:
Hi Stefano,
I was thinking a bit, and came to a proposal. What about you have a RFC
compliant *AnythingThatIsNotCompliantWillBeDropped* Handler. And another
Handler, which allows common Bendings of the RFC.
IMHO if other RFC compliant Mailservers (i.e. postfix, qmail) allow
this, James should allow this.
I am thinking about the same way HTML is able to distinct between
transitional and strict.
Could this be a way to go? That way the behaviour is still configurable,
as the user desires. Correct?
Kind regards
Juergen Hoffmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
