On 19. jun. 2014 17.04.49 CEST, John Levine via dmarc-discuss
dmarc-discuss@dmarc.org wrote:
So more specifically, the workaround for DMARC breaks S/MIME. Sigh.
yes, amavisd-new and postfix maillist let my dmarc get pass on my own domain,
silly to see that dmarc maillists try to make non
If your MUA shows you that this message is signed with a trusted
certificate, you're sorted. If you're in the minority (or so I believe)
for whom that isn't displayed, then boo; you're one of the few for whom
S/MIME signatures as a matter of course would achieve nothing.
Gmail: shows the
On Tue, 2014-06-10 at 15:08 +, Rock, Paul via dmarc-discuss wrote:
Depends on the client as well. Currently the version of Outlook (2010)
I'm using on my Windows box also treats the signature as an attachment
it doesn't know what to do with.
That's odd — that's one of the few things
The mail from you directly works fine in Outlook, showing up with the cert icon
in the mail list. Mail.app doesn't seem to have any indicator of the signing,
but it's not showing a warning either.
Now, the really amusing thing is that when the mail from the listserv came in,
it's merged with
