Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Disable user registration

by Mark Sapiro

On 3/20/21 1:22 PM, mailman3(a)digicrime.com wrote: > I believe that your patch was for the web front end, but that would still allow people to join by sending email to listname-join(a)example.com. We wouldn't be running any web interface anyway. I wanted to disable all methods of users joining and only rely upon an administrative process to handle who joins. It's easy to imagine a corporate use case for this, such as "all people with offices in building 43" or "all employees with dependents on health insurance" where the definition of who is on a list is maintained in an external system. We're not actually a corporation - we're a professional society with different member classes in our membership database. In any case, the decision of who belongs on a list is not made by the user. I understand these scenarios, but unless there is a high volume of spurious subscriptions, can't this be handled by setting the subscription police to include moderator approval? > In the interim I discovered another problem with DMARC failures in gmail when mail is sent through mailman3. Mail sent directly from our exim instance doesn't have this problem, so perhaps it's a problem with SRS. I won't be investigating this further, but I'm sure that SPF hard fails will be causing more problems for mailing lists in the future. SPF always fails DMARC alignment on forwarded mail, whether from a mailing list or other forwarding mechanism because even though SPF may pass, the domain is that of the forwarding server, not the original sender. While it is possible for a domain to set a DMARC policy and to rely only on SPF for validation, any domain with a DMARC policy should also be DKIM signing the mail because DKIM signatures will survive simple forwarding such as via .forward files or MTA aliases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: MM3 templates

by Mark Sapiro

On 2/15/23 23:04, Odhiambo Washington wrote: > > The last time I referred to the link, I deliberately duplicated the <LC> > folder in two locations: > [09:51 ~ ]$ ls -al /opt/mailman/mm/var/templates/site/en/ > total 48 > drwxr-xr-x 2 mailman mailman 512 Feb 14 08:53 . > drwxr-xr-x 3 mailman mailman 512 Feb 14 08:53 .. > -rw------- 1 mailman mailman 615 Jan 17 13:57 domain:admin:notice:new-list.txt > -rw------- 1 mailman mailman 341 Jan 17 13:54 list:admin:action:post.txt > -rw------- 1 mailman mailman 158 Dec 17 13:32 list:member:digest:footer.txt > -rw------- 1 mailman mailman 452 Jan 17 13:54 list:member:digest:masthead.txt > -rw------- 1 mailman mailman 137 Jan 17 13:55 list:member:generic:footer.txt > -rw------- 1 mailman mailman 1219 Dec 8 15:12 list:member:regular:footer.txt > -rw------- 1 mailman mailman 944 Jan 17 15:50 list:user:action:subscribe.txt > -rw------- 1 mailman mailman 247 Jan 17 13:56 list:user:notice:post.txt > -rw------- 1 mailman mailman 802 Jan 17 13:56 list:user:notice:probe.txt > -rw------- 1 mailman mailman 639 Jan 17 13:57 list:user:notice:welcome.txt > > Yet, it is NOT being picked. So definitely something is wrong somewhere. If you have the same list:* file in both /opt/mailman/mm/var/templates/site/en/ and /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ the ones in the lists directory will take precedence for that list over the ones in the site directory. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… for a discussion of the search order. >> >> Are the other templates such as list:member:regular:footer.txt used? >> > > I do see that in posts to the list, but I believe that is perhaps only > working because the list had that footer when it was imported from MM2. A template from import21 of the kictanet(a)lists.kictanet.or.ke list will be stored in the /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: how to administrate mailman3 in CLI ?

by Mark Sapiro

