Ok here we are...

For me it make sense to allow such configurable stuff. Its announing for people to not get reports etc. Even if the reports are not fully RFC conform.

bye
Norman


Noel J. Bergman (JIRA) schrieb:
[ http://issues.apache.org/jira/browse/JAMES-642?page=comments#action_12438894 ] Noel J. Bergman commented on JAMES-642:
---------------------------------------

Postal's Law is not an invitation to blithely ignore specifications.  RFC 2821 is quite 
clear that the '<' and '>" characters must always be present for MAIL and RCPT. 
 They are not required for VRFY and EXPN, but those are not implemented by JAMES.

JAMES has always intentionally enforced RFC compliance.  It would be a fairly 
sizable sea-change to stop doing so now, and should be discussed on the mailing 
list, not backdoored on the issue tracker.

Mail Address Error : Did not start and end with < > (brackets) - Compatibility 
leak
-----------------------------------------------------------------------------------

                Key: JAMES-642
                URL: http://issues.apache.org/jira/browse/JAMES-642
            Project: James
         Issue Type: Improvement
   Affects Versions: Trunk
        Environment: James 3.0
           Reporter: Guillermo Grandes
        Assigned To: Norman Maurer

I have a little problem with a few of historical applications (including Oracle 
packages to send mail) who do not send the brackets (<>) in MAIL FROM: address 
/ RCPT TO: address and James kick-out this with error:
2006-09-29 13:30:50,127 ERROR [smtpserver] Error parsing sender address: [EMAIL 
PROTECTED]: did not start and end with < >
MAIL FROM: [EMAIL PROTECTED]
501 5.1.7 Syntax error in MAIL command
RCPT TO: [EMAIL PROTECTED]
501 5.5.2 Syntax error in parameters or arguments
In sendmail and IIS-SMTP don't have this problem.




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to