james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 14381] New: - MX Chaining in the RemoteDelivery mailet is broken
Date Fri, 08 Nov 2002 08:19:59 GMT
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=14381>.
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=14381

MX Chaining in the RemoteDelivery mailet is broken

           Summary: MX Chaining in the RemoteDelivery mailet is broken
           Product: James
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: SpoolManager & Processors
        AssignedTo: james-dev@jakarta.apache.org
        ReportedBy: farsight@alum.mit.edu


MX chaining in RemoteDelivery is broken.  Basically, the code in place assumes 
that a given MessagingException generated while sending mail doesn't merit a 
retry unless it encapsulates an IOException.  This doesn't appear to be the 
exception generated when a server refuses a connection.  So the exception is 
rethrown, and the other SMTP servers are never tried.

Instead, there should be a separate try/catch block around the 
transport.connect() statement, to handle connect errors separately from errors 
that arise during message transmission.  Connect errors almost always 
indicates that further SMTP servers associated with the MX record should be 
tried, while errors in message transmission are generally protocol-level 
errors that would occur with any SMTP server associated with the MX record 
(the exception being IOExceptions that indicate a failure in the underlying 
transport).

I've got a code change and am working with the user who reported the problem 
to see if it resolves his issue.  As we are now past code freeze for 2.1, the 
committers will have to determine whether resolution of this defect merits 
code change at this late date.

--
To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>


Mime
View raw message