[GH-ISSUE #19] [Feature request] Verbose logging without logging private information #16

Closed
opened 2026-03-03 01:19:02 +03:00 by kerem · 3 comments
Owner

Originally created by @d99kris on GitHub (Jan 28, 2020).
Original GitHub issue: https://github.com/d99kris/nmail/issues/19

Originally assigned to: @d99kris on GitHub.

From @kabouik in #13:

Regarding the new debug logging feature, maybe it would be good to have two options for comprehensive logging or just the previous level of details, since the new comprehensive logging can cause unnecessary privacy issues in other cases?

We don't necessarily need to have three logging levels, but we should review how the logging can be improved.

Originally created by @d99kris on GitHub (Jan 28, 2020). Original GitHub issue: https://github.com/d99kris/nmail/issues/19 Originally assigned to: @d99kris on GitHub. From @kabouik in #13: > Regarding the new debug logging feature, maybe it would be good to have two options for comprehensive logging or just the previous level of details, since the new comprehensive logging can cause unnecessary privacy issues in other cases? We don't necessarily need to have three logging levels, but we should review how the logging can be improved.
kerem closed this issue 2026-03-03 01:19:02 +03:00
Author
Owner

@d99kris commented on GitHub (Jan 30, 2020):

Note that default logging generally is intended to capture sufficient details for a bug report. Verbose logging is intended for odd cases when default logging is not providing enough details.

<!-- gh-comment-id:580201008 --> @d99kris commented on GitHub (Jan 30, 2020): Note that default logging generally is intended to capture sufficient details for a bug report. Verbose logging is intended for odd cases when default logging is not providing enough details.
Author
Owner

@Kabouik commented on GitHub (Jan 30, 2020):

We don't necessarily need to have three logging levels

This is what I had in mind, just two levels: one for the former logging feature, and one for the verbose logging you implemented recently to debug the fetching issue with my Exchange account.

<!-- gh-comment-id:580225309 --> @Kabouik commented on GitHub (Jan 30, 2020): > We don't necessarily need to have three logging levels This is what I had in mind, just two levels: one for the former logging feature, and one for the verbose logging you implemented recently to debug the fetching issue with my Exchange account.
Author
Owner

@d99kris commented on GitHub (Feb 5, 2020):

With the fix for this issue a new "extra verbose" logging level is introduced, where private information may be logged (such as email message content). The regular "verbose" logging mode is logging all except email messages content. The default (non-verbose) logging logs just errors/warnings encountered.

<!-- gh-comment-id:582350847 --> @d99kris commented on GitHub (Feb 5, 2020): With the fix for this issue a new "extra verbose" logging level is introduced, where private information may be logged (such as email message content). The regular "verbose" logging mode is logging all except email messages content. The default (non-verbose) logging logs just errors/warnings encountered.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nmail#16
No description provided.