Link to home
Create AccountLog in
Avatar of suttons27
suttons27

asked on

New Exchange 2007 setup, People are not receiving email

Short Version: Our company purchased a company in another state a couple of months ago, I'm calling it "Purchased Company" to keep things straight, "Purchased Company" just recently hired an IT consulting group to come in and setup an exchange server 2007 and sbs 2008. It was setup last week. Today I returned from Holiday, and the owner's of the company want me to fix the problem, the problem I just found out is: they "Purchased Company" claim their email setup is fine (via IT consulting group), what is happening is "Purchased Company" is receiving our email fine. But when "Purchased Company" sends email to our company it bounces back saying it could not be delivered. Email flow back and forth prior to last week has been fine, no problem. They are claiming our server is on a blacklisted server listed with AHBL and TIOPAN, I have confirmed this, it is also because we are using a GoDaddy server for our SMTP relay, so I'm sure someone using this server out of the 1000s of accounts GoDaddy has, has done something to get it blacklisted.....but....wouldn't AHBL and TIOPAN only affect, receiving email, meaning, "Sorry your email was received from a blacklisted server, we are going to make you a spam account"....but that is not the problem, they are receiving our emails just fine. Anything I should be looking for before I call them, I do not have access to this new network, will be getting it here shortly, but need to resolve this issue first..Any suggestions on questions I should ask, would be great. I not being the one that set it up and not being able to see what they have done, makes it hard for me to troubleshoot.

Thanks in advance
Avatar of Mahmoud Sabry
Mahmoud Sabry
Flag of Egypt image

not your email server that is blcklisted this way, as u can send emails to them normally, the blacklisted one is their IP address or their domain name, as u can't receive emails from them, and the bounce back email say that the IP address is blacklisted

check their IP address in the following link
http://www.mxtoolbox.com/blacklists.aspx
ASKER CERTIFIED SOLUTION
Avatar of ClintSwiney
ClintSwiney

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of suttons27
suttons27

ASKER

Thanks for the responses, I agree on the bounce back message, they have been trying to send to a 3rd party email account, but nothing is passing through, and I am unable to get a hold of anyone especially the IT consulting group by phone. I did receive a text stating they (IT Consulting group) were there and something is seriously wrong. When I receive the error message, I'll post. Thank you for responding.
Alright have an error message, hope this helps:
Diagnostic information for administrators:

 

Generating server: SRV02.XXX.local

 

XXX.XXX@XXX.com
#550 4.4.7 QUEUE.Expired; message expired ##

 

Original message headers:

 

Received: from SRV02.XXX.local ([fe80::5cc3:9ab4:f91d:a757]) by
 SRV02.XXX.local ([fe80::5cc3:9ab4:f91d:a757%10]) with mapi; Fri, 31 Dec
 2010 08:36:19 -0500
From: XXX XXX<XXX@XXX.net>
To: XXX XXX<XXX.XXX@XXX.com>
Date: Fri, 31 Dec 2010 08:36:18 -0500
Subject: FW: Computer Setups
Thread-Topic: Computer Setups
Thread-Index: AcunxSr1FvElwMiFRrK3KPlCIfX5twBKeVAA
Message-ID: <AFF867F3ABF9DD4E87D172CAE17747BF0DA5FFA13F@SRV02.XXX.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0



 

Ad feedback |  
 © 2011 Microsoft Terms PrivacyAbout our adsAdvertise Help Center FeedbackEnglish
 
 {0}
 Manage folders
Add a new folder
Manage rulesGet email from another account
Send automated vacation repliesAdd friends
View all contacts
Manage categoriesThis message is too wide to fit your screen. Show full message

Mark as read
Mark as unread
Delete
Junk
Not junk
Move
View message source
Send email
Find email
Move all from...
Delete all from...Inbox
Calendar
Contacts
Send emailRecent documents
Your documents
Your groups
 New Word document
 New Excel workbook
 New PowerPoint presentation
 New OneNote notebookRecent photos
Your albums
Photos of you
Share photos
Home
Autos
Games
Money
Movies
Music
News
Sports
Weather


ContactsProfileAdd friends
{0}{2}
 {0}
 {0}
 {0}{0}{2}
Did you run the Telnet commands to see if the servers can communicate via SMTP? It appears from the message there is an issue with this or with the SMTP Queue settings. It could be something as simple as your ISP blocking port 25, this will not allow you to sent mail normally, without changing the SMTP port. If this is the case you have 2 options,
1 - call the ISP and request that they remove the block on port 25.
2 - change the Port for SMTP in the SBS config under Exchange Config.. If you need help with this let me know.

If you verify that it's not an ISP block, which is super common, it may work bettwe if you use a smarthost to sent e-mail, this will aleviate the need to setup a reverse DNS entry with your ISP for your IP, they wont do this for DHCP addresses.

It could also be a setting on your reuter, if it's been setup to block port 25 so users cant sent mail from a zombie server. If this is the case you'll need to get into the router and remove the block for the Server IP.
The IT consulting group came back and said it was a DNS issue, they had used DNS 4.2.2.2 and that server was blocking email from leaving exchange and sending to the godaddy servers, so they changed the dns to a time warner server and email is flowing....

I believe it is quite strange 4.2.2.2 is a common server because it is easy to remembered, i use it on everything, and for 4.2.2.2 to not work i think there is another issue or was atleast...

Thank you all for responding, sorry for the delayed response, been out of the office

Not sure if you suggestion worked ClintSweeny, I passed it on to the IT Consulting group, and about 15 mins later everything started working but they came back with this solution. I believe your solution had something to do with it...Thanks