XFOR: Dequeing SMTP Mail Outside of Dialup Connections

ID: Q175494


The information in this article applies to:
  • Microsoft Exchange Server, versions 5.0, 5.5

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

Microsoft Exchange Server has the ability to send a command or ETRN (with version 5.0 Service Pack 1) to another host to prompt that host to send any messages waiting for the specified domain (also known as "dequeuing").

However, by default, this functionality is limited to only dial-up connections.

If this functionality is required outside of the dial-up connections of the Internet Mail Service (like in the case of Dial-up or Dial-on-demand routers), you must use some method to send this command manually, either through a batch file or the use of a third-party dequeing application.


WORKAROUND

Create a batch file to run on Windows NT AT Command Scheduler (available in the Windows NT Resource Kit) or other third-party scheduling application. The following are example batch files:

Example 1: (assumes Internet Mail Service is always running)


PING <other_hosts_ip_address> ---> makes the dialup router initiate its connection
PING <other_hosts_ip_address> ---> verify connection
FINGER My.DomainA.Com@ISP.Host.DomainB.Com ---> to dequeue 
Example 2: (assumes Internet Mail Service is always running)

PING <other_hosts_ip_address> ---> makes the dialup router initiate its connection
PING <other_hosts_ip_address> ---> verify connection
<Retrieval Program> ---> third-party program that dequeues mail 
Example 3: (assumes Internet Mail Service is NOT running)

PING <other_hosts_ip_address> ---> makes the dialup router initiate its connection
PING <other_hosts_ip_address> ---> verify connection
NET START MSExchangeIMC ---> starts the Internet Mail Service
<Retrieval Method: command or executable>
NET STOP MSExchangeIMC ---> stops the Internet Mail Service 
Also, if the ability to use ETRN is needed outside of dial-up connections, there is another workaround available. The ETRN command can be configured to be sent to all hosts the Internet Mail Service connects to. To do so, use the following steps.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).
  1. Start Registry Editor (Regedt32.exe).


  2. Locate the following key in the registry:
    
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIMC
    \Parameters 
    NOTE: The above registry key is one path; it has been wrapped for readability.


  3. On the Edit menu, click Add Value, and then add the following registry value:


  4. Value Name: AlwaysUseETRN
    Data Type: REG_DWORD
    Value: 0x1
  5. Quit Registry Editor.


Setting this entry tells the Internet Mail Service to send the ETRN command to any ESMTP hosts it connects to (that advertise they support ETRN). This will use any domains listed on the routing table configured with the Internet Mail Service.

NOTE: It is recommended that this entry be used only when forwarding messages to a single host. This is due to the added time it takes to send and wait for a response to the ETRN command.

Additional query words: DEQUEUE ETRN RETRIEVAL

Keywords :
Version : winnt:5.0,5.5
Platform : winnt
Issue type : kbprb


Last Reviewed: June 15, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.