Since #392, a report has warnings only when a row failed DMARC, which matches the reports page. But a pass where SPF or DKIM failed is still worth seeing: it's how forwarding shows up (SPF fails, DKIM survives), and it can point at a sender that isn't in SPF yet, or a DKIM key that's failing on one path.
Proposal: count those separately, as something like "passed, but SPF or DKIM failed", on the dashboard and on the DMARC reports page next to the real failures. Don't go back to calling them warnings: the dashboard and the reports page should keep agreeing on what a failure is.
Suggested on the forum (https://community.coffeylabs.org/t/232, post 18).
Since #392, a report has warnings only when a row failed DMARC, which matches the reports page. But a pass where SPF or DKIM failed is still worth seeing: it's how forwarding shows up (SPF fails, DKIM survives), and it can point at a sender that isn't in SPF yet, or a DKIM key that's failing on one path.
Proposal: count those separately, as something like "passed, but SPF or DKIM failed", on the dashboard and on the DMARC reports page next to the real failures. Don't go back to calling them warnings: the dashboard and the reports page should keep agreeing on what a failure is.
Done in the console instead of the server: inbuxa/inbuxa-admin#203. The DMARC reports page now shows how many passing messages had SPF or DKIM failing, per domain and per sender, and the failure count and dashboard stay as they are. It works from the stored reports, so older ones show it too. Ships in the next console RC.
Done in the console instead of the server: inbuxa/inbuxa-admin#203. The DMARC reports page now shows how many passing messages had SPF or DKIM failing, per domain and per sender, and the failure count and dashboard stay as they are. It works from the stored reports, so older ones show it too. Ships in the next console 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.
Suggested on the forum (https://community.coffeylabs.org/t/232, post 18).
Since #392, a report has warnings only when a row failed DMARC, which matches the reports page. But a pass where SPF or DKIM failed is still worth seeing: it's how forwarding shows up (SPF fails, DKIM survives), and it can point at a sender that isn't in SPF yet, or a DKIM key that's failing on one path.
Proposal: count those separately, as something like "passed, but SPF or DKIM failed", on the dashboard and on the DMARC reports page next to the real failures. Don't go back to calling them warnings: the dashboard and the reports page should keep agreeing on what a failure is.
Done in the console instead of the server: inbuxa/inbuxa-admin#203. The DMARC reports page now shows how many passing messages had SPF or DKIM failing, per domain and per sender, and the failure count and dashboard stay as they are. It works from the stored reports, so older ones show it too. Ships in the next console RC.