> -----Original Message----- > From: Dmitri Maziuk [mailto:dmitri.maz...@gmail.com] > Sent: Thursday, April 13, 2017 8:30 AM > To: users@clusterlabs.org > Subject: Re: [ClusterLabs] Fraud Detection Check? > > On 2017-04-13 01:39, Jan Pokorný wrote: > > > After a bit of a search, the best practice at the list server seems to > > be: > > > >> [...] if you change the message (eg, by adding a list signature or by > >> adding the list name to the Subject field), you *should* DKIM sign. > > This is of course going entirely off-topic for the list, but DKIM's stated > purpose is to sign mail coming from *.clusterlabs.org with a key from > clustrlab.org's dns zone file. DKIM is not mandatory, so you strip all > existing > dkim headers and then either sign or not, it's up to you. > > None of this is new. SourceForge list manager, for example, adds SF footers > *inside* the PGP-signed MIME part, resulting in the exact same "invalid > signature" problem. > > Dima >
Thanks for all the feedback, guys. Bottom line for me is that I'm only seeing it in messages that I send to ClusterLabs list, but you guys are not seeing it at all, even in my messages. So if it isn't bothering anybody else, it is also not bothering me enough to do anything about it. I believe the problem is on my end (or rather, at Office 365) but if it is not being seen in the list then I don't care that much. I just want to make sure people in the list are not getting alerts that my mails are fraudulent. -- Eric Robinson _______________________________________________ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
