Mechiel Lukkien 2abac1a911 for dmarc reporting, be more conservate with sending reports to junky senders, and format textual dmarc report period in the message text in utc as claimed ... before this change, a message in the rejects folder that was read and marked as notjunk (e.g. automatically by webmail), could cause a dmarc report to be sent for another junky message from the domain. we now require positive signals to be for messages not in the rejects mailbox. the text/plain body of a dmarc report contains the period, but it was in local time while claiming to be in utc. make it utc, so we often get nicely rounded whole 24h utc days.		2023-11-04 23:24:47 +01:00
..
dmarcdb.go	implement outgoing dmarc aggregate reporting	2023-11-02 09:12:30 +01:00
eval.go	for dmarc reporting, be more conservate with sending reports to junky senders, and format textual dmarc report period in the message text in utc as claimed	2023-11-04 23:24:47 +01:00
eval_test.go	implement outgoing dmarc aggregate reporting	2023-11-02 09:12:30 +01:00
reports.go	implement outgoing dmarc aggregate reporting	2023-11-02 09:12:30 +01:00
reports_test.go	implement outgoing dmarc aggregate reporting	2023-11-02 09:12:30 +01:00