mox/tlsrpt
Mechiel Lukkien 61bae75228
outgoing dmarc/tls reporting improvements
- dmarc reports: add a cid to the log line about one run of sending reports, and log line for each report
- in smtpclient, also handle tls errors from the first read after a handshake. we appear to sometimes get tls alerts about bad certificates on the first read.
- for messages to dmarc/tls reporting addresses that we think should/can not be processed as reports, add an X-Mox- header explaining the reason.
- tls reports: send report messages with From address of postmaster at an actually configured domain for the mail host. and only send reports when dkim signing is configured for that domain. the domain is also the submitter domain. the rfc seems to require dkim-signing with an exact match with the message from and submitter.
- for incoming tls reports, in the smtp server, we do allow a dkim-signature domain that is higher-level (up to publicsuffix) of the message from domain. so we are stricter in what we send than what we receive.
2023-11-10 19:34:00 +01:00
..
alert.go implement outgoing tls reports 2023-11-09 19:47:26 +01:00
alert_go120.go implement outgoing tls reports 2023-11-09 19:47:26 +01:00
doc.go mox! 2023-01-30 14:27:06 +01:00
lookup.go implement dnssec-awareness throughout code, and dane for incoming/outgoing mail delivery 2023-10-10 12:09:35 +02:00
lookup_test.go simplify dns.MockResolver, changing MockReq to just a string representing the request 2023-10-12 16:07:53 +02:00
parse.go implement outgoing tls reports 2023-11-09 19:47:26 +01:00
parse_test.go mox! 2023-01-30 14:27:06 +01:00
report.go outgoing dmarc/tls reporting improvements 2023-11-10 19:34:00 +01:00
report_test.go implement outgoing tls reports 2023-11-09 19:47:26 +01:00