MailNews:Logging
The MailNews logging mechanism is activated by setting two environment variables before running a MailNews application.
Logging options within MailNews
The following modules/protocols may be logged within MailNews applications (SeaMonkey/Thunderbird) in both debug and release builds:
- mime
- imap
- nntp
- smtp
- pop3
- ldap
The following modules may or may not be available in release builds, but are available in debug builds:
- imapoffline
- bayesianfilter
- msgcompose
- mapi
- nsaboutlookcardlog
- nsabwinhelperlog
- ldapautocomplete
- nswabaddressbook
- nsaboutlookdirectorylog
- movemail
- msgbiff
- msgpurge
- appleimportlog
- import
Environment Variables to set
Two environment variables should set:
- NSPR_LOG_MODULES - Module name and level separated by colon
- Example: "ldap:5;smtp:3"
- NSPR_LOG_FILE - Path to the log file
- If NSPR_LOG_FILE is not set, then the output will be logged to the console where the application was launched.
On all platforms, the log is written over every time you re-launch the mozilla application.
Logging level
The number in the NSPR_LOG_MODULES example above specifies the level of logging to be used. A lower number reduces the amount of information that is logged to the file:
- PR_LOG_NONE = 0, /* nothing */
- PR_LOG_ALWAYS = 1, /* always printed */
- PR_LOG_ERROR = 2, /* error messages */
- PR_LOG_WARNING = 3, /* warning messages */
- PR_LOG_DEBUG = 4, /* debug messages */
Some modules may not work exactly according to the log levels noted above.
Specifying Environment Variables to Thunderbird/SeaMonkey
TODO (Migrate).
See MailNews troubleshooting for details.