I've been researching an issue where emails are getting rejected with these NDR errors:
An error occurred while trying to deliver this message to the recipient's e-mail address. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.
The following organization rejected your message: smoothwall.
_____ Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
#552 www.w3.org in multi.surbl.org: 74.63.164.174 ## #552 www.w3.org in multi.surbl.org: 204.232.162.153 ##
If I'm reading this correctly the emails are being rejected cause the multi.susrbl.org found a reference to w3.org in a HTML email??
How can this be fixed/removed/corrected?
Thanks, Duane
On 4/26/10, Wolf, Duane A. Duane.Wolf@nov.com wrote:
I've been researching an issue where emails are getting rejected with these NDR errors:
An error occurred while trying to deliver this message to the recipient's e-mail address. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.
The following organization rejected your message: smoothwall.
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
#552 www.w3.org in multi.surbl.org: 74.63.164.174 ## #552 www.w3.org in multi.surbl.org: 204.232.162.153 ##
If I'm reading this correctly the emails are being rejected cause the multi.susrbl.org found a reference to w3.org in a HTML email??
How can this be fixed/removed/corrected?
Thanks, Duane
www.w3.org is not blacklisted. You can confirm this on the lookup page:
The most likely reason for this is DNS corruption:
http://www.surbl.org/faq.html#opendns http://www.surbl.org/faq.html#dnsproxy
Please let your recipient's mail administrator know about this, and please let us know how/that they correct it.
On Mon, 26 Apr 2010, Wolf, Duane A. wrote:
I've been researching an issue where emails are getting rejected with these NDR errors:
An error occurred while trying to deliver this message to the recipient's e-mail address. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.
The following organization rejected your message: smoothwall.
_____ Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
#552 www.w3.org in multi.surbl.org: 74.63.164.174 ## #552 www.w3.org in multi.surbl.org: 204.232.162.153 ##
If I'm reading this correctly the emails are being rejected cause the multi.susrbl.org found a reference to w3.org in a HTML email??
How can this be fixed/removed/corrected?
Thanks, Duane
"w3.org" is not in any surbl.org list and to the best of my knowledge never has been. (it would be a mistake if it ever were).
Sometimes ISPs will provide a "special" customized DNS service that takes queries that 'miss' and provides an answer that routes their customers to a "helpful" web page (on the assumption that the DNS 'miss' was due to a customer mis-typing a host name in a web browser). Needless to say, such "helpfulness" causes chaos with DNS-based listings such as SURBL, Spamhaus, SORBS, CBL, and many others. So that false-positive may have been caused by FUBARed local DNS/network configuration.
Be that as it may, any intelligent implementation of surbl filtering will have a local "whitelist" of URLs that it will never bother even trying to look up such as "google.com" "hotmail.com" "msn.com", and "w3.org" (SpamAssassin does this). This is as much to reduce filtering and network overhead as it is to guard against false-positives.
Long story short, that NDR report is either wrong & misleading or an indication of a fundamental problem in that mail server, it isn't caused by SURBL. You'll have to try to get that mail administrator to figure out what's going on. Good luck there, MS Exchange has a long history of Bowdlerizing internet-RFC error messages to "not confuse people". ;(
Long story short, that NDR report is either wrong& misleading or an indication of a fundamental problem in that mail server, it isn't caused by SURBL. You'll have to try to get that mail administrator to figure out what's going on. Good luck there, MS Exchange has a long history of Bowdlerizing internet-RFC error messages to "not confuse people". ;(
One other note, I've also seen issues where DNS servers were hammering the public mirrors of black lists that caused false positives like this. I don't remember what SURBL returns when it's blacklisted but it's a scenario to consider.
regards, KAM