[ http://issues.apache.org/jira/browse/JAMES-358?page=comments#action_12330659 ]
Stefano Bagnara commented on JAMES-358: --------------------------------------- You are reporting only a part of the RFC you are referring to. I can bring a different example from the same RFC: --- The algorithm for a dual-stack SMTP sender is basically the same as that for an IPv4-only sender, but it now includes AAAA lookups of MX records for SMTP-over-IPv6 delivery. IPv4/v6 dual stack destinations should be treated just like multihomed destinations, as described in RFC 2821 [Klensin], section 5. ---- Let's go to RFC 2821, section 5: ---- Although the capability to try multiple alternative addresses is required, specific installations may want to limit or disable the use of alternative addresses. The question of whether a sender should attempt retries using the different addresses of a multihomed host has been controversial. The main argument for using the multiple addresses is that it maximizes the probability of timely delivery, and indeed sometimes the probability of any delivery; the counter- argument is that it may result in unnecessary resource use. Note that resource use is also strongly determined by the sending strategy discussed in section 4.5.4.1. ---- PLEASE NOTE that I simply would like to add an OPTIONAL configuration to let an user to specify this behaviour. Running a server that sends millions of mails per day I really know that when a server for a big domain is down the timeouts will consume most of the delivery time delaying a lot the whole delivery process for the "working" domains. I think we should be RFC compliant, and the RFC is clear enough about this issue: "The question .. has been controversial". If the question has been controversial for the RFC writers I think we should no more discuss about this and simply let the users decide the behaviour they prefer. > 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: DNSServer > Versions: 2.2.0 > Reporter: Stefano Bagnara > Assignee: Stefano Bagnara > Priority: Minor > Fix For: 2.3.0 > Attachments: DNSServer.java.singleIPperMX.diff, > james-config.xml.singleIPperMX.diff > > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
