Wednesday, 2023-10-11

@doug.pereira:matrix.orgIt looks like I'm not getting all the emails from the starlingX mailing list:12:20
https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.io/
I only got 3 new emails last night but the list seems to have 7 new messages... Is this happening to anyone else?
@fungicide:matrix.orgdoug.pereira: i received them all. have you checked to see if some of them ended up in your junk/spam folder for any reason? if you can't find them, i'll check the logs on the mailserver to see if i can find where your mail provider either accepted or rejected delivery on your behalf12:36
@fungicide:matrix.orgdoug.pereira: never mind, i see the problem. markmonitor/proofpoint, who hosts windriver.com's mailboxes, is checking dkim signatures on messages from some of the senders on the list and rejecting them because of the changes the mailing list makes to the messages (prepending the list name to the subject line, adding a footer to messages with unsubscribe instructions, et cetera). the mailing list software has several mitigations to choose from for dealing with dkim signatures, probably best if i work with ildikov to determine which one will be the least problematic12:44
@ildikov:matrix.orgfungi: that would be great, thank you for offering to help13:35
@doug.pereira:matrix.orgThank you fungi !13:43
@fungicide:matrix.orgildikov: when you get a chance, take a look in https://lists.starlingx.io/mailman3/lists/starlingx-discuss.lists.starlingx.io/settings/dmarc_mitigations and you'll see a few options to choose from in the *DMARC mitigation action* drop-down. the options worth considering are replacing the from address or wrapping the message. the *DMARC Mitigate unconditionally* radio button just below there chooses whether to apply the selected mitigation to all list messages or only to list messages which come from a domain with a dmarc policy published in dns15:53
@fungicide:matrix.orgthe main consideration is that these will result in the messages subscribers receive no longer being "from" the sender's address, but will instead come "from" the mailing list (though with the sender's name still)15:54
@ildikov:matrix.orgfungi: I think the main priority is to try to avoid messages ending up in spam as much as possible15:55
@fungicide:matrix.orgwell, these messages didn't end up in spam, they were never delivered to some subscribers because their mailservers rejected the messages comlpetely15:56
@fungicide:matrix.orgthere is another option not represented there, which is more of an incomplete (but fairly effective) workaround: turn off various list features which alter the message headers and body. we do that on some of our mailing lists, but depending on the signing policy it may not work for all domains15:57
@ildikov:matrix.orgI spoke to someone who said the ml messages went to spam on their end 15:57
@fungicide:matrix.orgthat may have happened for some messages, and may not have been the same messages. at the moment my concern is with the messages that windriver.com subscribers can't receive at all due to dmarc policy rejections15:58
@ildikov:matrix.orgBased on your experience, what would you suggest to do here?15:58
@fungicide:matrix.orgthe kata-dev mailing list had similar problems with subscribers using microsoft.com addresses, and i believe they're using *Replace From: with list address* as the mitigation action, and not doing it unconditionally16:00
@ildikov:matrix.orgOk, that’s good info.16:01
@fungicide:matrix.orgthe service-* lists for opendev, the zuul lists, and openstack-discuss are using the workaround i mentioned (disabling the list features that add a prefix to the subject, that append a footer with the unsubscribe instructions, and setting it not to add a reply-to header)16:01
@ildikov:matrix.orgHas OpenStack had this issue? Since it’s a high traffic ml16:01
@fungicide:matrix.org(i answered that question just as you asked it)16:05
@ildikov:matrix.orgThank you!16:10

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!