DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16832>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16832 James doesn't cope with malformed addresses Summary: James doesn't cope with malformed addresses Product: James Version: 2.1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: SMTPServer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have James configured to pass everything that reaches the "transport" processor to my mailet: <processor name="transport"> <mailet match="All" class="MyMailet"/> </processor> As part of testing my mailet, I then used fetchmail to present to James' SMTP interface the last ~1150 articles that arrived at the input to my personal procmail filters. Of these, only ~1060 reached my maillet. The rest landed in james-2.1/apps/james/var/mail/error. 'strings *.Respository.FileObjectStore' reveals that most of these contain javax.mail.internet.AddressException for one reason or another (illegal whitespace in local part, illegal character in local part, local part ends with '.', ...), often in the From: address rather than the To: address meaning that, in principle at least, delivery could still be performed. I don't have an immediate suggestion about how to fix this; presumably JavaMail's MimeMessage constructor is choking, which can't easily be fixed. Encapsulation as an application/octet-stream inside a failure message to the postmaster may be a useful workaround. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
