XADM: An Exchange 2000 POP3 Environment's Front-End and Back-End Server Logging Levels Are Different

Article translations Article translations
Article ID: 307330 - View products that this article applies to.
This article was previously published under Q307330
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

If you configure an Exchange 2000 environment to use Post Office Protocol version 3 (POP3), and then configure front-end and back-end servers, the logging levels may differ. To configure logging for POP3, on both the front-end and back-end servers, you need to change the POP3 Protocol Log Level value to 4 under the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\POP3Svc\Parameters
On the front-end server, the log file with level 4 logging (L00000001.log) may contain detailed information that includes mail message content. However, on the back-end server, the log file with level 4 logging does not contain any message content.

This discrepancy may cause problems if you have custom applications that use the POP3 protocol logs for example billing or user tracking. The same information should be logged on both front-end and back-end servers if those servers' POP3 Protocol Log Level values are configured identically.

CAUSE

This problem can occur because the logging levels for the front-end server are incorrect, so that the level 4 logging set on a front-end server actually logs at level 5.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:

Component: POP3

Collapse this tableExpand this table
File nameVersion
Pop3svc.dll 6.0.4720.79
Pop3fe.dll6.0.4720.79

NOTE: Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.

Properties

Article ID: 307330 - Last Review: October 24, 2013 - Revision: 1.3
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbexchange2000presp2fix kbexchange2000sp2fix kbfix KB307330

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com