From db17048e236a120da3918e3ea5badd4a5193e24c Mon Sep 17 00:00:00 2001 From: Phil Pennock Date: Mon, 26 Mar 2018 12:24:48 -0400 Subject: [PATCH] Add ARC signing caveats --- doc/doc-txt/experimental-spec.txt | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/doc/doc-txt/experimental-spec.txt b/doc/doc-txt/experimental-spec.txt index bc5bab77d..0828e9b67 100644 --- a/doc/doc-txt/experimental-spec.txt +++ b/doc/doc-txt/experimental-spec.txt @@ -805,6 +805,20 @@ is used as a basis (you must have added one on entry to the ADMD). Expanded as a whole; if unset, empty or forced-failure then no signing is done. If it is set, all three elements must be non-empty. +Caveats: + * There must be an Authentication-Results header, presumably added by an ACL + while receiving the message, for the same ADMD, for arc_sign to succeed. + This requires careful coordination between inbound and outbound logic. + * If passing a message to another system, such as a mailing-list manager + (MLM), between receipt and sending, be wary of manipulations to headers made + by the MLM. + + For instance, Mailman with REMOVE_DKIM_HEADERS==3 might improve + deliverability in a pre-ARC world, but that option also renames the + Authentication-Results header, which breaks signing. + * Even if you use multiple DKIM keys for different domains, the ARC concept + should try to stick to one ADMD, so pick a primary domain and use that for + AR headers and outbound signing. + -------------------------------------------------------------- -- 2.25.1