• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4983
  • Last Modified:

Exchange server Blacklisted with LashBack Blocking with return code 127.0.0.2

One of our clients got blacklisted  week ago and most of their emails from their exchange server started bouncing as a result.  I had comcast create reverse dns for mail.theirdominname.com to their IP address and created a SPF text record on their godaddy domain.

This helped me get them delisted and for a week we started making progress with ability to send to most domains, howerver yesterday they got blacklisted by lash back with "Sender has sent to LashBack Unsubscribe Probe accounts
Return codes were: 127.0.0.2"

I checked their mail server on mxtoolbox and there is no relay, and everything looks good.

What else can be causing them to get listed again?  I am running out of ideas and would appreciate any help

Thanks in advance
0
brandywine
Asked:
brandywine
  • 2
1 Solution
 
MrLonandBCommented:
On the mail server of your client, if you open IE and go to: whatismyip.com...is the ip address returned to you, the correct public IP address for the mail server? Just checking that, as sometimes NAT rules on firewalls might be translating the outgoing mail to an incorrect ip address.

If you do have the correct address, have you tried using an SMTP Connector to route your mail to your ISP rather than using DNS?

http://www.amset.info/exchange/smtp-connector.asp
0
 
brandywineAuthor Commented:
The WAN IP address is correct

I will try the smtp connector, however there is no one in the office today and I got them delisted from lashback and a few hours later they already got relisted with them - will the smtp connector even help?
0
 
MrLonandBCommented:
It sometimes does. In your original description of the problem, it was not indicated as to whether their outbound mail was using DNS or whether a Smart Host is setup...forwarding mail to their ISP for delivery. So I assumed DNS. If that is the case, set an SMTP Connector and have the mail delivered to their ISP as a Smart Host. Also, if you only have one Exchange Server in that organization, you can just setup the Smart Host in the SMTP Virtual Server and you won't need the SMTP Connector. Only if you just have one Exchange Server in that organization though...if you have multiple Exchangne Servers, you will have to create the Connector.
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.

Join & Write a Comment

Featured Post

Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now