Dualog Business Mail - Outlook IMAP Logging

INTRODUCTION

Sometimes, external third-party email clients are unable to parse some messages and may return a memory buffer exception warning. It is possible to log the interaction between mail clients and the Dualog IMAP server on board the ship to identify the issue.

IMAP STORAGE SERVER ISSUES AND MIME
One or more messages have been incorrectly MIME-parsed during insertion, or the source file stored on disk has been modified after parsing. When a message is inserted, the IMAP service parses its MIME structure and records all message body parts - including the start and end byte index within the source file. This information is stored in the IMAPBODYPART database table.
The Outlook error "Exception: Invalid end position. Outside of memory buffer allocated for mail" indicates that a stored end byte index exceeds the actual size of the source file.

OUTLOOK SYNC ISSUES
Enabling protocol logging will ensure that the IMAP logfiles in the Dualog environment are more verbose, and give us more insight into what a third-party client is doing, or requesting of our IMAP service. Enabling this elevated logging will assist us in troubleshooting common Outlook-related errors.

HOW TO ENABLE IMAP COMMAND/PROTOCOL LOGGING

In order to pinpoint the message(s) that are causing this error, it is possible to enable command logging for IMAP.

• Open the registry (regedit) in Windows.
• Access Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\DUALOG\ImapServer
• Click with the right mouse button on the right-hand pane of the registry window
• Select New -> String Value
• Call the string "LogProtocol" (without quotation marks) and hit enter
• Double-click on the newly created string, and when prompted for a value, type "True" (without quotation marks) and click on OK.
• Restart the Dualog IMAP Server services under services.msc.
• In the future, to disable this, simply change the value to "False".

The new log entries will be integrated into the DualogImapServer logfile within the LogDir folder on the main Connection Suite install folder.

Note: We recommend disabling protocol logging after troubleshooting has concluded. Verbose logging can occupy significant hard drive space.