MailEnable Enterprise Guide
In This Topic
    Troubleshooting SMTP connectivity issues & analyzing log files
    In This Topic

    1.1.1              Troubleshooting SMTP connectivity issues & analyzing log files

    MailEnable provides extensive logging of SMTP activity. There are three log files that are used by MailEnable. These are the debug, activity and W3C logs. The W3C log files are essentially a replica of the activity log, hence it is only required to investigate the activity and debug logs.

    The debug log contains "wordy" explanations of significant actions undertaken by MailEnable. For example, when a user attempts to relay a mail message, this is recorded and time-stamped in the SMTP Debug log.

    The activity log file contains a transcript of all SMTP commands exchanged between MailEnable and other remote clients or mail servers.

    The simplest way to find a message and debug a SMTP transaction is to open the SMTP Activity log in Notepad and search it. You can also load the log file into Microsoft Excel as follows:                              How to import the activity log into Microsoft Excel

    1.       File|Open Browse to C:\Program Files\Mail Enable\Logging\SMTP (or equivalent directory).

    2.       Change the Files of Type combo to All Files (*.*)

    3.       Select the activity file to open (the files are named as SMTP-Activity-YYMMDD).

    4.       Excels Text Import Wizard will now be displayed. Select the option to import the text as Delimited data and click Next

    5.       Select the format as Tab delimited and click next

    6.       Click Finish to import the data

    A worksheet will be displayed with data represented as follows:

    A=Transaction date and time

    B=Transaction Type (Inbound or Outbound)

    C=Message ID/Message filename (This is used to match with other logs to track messages)

    D=Internal socket number that the SMTP transaction was occurring on

    E=TCP/IP Address of the remote host involved in the SMTP transaction

    F=The name of SMTP Command that relates to the transaction

    G=The details for the SMTP command that relates to the current transaction

    H=The details for the response to the SMTP command that relates to the current transaction

    I=The number of bytes sent when executing this command

    J=The number of bytes received in executing this command

    There are two important types of transactions outlined in the SMTP Activity log file. These are SMTP Inbound Transactions and SMTP Outbound Transactions. These transactions are denoted in the log files as SMTP-IN and SMTP-OU in their respective lines in the Activity log file.                              How to relate activity log entries to the debug log file

    The most obvious way of relating an entry in the activity log file to the Debug log file is via the time stamp recorded in the file. The message ID can also be used (as this is often recorded in the debug log file). The message ID is also useful in tracking messages as they pass through the MTA. The MTA logs this message ID and therefore you can use the logs to track a message as it is routed through MailEnable's Connectors via the MTA.

    For example, a user may complain that they cannot send mail from Outlook. In this case an error message will be reported back to the remote mail client.

    e.g.: 503 This mail server requires authentication. Please check your mail client settings.

    Use this error string to locate the transaction sequence in the SMTP Activity log. Once the entry has been found in the SMTP Activity log, then check the SMTP Debug log for the same time period. The log will have recorded the reason why the relay request was denied.

    1.2                  Antivirus configuration