[Mailman-Users] Recommended reading before upgrading to 3.x ?
Andy Cravens writes: > I’m running mailman 2.x and I am getting ready to build a new > server and migrate my lists to 3.x. For those of you who have done > this already, do you have any recommended reading suggestions other > than the official web page at > > https://docs.mailman3.org/en/latest/migration.html The late Brian Carpenter wrote a bare-metal-to-bootable Mailman installation guide. It's Debian-specific, but most of the changes should be obvious for Red Hat, Centos, or hwat have you. I don't know where exactly it is (no time to look, gotta catch a bus), but it's strongly recommended as far as building the server goes. Search Brian in the mailman-us...@mailman3.org archives (I don't recall if he mentioned it on this list). For the migration proper, I think migration.html plus the mailing list archives are your best bet. It's a long shot, but if your time frame is something like "anytime between now and Halloween", we may have a nicer migration path (very very very beta, though) at the end of summer (it's our GSoC intern's project, so timeline is fixed, usability is not). Steve -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Trouble with DMARC on Mailing Lists
Hello everyone, I hope this email made it to the list. It has been crazy for a week. My SPF/DKIM/DMARC passes in most cases except for mailing lists. Recently, I observe that when I send emails to mailing lists, they get stashed after Mailman receives them. I administer Mailman for an organization, and this is what I am seeing: The email from my VPS arrives at the organization's server and passes authentication (including SPF/DKIM/DMARC checks) If the address is not a mailing list, dovecot delivers the email to local/virtual accounts without errors. It is all fine for regular destinations. If the address belongs to a mailing list, Mailman receives the email and includes it in the archives. Something goes wrong at this stage (i.e. when Mailman begins to send copies to subscribers). The log records the following: Jul 01 11:51:35 mail.organization.com opendkim[663]: 40D84274532: no signing table match for 'onye...@mydomain.com' Jul 01 11:51:35 mail.organization.com opendmarc[826730]: 40D84274532: mydomain.com fail It appears the mail server hosting Mailman on the other end wants to sign my email all over again before sending out copies to the list subscribers. The signing fails for obvious reasons. The host cannot possibly have signing keys for every subscribed domain on the list. The result is that Mailman archives an email that subscribers never see. Is any other list admin experiencing this? What do I do to get such emails to the list subscribers? How about lists that I subscribed to (the ones I do not administer?). Does the sender have any obligation too? This phenomenon is crazy. worriedly Onyeibo -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Trouble with DMARC on Mailing Lists
On 7/1/21 9:11 PM, Onyeibo wrote: The email from my VPS arrives at the organization's server and passes authentication (including SPF/DKIM/DMARC checks) If the address is not a mailing list, dovecot delivers the email to local/virtual accounts without errors. It is all fine for regular destinations. If the address belongs to a mailing list, Mailman receives the email and includes it in the archives. Something goes wrong at this stage (i.e. when Mailman begins to send copies to subscribers). The log records the following: Jul 01 11:51:35 mail.organization.com opendkim[663]: 40D84274532: no signing table match for 'onye...@mydomain.com' Jul 01 11:51:35 mail.organization.com opendmarc[826730]: 40D84274532: mydomain.com fail It appears the mail server hosting Mailman on the other end wants to sign my email all over again before sending out copies to the list subscribers. The signing fails for obvious reasons. The host cannot possibly have signing keys for every subscribed domain on the list. The result is that Mailman archives an email that subscribers never see. The Mailman server is trying to DKIM sign the outgoing mail, but opendkim on that server is misconfigured. It should have SenderHeaders List-Post,Sender,From in it's opendkim.conf so that it signs list mail with the list's domain. See the MAILING LISTS section near the bottom of http://www.opendkim.org/opendkim-README -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
