james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter M. Goldstein" <peter_m_goldst...@yahoo.com>
Subject RE: [PATCH/VOTE] - MX Chaining fix.
Date Mon, 11 Nov 2002 22:11:43 GMT


> I've now read the bug report and the code.  Seems reasonable.
> there are useful comments in the bug report that probably ought to be
> the
> code (or at least in the CVS).
> Specifically: "there should be a separate try/catch block around the
> transport.connect() statement, to handle connect errors separately
> errors that arise during message transmission.  Connect errors almost
> always
> indicates that further SMTP servers associated with the MX record
> be
> tried, while errors in message transmission are generally
> errors that would occur with any SMTP server associated with the MX
> (the exception being IOExceptions that indicate a failure in the
> underlying
> transport)" provides more elaboration than the current comments.
> I guess I'm not a big fan of having the bug database as the only (or
> source for why the code is as it is.

Ok.  I thought the comment I dropped in the code was sufficient, but we
can certainly cut and paste this into the code itself.

Personally I think we under use Bugzilla as a repository for useful
information.  This is exactly the sort of information a bug tracking
system is supposed to track.  :)


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

View raw message