from_is_list munging not working
![](https://secure.gravatar.com/avatar/ac847e3bb1213b500ff8941fb0d145bb.jpg?s=120&d=mm&r=g)
I just moved my Mailman lists to new hardware (or rather my ISP did) and I've spent several hours now fixing the resulting problems.
Here's one I can figure out though -- I've got "from_is_list" set to "Munge From" and it's not munging. Specifically, I sent a message to the list from a yahoo.com account and the "From" was:
Russell Clemings <rclemxxxings@yahoo.com> via <https://support.google.com/mail/answer/1311182?hl=en> list.domain
instead of
Russell Clemings via (listname) <listname@list.domain>
I don't see anything in the logs and the config.pck looks pretty much identical to the old version.
I've dumped the new config.pck into the attached file. Did I miss something stupid (again)?
Otherwise, any suggestions?
--
Russell Clemings <rclemings@gmail.com>
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 5/18/24 6:46 PM, Russell Clemings wrote:
I just moved my Mailman lists to new hardware (or rather my ISP did) and I've spent several hours now fixing the resulting problems.
Here's one I can figure out though -- I've got "from_is_list" set to "Munge From" and it's not munging. Specifically, I sent a message to the list from a yahoo.com account and the "From" was:
Russell Clemings <rclemxxxings@yahoo.com> via <https://support.google.com/mail/answer/1311182?hl=en> list.domain
instead of
Russell Clemings via (listname) <listname@list.domain>
I don't see anything in the logs and the config.pck looks pretty much identical to the old version.
I've dumped the new config.pck into the attached file. Did I miss something stupid (again)?
Your config looks OK. Was this message received via googlmail? Was it actually from the list or was it perhaps a direct CC:? Did the From: actually contain the <https://support.google.com/mail/answer/1311182?hl=en> link?
What changed in the move to new hardware? Is all the software such as Mailman and the outgoing MTA the same code or what?
Just guessing, but it looks like tis message may have been sent directly th a googlemail user, not from the list, gan google, for reasons alluded to at <https://support.google.com/mail/answer/1311182?hl=en>, added the via stuff.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/ac847e3bb1213b500ff8941fb0d145bb.jpg?s=120&d=mm&r=g)
Before CentOS v7.9.2009 STANDARD kvm cPanel 110.0.24 (yeah, I know) Mailman 2.1.39-1.cp108~el7 Exim 4.96.2-2.cp108~el7
After: AlmaLinux v8.9.0 STANDARD kvm cPanel 120.0.5 Mailman 2.1.39-1.cp108~el8 Exim 4.97.1-1.cp118~el8
The only thing I see in the cPanel changelogs since v110 doesn't look relevant:
- export_lists <https://api.docs.cpanel.net/openapi/cpanel/operation/export_lists/> - This function exports a cPanel account’s Mailman mailing lists into a CSV file. This file is located in the /mail/exported_lists directory, relative to the cPanel account’s home directory.
I sent the post from my Yahoo account with no cc's and it was received by my Gmail account, albeit in spam. My Yahoo account bounced the incoming post from the list as did Comcast. The list owner (me) got bounce notices from Mailman for both.
Gmail's from field for the incoming post says: Russell Clemings <rclemxxxings@yahoo.com> via list.domain -- i.e. 'I can find "via" and a website name next to the sender's name" on the link you sent.
This is a test list. If nothing else from this strikes you as worth digging into some more, I'll just wait until we have some on a real list and see if anything looks different there.
On Sat, May 18, 2024 at 6:11 PM Mark Sapiro <mark@msapiro.net> wrote:
On 5/18/24 6:46 PM, Russell Clemings wrote:
I just moved my Mailman lists to new hardware (or rather my ISP did) and I've spent several hours now fixing the resulting problems.
Here's one I can figure out though -- I've got "from_is_list" set to "Munge From" and it's not munging. Specifically, I sent a message to the list from a yahoo.com account and the "From" was:
Russell Clemings <rclemxxxings@yahoo.com> via <https://support.google.com/mail/answer/1311182?hl=en> list.domain
instead of
Russell Clemings via (listname) <listname@list.domain>
I don't see anything in the logs and the config.pck looks pretty much identical to the old version.
I've dumped the new config.pck into the attached file. Did I miss something stupid (again)?
Your config looks OK. Was this message received via googlmail? Was it actually from the list or was it perhaps a direct CC:? Did the From: actually contain the <https://support.google.com/mail/answer/1311182?hl=en> link?
What changed in the move to new hardware? Is all the software such as Mailman and the outgoing MTA the same code or what?
Just guessing, but it looks like tis message may have been sent directly th a googlemail user, not from the list, gan google, for reasons alluded to at <https://support.google.com/mail/answer/1311182?hl=en>, added the via stuff.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-leave@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: rclemings@gmail.com
--
Russell Clemings <rclemings@gmail.com>
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 5/18/24 9:43 PM, Russell Clemings wrote:
I sent the post from my Yahoo account with no cc's and it was received by my Gmail account, albeit in spam. My Yahoo account bounced the incoming post from the list as did Comcast. The list owner (me) got bounce notices from Mailman for both.
Did those notices have a DSN attached that included the headers of the bounced mail, and if so, what did the From: look like. And were the bounces for DMARC or something else?
Is Exim DKIM signing the outgoing mail. Does list.domain publish an SPF record, and if the IP changed does the SPF still allow the domain?
This is a test list. If nothing else from this strikes you as worth digging into some more, I'll just wait until we have some on a real list and see if anything looks different there.
This may be an issue with cPanel's Mailman. Try setting Privacy options... -> Sender filters -> dmarc_moderation_action to Munge From. It should be irrelevant when General Options -> from_is_list = Munge From, but I don't know what cPanel might be doing.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/ac847e3bb1213b500ff8941fb0d145bb.jpg?s=120&d=mm&r=g)
Well, a couple of posts just came through on another list and they were properly munged. I'll compare the two list configurations and report back.
On Sat, May 18, 2024 at 8:30 PM Mark Sapiro <mark@msapiro.net> wrote:
On 5/18/24 9:43 PM, Russell Clemings wrote:
I sent the post from my Yahoo account with no cc's and it was received by my Gmail account, albeit in spam. My Yahoo account bounced the incoming post from the list as did Comcast. The list owner (me) got bounce notices from Mailman for both.
Did those notices have a DSN attached that included the headers of the bounced mail, and if so, what did the From: look like. And were the bounces for DMARC or something else?
Is Exim DKIM signing the outgoing mail. Does list.domain publish an SPF record, and if the IP changed does the SPF still allow the domain?
This is a test list. If nothing else from this strikes you as worth digging into some more, I'll just wait until we have some on a real list and see if anything looks different there.
This may be an issue with cPanel's Mailman. Try setting Privacy options... -> Sender filters -> dmarc_moderation_action to Munge From. It should be irrelevant when General Options -> from_is_list = Munge From, but I don't know what cPanel might be doing.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-leave@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: rclemings@gmail.com
--
Russell Clemings <rclemings@gmail.com>
![](https://secure.gravatar.com/avatar/ac847e3bb1213b500ff8941fb0d145bb.jpg?s=120&d=mm&r=g)
OK, so the "pipeline" section in the test list config I sent earlier was not in the config for the list that was munging properly. I removed it from the test list config and now it's munging too.
(How to remove pipeline from a single list: https://tinyurl.com/ydrd8z96)
As an aside, I'm now pretty sure this problem resulted not from the hardware migration but from an experiment I did several years ago:
https://mail.python.org/pipermail/mailman-users/2010-July/069944.html
(Note to self: Next time, clean up after yourself.)
Thanks for your patience.
On Sun, May 19, 2024 at 9:10 AM Russell Clemings <rclemings@gmail.com> wrote:
Well, a couple of posts just came through on another list and they were properly munged. I'll compare the two list configurations and report back.
On Sat, May 18, 2024 at 8:30 PM Mark Sapiro <mark@msapiro.net> wrote:
On 5/18/24 9:43 PM, Russell Clemings wrote:
I sent the post from my Yahoo account with no cc's and it was received
by
my Gmail account, albeit in spam. My Yahoo account bounced the incoming post from the list as did Comcast. The list owner (me) got bounce notices from Mailman for both.
Did those notices have a DSN attached that included the headers of the bounced mail, and if so, what did the From: look like. And were the bounces for DMARC or something else?
Is Exim DKIM signing the outgoing mail. Does list.domain publish an SPF record, and if the IP changed does the SPF still allow the domain?
This is a test list. If nothing else from this strikes you as worth digging into some more, I'll just wait until we have some on a real list and see if anything looks different there.
This may be an issue with cPanel's Mailman. Try setting Privacy options... -> Sender filters -> dmarc_moderation_action to Munge From. It should be irrelevant when General Options -> from_is_list = Munge From, but I don't know what cPanel might be doing.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-leave@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: rclemings@gmail.com
--
Russell Clemings <rclemings@gmail.com>
--
Russell Clemings <rclemings@gmail.com>
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 5/19/24 6:03 PM, Russell Clemings wrote:
OK, so the "pipeline" section in the test list config I sent earlier was not in the config for the list that was munging properly. I removed it from the test list config and now it's munging too.
Had I looked more carefully at the config you posted initially, I might have seen that your list had a pipeline attribute and that it was based on an older version and was missing the WrapMessage handler which is why the From: wasn't munged.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/ac847e3bb1213b500ff8941fb0d145bb.jpg?s=120&d=mm&r=g)
Mystery solved. Thanks again.
On Sun, May 19, 2024 at 4:24 PM Mark Sapiro <mark@msapiro.net> wrote:
On 5/19/24 6:03 PM, Russell Clemings wrote:
OK, so the "pipeline" section in the test list config I sent earlier was not in the config for the list that was munging properly. I removed it from the test list config and now it's munging too.
Had I looked more carefully at the config you posted initially, I might have seen that your list had a pipeline attribute and that it was based on an older version and was missing the WrapMessage handler which is why the From: wasn't munged.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-leave@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: rclemings@gmail.com
--
Russell Clemings <rclemings@gmail.com>
participants (2)
-
Mark Sapiro
-
Russell Clemings