chaok
asked on
Mail being delayed and droped by exchange server
I am running Exchange SBS 2000. My users are having problems sending to and recieving emails from a specific domain.
We first get a message from the Exchange server saying:
--------------------------
This is an automatically generated Delivery Status Notification.
THIS IS A WARNING MESSAGE ONLY.
YOU DO NOT NEED TO RESEND YOUR MESSAGE.
Delivery to the following recipients has been delayed.
--------------------------
A little bit later we then recieve a message saying:
--------------------------
The following recipient(s) could not be reached:
user@problemdomain.com on 08/13/2004 9:33 AM
Could not deliver the message in the time limit specified. Please retry or contact your administrator.
<ourserver.Local.ourdomain
--------------------------
Any help would be appricated. I have tried everything I could think of, but nothing seems to work. I'm no expert with Exchange so you don't need worrie about treating me like I don't know anything, or asking me if I've tried some routine things because I probally haven't.
Let me know if you need any more information, I will be watching for any response with a sharp eye.
We first get a message from the Exchange server saying:
--------------------------
This is an automatically generated Delivery Status Notification.
THIS IS A WARNING MESSAGE ONLY.
YOU DO NOT NEED TO RESEND YOUR MESSAGE.
Delivery to the following recipients has been delayed.
--------------------------
A little bit later we then recieve a message saying:
--------------------------
The following recipient(s) could not be reached:
user@problemdomain.com on 08/13/2004 9:33 AM
Could not deliver the message in the time limit specified. Please retry or contact your administrator.
<ourserver.Local.ourdomain
--------------------------
Any help would be appricated. I have tried everything I could think of, but nothing seems to work. I'm no expert with Exchange so you don't need worrie about treating me like I don't know anything, or asking me if I've tried some routine things because I probally haven't.
Let me know if you need any more information, I will be watching for any response with a sharp eye.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well everything seems to be fine from www.dnsreport.com. I ran their dns report and their email report.
Have you changed anything from the default SMTP settings on the Exchange server?
Your second error I didn't see as you posted it while I was typing. That indicates that there is a problem with the remote server. Verification failure indicates that the remote site is attempting to authenticate for connection - which doesn't happen with SMTP inbound.
Simon.
Your second error I didn't see as you posted it while I was typing. That indicates that there is a problem with the remote server. Verification failure indicates that the remote site is attempting to authenticate for connection - which doesn't happen with SMTP inbound.
Simon.
ASKER
I just wanted to update on my version of exchange. It says Version 6.0 SP3. I belive this is Exchange 2000, please correct me if I am wrong.
I am attempting now to set up an SMTP connector, but have run into a problem. I do not have a First Routing group. Under my Administratove Groups folder, I have Folders, Servers, and Connectors.
Under connectors there is SmallBusiness SMTP connector, and Connector for POP3 Mailboxes. Just though I'd point this out since I did not see this in the picture from http://www.armset.info/exchange/smtp-connector.asp
How can I add a routing group? When I right-click on first Administrative Group, I can create a new System Policies. Not sure if that is what I need to do, but if it is, what do I do from there?
Thanks.
I am attempting now to set up an SMTP connector, but have run into a problem. I do not have a First Routing group. Under my Administratove Groups folder, I have Folders, Servers, and Connectors.
Under connectors there is SmallBusiness SMTP connector, and Connector for POP3 Mailboxes. Just though I'd point this out since I did not see this in the picture from http://www.armset.info/exchange/smtp-connector.asp
How can I add a routing group? When I right-click on first Administrative Group, I can create a new System Policies. Not sure if that is what I need to do, but if it is, what do I do from there?
Thanks.
ASKER
I do not belive anything has been changed from the default SMTP settings, but I am not totally sure because I am relitively new to this organization, and the orignal person who set this up is now gone.
I found how to add a routing group connector now. But by adding this, will it effect our current SMTP connector.
I found how to add a routing group connector now. But by adding this, will it effect our current SMTP connector.
hey
okay right click ur exchnage organization ,the one at the top of the tree in Exchange System manager (ESM)
Then select properties thensee if administrative group and routing group check box are selected.if not select it.
the u can see routing group in ur tree and then right click and add routing groups u want.
Shahnaz
okay right click ur exchnage organization ,the one at the top of the tree in Exchange System manager (ESM)
Then select properties thensee if administrative group and routing group check box are selected.if not select it.
the u can see routing group in ur tree and then right click and add routing groups u want.
Shahnaz
ASKER
Thanks Shahnaz
ASKER
When I get to step 6 on the guide to setting up an SMTP Connector, it brings me to ask a quick question.
Since I already have an SMTP connector, will this effect my current configuration? In my current SMTP connector, everything looks like default settings. In the Address Space tab it has Type - SMTP Address - * and Cost - 1
Since I already have an SMTP connector, will this effect my current configuration? In my current SMTP connector, everything looks like default settings. In the Address Space tab it has Type - SMTP Address - * and Cost - 1
You shouldn't need to change the cost levels unless you get problems. These are used for giving priority to certain messages. Lower cost levels get high precedance.
It shouldn't affect your existing connector - I have a couple of sites with mutiple connectors without any problems.
Simon.
It shouldn't affect your existing connector - I have a couple of sites with mutiple connectors without any problems.
Simon.
ASKER
Cool.
On the connector scope, do I use Entire Organization or Routing group?
I'm know the guide says to leave everything default (entire organization), but I just wanted to make sure I don't mess anything up.
On the connector scope, do I use Entire Organization or Routing group?
I'm know the guide says to leave everything default (entire organization), but I just wanted to make sure I don't mess anything up.
With SBS - leave it as entire org and you will be fine.
Simon.
Simon.
ASKER
Thank for all the fast help. I really appricate it.
Just 1 last check on everything. Here is my setup on my SMTP connectors.
Origanial Defaut connector - Use DNS to route to each address space on this connector
- in address space Type - SMTP Address - * Cost - 1 Entire organization
New Problem Domains - Forward all mail though this connector to the following smart hosts
- in address space Type - SMTP Address - problemdomain.com Cost - 1 Entire Organization
Just 1 last check on everything. Here is my setup on my SMTP connectors.
Origanial Defaut connector - Use DNS to route to each address space on this connector
- in address space Type - SMTP Address - * Cost - 1 Entire organization
New Problem Domains - Forward all mail though this connector to the following smart hosts
- in address space Type - SMTP Address - problemdomain.com Cost - 1 Entire Organization
ASKER
Ok its all set up and working but now I recieve a new error message. I guess this is progress :)
--------------------------
Your message did not reach some or all of the intended recipients.
Subject: Test from Administrator
Sent: 8/16/2004 10:36 AM
The following recipient(s) could not be reached:
'user@problemdomain.com' on 8/16/2004 10:36 AM
The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.
<server.Local.mydomain.com
--------------------------
Could this have something to do with my ISP's SMTP server. I'm not sure if it requires you to send your username and password or not.
When I recieved this message, it was right after I hit the send button, there was no delay.
--------------------------
Your message did not reach some or all of the intended recipients.
Subject: Test from Administrator
Sent: 8/16/2004 10:36 AM
The following recipient(s) could not be reached:
'user@problemdomain.com' on 8/16/2004 10:36 AM
The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.
<server.Local.mydomain.com
--------------------------
Could this have something to do with my ISP's SMTP server. I'm not sure if it requires you to send your username and password or not.
When I recieved this message, it was right after I hit the send button, there was no delay.
Looks like you have looped back on yourself or your ISP has rejected the message. Ask your ISP if they need to adjust something on their servers to allow your domain to relay through their servers. Sometimes they need to add your domain to their list.
Was "server.Local.mydomain.com
Simon.
Was "server.Local.mydomain.com
Simon.
ASKER
"server.Local.mydomain.com
Delivery to the following recipients has been delayed
ASKER
I have another coworker that is not able to send emails to a contact of his. He recieves this message.
--------------------------
Your message did not reach some or all of the intended recipients.
Subject: RE: Boston Fire
Sent: 8/13/2004 10:02 AM
The following recipient(s) could not be reached:
contact@anotherdomain.com on 8/13/2004 10:02 AM
There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.
<ourserver.Local.ourdomain
--------------------------
I havn't heard back from him wether he is able to email other users with this domain.