> Its announing for people to not get reports etc. Even if the
> reports are not fully RFC conform.
I empathize with the person's problem, but standards exist to enforce
compliance. Without them we have chaos. We should not waste a single line of
code nor a minute of time on allowing specification violations. However ...
As I said, JAMES is Open Source, and 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 you want to help the user, write a sample command
handler for MAIL and RCPT that repairs the addresses before the real handlers
are called. 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. I would be opposed to any logic in the
main handlers to deal with this situation.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
