Version 1 (modified by Cyrus Daboo, 11 years ago) (diff)


Protocol Logging

For diagnostic purposes, Mulberry is able to log data sent between itself and a server, as well as log specific actions that it executes itself. The logs that can be created are:

  • IMAP - logs IMAP network connections
  • POP3 - logs POP3 network connections
  • SMTP - logs SMTP network connections
  • IMSP - logs IMSP network connections
  • ACAP - logs ACAP network connections
  • HTTP - logs HTTP network connections
  • Show Authentication Details - by default authentication protocol is not in the logs (i.e. no passwords shown), turn this on to show authentication
  • Disconnected Playback - logs actions that are executed when playing back disconnected operations when synchronizing with the network server
  • Plugins - logs errors and status from certain plugins
  • Filtering - logs filtering/rules actions that are executed when filtering/ManageSIEVE network connections
  • Errors - logs internal exceptions

By default Mulberry does not log the authentication transaction that takes place on the network connections for security reasons, but does log all other in formation. Logging of authentication details can be turned on as an option, but may expose passwords in the log file.

To turn logging on, hold down the option (Mac OS), alt (Win32) or control (Unix) keys on the keyboard and select the Preferences menu item from the main menu. The resulting dialog allows you to turn on or off logging for each of the above. For security reasons, when logging is on for at least one type of log, Mulberry will display a warning when it is started up to indicate that data is being collected and stored on the local disk.

When logging is on, Mulberry writes the log data to files stored in a Logs directory in the Mulberry application directory (Mac OS & Win32), or the ~/.mulberry directory (Unix). The log files have names corresponding to the type of logging being done. Disconnected playback logs are stored in the Disconnected directory under each account used for disconnected operations.

The network connection log files are erased and started afresh on each restart of Mulberry if the overwrite on startup option is on.

NB When logging is turned on, Mulberry's performance will decrease slightly due to the overhead of logging. You are advised not to use it unless instructed by Cyrusoft support, for diagnostic purposes.