Re: postscreen delay inprovement - multple IP addresses
On 7/8/2017 2:54 PM, techlist06 wrote: > Will > such a client immediately retry on the next available DNS configured MX (if > available) Yes, many senders will immediately try the secondary MX if the primary gives a temporary error. If you have one MX, most senders will delay some time before a retry. > That > would be great presuming the undesirables don't. > Most clients -- good and bad -- that get a deferral from the primary will try the secondary. Some bad clients will try the secondary first. http://www.postfix.org/POSTSCREEN_README.html#white_veto -- Noel Jones
Re: Force IPv4 by Destination MX
Scott Talbert skrev den 2017-07-09 05:27: New to Postfix here. http://postfix.1071664.n5.nabble.com/smtp-IPv4-IPv6-map-td61342.html
Force IPv4 by Destination MX
Hello, New to Postfix here. Unfortunately Google has stopped accepting mail from my server via IPv6 and I haven't been able to figure out why or resolve the problem. However, it accepts mail via IPv4 just fine. Thus, I would like to configure Postfix to use IPv4 when sending mail to Google. I can see that this is posible by destination domain using transport_maps. So, I could use transport_maps to specify that all mail to @gmail.com would be sent via IPv4. However, there are many other domains that use Google's email services. Rather than try to list all of them, I was wondering if instead it was possible to force IPv4 by destination MX instead. In that case, I could just specify all of Google's MX's and work around this problem. Thanks, Scott
Re: postscreen delay inprovement - multple IP addresses
re "IP addresses, published in DNS as different IP addresses for the same MX hostname or for different MX hostnames. This avoids mail delivery delays with clients that reconnect immediately from the same IP address. " I understand now this had nothing to do with improving systems that (re)connect from different IPs. Hopefully not too elementary of a question I would like to understand how it helps for clients reconnecting immediately from the same IP. Will such a client immediately retry on the next available DNS configured MX (if available) vs. some other delay to retry on the same IP? As if the primary was considered unavailable so it immediately tries the secondary? That would be great presuming the undesirables don't. Thanks again, Scott -- View this message in context: http://postfix.1071664.n5.nabble.com/postscreen-delay-inprovement-multple-IP-addresses-tp91174p91197.html Sent from the Postfix Users mailing list archive at Nabble.com.
