[Mailman-Users] Amazon SES and mailman
Hi, We are running mailman2 with postfix and CentOS. For a long time the mail gateway was mailgun. Recently switched to Amazon SES. Now there are complaints that "threading" isn't right. That is, organizing the results according to topic, and correlating replies with specific other replies. It turns out that "The Amazon Simple Email Service (AWS SES) rewrites the Message-ID header of outgoing emails." This means the References and In-Reply-To headers can't be relied on anymore also, since they won't always match up. These headers: Message-ID: <127401d9389b$e874b7f0$b95e27d0$@gmail.com> References: <126301d93891$58081b80$08185280$@gmail.com> In-Reply-To: <126301d93891$58081b80$08185280$@gmail.com> might now appear as: In-Reply-To: <010f0187dca41ec8-478dfff5-d27d-4879-ab72-072be2f76176-000...@us-east-2.amazonses.com> References: <010f0187d80eb0dd-93bebdd9-cabf-4ad6-a7f4-b5515bd22d31-000...@us-east-2.amazonses.com> <010f0187dca41ec8-478dfff5-d27d-4879-ab72-072be2f76176-000...@us-east-2.amazonses.com> But perhaps a main problem is that for a large outgoing mailing, the Message-ID might not be consistent when sending to 1000's of recipients. Maybe not everyone sees the same Message-ID. Any thoughts on the topic? Has anyone used Amazon SES, and does the "threading" in the archives line up correctly? Thanks, Sam -- 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/ Member address: arch...@jab.org
[Mailman-Users] Hyperkitty new thread interface
Hi, At the website https://mail.python.org/archives/list/mailman-users@python.org/latest there is an option to "Start a new thread". I clicked that and entered a message. It said, if you are not already subscribed, sending the message will subscribe you. Perfect. So, did that, and sent a message and subscribed. However, not seeing the message in either the archive or my inbox. So, trying to "Start a new thead" again. Let's see. Thanks. -- 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/ Member address: arch...@jab.org
[Mailman-Users] Re: Hyperkitty new thread interface
Ok the question is probably answered now. It was in a moderation queue for a day. No problem. Thanks. -- 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/ Member address: arch...@jab.org
[Mailman-Users] Re: Hyperkitty new thread interface
On 5/4/23 09:43, samuel.d.dar...@gmail.com wrote: Hi, At the website https://mail.python.org/archives/list/mailman-users@python.org/latest there is an option to "Start a new thread". I clicked that and entered a message. It said, if you are not already subscribed, sending the message will subscribe you. Perfect. So, did that, and sent a message and subscribed. However, not seeing the message in either the archive or my inbox. So, trying to "Start a new thead" again. Let's see. You didn't see the messages because new member posts are held for moderation and are not accepted immediately. -- 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/ Member address: arch...@jab.org
[Mailman-Users] Re: Amazon SES and mailman
Also posted this question to the mailman3 list yesterday. Andrew Hodgson sent an informative answer, so that's probably it. "Amazon SES rewrites the Message-ID. Yep and for this reason I don't use it. The problem is worse in Mailman3 because it has a much more superior archive display which gets ruined when people reply to messages with different Message-Id headers and the threading can't be observed. I also had to use the anonymous mode with my list as Amazon didn't like me using random addresses in the From: header. I'm still looking for a tolerant mail gateway to use with Mailman." On Thu, May 4, 2023 at 9:18 AM Sam Darwin wrote: > > Hi, > > We are running mailman2 with postfix and CentOS. For a long time the > mail gateway was mailgun. Recently switched to Amazon SES. > > Now there are complaints that "threading" isn't right. That is, > organizing the results according to topic, and correlating replies > with specific other replies. > > It turns out that "The Amazon Simple Email Service (AWS SES) rewrites > the Message-ID header of outgoing emails." > > This means the References and In-Reply-To headers can't be relied on > anymore also, since they won't always match up. These headers: > > Message-ID: <127401d9389b$e874b7f0$b95e27d0$@gmail.com> > References: <126301d93891$58081b80$08185280$@gmail.com> > In-Reply-To: <126301d93891$58081b80$08185280$@gmail.com> > > might now appear as: > > In-Reply-To: > <010f0187dca41ec8-478dfff5-d27d-4879-ab72-072be2f76176-000...@us-east-2.amazonses.com> > References: > <010f0187d80eb0dd-93bebdd9-cabf-4ad6-a7f4-b5515bd22d31-000...@us-east-2.amazonses.com> > <010f0187dca41ec8-478dfff5-d27d-4879-ab72-072be2f76176-000...@us-east-2.amazonses.com> > > But perhaps a main problem is that for a large outgoing mailing, the > Message-ID might not be consistent when sending to 1000's of > recipients. Maybe not everyone sees the same Message-ID. > > Any thoughts on the topic? > > Has anyone used Amazon SES, and does the "threading" in the archives > line up correctly? > > Thanks, > Sam -- 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/ Member address: arch...@jab.org
[Mailman-Users] rebuilding and replacing.
Greetings. It's been a while since I've had an issue, mostly because mailman just works. (and thank you for that) We're running old - SciLin 7.9 / Mailman 2.1.20, but are upgrading out of necessity. We've chosen RHEL 8.7 and Mailman 2.1.39 All installed, created a new list... and stopped. Not sure what I missed, but in 2.1.20, after a newlist is created, we get a block of all the required aliases to put in the /etc alias file - similar to (for example) - ##jeffslist mailing list jeffslist: "|/usr/lib/mailman/mail/mailman post jeffslist" jeffslist-admin: "|/usr/lib/mailman/mail/mailman admin jeffslist" jeffslist-bounces: "|/usr/lib/mailman/mail/mailman bounces jeffslist" jeffslist-confirm: "|/usr/lib/mailman/mail/mailman confirm jeffslist" jeffslist-join: "|/usr/lib/mailman/mail/mailman join jeffslist" jeffslist-leave: "|/usr/lib/mailman/mail/mailman leave jeffslist" jeffslist-owner: "|/usr/lib/mailman/mail/mailman owner jeffslist" jeffslist-request: "|/usr/lib/mailman/mail/mailman request jeffslist" jeffslist-subscribe: "|/usr/lib/mailman/mail/mailman subscribe jeffslist" jeffslist-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe jeffslist" We then run 'newalises' and move along. This block did not appear, and it's been over a decade since I built the old one. I don't remember doing anything special to get the new alias information, so I'm blindly assuming - something changed? How do I get this information now? I can't seen any difference in the scripts. thank you - Jeff W -- 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/ Member address: arch...@jab.org
[Mailman-Users] Re: rebuilding and replacing.
On 2023-05-05 2:57 PM, Jeffrey Westgate wrote: All installed, created a new list... and stopped. Not sure what I missed, but in 2.1.20, after a newlist is created, we get a block of all the required aliases to put in the /etc alias file Back in centos 7 + postfix we'd have them in a separate file (mailman.aliases? -- something like that) that needed to be included in postfix config. No idea what they did in RH8 though. Dima -- 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/ Member address: arch...@jab.org
[Mailman-Users] Re: rebuilding and replacing.
On 5/5/23 12:57, Jeffrey Westgate wrote: All installed, created a new list... and stopped. Not sure what I missed, but in 2.1.20, after a newlist is created, we get a block of all the required aliases to put in the /etc alias file - similar to (for example) - Did you perhaps set MTA to something other than 'Manual' in mm_cfg.py? The Defaults.py setting is `MTA = 'Manual'`. See https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/Defaults.py.in#L530 Any value other than 'Manual' will not print aliases. 'Postfix' will write them to a file in Mailman's data/ directory and anything else will do nothing. Mailman's bin/genaliases will report a bad setting. -- 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/ Member address: arch...@jab.org
