LogReport for TlsReport (crates/smtp/src/reporting/inbound.rs) emits IncomingReportEvent::TlsReportWithWarnings once per policy with failures, up to five (self.policies.iter().take(5)). The dashboard counts those events as reports, so one TLS report with failures under two policies shows as 2 reports with warnings.
Fix: emit the warning event once per report (keep the per-policy details in it), so the count means reports, like the DMARC one.
Found while answering https://community.coffeylabs.org/t/232 (post 27), where the dashboard's "reports with warnings" came out higher than expected.
`LogReport for TlsReport` (`crates/smtp/src/reporting/inbound.rs`) emits `IncomingReportEvent::TlsReportWithWarnings` once per policy with failures, up to five (`self.policies.iter().take(5)`). The dashboard counts those events as reports, so one TLS report with failures under two policies shows as 2 reports with warnings.
Fix: emit the warning event once per report (keep the per-policy details in it), so the count means reports, like the DMARC one.
Fixed in #406. A TLS report now logs one event however many policies it covers, so the dashboard counts it once, and once with warnings when any policy had a failed session. The totals are summed over its policies, and each policy's figures are kept in the event. Thanks to khashmeshab (https://community.coffeylabs.org/t/232). In the next server RC.
Fixed in #406. A TLS report now logs one event however many policies it covers, so the dashboard counts it once, and once with warnings when any policy had a failed session. The totals are summed over its policies, and each policy's figures are kept in the event. Thanks to khashmeshab (https://community.coffeylabs.org/t/232). In the next server RC.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found while answering https://community.coffeylabs.org/t/232 (post 27), where the dashboard's "reports with warnings" came out higher than expected.
LogReport for TlsReport(crates/smtp/src/reporting/inbound.rs) emitsIncomingReportEvent::TlsReportWithWarningsonce per policy with failures, up to five (self.policies.iter().take(5)). The dashboard counts those events as reports, so one TLS report with failures under two policies shows as 2 reports with warnings.Fix: emit the warning event once per report (keep the per-policy details in it), so the count means reports, like the DMARC one.
Fixed in #406. A TLS report now logs one event however many policies it covers, so the dashboard counts it once, and once with warnings when any policy had a failed session. The totals are summed over its policies, and each policy's figures are kept in the event. Thanks to khashmeshab (https://community.coffeylabs.org/t/232). In the next server RC.