Blacklisted on Backscatter

Using exchange 2003
Incoming mail is router via a hosting company baracuda to my exchange

Hello for some reason some of my e-mails are being rejected wit the following   <webmail.mydomain.com #5.5.0 smtp;550 550
Dynamic/zombied/spam IPs blocked. Write
blockedbyearthlink@abuse.earthlink.net>
Reporting-MTA: dns; my-email-server.fwd.local

Final-Recipient: RFC822; outsideuser@domain.com
Action: failed
Status: 5.5.0
X-Supplementary-Info: <webmail.mydomain.com #5.5.0 smtp;550 550 Dynamic/zombied/spam IPs blocked. Write blockedbyearthlink@abuse.earthlink.net>
X-Display-Name: oking@stonehurst.net

form backscatter.org I get this
This IP IS CURRENTLY LISTED in our Database.
Please note that this listing does not mean you are a spammer, it means your mailsystem is either poorly configured or it is using abusive techniques.
This kind of abuse is known as BACKSCATTER (Misdirected Bounces or Misdirected Autoresponders or Sender Callouts). Click the links above to get clue how and why to stop that kind of abuse.


To track down what happened investigate your smtplogs near 09.02.2011 22:23 CET +/-1 minute.

You will either find that your system tried to send misdirected bounces or misdirected autoresponders to claimed but in reality faked senders, or your system tried sender verify callouts against our members near that time.

So you should look for outgoing emails that have a NULL SENDER or POSTMASTER in MAIL FROM.

Reading your logs carefully it shouldn't be a big deal to figure out what caused or renewed your listing.


History:
23.06.2007 23:01 CEST      listed      
22.07.2007 02:15 CEST      expired      
23.07.2007 11:11 CEST      listed      
21.12.2007 23:30 CET      expired      
19.06.2009 18:06 CEST      listed      
17.07.2009 18:25 CEST      expired      
18.12.2009 14:49 CET      listed      
15.01.2010 15:25 CET      expired      
28.01.2011 10:29 CET      listed
FalconTwoAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Alan HardistyConnect With a Mentor Co-OwnerCommented:
If you have Recipient Filtering enabled, it is either not working or you are using a 3rd party to spam filter for you and they are not Recipient Filtering.

If the latter, if they don't recipient filter and accept the message, then pass iton to you, because the message has been accepted already by the 3rd party, you are forced to generate an NDR.

Are you using a 3rd party for spam filtering?
0
 
Alan HardistyCo-OwnerCommented:
If you are blacklisted in Backscatterer then you are not Recipient Filtering and thus accepting messages for invalid Recipients, then because you have accepted the message, you are forced to send an NDR message once Exchange realises there is no valid recipient.

Please enable Recipient Filtering to cure the problem:

http://www.msexchange.org/tutorials/Sender-Recipient-Filtering.html
0
 
FalconTwoAuthor Commented:
I have recipient filtering enabled
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
FalconTwoAuthor Commented:
I also saw the link you suggested, I have all the correct settings in place hence the reason why I am stumped
0
 
FalconTwoAuthor Commented:
Yes I will contact them now
0
 
FalconTwoAuthor Commented:
Yes we are, I just sent an e-mail explaining the situation to them.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.