Exchange 2003, Delivery to the following recipients has been delayed.
The bounce back is in the message below.
This started happening after I reconfigured the network on the server using the Broadcom utility. It was using a single NIC before, and I created a team using both adapters. I then reconfigured the virtual NIC for the team to have the same TCPIP settings as the server had previously.
So esentially, to the OS, i changed the network adapter.
This started happening after I reconfigured the network on the server using the Broadcom utility. It was using a single NIC before, and I created a team using both adapters. I then reconfigured the virtual NIC for the team to have the same TCPIP settings as the server had previously.
So esentially, to the OS, i changed the network adapter.
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.
my@email.com
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ping means nothing.
The only test is to telnet to port 25 of the MX record host.
Pinging gmail.com doesn't prove anything.
You need to find the MX record host for that domain, then attempt to telnet to port 25 of that host.
Simon.
The only test is to telnet to port 25 of the MX record host.
Pinging gmail.com doesn't prove anything.
You need to find the MX record host for that domain, then attempt to telnet to port 25 of that host.
Simon.
ASKER
Solved.
The issue was that haviing the two IP's on one "team" interface caused either IP to be used to send mail.
Our firewall was configure to only allow one of those IP's to send mail. Choosing the correct IP as opposed to "All Unassigned" for the SMTP virtual server as Mestha suggested allowed queued emails to go out, but had the side effect of sometimes not being able to send new emails (Outlook would sometimes be trying to acce).
Points awarded for steering me in the right direction with that setting. Setting the setting to the one IP address showed me that it was a problem with exchange sometimes using the other address.
I would argue that a successful ping DOES mean something, it does mean that the computer is able to resolve the hostname and that there is a route to the target machine. I do realize that an unsuccessful ping does not necessarily mean anything, as the target machine could be blocking ping requests.
The issue was that haviing the two IP's on one "team" interface caused either IP to be used to send mail.
Our firewall was configure to only allow one of those IP's to send mail. Choosing the correct IP as opposed to "All Unassigned" for the SMTP virtual server as Mestha suggested allowed queued emails to go out, but had the side effect of sometimes not being able to send new emails (Outlook would sometimes be trying to acce).
Points awarded for steering me in the right direction with that setting. Setting the setting to the one IP address showed me that it was a problem with exchange sometimes using the other address.
I would argue that a successful ping DOES mean something, it does mean that the computer is able to resolve the hostname and that there is a route to the target machine. I do realize that an unsuccessful ping does not necessarily mean anything, as the target machine could be blocking ping requests.
ASKER
Thanks for the help, modifying this setting helped me find the cause of the issue.
"The issue was that haviing the two IP's on one "team" interface caused either IP to be used to send mail."
solved for me too, thanks
solved for me too, thanks
ASKER
The remote server did not respond to a connection attempt.
I can ping the various servers listed though (the ones that respond to ping requests anyways). For example, i tried sending an email to a gmail address, and it said the remote server did not respond to the connection attempt, however, from the same server I can ping gmail.com
I verified that it is using "All Unassigned" and restarted the SMTP server (even then tried rebooting the entire server). Still had the same problem.
I removed the team, causing both ethernet adapters to revert back to their original state, and all queued emails went out. I am going to leave it as is for now, but will eventually want to have these adapters teamed.
Any ideas?