On 9/23/23 07:40, testeur via Mailman-users wrote: > > |# mailman shell -l testlist(a)domain.tld | It looks like you are running `mailman shell` as `root`. You should always run mailman commands including starting mailman as the Mailman user, never as root. Running thing as root can create things that later can't be read by the mailman user. > ||>>> from mailman.interfaces.action import Action >>> for mbr in > m.members.members: mbr.moderation_action = Action.defer |||commit()| > > |||>>> from mailman.interfaces.action import Action |||||||>>> english = > getUtility(ILanguageManager).get('en')| >>> for mbr in > m.members.members: || mbr.preferences.acknowledge_posts = False > mbr.preferences.delivery_mode = DeliveryMode.regular > mbr.preferences.delivery_status = DeliveryStatus.enabled > mbr.preferences.hide_address = False mbr.preferences.preferred_language > = english mbr.preferences.receive_list_copy = False > mbr.preferences.receive_own_postings = True|commit()|| I'm not sure what the above actually says. The interaction should look like ``` >>> from mailman.interfaces.action import Action >>> english = getUtility(ILanguageManager).get('en') >>> for mbr in m.members.members: ... mbr.preferences.acknowledge_posts = False ... mbr.preferences.delivery_mode = DeliveryMode.regular ... mbr.preferences.delivery_status = DeliveryStatus.enabled ... mbr.preferences.hide_address = False ... mbr.preferences.preferred_language = english ... mbr.preferences.receive_list_copy = False ... mbr.preferences.receive_own_postings = True ... >>> commit() ``` Actually, importing Action is not necessary as it is among the things defined by default in `mailman shell` in interactive mode. > Before the shell command, the web interface was with an other language > (i tested with italian one) and other options preferences, but after the > shell command, after a web interface refresh, it doesn't change. The above shell interaction sets the preferred_language for all list members to english. This has nothing to do with the language for the web UI. This is set by Django. See <https://docs.djangoproject.com/en/4.2/topics/i18n/translation/#how-django-d…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: rest api runner not running

by Mark Sapiro

On 3/27/21 5:13 AM, Christine wrote: > Hi, > I have been using mailman for about ten years, now I want to move the > lists to another server, I have installed mailman3 there, most of it > seems to be running, but the "rest api runner" is not. Nothing is > listening on port 8001. What have I missed? What do I do to start the > restapi runner? I checked the logs, I don't see anything suspicious. > > this is what systemctl status says: > > root@lists:~# systemctl status mailman3 > ● mailman3.service - Mailman3 server > Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; > vendor preset: enabled) > Active: failed (Result: timeout) since Sat 2021-03-27 12:04:06 UTC; > 6min ago > Docs: man:mailman(1) > https://mailman.readthedocs.io/ > Process: 173111 ExecStart=/usr/bin/mailman -C > /etc/mailman3/mailman.cfg start --force (code=killed, signal=TERM) > > Mar 27 12:02:36 lists systemd[1]: Starting Mailman3 server... > Mar 27 12:04:06 lists systemd[1]: mailman3.service: start operation > timed out. Terminating. > Mar 27 12:04:06 lists systemd[1]: mailman3.service: Failed with result > 'timeout'. > Mar 27 12:04:06 lists systemd[1]: Failed to start Mailman3 server. Nothing is listening on port 8001 because apparently Mailman core failed to start. > There is nothing in mailman.log, nor in smtp.log What Mailman package is installed? Perhaps you should contact the packager for support. Can you run the mailman command manually, e.g. ``` sudo -u xxx mailman -C /etc/mailman3/mailman.cfg ``` where `xxx` is the Mailman user which if I'm guessing correctly that this is a debian/ubuntu package, is `list`. Otherwise it might be `mailman`. That should just produce a list of `mailman` subcommands. If that works, try ``` sudo -u xxx mailman -C /etc/mailman3/mailman.cfg info ``` and ``` sudo -u xxx mailman -C /etc/mailman3/mailman.cfg start ``` and see what they produce. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: changeaddress command and nonmembers

by Mark Sapiro

On 2/2/23 09:28, Mike Wertheim wrote: > > Now that we're on Mailman 3 and the email list was migrated from MM2 to > MM3, we see that newaddress(a)gmail.com is a Member of the list, and we see > that oldaddress(a)hotmail.com is a NonMember of the list. That all makes > sense. > > But now, this person has decided that they actually want to go back to > using the old address. > > So I ran the command "mailman changeaddress newaddress(a)gmail.com > oldaddress(a)hotmail.com". But that gave me this output: > > Usage: mailman changeaddress [OPTIONS] OLD_ADDRESS NEW_ADDRESS > Try 'mailman changeaddress -h' for help. > > Error: Address oldaddress(a)hotmail.com already exists; can't change. > > > Can anyone explain how I can do what I'm trying to accomplish? The user needs to create an account in the web UI for newaddress(a)gmail.com and once that is done and she is logged in, she can add oldaddress(a)hotmail.com to her account. There are alternatives that you as list owner can do such as mass subscribing oldaddress(a)hotmail.com to the list and then disabling delivery to newaddress(a)gmail.com. There are also things you can do in `mailman shell` such as ``` $ mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> mbr = m.nonmembers.get_member('oldaddress(a)hotmail.com') >>> mbr.role = MemberRole.member >>> commit() ``` > (Also, why is this error displaying the usage message? That seems odd, > since the number and type of arguments was correct.) That's the way the `mailman` command works. All errors start with the usage. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Default values for lists in Mailman 3

