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 <st...@blighty.com> wrote: > > > On Jul 14, 2016, at 1:38 PM, Brian Godiksen <br...@socketlabs.com> > 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 though. > > > > Example: > > > > ;; QUESTION SECTION: > > ;hotmai.com. IN MX > > > > ;; ANSWER SECTION: > > hotmai.com. 2530 IN MX 10 . > > > > Is anyone ignoring the preference number in their implementation? > > More generally, is anyone special-casing this rather than just treating it > as an idiomatic way of creating an email address that immediately fails to > deliver? > > Cheers, > Steve > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
