On 07/17/2017 07:55 AM, Henrik Rasmussen wrote:
On another note: Is it a setting in the mailman-users@mailman3.org list setup that make each of my postings to the list come back with the note "This sender failed our fraud detection checks and may not be who they appear to be."?
I suspect this is something in the MTA/MDA chain between the lists.mailman3.org server and you. I suspect that something in that path doesn't like the fact that your original message's DKIM signature has been broken by such things as subject prefixing and addition of the list's msg_footer.
When your message reaches my server at msapiro.net, it sees
Authentication-Results: sbh16.songbird.com; dkim=pass (1024-bit key; unprotected) header.d=mailman3.org header.i=@mailman3.org header.b=QBeM9elY; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=alumni.onmicrosoft.com header.i=@alumni.onmicrosoft.com header.b=GeTpYnXK; dkim-atps=neutral
I.e., the list's DKIM sig is valid but your original sig is not, even though it was valid when received by the list
Authentication-Results: mail.mailman3.org; dkim=pass reason="1024-bit key; unprotected key" header.d=alumni.onmicrosoft.com header.i=@alumni.onmicrosoft.com header.b=GeTpYnXK; dkim-atps=neutral
If my suspicion is correct, you should be seeing the same thing with other people's posts such as this reply and your posts to other lists. If you don't then my suspicion about DKIM is not the reason and it is something else or the conditions are more complex.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan