canmove, Confirmed users
2,188
edits
MailNews:Logging: Difference between revisions
Jump to navigation
Jump to search
m
tweaks
(Great reorg step 2 (mainly combine the two Thunderbird lists)) |
m (tweaks) |
||
| Line 67: | Line 67: | ||
# CMS (for S/MIME) | # CMS (for S/MIME) | ||
# Filters | # Filters | ||
# IMAP | # IMAP | ||
# IMAP_CS (for CONDSTORE) | # IMAP_CS (for CONDSTORE) | ||
# IMAP_KW (for keyword (tag) processing) | # IMAP_KW (for keyword (tag) processing) | ||
| Line 103: | Line 103: | ||
'''NOTE - do not use this section for ldap, nntp, pop3 and smtp. They are configured per [[MailNews:Logging#Thunderbird_logging|Thunderbird logging]]. | '''NOTE - do not use this section for ldap, nntp, pop3 and smtp. They are configured per [[MailNews:Logging#Thunderbird_logging|Thunderbird logging]]. | ||
Two variables must be set. (Except for logging of ldap, nntp, pop3 and smtp, which are configured in Thunderbird settings and log to the Error Console - per instructions above. So you may ignore this section and the next for these protocols.) You can set these variables globally as system environment variables (find instructions for your OS), or as local environment variables in a batch file/script (described [[MailNews:Logging# | Two variables must be set. (Except for logging of ldap, nntp, pop3 and smtp, which are configured in Thunderbird settings and log to the Error Console - per instructions above. So you may ignore this section and the next for these protocols.) You can set these variables globally as system environment variables (find instructions for your OS), or as local environment variables in a batch file/script (described [[MailNews:Logging#Generating_a_Gecko_Log|below]]), or just on the command line. | ||
# '''MOZ_LOG''' - '''CASE SENSITIVE''' module name and [[MailNews:Logging#Logging_level|log level]] separated by colon, multiple modules separated by comma, and additional options: | # '''MOZ_LOG''' - '''CASE SENSITIVE''' module name and [[MailNews:Logging#Logging_level|log level]] separated by colon, multiple modules separated by comma, and additional options: | ||
| Line 133: | Line 133: | ||
<small>Some modules may not work exactly according to the log levels noted above. Very few modules actually have more than one logging level</small> | <small>Some modules may not work exactly according to the log levels noted above. Very few modules actually have more than one logging level</small> | ||
== Generating a | === Generating a Gecko Log === | ||
'''NOTE - do not use this section for ldap, nntp, pop3 and smtp. They are configured in Thunderbird Settings, and log to the Thunderbird Error Console.''' Please refer to [[MailNews:Logging#Main_module_options_within_MailNews|module options]]. | '''NOTE - do not use this section for ldap, nntp, pop3 and smtp. They are configured in Thunderbird Settings, and log to the Thunderbird Error Console.''' Please refer to [[MailNews:Logging#Main_module_options_within_MailNews|module options]]. | ||
=== Windows === | ==== Windows ==== | ||
Create a batch file by copying the lines below and paste them into the notepad application, and save the file as "create_imap_log.bat". Variables MOZ_LOG and MOZ_LOG_file must not contain quotation marks. | Create a batch file by copying the lines below and paste them into the notepad application, and save the file as "create_imap_log.bat". Variables MOZ_LOG and MOZ_LOG_file must not contain quotation marks. | ||
| Line 155: | Line 155: | ||
Logging commands can also typed directly in the command prompt instead of running a batch file. On Windows 2000, XP, 2003 Server: Start>Programs>Accessories>Command Prompt. On later windows versions, you may type "cmd" and press enter in the launch dialog of the Start button. | Logging commands can also typed directly in the command prompt instead of running a batch file. On Windows 2000, XP, 2003 Server: Start>Programs>Accessories>Command Prompt. On later windows versions, you may type "cmd" and press enter in the launch dialog of the Start button. | ||
=== Mac OS X === | ==== Mac OS X ==== | ||
To generate an IMAP protocol log, create a text file that contains the desired commands in a text editor such as BBEdit: | To generate an IMAP protocol log, create a text file that contains the desired commands in a text editor such as BBEdit: | ||
| Line 184: | Line 184: | ||
Note, line starting with "<!DOCTYPE" should be oneline all the way to "dtd", but I'm not sure if that makes a difference. | Note, line starting with "<!DOCTYPE" should be oneline all the way to "dtd", but I'm not sure if that makes a difference. | ||
=== Linux/unix === | ==== Linux/unix ==== | ||
To generate an IMAP protocol log, run the following commands before running the application from the command line: | To generate an IMAP protocol log, run the following commands before running the application from the command line: | ||