Debug logging as main troubleshooting measure
If something goes wrong and you get an error or something doesn't work as expected, the most helpful troubleshooting measure is enabling logging, reproducing the issue and analyzing the log file.
Debug logging is used for troubleshooting in user area of webmail application. It can be enabled in Admin Panel / System / Logging. For example, if you click a message in message list, but its text is not shown or you save your account settings, but something is not saved, you should enable logging, reproduce the issue and analyze the log file (or provide us with it for examination).
In most cases, Verbosity level should be set to Debug.
To avoid irrelevant records in the log file (may significantly complicate analyzing), it's important to enable logging right before reproducing the issue and disable right after that.
Another reason of appearing irrelevant records is simultaneous access of multiple users to the same product installation. If hundreds of users work with your product installation at the moment when you're capturing the log file, all their actions will be logged and it'll be not possible to distinguish between relevant and irrelevant records.
In this case, personal logging may be helpful. To enable it, user should access Aurora installation with
?speclogon parameter added to URL. It will ensure that only session of this specific user will be reflected in the logs. For this to work, Aurora administrator need to set Verbosity level to Specified user.
To get back to the default logging mode, open Aurora primary URL with ?speclogoff parameter added to it.