IIS and SMTP - Message fails to one domain

This is Interesting: Free IT Magazines  
Home > Archive > IIS and SMTP > July 2006 > Message fails to one domain





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Message fails to one domain
John Cabot

2006-07-12, 1:21 pm

Hi - I'm running Exchanger Server 2000 and I'm having problems sending to a
particular domain. All other messages in the smtp queue are delivered as
expected. The messages comes back to the client stating that message sent to
xyz.com is delayed. After several more attempts the message returns to the
client as undeliverable. This is the only message and domain that we can't
seem to send to. I've contacted the xyz.com domain and they informed me that
the message is not reaching thier mail server. It almost appears that there
is a setting on my exchange server that is blocking access to this domain.
I'm pretty sure that we only have filters blocking incoming domains. I
couldn't find any ip or domain blocked at the smtp level. Any ideas?
Jeff Cochran

2006-07-14, 7:24 am

On Wed, 12 Jul 2006 09:19:02 -0700, John Cabot
<JohnCabot@discussions.microsoft.com> wrote:

>Hi - I'm running Exchanger Server 2000 and I'm having problems sending to a
>particular domain. All other messages in the smtp queue are delivered as
>expected. The messages comes back to the client stating that message sent to
>xyz.com is delayed. After several more attempts the message returns to the
>client as undeliverable. This is the only message and domain that we can't
>seem to send to. I've contacted the xyz.com domain and they informed me that
>the message is not reaching thier mail server. It almost appears that there
>is a setting on my exchange server that is blocking access to this domain.
>I'm pretty sure that we only have filters blocking incoming domains. I
>couldn't find any ip or domain blocked at the smtp level. Any ideas?


Log files would help you track this down. Testing network
connectivity to the destination server and name resolution for the MX
record for that domain would be logical next moves.

Jeff
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com