I think I may have it solved :) After spending two hours on the phone with MS it came down to a trailing period on my DNS name. Apparently some recipients are particular about correct DNS suffixes. Make sure that you have a correct and valid name setting as your DNS suffix on your exchange server box (such as domainname.com set in system properties, network identification). Our was domainname.com. and it caused some EHLO and HELO errors in the logs. If you want to see if this is the problem, just set your SMTP protocol logging to maximum and search the log files for EHLO and HELO errors (501 and 511 I think). Hope this helps Martin -----Original Message----- From: Scott Overfield [mailto:soverfield@xxxxxxxxxx] Sent: Thursday, February 21, 2002 10:20 AM To: [ExchangeList] Subject: [exchangelist] Re: Outbound messages stuck in IMS http://www.MSExchange.org/ I have the same problem with 2 domains.....started when I applied exchange service pack 4......at first I thought it was a dns problem, but nslookup is returning the correct mx record for the domains I can't send mail to...I finally gave up and am relaying all emails destined for those domain through my ISP....anyone find a solution to this? -----Original Message----- From: alex_castanheira@xxxxxxxxxxx [mailto:alex_castanheira@xxxxxxxxxxx] Sent: Wednesday, February 20, 2002 4:32 PM To: [ExchangeList] Subject: [exchangelist] Re: Outbound messages stuck in IMS http://www.MSExchange.org/ ªI have exactly the same problem running Exchange 5.5 in a NT4 server. I have done the same things you did and still the same. Any help out there? ------------------------------------------------------ You are currently subscribed to this MSExchange.org Discussion List as: soverfield@xxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ You are currently subscribed to this MSExchange.org Discussion List as: martin.buschbeck@xxxxxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')