Exchange 2003 ent edition - whats up with my ISP or microsoft

Posted on 2011-10-08
Medium Priority
Last Modified: 2012-05-12
Recently my ISP enforced us to change the whole networks external IPs.  I did that on thursday.  Obviously has to change the external exchange IP address too.  Since last night one of the domain user is having issue as under,  I wanted to send an email to the same domain as well but the same issue as under.  I can send emails to lots of domains.  Never had this issue before.  Where do I seek help?  is microsoft doing something or my ISP?

One of my domain user is trying to send an email to a specific domain and the message bounces back as:
 <mail.mydomain.com #5.7.1 smtp;550 5.7.1 Service unavailable; Client host [72.xx.xxx.xxx] blocked using Blocklist 2, mail from IP banned; To request removal from this list please forward this message to delist@messaging.microsoft.com.>
Question by:amanzoor
  • 3
  • 3

Accepted Solution

Gerald26 earned 1600 total points
ID: 36935839
Check your ISP has a valid reverse DNS record for your IP,
Check if this IP isn't blacklisted http://www.mxtoolbox.com/blacklists.aspx
Check your DNS public records and modify any SPF you might have created.
LVL 24

Assisted Solution

yo_bee earned 400 total points
ID: 36935851
Do you have a PTR for your public MX record?
Is this a static or dynamic ip-address being issued by your ISP?

If the receiving end's server has the reverse look feature enabled and you do not have a PTR then the message will be rejected.

I had a client that used Cable internet ISP that issued dynamic addresses for business class back in 2000 and AOL and other domains rejected the e-mails because they were part of a dynamic pool of addresses.  I had to use the SMARTHOST to forward all mail to my ISP's SMTP and relay off that.

These are some ideas to look at.

Author Comment

ID: 36938559
Thanks Guys:
Microsoft has released the IP, at least I am able to send to that particular domain.  I am unable to telnet to my excahnge as:
telnet mydomain.com 25
telnet externalIPofEXchange 25
could not open connection to the host on port 25
Is it good or bad?
Help plz

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.


Expert Comment

ID: 36938642
If your public IP is now you default MX for the domain you're hosting, then it is not good: You should be able to telnet your external IP on TCP Port 25 (SMTP).
Telnet Mydomain.com 25 will probably not work but telnet host.mydomain.com 25 should work (host can be SMTP, MAIL, MX or anyname you of the host you created in your DNS Zone.)

This is done by configuring your router/firewall to accept incoming connexion on public IP port 25 and NAT'ing the connexion to the Exchange server.
Depending on the firewall (ISA, Arkoon, fortigate, netasq, linux box,...) you must modify the "Public IP" object created to reflect the new public IP you got.
Turn on filtering logging and check errors to get a more verbose output and analysis.


Author Comment

ID: 36943320
My MX records are held by my ISP.  Do you think thats the reason, also when I nslookup, mail.mydomain.com, it gives me the preferred mail server of my ISP who is taking care of my mx of my mail.  Is it good?

Expert Comment

ID: 36943422
ahh sure,  it is good !
Your ISP holds your MX, analyzes mails and then you either go "pop the messages" with a pop conector or they forward these messages to your mail server using your ..... public IP! (In this case, only your ISP is allowed to telnet your exchange server from the outside.)

If this is the case, you must give them the new public IP to forward the mails.

Of course you still need to check your firewall rules and hosts unless your ISP also manages your firewall.

Author Closing Comment

ID: 36946061
Thanks Guys.

Featured Post


Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

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

If you have come across a situation where you need to find some EDB mailbox recovery techniques, then here you will find the same. In this article, we will take you through three techniques using which you will be able to perform EDB recovery. You …
You finally migrated Public Folders to Office 365, decommissioned the Public Folder mailbox database and since then, when you send an email from on-premise to mail-enabled Public Folders, you get the following error: "Misconfigured public folder mai…
In this video we show how to create a mailbox database 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 Servers >> Data…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Suggested Courses

580 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