RE: 7010 Events
- From: v-stezhu@xxxxxxxxxxxxxxxxxxxx (Steven Zhu [MSFT])
- Date: Wed, 05 Jul 2006 05:55:45 GMT
Hi Steve,
Thanks for posting here.
From your post, my understanding on this issue is: you receive the Even7010 every day. If I am off base, please feel free to let me know.
Based on my research, this applies to Exchange 2003 and Exchange 2000 SP4.
XEXCH50 is an Exchange specific extended command that should only be issued
between Exchange machines in the same Org. Basically, you can ignore this
event log.
To avoid this event log, you may set the diagnostic logging to none. To
achieve this, perform the following steps:
1> On the Exchange server 2000, open Exchange System Manager.
2> Expand Servers, right click on the servername, and click properties.
3> On the Diagnostic Logging tab, highlight MSEchangeTransport. In the
right pane, set all items to None.
Additional, There''s a work around that I know of that may turn off the
outbound XEXCH50. Though, bear in mind the steps that I will provide below
are unsupported and there are no public docs that references this. This may
or may not resolve the problem but I hope it does.
Method 1: Configure the XEXCH50 Registry Subkey
-----------------------------------------------
In Exchange Server 2003 and Exchange Server 2000 Service Pack 3 (SP3), you
can suppress the sending of the XEXCH50 command to external domains. To do
so, follow these steps.
WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using
Registry Editor incorrectly. Use Registry Editor at your own risk.
1. Click "Start", click "Run", type "regedit" (without the quotation marks)
in the "Open" box, and then click "OK".
2. Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMTPSVC\XEXCH50No te
If the XEXCH50 registry subkey is not present, create it. To do this, point
to
"New" on the "Edit" menu, and then click
"Key". In the "New Key #1" box, type
"XEXCH50" (without the quotation marks), and then press ENTER.
3. Right-click "XEXCH50", point to "New", and then click "DWORD Value".
4. In the "New Value #1" box, type "SuppressExternal" (without the
quotation marks), and then press ENTER.
5. Right-click "SuppressExternal", and then click "Modify".
6. In the "Value data" box, type "1" (without the quotation marks), and
then click "OK".
7. Quit Registry Editor.
Method 2: Configure the SMTP Connector
--------------------------------------
Configure the SMTP connector properties to use the HELO command instead of
the EHLO command. When Exchange Server sends the HELO command, it does not
receive the list of commands that the remote server supports, and reverts
to simple SMTP commands. None of the extended SMTP command verbs are used.
To configure the SMTP connector, follow these steps:
1. Start the Exchange System Manager utility.
2. If Administrative Groups are turned on, expand "Administrative
Groups", and then expand "First Administrative Group".
3. Expand "Connectors", right-click the SMTP connector that you use to
connect to the remote domain, and then click "Properties".
4. Click the "Advanced" tab, click to select the "Send HELO instead of
EHLO" check box, click "Apply", and then click "OK".
Hope the information helps.
Have a nice day.
Best Regards,
Steven Zhu
MCSE
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD were
updated on February 14, 2006.? Please complete a re-registration process
by entering the secure code mmpng06 when prompted. Once you have
entered the secure code mmpng06, you will be able to update your profile
and access the partner newsgroups.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
.
- Follow-Ups:
- Re: 7010 Events
- From: spm
- Re: 7010 Events
- References:
- 7010 Events
- From: spm
- 7010 Events
- Prev by Date: Re: THREE group companies on SBS Box - BEST way to set up?
- Next by Date: Re: THREE group companies on SBS Box - BEST way to set up?
- Previous by thread: 7010 Events
- Next by thread: Re: 7010 Events
- Index(es):
Relevant Pages
|
