Reported in forum https://community.coffeylabs.org/t/232 (post 15/16). The dashboard said "3 reports with warnings (3 DMARC)" while the DMARC reports page said 16 of 16 messages passed.
crates/smtp/src/reporting/inbound.rs:108 raises DmarcReportWithWarnings when any row has dkim_fail + spf_fail (or a quarantine/reject disposition) in policy_evaluated. DMARC passes when either aligned SPF or aligned DKIM passes, which is how the console's reports page counts (inbuxa-adminsrc/features/incomingReports/summarize.ts:46). Forwarded mail (DKIM pass, SPF fail) is therefore a warning on the dashboard and a pass on the reports page.
Fix: count a report as with warnings only when a row has neither aligned SPF nor aligned DKIM passing. Decide whether a quarantine/reject disposition on a row that passed (local override, e.g. forwarded) still counts, or gets its own wording.
Reported in forum https://community.coffeylabs.org/t/232 (post 15/16). The dashboard said "3 reports with warnings (3 DMARC)" while the DMARC reports page said 16 of 16 messages passed.
`crates/smtp/src/reporting/inbound.rs:108` raises `DmarcReportWithWarnings` when any row has `dkim_fail + spf_fail` (or a quarantine/reject disposition) in `policy_evaluated`. DMARC passes when either aligned SPF or aligned DKIM passes, which is how the console's reports page counts (`inbuxa-admin` `src/features/incomingReports/summarize.ts:46`). Forwarded mail (DKIM pass, SPF fail) is therefore a warning on the dashboard and a pass on the reports page.
Fix: count a report as with warnings only when a row has neither aligned SPF nor aligned DKIM passing. Decide whether a quarantine/reject disposition on a row that passed (local override, e.g. forwarded) still counts, or gets its own wording.
Fixed in #392. A DMARC report now counts as "with warnings" only when a message in it failed DMARC, so forwarded mail that passes on DKIM no longer shows as a warning, and the dashboard agrees with the reports page. Counts already on the dashboard stay as they were; reports that arrive after the upgrade use the new rule. Thanks to khashmeshab for spotting it in forum t/232. It will be in the next 27.1 RC.
Fixed in #392. A DMARC report now counts as "with warnings" only when a message in it failed DMARC, so forwarded mail that passes on DKIM no longer shows as a warning, and the dashboard agrees with the reports page. Counts already on the dashboard stay as they were; reports that arrive after the upgrade use the new rule. Thanks to khashmeshab for spotting it in forum t/232. It will be in the next 27.1 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.
Reported in forum https://community.coffeylabs.org/t/232 (post 15/16). The dashboard said "3 reports with warnings (3 DMARC)" while the DMARC reports page said 16 of 16 messages passed.
crates/smtp/src/reporting/inbound.rs:108raisesDmarcReportWithWarningswhen any row hasdkim_fail + spf_fail(or a quarantine/reject disposition) inpolicy_evaluated. DMARC passes when either aligned SPF or aligned DKIM passes, which is how the console's reports page counts (inbuxa-adminsrc/features/incomingReports/summarize.ts:46). Forwarded mail (DKIM pass, SPF fail) is therefore a warning on the dashboard and a pass on the reports page.Fix: count a report as with warnings only when a row has neither aligned SPF nor aligned DKIM passing. Decide whether a quarantine/reject disposition on a row that passed (local override, e.g. forwarded) still counts, or gets its own wording.
Fixed in #392. A DMARC report now counts as "with warnings" only when a message in it failed DMARC, so forwarded mail that passes on DKIM no longer shows as a warning, and the dashboard agrees with the reports page. Counts already on the dashboard stay as they were; reports that arrive after the upgrade use the new rule. Thanks to khashmeshab for spotting it in forum t/232. It will be in the next 27.1 RC.