by Mark Sapiro

On 9/19/24 05:46, Markus Grandpré wrote: > Dear list, > > I would like to activate the invitation setting for all lists as > default. In Mailman 2.1 I have done this in the file > </etc/mailman/mm_cfg.py>: > > > DEFAULT_SUBSCRIBE_OR_INVITE = Yes > > > How can I do this in Mailman 3? There is a draft merge request at https://gitlab.com/mailman/postorius/-/merge_requests/930 which implements a framework for setting Postorius defaults and creates a setting to set the default for pre-verified on the mass subscription page. Once merged, this can easily be extended to provide a default for Invitation. In the mean time, you can only do this by patching src/postorius/forms/list_forms.py like ``` --- a/src/postorius/forms/list_forms.py +++ b/src/postorius/forms/list_forms.py @@ -1283,7 +1283,7 @@ class ListMassSubscription(forms.Form): invitation = forms.BooleanField( label=_('Invitation'), - initial=False, + initial=True, required=False, help_text=_( 'If checked, the other checkboxes are ignored and the users will ' ``` > Can I also transfer other default values > like: > > ... > DEFAULT_SERVER_LANGUAGE = 'en' > DEFAULT_SEND_REMINDERS = 1 > DEFAULT_SUBSCRIBE_OR_INVITE = Yes > DEFAULT_PRIVATE_ROSTER = 2 > DEFAULT_ARCHIVE = Off > DEFAULT_ARCHIVE_PRIVATE = 1 > ... > > from the very same configuration file to Mailman 3? Is there a > documentation of the default values for lists in Mailman 3? This is done by creating a list style with the desired defaults. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/doc… for documentation of styles and see https://gitlab.com/mailman/example-mailman-plugin for an example of creating a plugin in Mailman core to make a persistent style. There is no specific doc for the list settings. You need to look at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/base.py for the various settings and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/default… to see which default classes are applied for various styles. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Pck files stuck in out queue

by Mark Sapiro

On 2/6/25 15:21, Lieuallen, Thomas Otis via Mailman-users wrote: > Mark, > > There were no apparent permissions problems on templates. I was getting the ‘Cannot connect to SMTP server’ message in mailman.log. > > I did end up applying the patch to decorate.py and messages went through. I’ve since removed the patch, as I’m still looking for an answer and might as well let it queue up again. Per the above, template access is definitely the problem. > The only thing that is making me ponder at the moment is that the list owners setup a template for list:member:regular:footer in postorius. It appears that each list has a copy of that file. The modifications I see in postorius are not in their …/templates/list/<listname>/en/list:member:regular:footer.txt file. Are their modifications stored somewhere else and causing the problem? Templates set in Postorius are stored in the database in the postorius_emailtemplate table. At the same time an entry is made in the template table with a uri to retrieve the template from a Postorius API. The uri is something like http(s)://host/mailman3/api/templates/list/LIST-ID/list:member:regular:footer where the http(s)://host part is from the setting for POSTORIUS_TEMPLATE_BASE_URL. The issue is that uri is not retrievable probably because the setting for POSTORIUS_TEMPLATE_BASE_URL is wrong. You should look at the uris in the template table in the database and figure out what they should be, probably by trying to retrieve one in a browser with the scheme and host what you actually use to access Postorius. Once you figure out what the correct uri is you can set POSTORIUS_TEMPLATE_BASE_URL appropriately, but this won't fix the existing template table entries. You can fix those manually in the database or you can delete and recreate the templates in Postorius after fixing POSTORIUS_TEMPLATE_BASE_URL and restarting the Mailman web service. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Mass subscribe gives HTTP Error 500 when using custom template

by Mark Sapiro

