Re: [mailop] Null MX & Preference

[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 are valid but their UI won't permit.


--
Dave Warren
http://www.hireahit.com/
http://ca.linkedin.com/in/davejwarren



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Null MX & Preference

[David Conrad]

Michael,

On Jul 15, 2016, at 2:06 PM, Michael Peddemors  wrote:
> Any one suggest a medium to encourage that amongst registrars?

http://icannregistrars.org
http://gnso.icann.org/en/about/stakeholders-constituencies/rrsg

Regards,
-drc
(ICANN CTO, but speaking only for myself)



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Null MX & Preference

[Michael Peddemors]

Wouldn't it be nice if registrars (the one that provide default DNS when 
you purchase) could be encouraged to add that TXT or SPF record as 
default on all new domain purchases?


This would also encourage adoption of it as a whole, would like to 
assume that real email admin's would update the record, vs delete the 
record.


Any one suggest a medium to encourage that amongst registrars?

On 16-07-15 01:31 PM, John Levine wrote:

In article  
you write:

Doesn't receive emails, sure. Doesn't send emails, I look for the "SPF
lockdown." Lots of places publish this as an SPF record: "v=spf1 -all"


Yes, that's what the RFC suggests.

In answer to the original question, I know that Gmam special cases
MX 0 . to fail the message immediately.

R's,
John

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop





--
"Catch the Magic of Linux..."

Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic

A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.

604-682-0300 Beautiful British Columbia, Canada

This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Null MX & Preference

[John Levine]

>In answer to the original question, I know that Gmam special cases
>MX 0 . to fail the message immediately.

Stupid laptop keyboard.  That's Gmail doing the special cases.


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Null MX & Preference

[John Levine]

In article  
you write:
>Doesn't receive emails, sure. Doesn't send emails, I look for the "SPF
>lockdown." Lots of places publish this as an SPF record: "v=spf1 -all"

Yes, that's what the RFC suggests.

In answer to the original question, I know that Gmam special cases
MX 0 . to fail the message immediately.

R's,
John

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Null MX & Preference

[John Levine]

>> That is what I was thinking.  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 preference MXs that may exist.

The RFC specifically says that if you have a null MX, you can't
have any others.


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Null MX & Preference

[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?



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Null MX & Preference

[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 seeing a variety of preferences specified though.

Example:

;; QUESTION SECTION:
;hotmai.com.IN  MX

;; ANSWER SECTION:
hotmai.com. 2530IN  MX  10 .

Is anyone ignoring the preference number in their implementation?

Thanks,
Brian
___
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

Re: [mailop] Null MX & Preference

[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  wrote:

>
> > On Jul 14, 2016, at 2:39 PM, Franck Martin  wrote:
> >
> > I kind of see the null MX as a way to say that this domain does not send
> emails.
>
> Eh... only indirectly, implicitly and only kinda.
>
> 0-mx-dot states that the domain does not receive email for any address. It
> doesn't say anything directly about whether mail is sent using email
> addresses in that domain.
>
> If you believe that you must be able to deliver an asynchronous bounce for
> any message you receive, and you receive mail with an 821.From that you
> know is undeliverable then it's reasonable to treat that mail with a lot of
> suspicion.
>
> But 0-mx-dot is not an explicit statement by the domain owner of "mail is
> not sent using this domain". That'd be an SPF -all, or something DMARCy.
>
> Cheers,
>   Steve
>
> > 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 
> 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.   2530IN  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
>
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Null MX & Preference

[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 
> 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.   2530IN  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

Re: [mailop] Null MX & Preference

[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 though.
> 
> Example:
> 
> ;; QUESTION SECTION:
> ;hotmai.com.  IN  MX
> 
> ;; ANSWER SECTION:
> hotmai.com.   2530IN  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