james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara (JIRA)" <server-...@james.apache.org>
Subject [jira] Commented: (JAMES-358) Too many RemoteDelivery attempts with many mx and many ip
Date Wed, 16 Mar 2005 11:49:20 GMT
     [ http://issues.apache.org/jira/browse/JAMES-358?page=comments#action_60959 ]
Stefano Bagnara commented on JAMES-358:

I've just read point 5 from RFC 2821:

"To provide reliable mail transmission, the SMTP client MUST be able to try (and retry) each
of the relevant addresses in this list in order, until a delivery attempt succeeds.  However,
there MAY also be a configurable limit on the number of alternate addresses that can be tried.
 In any case, the SMTP client SHOULD try at least two addresses."

>From a previous paragraph it seems that it is correct to try every IP address resolved
from an MX server.

So this "Improvement" should be reformulated: why don't we add a configurable limit for the
remotedelivery? I think that the sentence "the SMTP client SHOULD try at least two addresses"
is the lower limit and RemoteDelivery is currently working on the upper limit. I use james
for high volume mailing lists and it seems that for ML usage a lower limit would be better.

> Too many RemoteDelivery attempts with many mx and many ip
> ---------------------------------------------------------
>          Key: JAMES-358
>          URL: http://issues.apache.org/jira/browse/JAMES-358
>      Project: James
>         Type: Improvement
>   Components: Remote Delivery
>     Versions: 2.2.0
>     Reporter: Stefano Bagnara
>     Priority: Minor

> Take a domain with 5 mx servers each one with 6 associated ips. James currently try to
connect to each MX server even if the first server say "5.1.1 user unknown", but even worst,
james try to connect to each IP of each MX server.
> I think that james should only check each MX server once, at a random IP address from
the IP list for that mx hostname.
> The permanent user error issue would be only a further optimization but the IP issue
is probably against the RFC specifications.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

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

View raw message