[Mailman-Users] Re: New install - Where's 'chang...@example.com' coming from?

2022-06-18 Thread Andy Smith
Hello,

On Sat, Jun 18, 2022 at 01:57:29AM +, Andy Smith wrote:
> I thought I'd gone through /etc/mailman3/mailman.cfg thoroughly,
> but I am seeing the From: address chang...@example.com in some
> administrative notifications.

Well, I rebooted the host and afterwards the site_owner was set as I
expected. I really thought I  had restarted mailman3.service and
mailman3-web.service several times, but perhaps not…

Cheers,
Andy
--
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] New install - Where's 'chang...@example.com' coming from?

2022-06-18 Thread Andy Smith
Hi,

I've just installed mailman3 (well, mailman3-full) on a Debian 11
host from Debian packages. I thought I'd gone through
/etc/mailman3/mailman.cfg thoroughly, but I am seeing the From:
address chang...@example.com in some administrative notifications.

Now, when I search for help on this everything says that I have not
set site_owner in /etc/mailman3/mailman.cfg, but I have!

As an example of what I am seeing, when I use the web interface to
unsubscribe a list member, the member themself gets a notification
as expected:

From: testing-boun...@lists.strugglers.net
To: andy-ag...@strugglers.net
Subject: You have been unsubscribed from the Testing mailing list

but the list's owner gets one from "chang...@example.com":

From: chang...@example.com
To: testing-ow...@lists.strugglers.net
Subject: Testing unsubscription notification

andy-aga...@strugglers.net has been removed from Testing.

I can't for the life of me work out where this is coming from:

$ sudo ack site_owner /etc/mailman3
/etc/mailman3/mailman.cfg
28:site_owner: postmas...@lists.strugglers.net
$ sudo ack changeme /etc/mailman3

(no output)

It's not in any of the sqlite DBs either (still on sqlite while
testing things out):

$ sudo sqlite3 /var/lib/mailman3/data/mailman.db .dump | grep -i changeme
$ sudo sqlite3 /var/lib/mailman3/web/mailman3web.db .dump | grep -i changeme

So where can this possibly be coming from?

I have not yet configured the MTA (Exim) for delivering to Mailman,
and I haven't done anything special about sending settings:

[mta]
# …
outgoing: mailman.mta.deliver.deliver
smtp_host: localhost
smtp_port: 25
configuration: python:mailman.config.exim4

Thanks,
Andy
--
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] Web links in templates - is this non-default?

2022-06-18 Thread Andy Smith
Hi,

>From Mailman 2 I am used to various administrative emails having web
links in them for ease of use. For example, when confirming your
subscription to a list I am used to the confirmation email having
both an embedded code for replying back and also a link to the web
interface for confirming by web.

On a new install of mailman3-full on Debian 11 I am not seeing any
web links, only text regarding replying by email, how to change
options by email, etc.

Am I right in thinking that this is intentional, it is not some
simple thing that I missed or forgotten to enable? I'm assuming
because mailman3 can function without any web interface so it was
considered that adding links to Postorious by default would not be
the correct thing to do?

If that is the case, is the correct way to achieve what I want to
add a bunch of custom templates? It seems like it might be a common
desire, so have anyone done this already? I searched around but I've
found it difficult to come up with good search terms for this.

Thanks,
Andy
--
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: What can cause "Munge From" (from_is_list) to have no effect?

2022-06-18 Thread Mark Hills
On Tue, 14 Jun 2022, Mark Sapiro wrote:

> On 6/14/22 15:07, Mark Hills wrote:
> > 
> > In diagnosing a DMARC "FAIL" reported in Gmail I notice that some settings
> > are having absolutely no effect:
> > 
> >from_is_list
> >dmarc_moderation_action
> >dmarc_quarantine_moderation_action
> >dmarc_none_moderation_action
> > 
> > So in my testing today, at no point have I been able to get Mailman to
> > "Munge From" or "Wrap Message" in any way.
> 
> 
> Do you have a definition of `GLOBAL_PIPELINE` in mm_cfg.py or a setting for
> `pipeline` in the list's config.pck.
> 
> If so, do these include the `WrapMessage` handler?

Not the exact problem, but thanks for setting me on the right path.

There _was_ the following in mm_cfg.py for some time:

  GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('Approve'), 'SizeLimit')

I removed this completely and repeated the test; no change.

It took me a while but I eventually worked out I needed to refresh the 
pipeline of the individual lists, with something like:

  echo "del mlist.pipeline" | config_list -i /dev/stdin mylist

This command succeeded the first time; successive attempts failed with:

  AttributeError: MailList instance has no attribute 'pipeline'

which seems to suggest where was a list-specific pipeline, but no more.

So I think what's happened here is our lists ended up with a pipeline 
definition fixed into each list. It's possibly someting from a series of 
upgrades; there's never been a reason to want to maintain a separate 
pipeline for each list (only to ensure the "SizeLimit" above applied to 
all lists on the system.)

We have a script periodically using config_list to set "known good" values 
on every list. To prevent the problem above happening again, I've added 
the following:

  if hasattr(mlist, 'pipeline'):
del mlist.pipeline

