Hi Starlingx Community, I’m reaching out to you with updates about addressing DMARC-related mail delivery issues. As I have not received any objections to the below outlined plan, I went ahead and executed ‘option 1’. The following changes were made to the mailing list settings: - The ’subject prefix' was removed, Mailman will not add the '[Starlingx-discuss]’ prefix to the subject line - Stopped converting messages to plain text - Mailman will not convert HTML messages to plain text from now on - Removed the footer text - Mailman will not add a footer to the end of the emails (it is implemented through adding an empty footer) Please let me know if you have any questions. Thanks and Best Regards, Ildikó ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
On Nov 1, 2023, at 19:40, Ildiko Vancsa <ildiko@openinfra.dev> wrote:
Hi StarlingX Community,
I’m reaching out to follow up on this thread.
Does anyone have a preference in terms of taking ‘option 1’ or 'option 2’ as a step towards solving mail delivery issues for that starlingx-discuss mailing list?
__Please respond by the end of day next Friday (November 10).__
If I don’t hear any (other) preferences, I will proceed to implement ‘option 1’.
Also, please help sharing this information with people who you know are having issues with receiving mailing list emails. The link to the email in the archive is: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i...
Thanks and Best Regards, Ildikó
———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
On Oct 18, 2023, at 10:53, Ildiko Vancsa <ildiko@openinfra.dev> wrote:
Hi StarlingX Community,
I’m reaching out to you about the starlingx-discuss mailing list. It’s been an issue for some subscribers in the community to receive emails from the mailing list, which can potentially be improved by changing some of the configuration options.
Some mail servers on the client side either mark emails as spam or reject incoming emails depending on dmarc configuration settings. There are multiple options to try and be compatible to most mail server configurations.
Options, based on other OpenInfra communities’ approaches:
1. Turn off various list features which alter the message headers and body (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) - Communities using this option: OpenDev, Zuul, OpenStack
2. Replace From: with list address as the mitigation action, and not doing it unconditionally - Communities using this option: Kata Containers
Both options change how the mailing list alters and delivers the messages.
What is your preference moving forward? __Please vote with either ‘option 1’ or ‘option 2’, or ’none’ if you would prefer a different approach.__
Please let me know if you have any questions.
Best Regards, Ildikó
———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
_______________________________________________ Starlingx-discuss mailing list -- starlingx-discuss@lists.starlingx.io To unsubscribe send an email to starlingx-discuss-leave@lists.starlingx.io
_______________________________________________ Starlingx-discuss mailing list -- starlingx-discuss@lists.starlingx.io To unsubscribe send an email to starlingx-discuss-leave@lists.starlingx.io