james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Danny Angus" <da...@apache.org>
Subject RE: [PATCH/VOTE] - POP3 Performance/Functionality Fix.
Date Tue, 12 Nov 2002 09:55:53 GMT
To this and peter's previous patch.

I accept your logic but I'm extremely wary of introducing bugs at this stage.
Any more late changes will get a -0 or even -1 from me on this basis alone.

In particular the MX patch could, although I trust you to have got it right, easily lead to
unforseen loops or recursions especially as here we are making decisions base on a set of
possible responses which we cannot be 100% sure we have fully enumerated. Even if we have
identified every possible legal response we may still find illegal responses.

For what its worth I think that handling mail server routing by terminating connections after
they have been made and relying on the sender to try another host until one accepts the mail
is a pretty poor hack in the first place when compared with using alternatives, like packet
filtering to route the connection to the correct host in the first instance, and good old
mail forwarding by rules.
I was under the impression (I may be wrong) that MX priorities exist only in order to provide
fail-over and basic load sharing.


> As we are past code freeze, this requires a vote of the committers to be
> accepted.  I think the problem is severe enough (as it is impacting our
> user community) and the fix is localized enough to merit a patch, so I
> vote +1.  Thoughts?

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