Well we need a new entry point for out fastfail stuff. So we should
remember to allow such stuff.
bye
Norman
Guillermo Grandes schrieb:
mmm, Good, for anything like FixMissingBrackets we need add a
setCommandArgument in SMTPSession to rewrite/intercept the Argument
parsed by core MAIL/RCPT without polute the main code, right?. (seems
like (org.apache.mailet.Mail) setState())
----- Original Message ----- From: "Noel J. Bergman" <[EMAIL PROTECTED]>
To: "James Developers List" <server-dev@james.apache.org>
Sent: Saturday, September 30, 2006 7:51 PM
Subject: RE: [jira] Commented: (JAMES-642) Mail Address Error : Did
not start and end with < > (brackets) - Compatibility leak
Guillermo Grandes wrote:
if we forced users with strict things (all are not programmers), what
happens?
There is incentive for defective products to be corrected. If
everyone bows down to the defective implementors, there is no reason
to implement standards correctly. Compliance should be strict.
However, I'm aware that not all defective products can be corrected,
due to the lack of care from their implementors, lack of those
implementors still existing, and/or lack of available source code for
users to correct the defects.
So if someone really needs for a filter to support bogus client
products, there is a way to insert it into JAMES without polluting
core code.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
!EXCUBATOR:1,451eafa853074413711464!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
