Re: [mailop] Null MX & Preference

2016-07-14 Thread Suresh Ramasubramanian
On 15/07/16, 6:33 AM, "mailop on behalf of Mark Foster" wrote: > Why would any other preference MX exist for a domain not intended to > be used for email? They shouldn’t. Normally. But what if they do?

Re: [mailop] Null MX & Preference

2016-07-14 Thread Mark Foster
Surely if the MX record is declared as a . then the preference is irrelevant? On 15/07/2016 8:38 a.m., Brian Godiksen wrote: I noticed inconsistencies in how domains are publishing null MX records. In RFC7505 it states these records should be published with a preference number 0. I am

Re: [mailop] Null MX & Preference

2016-07-14 Thread Franck Martin via mailop
indeed... I think the null MX makes sense when there is an A or on the same domain. It stops the mail server to try to deliver and wait 4+ days to bounce the message. Other MX that are always fun to use: MX 10 localhost ;) On Thu, Jul 14, 2016 at 2:46 PM, Steve Atkins

Re: [mailop] Null MX & Preference

2016-07-14 Thread Franck Martin via mailop
I kind of see the null MX as a way to say that this domain does not send emails. So it is more a test on the receiving side than on the sending side. On Thu, Jul 14, 2016 at 2:04 PM, Steve Atkins wrote: > > > On Jul 14, 2016, at 1:38 PM, Brian Godiksen

Re: [mailop] Null MX & Preference

2016-07-14 Thread Steve Atkins
> On Jul 14, 2016, at 1:38 PM, Brian Godiksen wrote: > > I noticed inconsistencies in how domains are publishing null MX records. In > RFC7505 it states these records should be published with a preference number > 0. I am seeing a variety of preferences specified