Re: [mailop] SPF for domains that don't send e-mail

2015-04-02 Thread Suresh Ramasubramanian
Yeah, thanks. Those were what I was wondering whether they had happened again. --srs > On 02-Apr-2015, at 11:30 pm, John Levine wrote: > > There were some surprising (and I think rather ill-informed) objectsions when > we did last call on the nullmx draft, but they were resolved long ago.

Re: [mailop] SPF for domains that don't send e-mail

2015-04-02 Thread John Levine
In article you write: >Out of curiosity, which catch 22 references? I contributed a bit to that >draft back in the day. There's a new 5xx code for servers that reject mail due to the reverse path being nullmx. It's defined in a draft that just got out of last call yesterday so whould go to the

Re: [mailop] SPF for domains that don't send e-mail

2015-04-02 Thread Scott Bonacker CPA
Subject: Re: [mailop] SPF for domains that don't send e-mail On Thu, Apr 2, 2015 at 7:27 AM, Aaron C. de Bruyn wrote: On the note of trying to be a good netzin, should I publish a SPF record for a domain that should never be used to send e-mail? Would "v=spf1 -all" cause milter

Re: [mailop] SPF for domains that don't send e-mail

2015-04-02 Thread Suresh Ramasubramanian
Out of curiosity, which catch 22 references? I contributed a bit to that draft back in the day. --srs > On 02-Apr-2015, at 8:43 pm, Kurt Andersen (b) wrote: > > APPSWG is working on getting it accepted. There have been some Catch-22 > references that needed to get sorted out. __

Re: [mailop] SPF for domains that don't send e-mail

2015-04-02 Thread Kurt Andersen (b)
On Thu, Apr 2, 2015 at 8:00 AM, Suresh Ramasubramanian wrote: > And if you don't want to receive mail on that domain either .. > > example.com.MX 0 . > > Yeah, mx zero dot. > > There's an old rfc that never got beyond draft stage that explains it all, > but rfc or no rfc, it works fine. >

Re: [mailop] SPF for domains that don't send e-mail

2015-04-02 Thread Suresh Ramasubramanian
And if you don't want to receive mail on that domain either .. example.com.MX 0 . Yeah, mx zero dot. There's an old rfc that never got beyond draft stage that explains it all, but rfc or no rfc, it works fine. --srs > On 02-Apr-2015, at 7:57 pm, Aaron C. de Bruyn wrote: > > On the n

Re: [mailop] SPF for domains that don't send e-mail

2015-04-02 Thread Michael Wise
Yes. Aloha, Michael. -- Sent from my Windows Phone From: Aaron C. de Bruyn<mailto:aa...@heyaaron.com> Sent: ‎4/‎2/‎2015 7:36 AM To: mailop@mailop.org<mailto:mailop@mailop.org> Subject: [mailop] SPF for domains that don't send e-mail On the note

Re: [mailop] SPF for domains that don't send e-mail

2015-04-02 Thread Aaron C. de Bruyn
That's a *great* document. It even answered my question about abuse@. Thanks for the pointer. -A On Thu, Apr 2, 2015 at 7:39 AM, Kurt Andersen (b) wrote: > On Thu, Apr 2, 2015 at 7:27 AM, Aaron C. de Bruyn > wrote: >> >> On the note of trying to be a good netzin, should I publish a SPF >> rec

Re: [mailop] SPF for domains that don't send e-mail

2015-04-02 Thread Kurt Andersen (b)
On Thu, Apr 2, 2015 at 7:27 AM, Aaron C. de Bruyn wrote: > On the note of trying to be a good netzin, should I publish a SPF > record for a domain that should never be used to send e-mail? > > Would "v=spf1 -all" cause milters to reject all mail from the domain? > Referring to the M3AAWG BCP for

[mailop] SPF for domains that don't send e-mail

2015-04-02 Thread Aaron C. de Bruyn
On the note of trying to be a good netzin, should I publish a SPF record for a domain that should never be used to send e-mail? Would "v=spf1 -all" cause milters to reject all mail from the domain? -A ___ mailop mailing list mailop@mailop.org http://ch