> > Other nearby settings work, so I am able to change the config; it's the
> > correct list etc. I've also tried re-starting. Logs in
> > /usr/local/mailman/log aren't showing any errors or hints.
> > 
> > As some feedback, an FAQ [*] mentions ALLOW_FROM_IS_LIST; setting this has
> > no impact, not suprising as the source code doesn't seem to mention this
> > string anyway. Reading more carefully, I can see this doesn't apply to the
> > current version; perhaps someone with Wiki access might consider the
> > manner it's written, whilst technically correct, is a little
> > backward/confusing, or removing old information.
> 
> 
> I changed the line
> ```
> 1) If you have Mailman 2.1.16 or later, set
> ```
> to
> ```
> 1) If you have Mailman 2.1.16 or 2.1.17, set
> ```
> Does that help?

I think that's a good change that will save time/confusion for others. 
Thanks.

-- 
Mark
--
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: Web links in templates - is this non-default?

2022-06-18 Thread Mark Sapiro

This thread really belongs on mailman-us...@mailman3.org

On 6/18/22 11:26, Andy Smith wrote:


On a new install of mailman3-full on Debian 11 I am not seeing any
web links, only text regarding replying by email, how to change
options by email, etc.

Am I right in thinking that this is intentional, it is not some
simple thing that I missed or forgotten to enable? I'm assuming
because mailman3 can function without any web interface so it was
considered that adding links to Postorious by default would not be
the correct thing to do?



That is correct. Mailman core does not know how to access your web UI or 
if you even have one.




If that is the case, is the correct way to achieve what I want to
add a bunch of custom templates? It seems like it might be a common
desire, so have anyone done this already? I searched around but I've
found it difficult to come up with good search terms for this.


Yes, that is the solution. In Postorius, you can set list specific or 
domain specific templates, but not site wide templates. You can set site 
templates in Mailman's var/templates/site//


On the server for this list we have these templates which include 
appropriate URLs

```
$ ll /opt/mailman/mm/var/templates/site/en
total 64
drwxr-xr-x 2 mailman mailman 4096 Jun 29  2021 .
drwxr-xr-x 4 mailman mailman 4096 Jul  2  2021 ..
-rw-rw-r-- 1 mailman mailman  608 Dec 31  2018 
domain:admin:notice:new-list.txt

-rw-rw-r-- 1 mailman mailman  338 Dec 31  2018 list:admin:action:post.txt
-rw-r- 1 mailman mailman  252 Feb 18  2020 
list:admin:action:subscribe.txt
-rw-r- 1 mailman mailman  256 Jun 29  2021 
list:admin:action:unsubscribe.txt

-rw-r- 1 mailman mailman  173 Jun 29  2021 list:admin:notice:pending.txt
-rw-r- 1 mailman mailman  203 Apr 30  2020 list:member:digest:footer.txt
-rw-rw-r-- 1 mailman mailman  421 Dec 31  2018 
list:member:digest:masthead.txt
-rw-rw-r-- 1 mailman mailman  231 Apr 30  2020 
list:member:regular:footer.txt

-rw-r- 1 mailman mailman  688 Jan 21  2021 list:user:action:invite.txt
-rw-r- 1 mailman mailman  880 Jan 21  2021 
list:user:action:subscribe.txt
-rw-r- 1 mailman mailman  866 Jan 21  2021 
list:user:action:unsubscribe.txt

-rw-rw-r-- 1 mailman mailman  241 Dec 31  2018 list:user:notice:post.txt
-rw-rw-r-- 1 mailman mailman  804 Dec 31  2018 list:user:notice:probe.txt
-rw-rw-r-- 1 mailman mailman  633 Dec 31  2018 list:user:notice:welcome.txt
```

--
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/


[Mailman-Users] Re: What can cause "Munge From" (from_is_list) to have no effect?

2022-06-18 Thread Mark Sapiro

On 6/18/22 14:53, Mark Hills wrote:


Not the exact problem, but thanks for setting me on the right path.

There _was_ the following in mm_cfg.py for some time:

   GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('Approve'), 'SizeLimit')

I removed this completely and repeated the test; no change.



I would not expect that to have an effect.



It took me a while but I eventually worked out I needed to refresh the
pipeline of the individual lists, with something like:

   echo "del mlist.pipeline" | config_list -i /dev/stdin mylist

This command succeeded the first time; successive attempts failed with:

   AttributeError: MailList instance has no attribute 'pipeline'

which seems to suggest where was a list-specific pipeline, but no more.



Yes, and those list specific pipelines overrode mm_cfg.GLOBAL_PIPELINE 
and probably predated Mailman 2.1.16 and didn't include the WrapMessage 
handler.




So I think what's happened here is our lists ended up with a pipeline
definition fixed into each list. It's possibly someting from a series of
upgrades; there's never been a reason to want to maintain a separate
pipeline for each list (only to ensure the "SizeLimit" above applied to
all lists on the system.)



Possible in testing the SizeLimit handler you wound up setting list 
specific pipelines.




We have a script periodically using config_list to set "known good" values
on every list. To prevent the problem above happening again, I've added
the following:

   if hasattr(mlist, 'pipeline'):
 del mlist.pipeline



That shouldn't be necessary, but it won't hurt. Lists don't grow a 
pipeline attribute by themselves. You have to do something to set one.


--
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/