Enable mail debugging mode in Confluence Data Center and Server
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Purpose
To detail clearly how to enable debug mode for both the incoming and outgoing emails in Confluence.
Solution
This feature is only available on Confluence Server or Data Center 7.20 or later.
You need System Administrator global permissions to do this.
Change the logging level of the com.atlassian.confluence.mail.session package
- Go to
> General Configuration > Logging and Profiling. - If you run Confluence in a cluster, select a cluster node.
- Locate the
com.atlassian.confluence.mail.sessionpackage, and select DEBUG value from the New Level menu. - Save your changes.
Remember, your changes will not be written to the log4j.properties file and will be discarded when you next stop Confluence.
To enable email logging at the protocol level (more verbose), add -Dmail.debug=true to the Confluence System Properties.
For more information on the subject, refer to Configuring Logging on Confluence Server and Data Center.
Keep in mind that the primary goal of debug logging is troubleshooting. It is good practice to disable the debug logging after the problem is solved to avoid potential performance impacts and logs with too many entries.