Re: [mailop] proper NULL MX behaviour for MTAs?

2016-02-27 Thread John Levine
>What is an MTA supposed to do with a message addressed to a domain with >a NULL MX? Reject it with a 556 status code and 5.1.10 enhanced status code. If the message was already relayed, return a DSN if it makes sense. See section 4.1. You can also feel free to reject mail if the return address

Re: [mailop] proper NULL MX behaviour for MTAs?

2016-02-27 Thread Michael Wise
I'm no expert on Exchange ... Only the filtering in our service. It should be checked out. I'll see if I can wave the RFC under some noses... Next week. Aloha, Michael. -- Sent from my Windows Phone From: Suresh Ramasubramanian Sent: ‎

Re: [mailop] proper NULL MX behaviour for MTAs?

2016-02-27 Thread Suresh Ramasubramanian
If there's an nxdomain for mx sendmail etc will fall back to the A - not to my knowledge if there's just a servfail No idea about exchange, you should be the expert on that, Mike --srs > On 28-Feb-2016, at 9:39 AM, Michael Wise wrote: > > And Exchange. > > Aloha, > Michael. > -- > Sent fr

Re: [mailop] proper NULL MX behaviour for MTAs?

2016-02-27 Thread Suresh Ramasubramanian
That would be a reasonable supposition --srs > On 28-Feb-2016, at 8:53 AM, Mark Jeftovic wrote: > > >> On 2016-02-27 9:59 PM, Suresh Ramasubramanian wrote: >> A domain with a null mx may well originate email but will absolutely not >> receive email - so mail gets trashed at your end as well

Re: [mailop] proper NULL MX behaviour for MTAs?

2016-02-27 Thread Michael Wise
And Exchange. Aloha, Michael. -- Sent from my Windows Phone From: Franck Martin via mailop Sent: ‎2/‎27/‎2016 7:39 PM To: Mark Jeftovic Cc: Suresh Ramasubramanian; mailop

Re: [mailop] proper NULL MX behaviour for MTAs?

2016-02-27 Thread Franck Martin via mailop
On Sat, Feb 27, 2016 at 7:23 PM, Mark Jeftovic wrote: > > On 2016-02-27 9:59 PM, Suresh Ramasubramanian wrote: > > A domain with a null mx may well originate email but will absolutely not > receive email - so mail gets trashed at your end as well without staying > endlessly on your mall queues >

Re: [mailop] proper NULL MX behaviour for MTAs?

2016-02-27 Thread Franck Martin via mailop
If a domain is telling me it does not accept emails, why should I accept mail from such domain if I cannot reply back to it? On Sat, Feb 27, 2016 at 6:59 PM, Suresh Ramasubramanian wrote: > A domain with a null mx may well originate email but will absolutely not > receive email - so mail gets tr

Re: [mailop] proper NULL MX behaviour for MTAs?

2016-02-27 Thread Mark Jeftovic
On 2016-02-27 9:59 PM, Suresh Ramasubramanian wrote: > A domain with a null mx may well originate email but will absolutely not > receive email - so mail gets trashed at your end as well without staying > endlessly on your mall queues > > You can possibly correlate that mx with the behavior of

Re: [mailop] proper NULL MX behaviour for MTAs?

2016-02-27 Thread Suresh Ramasubramanian
A domain with a null mx may well originate email but will absolutely not receive email - so mail gets trashed at your end as well without staying endlessly on your mall queues You can possibly correlate that mx with the behavior of domains that are sending you mail.. Though a domain rather tha

[mailop] proper NULL MX behaviour for MTAs?

2016-02-27 Thread Mark Jeftovic
What is an MTA supposed to do with a message addressed to a domain with a NULL MX? RFC 7505 talks about domains with a NULL MX should not originate email (in their sender envelopes, etc) but what about the converse? I'm looking at some logs and seeing attempts to deliver email to lots of domains