Re: Exchange 2003 SMTP Timeouts when sending to Security/Distribution Groups
From: Dan Lehman (del3_at_psu.edu)
Date: 05/27/04
- Next message: dlbrum: "Re: NSPI not available on DC/GC after reboot"
- Previous message: Lee Derbyshire: "Re: OWA and Exchange 5.5"
- In reply to: Al Mulnick: "Re: Exchange 2003 SMTP Timeouts when sending to Security/Distribution Groups"
- Next in thread: Dan Lehman: "Exchange 2003 SMTP Timeouts when sending to Security/Distribution Groups"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 27 May 2004 06:49:00 -0700
They very well may be part of the issue, although as this
seems to be a not so uncommon configuration, I would have
expected to find some reference to these programs causing
problems. Futhermore, it seems strange to me that the
only problem we have is with Security or Distribution
Groups - meaning we can send all other messages without
problem, including messages that are addressed to the
members of the groups (i.e., not sent to the groups, but
the list of members).
-Dan
>-----Original Message-----
>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?
>
>
>.
>
- Next message: dlbrum: "Re: NSPI not available on DC/GC after reboot"
- Previous message: Lee Derbyshire: "Re: OWA and Exchange 5.5"
- In reply to: Al Mulnick: "Re: Exchange 2003 SMTP Timeouts when sending to Security/Distribution Groups"
- Next in thread: Dan Lehman: "Exchange 2003 SMTP Timeouts when sending to Security/Distribution Groups"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
