Hey Carl, Thanks for noticing that. We’re going to get that header included in the signature shortly.
Thanks, Matt Gilbert -- Deliverability Engineer | Mailchimp delivery.mailchimp.com > On Nov 25, 2019, at 9:50 PM, Carl Byington via mailop <[email protected]> > wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On Mon, 2019-11-25 at 10:32 -0800, Kurt Andersen (b) via mailop wrote: >> Are you seeing any significant portion of these messages bearing the >> Form-Sub header? (documented in https://tools.ietf.org/html/draft- >> levine-mailbomb-header-01) > > On a low volume mail server, the only messages I see with that header > are also dkim signed by mail*.mcsignup.com. MailChimp are using > > h=From:Reply-To:To:Date:Message-ID:Sender:Subject:MIME-Version: Content- > Type; > > So their signature does not include the Form-Sub: header, contrary to > the recommendation in that draft. > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.14 (GNU/Linux) > > iEYEAREKAAYFAl3cksAACgkQL6j7milTFsG9zQCdE6YkaHRj+a4I+79b/quTXZrc > CsoAn1kB22Ss/Q34UIsR4zg7SIlheRC8 > =LF9o > -----END PGP SIGNATURE----- > > > > _______________________________________________ > mailop mailing list > [email protected] > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
_______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
