Re: Exchange 2003 SMTP Timeouts when sending to Security/Distribution Groups

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Al Mulnick (amulnick_No_SPAM_at_ncDOTrr.com)
Date: 05/27/04 

Date: Wed, 26 May 2004 22:33:25 -0400

Have you checked to see what Symantec and iHateSpam are doing in the
situation?
I assume both are in the stack right? Why couldn't they be part of the
issue? I assume they are both updated for 2003, but..

Al

"Dan Lehman" <del3@psu.edu> wrote in message
news:400697e2.0405260851.510e457a@posting.google.com...
> Our setup:
> -Windows Server 2003 domain-wide
> -Exchange Server 2003 on a member server
> -Symantec Mail Security 4.5 and Sunbelt iHateSpam installed along with
> Exchange
>
> Within our Active Directory we have a number of mail-enabled Security
> Groups that we use to announce server maintenance, shutdowns and
> outages. Most of our users have Exchange accounts, but some use other
> e-mail accounts outside of our domain (but still within the
> University). Since upgrading from Exchange 2000, the members of these
> groups outside of Exchange no longer receive messages. What I get
> instead is a 4.4.7 NDR.
>
> What I have done so far to troubleshoot:
> -Sent messages to the individual accounts - messages received no
> problem.
> -Removed and then recreated the e-mail account for the Security Group.
> -Constructed new Global and Universal Security and Distribution Groups
> to test on known working accounts outside our domain.
> -Tested various recipient domains to remove the possibility of the
> problem being with one recipient's domain.
> -Verified the MX and PTR records in case the receiving domains are
> performing RDNS.
>
> I've also watched the SMTP log files. Essentially, our server
> communicates with the receiving server, issues the recipient lists,
> and then hangs. The last transmission is the receiving server's 354
> telling my server to go ahead and send the data. After a number of
> minutes the log displays a 451 timeout, and after a number of retry
> attempts I receive a 4.4.7 NDR.
>
> Now, watching the logs and sending directly to a member (or multiple
> members) of the Security Group I see the recipient list, the receiving
> server's 354 response followed almost immediately with a 250 and,
> depending on the receiving server, a "Message accepted" statement.
>
> Thoughts?

Relevant Pages

  • Re: Setup problem with SenderID and OWA
    ... Both the Sending and Receiving Mail servers are Exchange 2003 with SP2. ... Exchange server and watch the exact data being sent. ...
    (microsoft.public.exchange.admin)
  • Re: Setup problem with SenderID and OWA
    ... >Both the Sending and Receiving Mail servers are Exchange 2003 with SP2. ... >Only one Received from header was in the SMTP DATA Portion. ... >Exchange server and watch the exact data being sent. ...
    (microsoft.public.exchange.admin)
  • Re: 2 users not receiving mail
    ... Should cached exchange be enabled for clients? ... My customers server is SBS Standard and has ... Hard Drives and memory, that is the only thing that has ever needed ... had a user that was not receiving mail and another user that was ...
    (microsoft.public.windows.server.sbs)
  • Am I relaying emails??
    ... Exchange server is configured not to relay. ... If you ARE having difficulty sending and receiving mail ... connection to fail. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange Disaster Recovery Server
    ... The backup server is setup also in the lab so I ... >>> The Microsoft Exchange Server computer is not available. ... >>> Microsoft Exchange Server Information Store ...
    (microsoft.public.exchange2000.admin)