Solved

Exchange server Blacklisted with LashBack Blocking with return code 127.0.0.2

Posted on 2009-04-11
3
4,797 Views
Last Modified: 2013-12-09
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
Comment
Question by:brandywine
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 19

Expert Comment

by:MrLonandB
ID: 24121983
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
 

Author Comment

by:brandywine
ID: 24123751
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
 
LVL 19

Accepted Solution

by:
MrLonandB earned 500 total points
ID: 24125357
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

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
This article explains how to install and use the NTBackup utility that comes with Windows Server.
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question