Mweb & Anti-BackScatter

Brandon

Well-Known Member
Joined
Feb 18, 2004
Messages
276
Reaction score
54
Location
National Bank of Zuma
In my never ending quest to keep company spam to less than .001%, I have employed the use of anti-backscatter features - which basically adds a code in front of all outgoing messages. If there is a NDR or other automated response it will be sent to the coded address and thereby be accepted a legitimate notification message.
MWEB - being very “state-of-the-art” with wonderful delaying tools such as greylisting seem not to support the anti-backscatter code, and as a result reject messages with:

Thu 2007-09-06 12:14:42: <-- 550-Verification failed for <REMOVED>
Thu 2007-09-06 12:14:42: <-- 550-Called: 196.2.16.216
Thu 2007-09-06 12:14:42: <-- 550-Sent: RCPT TO:<REMOVED>
Thu 2007-09-06 12:14:42: <-- 550-Response: 550 Previous (cached) callout verification failure
Thu 2007-09-06 12:14:42: <-- 550-MWEB-Sender-Verify-Failed: The email address
Thu 2007-09-06 12:14:42: <-- 550-<REMOVED> is invalid, please use a valid email
Thu 2007-09-06 12:14:42: <-- 550 address.

I would love to know what “MWEB-Sender-Verify” is as they don’t seem to use SPF or DK, much less hashcash – although I may be mistaken…
What really gets to me is their “support” which is geared towards helping with basic client connection type problems. I forwarded them the NDR from THEIR servers explaining how my server is configured and if they could please investigate. The reply I get is detailed instructions telling me to login into my –non existent- mweb account and check MY spam filter settings!! FFS!
 
Top
Sign up to the MyBroadband newsletter
X