james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Closed: (JAMES-66) MX Chaining in the RemoteDelivery mailet is broken
Date Sun, 06 Jun 2004 21:21:54 GMT
Message:

   The following issue has been closed.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JAMES-66

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JAMES-66
    Summary: MX Chaining in the RemoteDelivery mailet is broken
       Type: Bug

     Status: Closed
 Resolution: FIXED

    Project: James
 Components: 
             SpoolManager & Processors

   Assignee: 
   Reporter: Peter M. Goldstein

    Created: Fri, 8 Nov 2002 8:19 AM
    Updated: Sun, 6 Jun 2004 2:21 PM
Environment: Operating System: Other
Platform: Other

Description:
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.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message