EMWAC Internet Mail Services Frequently Asked Questions

 

Mail to local users is not being delivered

This may occur if the domain name being used for local mail is not known to SMTPDS. For instance if you send mail to user@abc.com, expecting it to be delivered to user on the Windows NT machine running IMS, called say mail.abc.com, then you may encounter problems. The way round this is to put abc.com in the Accept Mail For: list in the Misc configuration page.

POP3S says LogonUserA could not be located

If you try to run POP3S.EXE on a NT 3.50, an error message says "The procedure entry point LogonUserA could not be located in the dynamic link library ADVAPI32.dll".

The EMWAC IMS POP3S.EXE (all versions) uses NT 3.51 security features for user and password validation. Therefore, you have to use NT 3.51 for the POP3S service.

NT 3.51 is required to run the EMWAC IMS.

Logon Failure[1385]

If you received "Logon failure[1385]" from your POP3S, the user does not have "Log on as batch job" right. You should assign this right for any IMS POP3S users on NT Workstation or Server. See step 12 in the Installing section of Obtaining and installing the software.

Please note the right should be assigned against NT Computer name.

Logon Failure[1907]

If you received "Logon failure[1907]" for a user from your POP3S, the user must change his password before he logs on the first time. This is determined by NT User Manager where you can specify the user should change his password before he logs on. Alternatively the user can use NT Ctrl-Alt-Del to change his password on the NT.

Cannot determine IP address

If you received "Cannot deteermine this computer's IP address" by "-IPADDRESS" option for any IMS service, you can fix this by reconfigure your TCP/IP protocol with hostname and domain name. You can configure TCP/IP protocol by Control Panel->Network->TCP/IP Protocol->Configure, see more information from NT document if need. Your host name and domain should exist in the DNS dialog by Control Panel->Network->TCP/IP Protocol->Configure->DNS. If host name and domain name are not found, please enter your correct host name and domain in the dialog.

Error 2140

Could not start the service name service on \\yourmachine.
Error 2140: An internal Windows NT error occurred.

This usually means a problem with the initialisation of the service. Further information detailing the precise problem will be recorded in the Application Event Log - see the Error Logging page for details on how to view this information.

Error 2186

Could not start the service name service on \\yourmachine.
Error 2186: The service is not responding to the control function.

The problem is that the service is asking the DNS for information during startup, and if the DNS takes a while to respond, then the Service Control Manager gets tired of waiting and shows an error.

Troubleshooting using Telnet session

If your POP3 client give you a funny error message, you had better run a telnet session to get the exact responses from your POP3 server.

Try to run following commands in the Command Prompt:

  1. telnet your_machine 110
  2. USER your_username
  3. PASS your_password
  4. RETR 1
  5. QUIT Where after the telnet command, you type the rest commands in the Telnet window. It is also assumed that you have at least one message in the mail inbox otherwise you can skip the "RETR 1" command.

    You can run a telnet session from a UNIX host or any other telnet client.

    Problem with large message retrieve

    If your POP3 clients give some error messages during downloading some large messages and the IMS POP3 server is still running after the messages, it is mostly the problem of your POP3 client.

    You can validate this by a Troubleshooting using Telnet session. You can leave only the problematic message in your mail inbox and you should be able to see the whole message in your screen after the "RETR 1" command and the QUIT command should also finish with "+OK".

    Socket I/O Error 64

    During normal operation of the POP3S service, if the POP3 Log check box in the Log page of EMWAC Control Applet is checked, an error or warining message in version 0.60 or in 0.70 or later may be logged into the POP3 log file very often. One of possible scenario causes this log message is that a POP3 client close the POP3 connection to the POP3 server first and the POP3S logged this. For example, Eduora will check new messages in a mailbox regularly. If no new message, Eduora will close the POP3 connection first.

    It is quite common and the log message should be considered as a normal behaviour of the POP3S operation in this scenario

    I have assigned "Log on as a batch job" but got Logon Failure[1385] again

    If you receive "Logon failure[1385]" again after you have assigned "Log on as batch job" right, you have not assigned the right properly. And it is almost 100% sure that you are running IMS on an NT Server.

    If IMS is running on an NT Server, you need assigned the right against the local NT Server not the local NT domain. For example, if your NT Server is called "PCNTSVR1" and your NT domain name is "NTDOMAIN1", you need bring up User Manager for Domain: Run "Select Domain" command in User menu, enter "\\PCNTSVR1" and press OK, then assign the right. See step 12 for the same instruction in the Installing section of Obtaining and installing the software.

    SMTPDS Delivery Delays...

    There is a registry entry for SMTPDS for the timeout (interval) for how often it should check the directories. When you use the filter, you can shorten this delay so that when the mail shows up in INCOMING it is delivered more quickly.

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMTPDS\Parameters

    Value under this key:
    Timeout (REG_DWORD)
    Time in seconds, default=120 seconds.

    Created this value (if it doesn't exist by default) and set it to 15.

    --------------------------------------------------------------------------------

    Windows 2000 Fix to install IMS

    To install IMS under Windows 2000, the following registry entry must be added since it appears to no longer be used :
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Domain
    type REG_SZ
    value yourdomain.com

    Windows 2000 Fix to allow SMTPDS to deliver mail

    In addition, it appears that W2K no longer fills in the Nameserver registry parameter :
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Nameserver
    type REG_SZ
    value(s) nameserver IP addresses.
    If this parameter is blank, it will cause IMS to fail to deliver messages. They will sit in the holding directory.