Markco Wong
New Member
Hi, anyone got the return mail like this, about the NULL MX records.
What should I do on the zoneedit.com DNS MX records?
Return message:
----------------------------------------------------------------------------------------------------------------
收件人
郵件內文
Sorry, we were unable to deliver your message to the following address.
<mxxxx@mxxxx.com>:
Remote host said:
550 5.7.1 Service unavailable; Client host [67.195.87.220] blocked using nullmx.easyrbl.com; Attempting to deliver to NULLMX See:http://nullmx.easyrbl.com
[RCPT_TO]
--- Below this line is a copy of the message.
Received: from [127.0.0.1] by nm43.bullet.mail.gq1.yahoo.com with NNFMP; 18 May 2016 09:38:02 -0000
Received: from [216.39.60.182] by nm43.bullet.mail.gq1.yahoo.com with NNFMP; 18 May 2016 09:35:01 -0000
Received: from [98.137.12.194] by tm18.bullet.mail.gq1.yahoo.com with NNFMP; 18 May 2016 09:35:01 -0000
Received: from [127.0.0.1] by omp1002.mail.gq1.yahoo.com with NNFMP; 18 May 2016 09:35:01 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 863184.78639.bm@omp1002.mail.gq1.yahoo.com
-----------------------------------------------------------------------------------------------------------------------
Reason:
http://nullmx.easyrbl.com/?index
Reason:
When a domain publishes it's MX handlers as:
example.com. IN MX 0 .
Then any originating mailers are supposed to reject any messages addressed to anybody@example.com with a 556 status code and 5.1.10 enhanced status code.
What they are not supposed to do is try to deliver the message to example.com's A Record
Those MTAs who attempt to do that, are (to quote the words of the author or RFC 7505):
"Any MTA that tries the A address if you publish a null MX (that's "domain MX 0 .") is so broken that it deserves to die if it's not already spamware. "
What an MTA can do is sit on the message for awhile in it's own queue periodically retrying the MX lookup to see if anything has changed. But what it certainly can't do, and should not do upon finding the NULLMX is to fallback to the A for the domain. That is just plain broken or deliberate.
What should I do on the zoneedit.com DNS MX records?
Return message:
----------------------------------------------------------------------------------------------------------------
收件人
郵件內文
Sorry, we were unable to deliver your message to the following address.
<mxxxx@mxxxx.com>:
Remote host said:
550 5.7.1 Service unavailable; Client host [67.195.87.220] blocked using nullmx.easyrbl.com; Attempting to deliver to NULLMX See:http://nullmx.easyrbl.com
[RCPT_TO]
--- Below this line is a copy of the message.
Received: from [127.0.0.1] by nm43.bullet.mail.gq1.yahoo.com with NNFMP; 18 May 2016 09:38:02 -0000
Received: from [216.39.60.182] by nm43.bullet.mail.gq1.yahoo.com with NNFMP; 18 May 2016 09:35:01 -0000
Received: from [98.137.12.194] by tm18.bullet.mail.gq1.yahoo.com with NNFMP; 18 May 2016 09:35:01 -0000
Received: from [127.0.0.1] by omp1002.mail.gq1.yahoo.com with NNFMP; 18 May 2016 09:35:01 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 863184.78639.bm@omp1002.mail.gq1.yahoo.com
-----------------------------------------------------------------------------------------------------------------------
Reason:
http://nullmx.easyrbl.com/?index
Reason:
When a domain publishes it's MX handlers as:
example.com. IN MX 0 .
Then any originating mailers are supposed to reject any messages addressed to anybody@example.com with a 556 status code and 5.1.10 enhanced status code.
What they are not supposed to do is try to deliver the message to example.com's A Record
Those MTAs who attempt to do that, are (to quote the words of the author or RFC 7505):
"Any MTA that tries the A address if you publish a null MX (that's "domain MX 0 .") is so broken that it deserves to die if it's not already spamware. "
What an MTA can do is sit on the message for awhile in it's own queue periodically retrying the MX lookup to see if anything has changed. But what it certainly can't do, and should not do upon finding the NULLMX is to fallback to the A for the domain. That is just plain broken or deliberate.
