Re: [mailop] Null MX & Preference

2016-07-18 Thread Kurt Andersen (b)
On Fri, Jul 15, 2016 at 9:33 PM, John Levine wrote: > >> I wasn’t sure if there is a specific > >> reason the preference is called out in the RFC. > > We wanted something consistent. > > >0 is the lowest preference MX and will therefore be tried first, > hopefully overriding any other higher pref

Re: [mailop] Null MX & Preference

2016-07-18 Thread John R Levine
But that's also part of the logic for specifying the precedence as "0" (zero). Even if there are others, they will never be considered. That's not how MX priority works. Lacking a special case to recognize the dot name, if there are lower priority MXes, it'll try them when it can't contact th

Re: [mailop] Null MX & Preference

2016-07-18 Thread Dave Warren
On 2016-07-18 04:45, Kurt Andersen (b) wrote: We have certainly encountered some that do not support a '.' value. DNS Made Easy's web UI is like this. I've used their secondary services for years, but recently I've been looking at their primary services and it's a sloppy mess of things that a