(admin) email cfg - NC loglevel 0 required for Mailer debugging
#11080
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Josh Richards <josh.t.richards@gmail.com>
joshtrichards
changed the title
loglevel 0 required for Mailer debugging
9 tasks
szaimen
approved these changes
Aug 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
☑️ Resolves
It also arose in nextcloud/server#40073 (and anytime anyone has email config problems) that the documentation doesn't make clear that enabling
mail_smtpdebugalone doesn't provide the debug output. This is because the output it generates is still sent to the debug level of the NC logger. So globalloglevelalso has to be set to0during troubleshooting. This just adds a note about that as well as how to turn it back off.🖼️ Screenshots