Link to home
Start Free TrialLog in
Avatar of Sean Meyer
Sean MeyerFlag for United States of America

asked on

Email bouncing back -- New Exchange 2007 Server

We implemented a new Exchange server this weekend. We were using our ISP for mail before this weekend.

I am looking for reasons that mail might be bouncing back.

I know one of the reasons was our ISP messed up our MX record and it was not fixed until last night.  I also know that this may take up to 24 hours for this change to propagate throughout the web.

We have not completed our secure certificate as of yet.  Plan to have this done by this evening.

I used http://www.mxtoolbox.com/   to find the faulty MX record.

I have been using message headers and details of delivery failures to track progress.

I am fairly confident that once the MX record change is known to all senders / receivers that things will be working fine.  

HOWEVER,  what other problems may I encounter and how do I watch for them?  Looking for all Exchange  administration tips I can get my hands on.
ASKER CERTIFIED SOLUTION
Avatar of Matthew Millers
Matthew Millers
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Sean Meyer

ASKER

Good question.  We do not have an edge server but we have enabled anonymous user access on the default receive connector on the HT.  ip's allowed 0.0.0.0 -255.255.255.255   Specify who is able to use this  Receive connector.  Anonymous users checked.

Any more tips?  That one was exactly the type of thing for which I am looking.
Also our firewall has  port 25 and port 443 traffic forwarded to the mail server.
Is it working now?
Can you look at my profile and send me an email please, with your correct email address.
Test message sent.  It is working at times but at others it is still not working.

Still trying to get offsite OWA working.  I have it working internally.
Problem was with reverse DNS lookup.  Reverse DNS lookup had to be explicitly requested from our ISP. So anyone who was testing our reverse DNS was disallowing those messages.