On 1/28/20 6:15 AM, Jeffrey D wrote: > Hi, > > I have some issues with the Mass Subscribe option on Mailman 3.2.1. When using a custom "The notice sent to a member when they are subscribed to the mailing list." template, Postorius will throw an exception after pushing the "Subscribe Users" button on Mass Subscribe. ... > requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /postorius/api/templates/list/<MAILINGLIST>/list:user:notice:welcome (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f0b5ce8d8d0>: Failed to establish a new connection: [Errno 111] Connection refused')) > > Postorius/Mailman is running on port 8001, only Postorius still connecting on port 8000. What is your setting in settings(_local).py for POSTORIUS_TEMPLATE_BASE_URL? It looks like you have the default POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' It should be the base URL for connecting to Postorius. I.e., if you normally connect to Postorius via https://www.example.com/postorius, it should be https://www.example.com You say Postorius/Mailman is running on port 8001. Mailman core's rest server should be listening on port 8001, but your web server can't proxy to Postorius on that port. Normally, the wsgi server that supports wsgi access to Django (Postorius and HyperKitty) listens on port 8000, at least if it is gunicorn or uwsgi proxied from your web server, or if it's Apache and mod_wsgi, proxying is not involved. Again, it looks like you may be using Apache and mod_wsgi in which case you could have POSTORIUS_TEMPLATE_BASE_URL set to something like https://www.example.com or even http://localhost or http://localhost:80, but not port 8000 if no wsgi server is listening there. Also, the URL is now in the database entry for this template in the postorius_emailtemplate table, so even after you fix POSTORIUS_TEMPLATE_BASE_URL, you'll probably have to delete and recreate the template in Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/21/20 7:52 PM, Alan So wrote: > > Since the CC header remains unchanged if we test using "mailman inject", we may further check whether Mailman LMTP Runner change the CC header. You are correct. If I post your test via email rather than `mailman inject`, I see the issue. I'm working on figuring out why. (Sorry for spamming you with test Ccs.) I'm at a loss to explain why `mailman inject` doesn't show this. I have captured the queued message and the only differences I see between the one from the lmtp runner and the one from inject is the one from lmtp runner has an X-MailFrom: header and 'received_time': datetime.datetime(2020, 5, 22, 3, 45, 24, 532711), 'to_list': True, and I even tried running `mailman inject` with `-m to_list=True` and it still didn't fail. However, if I take the qfile that dumps as ``` > $ bin/mailman qfile 1590119124.5909426+9a002936a59e194f70187405ac624173cbf470b5.pck > [----- start pickle -----] > <----- start object 1 -----> > Received: by msapiro.net (Postfix, from userid 1000) > id 60624340253; Thu, 21 May 2020 20:45:24 -0700 (PDT) > From: mark(a)msapiro.net > To: list(a)example.com > CC: "ABC DEF > (XYZ)" <mark(a)msapiro.net> > Subject: testing please ignore > Message-ID: <something_more(a)example.net> > Date: Fri, 22 May 2020 09:53:58 +0800 (HKT) > Message-ID-Hash: NDG3FHLPO35F2Y4YXFAKFIKDXAC6FHGM > X-Message-ID-Hash: NDG3FHLPO35F2Y4YXFAKFIKDXAC6FHGM > X-MailFrom: mark(a)msapiro.net > > hello > > <----- start object 2 -----> > { '_parsemsg': False, > 'listid': 'list.example.com', > 'original_size': 326, > 'received_time': datetime.datetime(2020, 5, 22, 3, 45, 24, 532711), > 'to_list': True, > 'version': 3} > [----- end pickle -----] ``` and put it in the 'in' queue the received message from the list does contain CC: XYZ <ABCDEF(a)msapiro.net> Thus, the issue occurs downstream of lmtp runner. It will take more investigation to determine where. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list

by Mark Sapiro

On 9/30/20 9:25 AM, Mohsen Masoudfar wrote: > Hi, > > I am trying to find a way for content filtering to remove executables from the emails sent to the list. I found some hints under: > https://mailman.readthedocs.io/en/stable/build/lib/mailman/handlers/docs/fi… > > but still not clear how to do it for all type of excecutables. There are four list settings that affect this. They are pass_types, pass_extensions, filter_types and filter_extensions. the pass_* settings specify message parts the list will accept while the filter_* settings specify message parts the list won't accept. The page at <https://mailman.readthedocs.io/en/stable/src/mailman/handlers/docs/filterin…> only discusses filter_types and needs updating for the others. Filtering by extension only works on message parts that have an associated file name. Thus, while you can add things like 'exe', 'bat', 'cmd', 'com', 'pif', 'scr', 'vbs' and 'cpl' to filter_extensions, it won't be completely effective. A better approach is to use MIME types[1] and only allow those you want. For a discussion list, a reasonable set is what this list uses: multipart message/rfc822 text application/pgp-signature This will accept any multipart and message/rfc822 parts for further analysis and ultimately accept only text/* and application/pgp-signature elemental parts. If you want to accept images and pdfs, you can add image application/pdf See <https://www.iana.org/assignments/media-types/media-types.xhtml> for a list of all registered MIME types. Note that these are all of the form main_type/sub_type and putting just main_type in *_types passes or filters all subtypes for that maintype. [1] You can use both, e.g. filter_extensions to remove those you don't want and pass_types to accept the MIME types you do want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

Search results for query "sapiro"