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

[MM3-users] Re: Could not locate column in row for column 'user.id'

by Mark Sapiro

On 7/27/20 2:48 AM, Shashikanth Komandoor wrote: > Hi Mark, > > Thank you for your response. And sorry for not giving you > complete information as I am not sue what to share with you. > > I am using Postgresql-11.7 as my backend database. The below is > the structure of the address table in* mailman *database: > > mailman=# \d address; > Table "public.address" > Column | Type | Collation | Nullable | > Default > ----------------+-----------------------------+-----------+----------+------------------------------------- > id | integer | | not null | > nextval('address_id_seq'::regclass) > email | character varying | | | > _original | character varying | | | > display_name | character varying | | | > verified_on | timestamp without time zone | | | > registered_on | timestamp without time zone | | | > user_id | integer | | | > preferences_id | integer | | | > Indexes: > "address_pkey" PRIMARY KEY, btree (id) > "ix_address_email" UNIQUE, btree (email) > "ix_address_preferences_id" btree (preferences_id) > "ix_address_user_id" btree (user_id) > Foreign-key constraints: > "address_preferences_id_fkey" FOREIGN KEY (preferences_id) REFERENCES > preferences(id) > "address_user_id_fkey" FOREIGN KEY (user_id) REFERENCES "user"(id) > Referenced by: > TABLE ""user"" CONSTRAINT "_preferred_address" FOREIGN KEY > (_preferred_address_id) REFERENCES address(id) ON DELETE SET NULL > TABLE "autoresponserecord" CONSTRAINT > "autoresponserecord_address_id_fkey" FOREIGN KEY (address_id) REFERENCES > address(id) > TABLE "member" CONSTRAINT "member_address_id_fkey" FOREIGN KEY > (address_id) REFERENCES address(id) > TABLE "onelastdigest" CONSTRAINT "onelastdigest_address_id_fkey" > FOREIGN KEY (address_id) REFERENCES address(id) > > The below is the structure of *user* table: > > mailman=# \d user; > Table "public.user" > Column | Type | Collation | Nullable > | Default > -----------------------+-----------------------------+-----------+----------+---------------------------------- > id | integer | | not null > | nextval('user_id_seq'::regclass) > display_name | character varying | | > | > password | character varying | | > | > _user_id | uuid | | > | > _created_on | timestamp without time zone | | > | > is_server_owner | boolean | | > | > _preferred_address_id | integer | | > | > preferences_id | integer | | > | > Indexes: > "user_pkey" PRIMARY KEY, btree (id) > "ix_user__user_id" btree (_user_id) > "ix_user_preferences_id" btree (preferences_id) > Foreign-key constraints: > "_preferred_address" FOREIGN KEY (_preferred_address_id) REFERENCES > address(id) ON DELETE SET NULL > "user_preferences_id_fkey" FOREIGN KEY (preferences_id) REFERENCES > preferences(id) > Referenced by: > TABLE "address" CONSTRAINT "address_user_id_fkey" FOREIGN KEY (user_id) > REFERENCES "user"(id) > TABLE "domain_owner" CONSTRAINT "domain_owner_user_id_fkey" FOREIGN KEY > (user_id) REFERENCES "user"(id) > TABLE "member" CONSTRAINT "member_user_id_fkey" FOREIGN KEY (user_id) > REFERENCES "user"(id) > > mailman=# \dn > List of schemas > Name | Owner > --------+---------- > public | postgres > (1 row) > > mailman=# select * from user; > user > ---------- > postgres > (1 row) > > *The above command output is not showing any fields. But if use the table > as public.user (schema.tablename) with select command, it is showing the > data. But without schema name this table is not showing those fields. Not > sure if this the expected behavior or not.* This is expected. psql gets confused because it has its own user table. The above table definitions look fine. Is there any entry in the `address` table for which `id` is not an integer? -- 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

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 11:56 AM, David Newman wrote: > > I created a pending subscription request on a test list. Here is the > text I'm using in a file called 'list:admin:action:subscribe.txt' (minus > the rows of hypens): > > ---------- > > > As list administrator, your authorization is required for a mailing list > subscription request approval: > > For: $member > List: $listname > > At your convenience, visit: > > https://${domain}/mailman/admindb/lists/${short_listname}.${domain}/ This looks like a Mailman 2.1 URL. Are you sure you don't want something like https://${domain}/mailman3/lists/${short_listname}.${domain}/ > > to approve or deny the request. > > ---------- > > Instead the message that goes out at midnight daily reads like this: That's a different message. It is sent from the `mailman notify` command run by cron. It's built from the list:admin:notice:pending template. > > On successive nights I have placed copies of the > 'list:admin:action:subscribe.txt' file above in these locations: > > mm/var/templates/lists/test.lists.domain.tld/en I hope you mean /opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en > /opt/mailman/mm/var/templates/site/en Either of those should work. The lists one will take priority over the site one for that list. > and then in Postorius, with the same contents as above. If you set a template in Postorius, it takes priority. If you later decide you want to use one in /opt/mailman/mm/var/templates/ you have to delete the postorius one. > The file > versions are owned by the mailman user, and have 0644 permissions. Not > sure this is necessary but I've restarted the mailman3 and mailmanweb > services each time after a change. > > There is no sign of trouble in the MM3 or web logs. The only thing I see > is in the Postfix log, where the shorter and less helpful message goes > out each night. I don't see anything in the template docs about this. > > Questions: > > 1. What to do to get the custom message working? It should work. I suspect you need to go to the list's Settings -> Automatic Responses and set `Admin immed notify` to Yes. > 2. Is there a way to trigger a subscribe reminder for one list only? If by subscribe reminder you mean the `list:admin:action:subscribe.txt` message, yes that's the above list setting. If you mean the one sent from the `mailman notify` command, see `mailman notify --help` for the options. You can specify one or more lists (default is all lists) via options and put them in your cron. > Asking because there are other lists on this server with other requests > pending, and I don't want to bother other moderators with multiple > reminders per day. Not a big deal, but it would be nice to test this > with one list rather than waiting up to 24 hours after each change. You can test `mailman notify` at any time by running it by hand. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Christian Stalberg

Yes, I have django_mailman3/templatetags/d_gravatar.py in my installation. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, October 13, 2021 5:11 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ On 10/13/21 3:53 PM, Christian Stalberg via Mailman-users wrote: > Is this anything to be concerned about? It seems like an attempted break-in as I have no user named alekos.pantazis. First, this is a Django user, not a Mailman user. > -----Original Message----- > From: noreply(a)lists.ccalternatives.org > <noreply(a)lists.ccalternatives.org> > Sent: Tuesday, October 12, 2021 7:55 AM > To: csa(a)web-analysts.net > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: > /user-profile/ > > Internal Server Error: /user-profile/ > > TemplateSyntaxError at /user-profile/ > 'd_gravatar' is not a registered tag library. Must be one of: The d_gravatar template tag was introduced by https://gitlab.com/mailman/django-mailman3/-/merge_requests/114 to support the `HYPERKITTY_ENABLE_GRAVATAR = False` setting for the user profile page. It should be OK. The error you see seems to say that django_mailman3/templates/django_mailman3/profile/profile.py contains {% load gravatar %} at line 3 but there is no django_mailman3/templatetags/d_gravatar.py file. Do you have the django_mailman3/templatetags/d_gravatar.py file in your installation? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 1 month

[MM3-users] Re: Clean-up of non-members

by Odhiambo Washington

On Tue, Dec 24, 2024 at 8:39 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/24/24 08:13, Odhiambo Washington via Mailman-users wrote: > > On Mon, Dec 23, 2024 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> I saw that too. Reported > >> https://gitlab.com/mailman/mailman/-/issues/1187 and fixed > >> https://gitlab.com/mailman/mailman/-/merge_requests/1297 > > > > > > It isn't clear to me what I should do to mitigate the error. > > > Apply this patch: > ``` > --- a/src/mailman/commands/cli_members.py > +++ b/src/mailman/commands/cli_members.py > @@ -103,7 +103,12 @@ def display_members(ctx, mlist, role, regular, digest, > if nomail is not None: > if member.delivery_status not in status_types: > continue > - dn = address.display_name or member.user.display_name > + # Non-members may have empty address.display_name and > member.user can > + # be None resulting in AttributeError on member.user.display_name. > + try: > + dn = address.display_name or member.user.display_name > + except AttributeError: > + dn = '' > if email_only or not dn: > print(address.original_email, file=outfp) > else: > ``` > Thank you. Now only if you can help me reconcile the fact that Postorius tells me that I have ``` List Nonmembers (872) ``` ..while the CLI command gives me only 13 addresses. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

11 months, 2 weeks

[MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails - Hyperkitty - CERT Issue

by Willie Castillo

Got it. Is there a command that one can manually run to test/expedite the process? ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, July 28, 2025 12:11 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [NON-INTERNAL] [MM3-users] Re: Missing Archived emails - Hyperkitty - CERT Issue CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 7/28/25 7:07 AM, willie.castillo(a)caemilusa.com wrote: > Looks like "hyperkitty" stopped archiving right after the CERT for the mailman3 website expired, How can I make the missing archives visible on the website? I see there "*pck" files in the/opt/mailman/mm/var/archives/hyperkitty/spool/ directory. The list archive does not show that last posting [of 25 July 2025. > > ~$ ll -t /opt/mailman/mm/var/archives/hyperkitty/spool/ > -rw-rw---- 1 mailman mailman 98215 Jul 25 12:01 1753459289.7901242+f3fd7ee77272862f8c1023394bf88d0d4bbe9053.pck > -rw-rw---- 1 mailman mailman 98109 Jul 25 12:01 1753459289.7726512+ee1264c36a194eb0ec1a52089f053e6963f24369.pck > -rw-rw---- 1 mailman mailman 88479 Jul 25 12:01 1753459289.7564857+2e27f35a57f757f058dc95e34c56722a76307900.pck > > The CERT on the website is now up-to-date Those queued messages will be reprocessed on the next post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://urldefense.us/v3/__https://lists.mailman3.org/mailman3/lists/mailma… Archived at: https://urldefense.us/v3/__https://lists.mailman3.org/archives/list/mailman… This message sent to willie.castillo(a)caemilusa.com

4 months, 2 weeks

[MM3-users] Re: Mailman 3 Installation

by Mark Sapiro

On 1/16/21 6:06 PM, bruce.dubbs(a)gmail.com wrote: > I am trying to set up Mailman 3 on a new server. So far I have run: > > pip3 install Django==3.1.5 This will be a minor issue. django-mailman3 requires Django>=2.0,<3.2; HyperKitty requires Django>=2.2,<3.2, but postorius requires Django>=1.11,<3.1. We really should be more consistent with these requirements, but what this means is > pip3 install postorius will install Django 3.0.11 alongside Django 3.1.5. > pip3 install Hyperkitty > pip3 install mailman > pip3 install uwsgi > > All that went well. I've been struggling with the configuration though. I am using /etc/mailman.cfg and that seems to be explained in the documentation OK. From there I am confused. > > I do have sqlite installed, but the documentation discusses mysql/mariadb and postresql. What are the considerations as to why I would need one of these other DBs? You can use sqlite, but if you don't already have a mysql/mariadb database on the server, we recommend postgresql for performance and robustness. I personally have had issues with mysql and use postgresql on one production server that uses mysql for other applications. > I think I can follow the instructions to set up postfix. > > In the section 'Configure Web Frontend', it discusses setting up the administrator. As I want to put Mailman on /srv/mailman I can create that, but what should the owner/permissions be? Later the docs discuss editing Django's settings.py. Where do I find that file? I'll note here that my experience with python is quite limited and my knowledge of Django is nil. There should be a 'mailman' user that is the user under which you run things. Don't run things as root. sudo chown -R mailman:mailman /srv/mailman For settings.py and some others, see <https://gitlab.com/mailman/mailman-suite/-/tree/master/mailman-suite_project>. The end of settings.py imports from settings_local so you put your local overrides in settings_local.py in the same directory as settings.py > Later in the section 'Set up HyperKitty', it sends me to a page that discusses installing it. I did that with pip3. Then it says to 'Setup your django project'. What django project is that. Postorius and HyperKitty. See settings.py. These files, settings.py and settings_local.py need to be in a directory that also includes an empty __init__.py so python can import from it and this directory needs to be in the path that Django runs with. This is a shell script I use to run django. It uses a virtualenv, but that isn't necessary. Also my stuff is in /opt/mailman/mm/, but it could just as well be /srv/mailman. #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ > I would appreciate advice or a pointer to where I can figure this out. Thanks. There is a work in progress you may find more helpful. See <https://gitlab.com/mailman/mailman-suite-doc/-/merge_requests/55#note_48712…> and the 'Rendered documentation' linked therefrom. You might also find <https://wiki.list.org/x/17891998> and/or the docs linked from its first paragraph to be helpful. -- 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: Installing mailman 3

by Rafael Mora

I want to use Mailman to send emails to our customers. I´m getting this error when I click on sign up and log in: FilterError at /accounts/login/ /bin/sh: sassc: command not found Request Method: GET Request URL: http://192.168.1.42:8000/accounts/login/?next=/postorius/lists/ Django Version: 1.11.3 Exception Type: FilterError Exception Value: /bin/sh: sassc: command not found Exception Location: /var/lib/mailman/env2/lib/python2.7/site-packages/compressor/filters/base.py in input, line 196 Python Executable: /var/lib/mailman/env2/bin/python2 Python Version: 2.7.5 What's missing??? El vie., 21 jul. 2017 a las 19:57, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 04:57 PM, Rafael Mora wrote: > > Should Sign Up ?? Log In?? > > > Yes. > > > > El vie., 21 jul. 2017 a las 18:56, Rafael Mora (< > rafael.mora.guti(a)gmail.com>) > > escribió: > > > >> Nice! Up and running! > >> > >> How do I start using mailman? what are the steps?? > > > What do you want to do with Mailman? This is the key question. > > There is some list subscriber documentation at > <http://docs.list.org/en/latest/userguide.html>. > > You can create domains and lists via Postorius or via the core's > bin/mailman commands ('bin/mailman --help' for a list). > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 4 months

[MM3-users] Re: Lessons learned and a couple little gotcha for newbies

by William Oliver

On Tue, 2021-12-28 at 20:05 -0800, Mark Sapiro wrote: > On 12/28/21 5:58 PM, William Oliver wrote: > > On Tue, 2021-12-28 at 17:50 -0800, Mark Sapiro wrote: > > > The recommended uwsgi.ini includes > > > > > > pythonpath = /etc/mailman3/ > > > > > > according to > > > https://uwsgi-docs.readthedocs.io/en/latest/Options.html?highlight=pythonpa… > > > > > > this should work. Did you have that? If you did and it doesn't > > > work, > > > perhaps adding > > > > > > env = PYTHONPATH=/etc/mailman3 > > > > > > > Yes, I had the first, and does not work. The second entry works. > > > I updated the doc to use > > env = PYTHONPATH=/etc/mailman3 > > I don't know enough about uwsgi to know for sure, but the issue may > be > that setting pythonpath in a running python process doesn't work - > it's > too late as the path is already set in python's initialization. > You might add that it may be necessary to do it in .bashrc for linux folk -- I got it to work but as I've demonstrated, I can sometimes make mistakes and leave detritus around. I may not have successfully cleared my previous setting. That being said, I think it works. I am, I am afraid not a details-oriented guy, which is a bit of a drawback for someone doing system admin...

3 years, 11 months

[MM3-users] Re: 'str' object has no attribute 'token_type'

by Mark Sapiro

On 11/15/21 6:06 AM, Marco Marinello wrote: > Hi everybody, > > I'm sorry for being always the strange guy with strange errors here but for some reason... I am. > On a Mailman installation that was doing just fine for more than a year, I started receiving error messages per email. It happens when mailman daemon archives a messages. Although the messages is correctly archived, this exception is thrown by Hyperkitty: > > > Traceback (most recent call last): > File "/usr/local/lib/python3.9/dist-packages/django/core/handlers/exception.py", line 47, in inner > response = get_response(request) > File "/usr/local/lib/python3.9/dist-packages/django/core/handlers/base.py", line 181, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/local/lib/python3.9/dist-packages/django/views/decorators/http.py", line 40, in inner > return func(request, *args, **kwargs) > File "/usr/local/lib/python3.9/dist-packages/hyperkitty/views/mailman.py", line 118, in _decorator > return func(request, *args, **kwargs) > File "/usr/local/lib/python3.9/dist-packages/django/views/decorators/csrf.py", line 54, in wrapped_view > return view_func(*args, **kwargs) > File "/usr/local/lib/python3.9/dist-packages/hyperkitty/views/mailman.py", line 164, in archive > add_to_list(mlist_fqdn, msg) > File "/usr/local/lib/python3.9/dist-packages/hyperkitty/lib/incoming.py", line 79, in add_to_list > from_str = header_to_unicode(message['From']) > File "/usr/lib/python3.9/email/message.py", line 391, in __getitem__ > the values matching a header field name. > File "/usr/lib/python3.9/email/message.py", line 471, in get > for k, v in self._headers: > File "/usr/lib/python3.9/email/policy.py", line 163, in header_fetch_parse > return self.header_factory(name, value) > File "/usr/lib/python3.9/email/headerregistry.py", line 601, in __call__ > return self[name](name, value) > File "/usr/lib/python3.9/email/headerregistry.py", line 196, in __new__ > cls.parse(value, kwds) > File "/usr/lib/python3.9/email/headerregistry.py", line 343, in parse > [Address(mb.display_name or '', > File "/usr/lib/python3.9/email/headerregistry.py", line 343, in <listcomp> > [Address(mb.display_name or '', > File "/usr/lib/python3.9/email/_header_value_parser.py", line 462, in display_name > return self[0].display_name > File "/usr/lib/python3.9/email/_header_value_parser.py", line 393, in display_name > return self[0].display_name > File "/usr/lib/python3.9/email/_header_value_parser.py", line 574, in display_name > if res[-1][-1].token_type == 'cfws': > > Exception Type: AttributeError at /hyperkitty/api/mailman/archive > Exception Value: 'str' object has no attribute 'token_type' > Request information: > USER: AnonymousUser > > > I upgraded both to Debian 11 (from 10) and to latest versions of Hyperkitty, mailman-hyperkitty and mailman but still getting the error. Other installations with same specs I'm managing to do not encounter this problem. > Any clue of what could have happened, why and how to fix it? The exception is thrown in the Python email package on HyperKitty's attempt to get the From: header of the message. This looks like https://bugs.python.org/issue43501 and/or https://bugs.python.org/issue30988. These issues refer to display names beginning or ending with a dot. Is that the case with the From: header of the problem messages? Note that display names containing dot should be quoted. It appears that at least one of the people posting posts with the problem From: header. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Installing mailman 3

by Rafael Mora

my mailman.cfg file is: # AUTOMATICALLY GENERATED BY MAILMAN ON 2017-07-16 20:44:24 UTC # # This is your GNU Mailman 3 configuration file. You can edit this file to # configure Mailman to your needs, and Mailman will never overwrite it. # Additional configuration information is available here: # # http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html # # For example, uncomment the following lines to run Mailman in developer mode. # # [devmode] # enabled: yes # recipient: your.address(a)your.domain #[mailman] #layout: fhs [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix my mailman.config.postfix file is: [postfix] transport_file_type: regex are they ok? El mar., 1 ago. 2017 a las 15:10, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 12:52 PM, Rafael Mora wrote: > > I made a change for test purpose on the mailman.cfg file and I got this: > > > > > > (env) [mailman@localhost etc]$ mailman restart > > Restarting the Mailman runners > > PID unreadable in: /var/lib/mailman/var/etc/var/master.pid > > [Errno 2] No such file or directory: > > '/var/lib/mailman/var/etc/var/master.pid' > > Is the master even running? > > > > How do I solve this? > > > Try > > mailman stop > mailman start > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 4 months

[MM3-users] Re: Docker Support Sucks

by Mark Sapiro

On 7/21/20 6:31 PM, Brian Carpenter wrote: > > This is with the configuration line enabled in mailman-extra.cfg: > > # docker-compose restart mailman-core > Restarting mailman-core ... done > [root@nicu-net docker-mailman]# tail -f > /opt/mailman/core/var/logs/mailman.log > Jul 22 01:25:17 2020 (22) in runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (25) out runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (25) out runner exiting. > Jul 22 01:25:17 2020 (21) command runner exiting. > Jul 22 01:25:17 2020 (22) in runner exiting. > Jul 22 01:25:17 2020 (24) nntp runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (24) nntp runner exiting. > [2020-07-22 01:25:19 +0000] [27] [INFO] Shutting down: Master > Jul 22 01:25:21 2020 (1) Master stopped > Jul 22 01:25:26 2020 (1) Master started > Jul 22 01:25:44 2020 (27) rest runner started. > Jul 22 01:25:44 2020 (26) pipeline runner started. > Jul 22 01:25:44 2020 (20) bounces runner started. > Jul 22 01:25:45 2020 (22) in runner started. > Jul 22 01:25:45 2020 (28) retry runner started. > Jul 22 01:25:46 2020 (29) virgin runner started. > Jul 22 01:25:46 2020 (25) out runner started. > Jul 22 01:25:46 2020 (23) lmtp runner started. > Jul 22 01:25:46 2020 (24) nntp runner started. > Jul 22 01:25:47 2020 (30) digest runner started. > Jul 22 01:25:47 2020 (19) archive runner started. > Jul 22 01:25:47 2020 (21) command runner started. > > This is with the configuration line disabled in mailman-extra.cfg: > > # docker-compose restart mailman-core > Restarting mailman-core ... done > [root@nicu-net docker-mailman]# tail -f > /opt/mailman/core/var/logs/mailman.log > Jul 22 01:27:49 2020 (1) Master stopped > Jul 22 01:27:53 2020 (1) Master started > Jul 22 01:28:10 2020 (30) digest runner started. > Jul 22 01:28:10 2020 (29) virgin runner started. > Jul 22 01:28:10 2020 (24) nntp runner started. > Jul 22 01:28:10 2020 (25) out runner started. > Jul 22 01:28:10 2020 (22) in runner started. > Jul 22 01:28:11 2020 (28) retry runner started. > Jul 22 01:28:11 2020 (27) rest runner started. > [2020-07-22 01:28:11 +0000] [27] [INFO] Starting gunicorn 19.9.0 > [2020-07-22 01:28:11 +0000] [27] [INFO] Listening at: > http://172.19.199.2:8001 (27) > [2020-07-22 01:28:11 +0000] [27] [INFO] Using worker: sync > [2020-07-22 01:28:11 +0000] [32] [INFO] Booting worker with pid: 32 > [2020-07-22 01:28:11 +0000] [33] [INFO] Booting worker with pid: 33 > [2020-07-22 01:28:11 +0000] [34] [INFO] Booting worker with pid: 34 > [2020-07-22 01:28:11 +0000] [35] [INFO] Booting worker with pid: 35 > Jul 22 01:28:11 2020 (19) archive runner started. > Jul 22 01:28:11 2020 (21) command runner started. > Jul 22 01:28:12 2020 (23) lmtp runner started. > Jul 22 01:28:12 2020 (20) bounces runner started. > Jul 22 01:28:12 2020 (26) pipeline runner started. > Is there perhaps some permissions issue in reading your added gonicorn.cfg? Also, note that gunicorn is set-up to log to the logging.http path, the default for which is mailman.log in the configured log_dir, but if this is changed to something other than mailman.log (see `mailman conf -k path -s logging.http`), it could be elsewhere. I'd expect gunicorn to log something if it couldn't start. Also, as Alan Hansen notes, you can export a list of members with `mailman members` -- 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

[MM3-users] Re: spanish localization

by Abhilash Raj

On Sat, Feb 13, 2021, at 9:26 PM, Mark Sapiro wrote: > On 2/13/21 5:42 PM, Abhilash Raj wrote: > > > > You can actually translate the templates in Weblate too. That is > > actually the whole > > reason to go with monolingual template format in Mailman Core. > > > > Mailman uses the template file's name as the msgid for translations and > > all in-tree > > templates are copied into English's .po file when we re-generate them. > > > > For example in here: > > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC… > > > > > > The english .po file is considered as reference in Weblate and used for > > source string. > > > But it appears that we are lacking a mechanism (other than some manual > process which isn't reliably done) to move the translated templates from > the translated .po file to the appropriate templates/<lc>/ directory. Yeah, you are absolutely right. I thought in my head that I had modified the lookup mechanism to use gettext for in-source templates, but that doesn't seem to be the case. https://gitlab.com/mailman/mailman/-/issues/825 I have opened an issue to track that. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 9 months

[MM3-users] Re: Trying to set up mailman3 on my mail server

by Mark Sapiro

On 10/14/21 7:51 PM, Shawn Heisey wrote: > I'm having a lot of trouble with trying to set up mailman3 on my mail > server. > > It's on an AWS instance, running Ubuntu 20.04 LTS. All software is > installed from Ubuntu packages. Mailman version is 3.2.2. Please see <https://wiki.list.org/x/12812344>[1] > The problem I am trying to troubleshoot first is how this can be happening: > > Oct 14 11:27:26 2021 (2341) ACCEPT: > <f36e1ed0-9d25-b661-9c94-4ce999f6d5fd(a)elyograg.org> > Oct 14 11:27:27 2021 (2344) Cannot connect to SMTP server 127.0.0.1 on > port 25 > > From the shell, I can "telnet localhost 25" successfully, even as the > "list" user. Apparmor is disabled. The UFW firewall is enabled, which > allows all traffic on the loopback interface. I disabled ipv6 at the > kernel level, but had the same problem with ipv6 enabled, so I don't > think ipv6 is related at all. I do not see any connections in the > postfix log that correspond to the mailman connection error. There's a long thread on this at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. Your issue may not be the same, but that one had to do with templates, perhaps created in Postorius, that couldn't be accessed. > From a fresh install of mailman, I created two mailing lists. Once upon > a time I had those lists active on a Debian 6 machine running mailman > 2.1.13 ... I copied the mailing list config from that machine over and > used the "import21" facility to import the configuration into the new > mailman3 install. That worked without error and I can see the lists and > their members with the "mailman" command. I found instructions for > integration with postfix, and added the required three config lines to > the postfix config. > > When I try to send a message to the list, I get what I pasted above in > the mailman log. I think that means the postfix integration is working, > and is forwarding to mailman. Yes, and the message should be archived in whatever archivers are enabled. If the prototype archiver is enabled you should see the message in Mailman's var/archives/prototype/<list-id>/new/ directory and if HyperKitty is enabled, in mailman's database in the hyperkitty_email table. > I'm hoping somebody can give me some pointers, and if more information > is needed for troubleshooting, let me know what is needed. If your web UI isn't working, you probably haven't created any templates in Postorius, but import21 will create templates and if you ran import21 as root, you may have created templates and perhaps other things that can't be accessed by the Mailman user (`list` in your case). All Mailman related commands should be run only by the Mailman user. [1] This FAQ says you should be going to Debian/Ubuntu for support. If you've tried that and are not getting help there, I respectfully submit that you should purge the Debian/Ubuntu package and start over from here <https://docs.mailman3.org/en/latest/install/virtualenv.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: How to let mailman log every single email that it sends out?

by Mohsen Masoudfar

Thank you, Mark, but Sorry, I don't see them there. I read that the mta log level should be set to debug in order to see them. When I send an email to a list with +3000 subscribers and need to see in the log email has been sent to each of those email addresses Thanks Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, September 8, 2023 3:58:10 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: How to let mailman log every single email that it sends out? [EXTERNAL EMAIL] On 9/8/23 12:41, Mohsen Masoudfar wrote: > > I'm curious about the configuration required to have Mailman record logs for every individual email it sends. I see that it sends to the entire list, but I'm interested in obtaining log entries for each email sent to every individual subscriber on the list. > How can I access this information? > > Is it a postfix setting, or a Mailman3 setting? > I have checked /var/log/mail.log and all the logs under /var/log/Mailman3/* > Mailman is running on Ubuntu 18.3 You should see the information about the mail being sent an delivered to recipient MX servers in /var/log/mail.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

2 years, 3 months

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/26/21 3:06 PM, William Oliver wrote: > > When running mailman3, do I need to set up a completely different > virtual domain for it to run in? No. > My "real" domain name is > libertyfp.org, and I'm trying to make mailman work on that domain, e.g. > "testlist(a)libertyfp.org." I'm starting to get the idea that I need to > stick a completely different domain in there for the mailinglist. No. However, in Postfix, libertyfp.org is a virtual_mailbox_domain so you have to use an alias domain in Mailman. An alias domain is not a real domain. It is only known to Mailman and Postfix. It is not exposed in DNS or anywhere outside your server. Have you actually set an alias domain in Postorius for the libertyfp.org domain. It doesn't matter what name it is as long as it isn't a real domain. A good choice is x.libertyfp.org. Have you set that or something similar? If you do and run `mailman aliases` you should get things like testlist(a)libertyfp.org testlist(a)x.libertyfp.org testlist-bounces(a)libertyfp.org testlist-bounces(a)x.libertyfp.org testlist-confirm(a)libertyfp.org testlist-confirm(a)x.libertyfp.org ... in postfix_vmap and things like testlist(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-bounces(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-confirm(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 ... in postfix_lmtp > Which I can do -- I've got another two or three domain names to play > with. Is it a problem to run the mailinglist on the same domain that > the machine sits on for its regular business? A lot of the errors I'm > getting seem to be from trying to do regular mail *and* the mailinglist > on the same domain. > > Now that I've installed all this stuff a couple of times, I can easily > re-install for a second virtual domain, if that's what I should be > doing. > > But, on to what's not working now... > > Unfortunately, I seem to have completely screwed the pooch on getting > postfix/dovecot to play nicely with respect to *receiving* mail. > > First, adding "virtual_alias_domains" (and putting libertyfp.org in it) > and commenting out "virtual_mailbox_domains" resulted in postfix > ignoring all my virtual mailboxes. Don't do that. Leave libertyfp.org as a virtual_mailbox_domain and don't set it as a virtual_alias_domain. I think that should work., but you may need to add hash:hash:/opt/mailman/mm/var/data/postfix_vmap to virtual_mailbox_maps instead of virtual_alias_maps. ... > # mailman3 changes > > owner_request_special = no > always_add_missing_headers = yes > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/opt/mailman/mm/var/data/postfix_lmtp You shouldn't need to add hash:/opt/mailman/mm/var/data/postfix_lmtp to local_recipient_maps, but it probably doesn't hurt. > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains > default_destination_recipient_limit = 30 > default_destination_concurrency_limit = 15 > virtual_alias_domains = hash:/etc/postfix/domains You don't want virtual_alias_domains. > virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap > #hash:/etc/postfix/virtual Everything you've posted so far says you haven't set an alias domain in Mailman for the libertyfp.org domain. Please be sure you have. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Mailman sends Welcome emails, but does not send [List] postings emails

by Mark Sapiro

On 6/8/23 11:16, Nelson Strother wrote: > Here are the (four identical, but for timestamps and process numbers, at > a glance) tracebacks, and some related info: > > --- from /var/log/syslog > Jun 8 03:35:47 localhost mailman[13107]: Traceback (most recent call > last): > Jun 8 03:35:48 localhost mailman[13107]: File > "/var/tmp/mailman/.local/bin/runner", line 8, in <module> > Jun 8 03:35:48 localhost mailman[13107]: sys.exit(main()) > Jun 8 03:35:48 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", > line 1130, in __call__ > Jun 8 03:35:48 localhost mailman[13107]: return self.main(*args, > **kwargs) > Jun 8 03:35:48 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", > line 1055, in main > Jun 8 03:35:48 localhost mailman[13107]: rv = self.invoke(ctx) > Jun 8 03:35:48 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", > line 1404, in invoke > Jun 8 03:35:48 localhost mailman[13107]: return > ctx.invoke(self.callback, **ctx.params) > Jun 8 03:35:48 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", > line 760, in invoke > Jun 8 03:35:48 localhost mailman[13107]: return __callback(*args, > **kwargs) > Jun 8 03:35:48 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func > Jun 8 03:35:48 localhost mailman[13107]: return > f(get_current_context(), *args, **kwargs) > Jun 8 03:35:48 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/bin/runner.py", line 160, in main > Jun 8 03:35:49 localhost mailman[13107]: initialize(config_file, verbose) > Jun 8 03:35:49 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/core/initialize.py", line 231, in initialize > Jun 8 03:35:49 localhost mailman[13107]: > initialize_2(propagate_logs=propagate_logs) > Jun 8 03:35:49 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/core/initialize.py", line 189, in initialize_2 > Jun 8 03:35:49 localhost mailman[13107]: config.db = > getUtility(IDatabaseFactory, utility_name).create() > Jun 8 03:35:49 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/database/factory.py", line 60, in create > Jun 8 03:35:49 localhost mailman[13107]: return database > Jun 8 03:35:49 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py", line 470, in __exit__ > Jun 8 03:35:49 localhost mailman[13107]: self.unlock() > Jun 8 03:35:49 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py", line 420, in unlock > Jun 8 03:35:49 localhost mailman[13107]: raise > NotLockedError('Already unlocked') > Jun 8 03:35:49 localhost mailman[13107]: > flufl.lock._lockfile.NotLockedError: Already unlocked The runners are all trying to access the Mailman database. During the access <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/database/facto…> the database is locked. This code is executed by each runner and the lock keeps them from stepping on each other. It should only take milliseconds to execute, not minutes. The lock is created with the DEFAULT_LOCK_LIFETIME which is 15 seconds. The runner which has the lock is taking longer than 15 seconds in the create code and another waiting runner breaks the lock causing this error I would look to your database manager for the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Error Logging - what changed with the New Year releases?

by Odhiambo Washington

On Sat, Jan 14, 2023 at 11:57 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/14/23 11:44, Odhiambo Washington wrote: > > On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Nothing in those releases per se would affect this. This is Django and > >> django-allauth. Perhaps when you updated the Mailman packages, you also > >> updated these dependencies. > >> > > > > Which dependencies would those be? > > Django and django-allauth. > (venv) [mailman@gw ~/mm]$ pip freeze | grep jango Django==4.1.5 django-allauth==0.52.0 django-appconf==1.0.5 django-compressor==4.1 django-extensions==3.2.1 django-gravatar2==1.4.4 django-haystack==3.2.1 django-mailman3==1.3.9 django-picklefield==3.1 django-q==1.3.9 djangorestframework==3.14.0 > > > > When I upgraded, the command I ran was: > > > > pip install --upgrade --force mailman mailmanclient postorius hyperkitty > > mailman-hyperkitty django-mailman3 > > > Do you mean --force-reinstall? pip has no --force option. I *think* > --force-reinstall will upgrade dependencies. Depending on your pip > version, --upgrade alone may or may not upgrade dependences. Older > versions of pip will, but newer versions, at least without > --force-upgrade require --upgrade-strategy eager to update dependencies. > I have used --force-reinstall. > > And how do I find out what is suppressing the logging for the social > > accounts? > > That's a django-allauth question. > Let me go RTFM again :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Mark Sapiro

On 12/11/19 12:43 AM, Marvin Gülker wrote: > > Thanks for this information. Ubuntu's mailman stores the messages below > /var/lib/mailman3/messages. The "mailman" command is in the $PATH. > >> This should print the file name and Message-ID-Hash (two lines the same) >> for each message in the messages directory until it prints only one line >> followed by the UnicodeEncodeError exception. That list line is the file >> name/Message-ID-Hash of the offending message. > > I've execucted that code, but it does not cause an exception at all. It > quietly runs through. I've attached the transcript of the shell session > to this mail. With a little crude use of grep(1), however I found my > held message in WQ/ZS/WQZSFFJLVMWQHMG4VYKGXJEKQVQXVK67. Here's a revised script: ``` $ mailman shell Welcome to the GNU Mailman shell >>> import os >>> import pickle >>> for root, dirs, files in os.walk('/var/lib/mailman3/messages'): ... for fn in files: ... print(fn) ... with open(os.path.join(root, fn), 'rb') as fp: ... msg = pickle.load(fp) ... print(msg['Message-ID']) ... x = msg.as_string() ... ``` I have adjusted the paths for your package, changed the second print to print the message-is and added the ` x = msg.as_string()` line. Now we expect to see the hash of each message-id followed by the message-id followed by the exception for the offending message. > Does the messages directory contain only held messages? I've looked at > some messages and all of these I looked at were spam. The directory > structure contains 40 messages in total, accumulating to 480 KiB disk > space. Yes, the directory and the corresponding database table contains only messages held for moderator approval. > >> DELETE FROM message WHERE message_id_hash = xxx; > > As the exception you expected did not occur, I didn't do this yet. I can > make a database and directory backup and then run it, though. Should I try? > > I assume after this I should also delete the respective files from the > messages/ directory? Actually, a better way to deal with this is in mailman shell ``` Welcome to the GNU Mailman shell >>> ms = getUtility(IMessageStore) >>> ms.delete_message('xxx') >>> ``` where xxx is the message-id value printed from the above script. >> As of Mailman core 3.3.0 there is a 'mailman notify' command designed to >> be run periodically by cron to notify owners/moderators of pending >> requests. > > I did receive an e-mail to the list owner address that told me that the > e-mail from my incorrect e-mail address "requires approval". That was > the first time I received such an e-mail. In parallel, on the incorrect > e-mail address, I received the notification for moderator approval. Yes, those are the only messages unless you are running `mailman notify`. It seems however that the latest Debian (hence Ubuntu) package doesn't have 3.3 yet. As to why you didn't receive owner notices about the held spam, perhaps they were spam filtered or somehow otherwise lost. -- 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: Bulk delivery status change?

by Stephen Daniel

Thanks all! I will use these pronto. On Sun, Nov 10, 2024 at 11:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: > > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: > > > >> Mistakes were made, and for while every single outbound email bounced. > >> I've fixed the mistakes, but now in my largest and most active email > list, > >> every single user's delivery status is "Disabled by Bounces". > >> > >> Is there a way to bulk fix this? Or do I have to go into each user, > one at > >> a time, and fix them? > > > > Please see this thread: > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > The script in that post does all lists. For a single list see > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > but note that the command line > ``` > $ shell -l list(a)example.com > ``` > should be > ``` > $ mailman shell -l list(a)example.com > ``` > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to swd(a)pobox.com >

1 year, 1 month

[MM3-users] Re: 120 gmail users removed from lists !

by Thomas Ward

Mark: Gmail will handle it as Gmail handles it. If the mail domain is Google even if it's custom-domain-example.com and it points to Google Workspace and Google Mail stuff, it'll bounce on the same rules unfortunately. I know this from working with Google Workspace domains myself with lists, it's a pain and they want a lot more stringent controls now. Thomas -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 24, 2023 1:21 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: 120 gmail users removed from lists ! On 10/24/23 10:04 AM, Andrew Hodgson wrote: > > Speaking of the new additions in Mailman 3.3.9, does anyone have a list of the domains Google are using which we can add to the list so we can disable the unconditional DMARC mitigations for all list posts? Its probably somewhere obvious on a Gitlab issue or similar, but haven't found it yet. The only domains you need to consider are those of your list members, probably only gmail.com, and maybe googlemail.com. I'm not sure how gmail would treat mail From: user(a)some.other.domain where the MX for some.other.domain is a google server, but that could be potentially any domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to teward(a)thomas-ward.net

2 years, 1 month

[MM3-users] Re: All messages to a new list/domain shunted from "in" queue with no logged exceptions

by Jered Floyd

This was entirely my fault. *facepalm* I replace styles/base.py when I do my container builds, so that I can override list defaults (personalization, subscription_policy, and dmarc_mitigate_action). I failed to notice the added dmarc_attributes attribute added to apply() --Jered ----- On Nov 25, 2023, at 7:49 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 11/25/23 16:25, Jered Floyd wrote: >> Via mailman-web. I’ll try to reproduce the behavior tomorrow, once I am home >> from another episode of turkey overconsumption. >> >> I confess that I am not a python expert - once I create a new list, what’s the >> easiest way to inspect the object state? > > ``` > $ mailman shell -l list(a)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(a)example.com mailing list > >>> print(m.dmarc_addresses) > [] > >>> > ``` > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

2 years

[MM3-users] Re: warning: database postfix_domains.db is older than source file postfix_domains

by Mark Sapiro

On 10/26/20 10:07 AM, Torge Riedel wrote: > Hi, > > I frequently get this warning mail.log. stat'ing the files give: > > # stat /opt/mailman/var/data/postfix_domains > File: /opt/mailman/var/data/postfix_domains > Size: 361 Blocks: 8 IO Block: 4096 regular file > Device: 801h/2049d Inode: 1573095 Links: 1 > Access: (0660/-rw-rw----) Uid: ( 1004/ mailman) Gid: ( 1002/ mailman) > Access: 2020-10-24 19:52:16.887258326 +0200 > Modify: 2020-10-20 07:09:48.792000000 +0200 > Change: 2020-10-20 07:09:48.792000000 +0200 > Birth: - > # stat /opt/mailman/var/data/postfix_domains.db > File: /opt/mailman/var/data/postfix_domains.db > Size: 12288 Blocks: 24 IO Block: 4096 regular file > Device: 801h/2049d Inode: 1583965 Links: 1 > Access: (0640/-rw-r-----) Uid: ( 1004/ mailman) Gid: ( 1002/ mailman) > Access: 2020-10-26 07:46:54.569935782 +0100 > Modify: 2020-10-20 07:09:47.575889000 +0200 > Change: 2020-10-20 07:09:47.575889000 +0200 > Birth: - I don't understand how this is happening. With defaults for mailman.cfg settings you should have in the [mta] section configuration: python:mailman.config.postfix which points to the file mailman/config.postfix.py in the installation which has in its [postfix] section postmap_command: /usr/sbin/postmap These settings say whenever mailman updates `/opt/mailman/var/data/postfix_domains`, it runs `/usr/sbin/postmap` /opt/mailman/var/data/postfix_domains` to update `/opt/mailman/var/data/postfix_domains.db`. These files, `postfix_domains` and `postfix_lmtp`should be written and closed before invoking the posymap command, so Y don't understand why the modify/change times on the .db files would be 1.22 seconds earlier than those on the source. > I do not have the feeling that this is really a problem, cause > everything works well. But it is confusing and misleading and might > makes me missing a problem in the future, when the database is really > outdated. > > Could this be easily fixed in mailman? I don't think it's a Mailman issue. For example on the server that supports this list I see $ stat /opt/mailman/mm/var/data/postfix_* File: ‘/opt/mailman/mm/var/data/postfix_domains’ Size: 391 Blocks: 8 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5113910 Links: 1 Access: (0660/-rw-rw----) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-24 19:30:44.787818101 +0000 Modify: 2020-10-24 19:30:44.731817318 +0000 Change: 2020-10-24 19:30:44.731817318 +0000 Birth: - File: ‘/opt/mailman/mm/var/data/postfix_domains.db’ Size: 12288 Blocks: 24 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5112421 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-26 19:39:45.452615116 +0000 Modify: 2020-10-24 19:30:44.787818101 +0000 Change: 2020-10-24 19:30:44.787818101 +0000 Birth: - File: ‘/opt/mailman/mm/var/data/postfix_lmtp’ Size: 3465 Blocks: 8 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5113909 Links: 1 Access: (0660/-rw-rw----) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-24 19:30:44.775817934 +0000 Modify: 2020-10-24 19:30:44.719817150 +0000 Change: 2020-10-24 19:30:44.719817150 +0000 Birth: - File: ‘/opt/mailman/mm/var/data/postfix_lmtp.db’ Size: 12288 Blocks: 24 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5112424 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-26 19:40:38.509356931 +0000 Modify: 2020-10-24 19:30:44.775817934 +0000 Change: 2020-10-24 19:30:44.775817934 +0000 Birth: - Which is what I expect. Note that the only times both the `postfix_domains` and `postfix_lmtp` are updated together is when one of the `mailman` subcommands `aliases` or `start` is run. Are you possibly running both these at the same time causing some kind of race condition? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Migration from 2.1 to 3

by Mark Sapiro

On 12/26/19 5:22 AM, brunol(a)agro.uba.ar wrote: > > No errors/tracebacks in mailman.log. This is the output of debug.log configured as shown in my first post: > > Dec 26 10:02:37 2019 (696) <CAOwJ5NW3sYhUCCJAVS7ZdiwtyU8SGrArfnPTt5052m1H+V=+nQ(a)mail.gmail.com> to: lispruebas(a)mailman3.agro.uba.ar, list: lispruebas, sub: None, dom: mailman3.agro.uba.ar > Dec 26 10:02:37 2019 (696) <CAOwJ5NW3sYhUCCJAVS7ZdiwtyU8SGrArfnPTt5052m1H+V=+nQ(a)mail.gmail.com> subaddress: None, queue: in > Dec 26 10:02:37 2019 (696) b'250 Ok\r\n' > Dec 26 10:02:37 2019 (696) _handle_client readline: b'QUIT\r\n' > Dec 26 10:02:37 2019 (696) ('127.0.0.1', 43354) Data: b'QUIT' > Dec 26 10:02:37 2019 (696) b'221 Bye\r\n' > Dec 26 10:02:37 2019 (696) ('127.0.0.1', 43354) connection lost > Dec 26 10:02:37 2019 (696) Connection lost during _handle_client() > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7fbbb70> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7f83fd0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d483e0b8> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d8079438> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7f70f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4a60f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4981860> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d483eda0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49e2f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d80792b0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4981e10> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49e9780> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4d02c50> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7fbb550> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49cf048> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4983fd0> > > Those "Using agent: <mailman.mta.bulk.BulkDelivery object at " are constantly appearing, is this behavior normal due to the verbosity of the level? What do you mean by constantly appearing? Do you mean endlessly repeating or that they just repeat a number of times equal to the number of expected recipients of the post? On 12/26/19 10:24 AM, brunol(a)agro.uba.ar wrote: > I've also noticed that the messages are stuck in the "message" table (postgresql) and the corresponding files exists under /var/lib/mailman3/messages/ This indicates the held message has not been removed from the held message queue. You previously posted that you saw a log message > Dec 23 12:35:47 2019 (701) held message approved, message-id: CAOwJ5NX=_bUnfb5ZNqVLFeF3EeOP0GMJW7NeeOWZqVmn5ViyBg(a)mail.gmail.com This message comes from mailman.app.moderator.handle_message() (in mailman/app/moderator.py). After logging that message, it requeues it in the 'pipeline' queue for further processing and deletes it from the message table and /var/lib/mailman3/messages/. This indicates that possibly subsequent processing is holding the message again. > Is there any relevant logger i should look on debug too besides the ones i already configured? set [logging.debug] level: debug in mailman.cfg to get more in debug.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Wed, Dec 28, 2022 at 8:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/27/22 21:46, Odhiambo Washington wrote: > > On Tue, Dec 27, 2022 at 8:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> I see from another post that you've decided against using Twitter, but > >> to answer the question, Twitter does not require adding anything to > >> SOCIALACCOUNT_PROVIDERS. > >> > > > > I tried it and ended up with: > > > > ERROR 2022-12-28 08:40:18,895 97440 django.request Internal Server Error: > > /accounts/twitter/login/ > > Traceback (most recent call last): > ... > > allauth.socialaccount.models.SocialApp.DoesNotExist: SocialApp matching > > query does not exist. > > > Do you have > > 'allauth.socialaccount.providers.twitter', > > in INSTALLED_APPS? > Here is what I have in settings_local.py: INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', #'django_mailman3.lib.auth.fedora', #'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', #'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google', 'allauth.socialaccount.providers.facebook', 'allauth.socialaccount.providers.twitter', #'allauth.socialaccount.providers.stackexchange', ) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

[MM3-users] Re: Cron error

by Mark Sapiro

On 9/28/20 7:38 AM, gordon(a)dickens.com wrote: > I recently upgraded to mailman3 on two Debian servers and I am getting a cron error periodically sent to me as depicted below. It looks like a permission problem, however, /var/lib/mailman3/locks and /var/lib/mailman3/* all have user = "list" and group = "list" and the cron job runs as user = "list" so I don't quite understand why I am getting these errors. > > ls -l locks" output: > total 12 > -rw-rw---- 1 list list 80 Sep 28 00:00 'dbcreate.lck|slc.mailhub4u.com|24435|4056142050254595815' Does PID 24435 exist and if so, what is it? This is strange because it says PID 24435 has claimed the lock, but there is no lock which would be a file named dbcreate.lck if there is no PID 24435 or if it isn't related to Mailman, just remove the 'dbcreate.lck|slc.mailhub4u.com|24435|4056142050254595815' file. > -rw-rw---- 2 list list 77 Sep 28 2020 master.lck > -rw-rw---- 2 list list 77 Sep 28 2020 'master.lck|slc.mailhub4u.com|5291|3708878559945320758' > > Here is the error message that is emailed to me: What command is cron running? Although it is some `mailman` command and the sub-command isn't relevant as it never gets that far, but the -C/--config option may be. > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 216, in lock > os.link(self._claimfile, self._lockfile) > FileExistsError: [Errno 17] File exists: '/var/lib/mailman3/locks/dbcreate.lck|slc.mailhub4u.com|24435|4056142050254595815' -> '/var/lib/mailman3/locks/dbcreate.lck' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/bin/mailman", line 11, in <module> > load_entry_point('mailman==3.2.1', 'console_scripts', 'mailman')() > File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ > return self.main(*args, **kwargs) > File "/usr/lib/python3/dist-packages/click/core.py", line 716, in main > with self.make_context(prog_name, args, **extra) as ctx: > File "/usr/lib/python3/dist-packages/click/core.py", line 641, in make_context > self.parse_args(ctx, args) > File "/usr/lib/python3/dist-packages/click/core.py", line 1089, in parse_args > rest = Command.parse_args(self, ctx, args) > File "/usr/lib/python3/dist-packages/click/core.py", line 940, in parse_args > value, args = param.handle_parse_result(ctx, opts, args) > File "/usr/lib/python3/dist-packages/click/core.py", line 1477, in handle_parse_result > self.callback, ctx, self, value) > File "/usr/lib/python3/dist-packages/click/core.py", line 96, in invoke_param_callback > return callback(ctx, param, value) > File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in initialize_config > initialize(value) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 218, in initialize > initialize_2(propagate_logs=propagate_logs) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 177, in initialize_2 > config.db = getUtility(IDatabaseFactory, utility_name).create() > File "/usr/lib/python3/dist-packages/mailman/database/factory.py", line 50, in create > with Lock(os.path.join(config.LOCK_DIR, 'dbcreate.lck')): > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 334, in __enter__ > self.lock() > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 248, in lock > elif self._read() == self._claimfile: > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 442, in _read > with open(self._lockfile) as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/dbcreate.lck' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/

by Mohsen Masoudfar

Thank you Mark for your help. I see fedora under Django administration: Home > Social Accounts > Social Accounts as a provider listed, but we do not use it and I would like to remove it. So far I did not find a way to delete it. We do not need Hyper Kitty either, because we do not archive any emails. I appreciate if you could point me how I may delete Fedora as a provider. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, December 27, 2022 4:25 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/ [EXTERNAL EMAIL] On 12/27/22 10:27, Mohsen Masoudfar wrote: > Hi, > I am getting the following errors starting some days ago. It is unclear to me what is causing this. I searched internet, there are some similar reports that mention bugs causing this. I am running mailman3 as Ubuntu 18 package and they do not provide any update for this. These are probably from some spammer trying to post to the sec_g_zoom(a)listserv2.aaas.org list from hyperkitty and trying to login via the fedora OpenID app which is not properly configured on your server. Do you actually want to support fedora as an OpenID provider? If not, you might remove 'django_mailman3.lib.auth.fedora', from INSTALLED_APPS in your Django settings. Otherwise, see https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdjango-al… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… This message sent to mmasoudf(a)aaas.org

2 years, 11 months

[MM3-users] Re: ***SPAM*** Re: How to hide sender completely

by Bill Oliver

Oops. Sorry for the digression. When I read the question, I thought the OP was asking about making the list itself anonymous -- difficult to find and resistant to subpoena -- not turning on anonymization inside of mailman. So... never mind On May 9, 2023 11:12:36 AM EDT, Mark Sapiro <mark(a)msapiro.net> wrote: >On 5/9/23 02:00, Roland Miyamoto via Mailman-users wrote: >> Could anyone tell me whether there is a way to hide >> the sender address of list mails completely from the recipients. >> >> Even for an anonymous list, the sender still occurs in two fields >> >> envelope-from <sender(a)sender-domain.tld> >> X-MailFrom: sender(a)sender-domain.tld >> >> of the mail header. >> Is there a way to suppress this information? > > >Anonymous lists should be removing any X-MailFrom: or X-Envelope-From: headers from delivered mail. The envelope-from in the outgoing mail should be the list-bounces address, not the original sender. > >If you are seeing this information in mail from an anonymous list, it is a bug and I would like to see a raw message as received from the list with this information. > >-- >Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >San Francisco Bay Area, California better use your sense - B. Dylan > >_______________________________________________ >Mailman-users mailing list -- mailman-users(a)mailman3.org >To unsubscribe send an email to mailman-users-leave(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >This message sent to billo(a)billoblog.com

2 years, 7 months

[MM3-users] Re: Post-installation documentation?

by David Newman

On 11/25/21 10:28 AM, Mark Sapiro wrote: > On 11/24/21 10:17 PM, David Newman wrote: >> On 11/24/21 2:36 PM, Mark Sapiro wrote: >>> >>> To import archives run the Django admin command with arguments >>> >>> hyperkitty_import -l alist(a)example.com >>> /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox >> >> Good up to here, but ... hyperkitty_import not found. >> >> This wasn't covered in the venv docs: > > It is covered at > https://docs.mailman3.org/en/latest/migration.html#upgrade-strategy > > Your issue is probably that the Django admin command you ran is not > accessing your `settings.py`. You may need to do > ``` > export DJANGO_SETTINGS_MODULE=settings > export PYTHONPATH=/path/to/directory/containing/settings.py > ``` > before running the Django admin command. These can also be given as > --settings and --pythonpath options to the Django admin command. Thanks for this. After setting these variables and restarting mailman3 and mailmanweb, the mailman user still cannot find a hyperkitty_import command (neither can root, btw). Again, I installed MM3 and Django/Postorius/Hyperkitty using the venv and web docs previously referenced. On the plus side, all lists now appear in the admin web page. However, lists created from the admin page do not appear in a site list page, even though all lists are in the same site/domain. Finally, how to make these exports permanent? I did not see this covered in the migration doc above. This is on a Debian system where the mailman user's shell is bash. Is this simply a matter of adding environment variables in the mailman user's .bashrc file? Thanks dn

4 years

[MM3-users] Re: mail for lists.ccalternatives.org loops back to myself, then Recipient address rejected

by Christian Stalberg

Main.cf had transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains I then changed local_recipient_maps to transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains I then restarted postfix & mailman. When sending a message to the list I am still getting the same error I had before <Deepadaptation(a)lists.ccalternatives.org>: host lists.ccalternatives.org[192.46.218.224] said: 550 5.1.1 <Deepadaptation(a)lists.ccalternatives.org>: Recipient address rejected: User unknown in local recipient table (in reply to RCPT TO command) help please! -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, June 10, 2022 4:22 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mail for lists.ccalternatives.org loops back to myself, then Recipient address rejected On 6/9/22 18:12, Christian Stalberg via Mailman-users wrote: > > -Added lists.ccalternatives.org to the mydestination line in > /etc/postfix/main.cf and restarted Postfix -Now a new error message: > <Deepadaptation(a)lists.ccalternatives.org>: host > lists.ccalternatives.org[192.46.218.224] said: 550 5.1.1 > <Deepadaptation(a)lists.ccalternatives.org>: Recipient address rejected: > User > unknown in local recipient table (in reply to RCPT TO command) See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht ml#transport-maps - in particular local_recipient_maps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 6 months

[MM3-users] Re: Good choice of defaults for content filtering?

by Allan Hansen

Excellent. Thank you, Mark. Allan Hansen P.O. Box 2423 Cypress, CA 90630 > On Jul 30, 2020, at 18:00, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/30/20 5:00 PM, hansen(a)rc.org wrote: >> Hi all, >> >> I had MM2 set to the default filtering that I think came OOTB. MM3 has none such and I was wondering: >> a. What were those MM2 defaults (My MM2 server is long gone now). > > > You will find the content filtering defaults beginning at > <https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman…>. > These have been the defaults for new lists since Mailman 2.1.21. Prior > th that, the the default for pass_mime_types was > > ['multipart/mixed', > 'multipart/alternative', > 'text/plain'] > > >> b. Is there a better set today. I know that MIME types can be faked, but they have worked. I want to avoid anything that can contain malicious code while also allowing simple text to go through. > > > If you go with the current defaults, except of course for setting filter > content on, you can add text/html to pass_types and any html parts that > aren't collapsed out by collapse alternatives will be kept and converted > to plain text. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 4 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Simon Hanna

On 05/14/2016 07:11 AM, Mark Sapiro wrote: > On 5/13/16 5:05 PM, Simon Hanna wrote: >> On 05/12/2016 09:26 PM, Barry Warsaw wrote: >>> On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: >>> >>>> It is the intent that Postorius will eventually expose all these >>>> settings. We're not there yet. At present you could possibly do this by >>>> interacting with mailmanclient, although I'm not certain the settings are >>>> exposed there. >>> >>> I'm not sure if they're exposed in mailmanclient, but they are exposed in the >>> core's REST API, on the member resource. It's the `delivery_mode` attribute >>> and it takes as legal values one of 'regular', 'plaintext_digests', >>> 'mime_digests', and 'summary_digests' (IOW, the enum item names for the >>> DeliveryMode enum). > >> They are exposed in mailmanclient and are used in postorius. They can be >> found in the users personal subscription settings >> https://lists.mailman3.org/mailman3/accounts/mailmansettings/ > > > You are correct. When I checked this before my initial reply, I never > pulled down the Delivery Mode list to see all the options. My bad. > > However, please correct me if I'm wrong, but there does not appear to be > a way in Postorius to set a list's mime_is_default_digest attribute. > You've got that one right. But I don't think core is exposing this through rest. At least it's not exposed via mailmanclient.

9 years, 6 months

[MM3-users] Re: MTA setup

by Arte Chambers

The shunt queue is empty. I see a 400 error "Bad Request" in the mailman logs, not sure what my next troubleshooting steps should be. mailman log: Dec 23 16:58:51 2024 (684048) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError: <!doctype html> <html lang="en"> <head> <title>Bad Request (400)</title> </head> <body> <h1>Bad Request (400)</h1><p></p> </body> </html> Dec 23 16:58:51 2024 (684058) HyperKitty failure on http://127.0.0.1:8000/archives/api/mailman/urls: <!doctype html> <html lang="en"> <head> <title>Bad Request (400)</title> </head> <body> <h1>Bad Request (400)</h1><p></p> </body> </html> (400) Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Mon, Dec 23, 2024 at 1:29 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/23/24 09:03, Arte Chambers via Mailman-users wrote: > > Update: After changing the DMARC settings messages are now going through > to > > my inbox, however they are still not being archived. > > > Yes, that's always been a separate issue. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to paul.m.robey(a)gmail.com >

11 months, 2 weeks

[MM3-users] Re: Incoming command emails (i.e. listname-leave) routed to list itself

by Mark Sapiro

On 04/20/2017 05:37 PM, Mark Lindsay wrote: > > I'm new to Mailman 3 and Mailman in general, but I've got it up and > running, and my external app is communicating quite well with the > administrative REST API. Cool. > Here's the only problem I haven't been able to figure out: > > Say I have a list called "potato." List members can post to the list by > emailing potato(a)lists.mydomain.org. This works fine. However, incoming mail > for command addresses (e.g. potato-leave(a)lists.mydomain.org) is routed to > the list too. The command email gets sent out to all members, as if the > user who wanted to unsubscribe had just written to potato(a)lists.mydomain.org. > This is also the case with the potato-request(a)lists.mydomain.org address. > > I am using exim4 on Ubuntu. I followed the instructions here: > http://mailman.readthedocs.io/en/release-3.0/src/mailman/docs/MTA.html. The > only change I had to make to the exim4 config files in the readthedocs > instructions was in this line: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > > I had to change it to: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} > > That is how the subdirectories are named in my lists directory. e.g. > potato.lists.mydomain.org. If I use the exact MM3_LISTCHK value from > readthedocs, I get 550 Unrouteable bounces. OK. That document needs updating. Also, the '-admin' local_part_suffix should not be there, but that's not related to your issue. '-admin' is from MM 2.1 and isn't used in MM 3. > Here are some baffling lines from /var/log/exim4/mainlog from the incoming > potato-leave(a)lists.mydomain.org email: > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r DKIM: d=nervous-org.20150623. > gappssmtp.com s=20150623 c=relaxed/relaxed a=rsa-sha256 [verification > succeeded] > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r <= redacted(a)nervous.org H= > mail-qk0-f170.google.com [209.85.220.170] P=esmtp S=2466 id= > CABPy5zyQtJHXtCgrN37GHCUOjuo3J=DO_j0ZD03zm8gk+4shww(a)mail.gmail.com > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r => potato(a)lists.mydomain.org < > potato-leave(a)lists.mydomain.org> R=mailman3_router T=mailman3_transport > H=localhost [127.0.0.1] C="250 Ok" > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r Completed > > Why does it say `potato(a)lists.mydomain.org <potato-leave(a)lists.mydomain.org >> `? That's the key question. The transport is supposed to just relay the message to Mailman via LMTP to MM3_LMTP_PORT, but it appears to be rewriting the envelope recipient from potato-leave(a)lists.mydomain.org to potato(a)lists.mydomain.org. I suspect the router is somehow stripping local_part_suffix from the recipient address, but why, I don't know. > I think this is actually an exim4 problem, so if the solution is to just > switch to postfix, then I will definitely do that. But I'm just asking in > case someone had a similar issue with exim4 and was able to work through it. We want to make MM 3 work with Exim as an MTA. Unfortunately, I have not used Exim as an MTA in a long time and not with Mailman 3 at all, so I may not be much help. I think the person who set up Exim is on this list and may reply. If not, I'll try to research this further. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/23/20 11:19 AM, Mark Sapiro wrote: > Here's a thought. For Affinity/Empathy at least, how about using Mailman > core's user as the Affinity registered user. I.e., if someone's first > interaction is to register with Affinity, have that registration create > a core user to keep the Affinity registration data. This core user > already accommodates a display_name and password and email address(es). > > If the person already is a core user when registering for Affinity, just > update the core user as needed, probably only a password reset or just > setting it if it is currently None. > > Then you don't have the issue of another, separate registration for > Affinity. > > This would be more difficult for Postorius/Hyperkitty because those > users are Django users, but that isn't an issue for Affinity. > > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San > Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ Mailman-users mailing > list -- mailman-users(a)mailman3.org To unsubscribe send an email to > mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ How would a person already be a core user outside of a registration with Affinity? Via a list subscription or the import21 script? I do agree overall that we can more easily address some/all of these issues more easily and quicker due to not being tied to Django. I hope to get all of this address in our Nov development cycle. I do want to apologize for my tone Mark. I was wrong in the way I communicated. > -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Question about whitlisting a domain for specific mailing list

by Odhiambo Washington

So the MTA option that doesn't involve any regex is better than no? On Thu, Mar 30, 2023, 20:17 Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/30/23 08:55, Zaheer Abbas wrote: > > Hi All, > > > > I need to whitelist a domain for a specific mailing list on your > platform. > > Only *(a)example.com email addresses should be allowed to post messages to > > this list. > > > > Could you please provide me with documentation or instructions on how to > > achieve this? I have already searched the knowledge base and user manuals > > without success. > > > In Postorius Header filters add a filter with Header = from, pattern = > ^.*(a)(?!example\.com(\W|$)) and Action as desired. That pattern will > match anything in a From: header which contains an @ followed by > anything other than example.com and a non-alphanumeric or the end of > string. I.e., things that won't match are for example > > xxx(a)example.com > xxx(a)example.com> > xxx(a)example.com yyy > > Things that will match are for example > > xxx(a)other.domain > xxx(a)example.comp > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 8 months

[MM3-users] Re: UnpicklingError on mailman lists command

by Bryan Loniewski

Okay, that helped identify possible culprits. Three of our lists are hitting/over the max BLOB length (65,535 bytes) for accept_these_nonmembers. I executed this SQL command for each of the BLOB cols you referenced and only accept_these_nonmembers is borked: MySQL [mailman]> SELECT list_name, OCTET_LENGTH(accept_these_nonmembers) as howManyBytes from mailinglist where OCTET_LENGTH(accept_these_nonmembers) > 64000; +---------------+--------------+ | list_name | howManyBytes | +---------------+--------------+ | <snip> | 65535 | | <snip> | 65535 | | <snip> | 65535 | +---------------+--------------+ 3 rows in set (0.01 sec) So, putting aside *why* these lists are so large wrt that column, can or should I alter the col type(s) to MEDIUMBLOB? If yes, would that remain on suite upgrades? If no, is there a better alternative? Or some recommendation in between? ________________________ Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator ________________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, August 3, 2021 12:15 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: UnpicklingError on mailman lists command On 8/2/21 7:35 PM, Bryan Loniewski wrote: > $ /opt/mailman/mm/bin/mailman version > GNU Mailman 3.3.2 (Tom Sawyer) > > So, I'm running > 3.2. Any other advice on debugging the truncated data? The traceback indicates sqlalchemy is unpickling data whose type is PickleType. The only mailinglist columns which are PickleType are the legacy *these_nonmembers and topics. You could try invoking mysql on Mailman's database and doing SELECT list_name, accept_these_nonmembers, hold_these_nonmembers, reject_these_nonmembers, discard_these_nonmembers, topics FROM mailinglist; and look for the longest values to possibly identify the problem list and attribute. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

4 years, 4 months

[MM3-users] Re: Social signup?

by Duane Raymond

Wow - thanks for the redirection on where to patch it and the first-cut code. I'll look into this in 2 weeks when I am able to focus on it. Cheers, Duane On Wed, 15 Mar 2023 at 16:18, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/15/23 05:08, Duane Raymond wrote: > > > > I'll jump over to the developers list when I start this (I'm about to > > travel for a week to run an annual event in Oxford - so the far removed > > from programming)...but which chatGPT suggested so far was > > > > 1. Extending postorius/signups.html with a loop to get the configured > > social login providers PLUS adding a csrf_token field to the form > > 2. Modifying postorius/views.py (which doesn't seem to exist but > there > > is a postorius/views folder) - so perhaps this is views/urls.py > > > This is not what you want to do for this. The changes need to be in > django-mailman3, not postorius. I have attached a patch which might work > for you. I think it is good, but some of the wording is stuff that may > not be appropriate. See what you think. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to duane(a)fairsay.com >

2 years, 8 months

[MM3-users] Re: Held messages not delivered after approval

by Mark Sapiro

On 7/31/25 04:29, Stephan Krinetzki wrote: > > /opt/mailman/var/queue/out: > total 2868 > drwxrwx--- 2 mailman mailman 4096 Jul 31 13:26 . > drwxr-xr-x 14 mailman mailman 165 Jun 27 2024 .. > -rw-rw---- 1 mailman mailman 221708 Jul 30 13:16 1753874180.0845337+0cc7849043859a79dc3678a0d8b63c1c66df0c66.pck.tmp > -rw-rw---- 1 mailman mailman 733425 Jul 31 00:00 1753912841.8847518+da55f8789ae41b75d19a02b595e3fd6d45983ade.pck.tmp These indicate a problem of some sort. .pck.tmp files should only exist for a fraction of a second. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/switchboa… What does `mailman qfile report for these? Are they the missing messages? > -rw-rw---- 1 mailman mailman 17758 Jul 31 13:26 1753961185.0481033+6adf966467266567275f1146f5054c95e4365c13.pck > -rw-rw---- 1 mailman mailman 31122 Jul 31 13:26 1753961185.1064982+b1f502e2af56b9b11680135c6de5fcc5285d967e.bak > -rw-rw---- 1 mailman mailman 12945 Jul 31 13:26 1753961185.1562705+a88534cfa9b03012c248ac00cbb54f4fc08c8dcc.pck > -rw-rw---- 1 mailman mailman 1407634 Jul 31 13:26 1753961185.2598634+96e501d7aa8e72fbb9f9a5c953d48fc2c7db2bc7.pck > -rw-rw---- 1 mailman mailman 17570 Jul 31 13:26 1753961185.3654013+d693065f2b9a2338f887d3ac9c0669c957131100.pck > -rw-rw---- 1 mailman mailman 60624 Jul 31 13:26 1753961185.4132354+8998ee9eb9a8a99faf1fcf045d604e669f5d0c9e.pck > -rw-rw---- 1 mailman mailman 7361 Jul 31 13:26 1753961185.413462+50dcef9bb178f54ecb2d4707ccfe02773f92336c.pck > -rw-rw---- 1 mailman mailman 84848 Jul 31 13:26 1753961185.4464717+17836b8875aa6643f7e5fb0744e72940ce5603c6.pck > -rw-rw---- 1 mailman mailman 18003 Jul 31 13:26 1753961185.4929028+17e9c78a2721cbc344124c6e04a129217ea6c794.pck > -rw-rw---- 1 mailman mailman 66982 Jul 31 13:26 1753961185.5228019+4ef59e61c6a79dd4cdee6d1110fb0582fcfafb6c.pck > -rw-rw---- 1 mailman mailman 221723 Jul 31 13:26 1753961185.5756643+6de90ae99b3d528ce5234b78a287e19f7b6686fc.pck Also, this is a lot of outgoing messages to be queued. Are you sending periodic digests at this time? If you normally see a lot of messages in the out queue, you might consider setting it's `instances` to 2 or 4. E.g., ``` [runner.out] instances: 4 ``` in mailman.cfg > /opt/mailman/var/queue/shunt: > total 3304 > drwxrwx--- 2 mailman mailman 4096 Jul 31 11:44 . > drwxr-xr-x 14 mailman mailman 165 Jun 27 2024 .. > -rw-rw---- 1 mailman mailman 451 Jul 31 00:00 1753912822.2651796+28eceef7e18eb70393377b88dc7117af8f9362a0.pck > -rw-rw---- 1 mailman mailman 490 Jul 31 00:00 1753912838.4197352+ea531cf0262c1faa58b1679b907fee92bc16822c.pck > -rw-rw---- 1 mailman mailman 1407870 Jul 31 00:00 1753912841.9177196+ccea15bdefce3a54301281c8eddf86e8230244a6.pck > -rw-rw---- 1 mailman mailman 86108 Jul 31 00:00 1753912841.9197443+7dcef4febc71e44c6d9309a24a08b08753e1ff42.pck > -rw-rw---- 1 mailman mailman 1407668 Jul 31 00:00 1753912841.9849963+a3f1869b750060c97262ece38737480d91652828.pck > -rw-rw---- 1 mailman mailman 38992 Jul 31 00:01 1753912860.5167956+940584c4f361cbd8c29e390b2f60590558effe40.pck > -rw-rw---- 1 mailman mailman 440 Jul 31 00:01 1753912860.6972685+635c065bac8dff5f9d562275d707001d773b84c1.pck > -rw-rw---- 1 mailman mailman 445 Jul 31 00:01 1753912868.7903054+befa066f254d7a3529a8555a6c942a554715d837.pck > -rw-rw---- 1 mailman mailman 33494 Jul 31 00:01 1753912878.7562895+82b724fd93260ab9a2bb49709d3a42a2f32f2c80.pck > -rw-rw---- 1 mailman mailman 217073 Jul 31 00:01 1753912878.9337828+de73a65d9c6febfa80275853921f4b53fd1d9e2a.pck > -rw-rw---- 1 mailman mailman 85888 Jul 31 00:02 1753912950.303359+8a87bce0be63ac1df8493c6b1ad6ae154fcedba7.pck > -rw-rw---- 1 mailman mailman 50244 Jul 31 00:02 1753912950.4970112+d44d493912bb3024547b8a5112f86f035dcb352f.pck > -rw-rw---- 1 mailman mailman 12887 Jul 31 00:02 1753912970.038427+31bcbd7fb2ebdf81f6de24b7283b50bcda6ded21.pck.tmp > -rw-rw---- 1 mailman mailman 443 Jul 31 11:44 1753955094.900898+67bc76525412da66a7c76363f65f583989716305.pck > > /opt/mailman/var/queue/virgin: > total 32 > drwxrwx--- 2 mailman mailman 81 Jul 31 13:17 . > drwxr-xr-x 14 mailman mailman 165 Jun 27 2024 .. > -rw-rw---- 1 mailman mailman 32013 Jan 11 2025 1736550035.6163204+472f81ece5e45a2651a4499bef418f611b43c619.pck.tmp > > Nothing special there (shunt should be checked, but not in correlation with my mail). Actually those .pck.tmp files indicate some issue. > I have one list which archives the mail. In the archive there is the mail, but it doesn't get deliverd Which says the pipeline to_archive handler is adding the message to the archive queue and the archive runner is handling it, so presumably the pipeline to_outgoing handler is adding the message to the out queue, so the issue is in the outging runner. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 1 week

[MM3-users] Re: Message-Footer after migrating to Mailman3

by Mark Sapiro

On 5/24/21 10:43 AM, christopher.claus(a)tgcamberg1848.de wrote: > > I found the file > [code] > /usr/lib/python3.8/site-packages/mailman/templates/de/list:member:generic:footer.txt > [/code] > which includes the old footer: > [code] > _______________________________________________ > $display_name Mailingliste -- $listname > Zur Abmeldung von dieser Mailingliste senden Sie eine Nachricht an ${short_listname}-leave@${domain} > [/code] > > but no configuration item to disable this behaviour. That is the default footer template that's part of the Mailman distribution. That template is overridden by those in Mailman's var/templates/ directory. Mailmnan's import21 process created footers template in var/templates/lists/<LIST_ID>/list:member:regular:footer.txt and var/templates/lists/<LIST_ID>/list:member:digest:footer.txt > I created a new template list:member:regular:footer for the list to override the footer. But the old footer is still used where did you put it? > in detail: the resulting message sent to all subcribers of the list contains only the footer and the content sent to the list is an attachement of that "footer-message". This is the basic reason why I want to change it. > > In the logfiles I found an error and a warning: > [code] > ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. > WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer > [/code] It appears you created the new template with Postorius, but there is an issue for Postorius templates. Possibly your Django setting for POSTORIUS_TEMPLATE_BASE_URL needs to be adjusted. > Obviously I have a problem with the hostname. I set > [code] > POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 > [/code] > where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost > [code] > wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamber… > [/code] > will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? If that works, yes. > I think, resolving this issue will use the newly configured footer. But I started with the intention to remove alle footers due to the attachement situation described above. > > Does anybody have an idea how to change the configuration of my list? Are these problems probably related to the import? Currently we are using more then 25 lists with a lot of users. Manually recreating all lists is not possible an could only be a test for a single list. The issue you are seeing has only to do with the fact that the footer is non-empty. It is not related to footer content. It is because you are posting other than text/plain messages and the MUAs you are viewing the mail with are confused by the footer being a separate MIME part. See the FAQ article at https://wiki.list.org/x/4030707 for discussion of this issue in MM 2.1 which is also relevant to MM 3. To disable adding footers entirely, sitewide, create an empty file, readable by Mailman at Mailman's ``` var/templates/site/de/list:member:generic:footer.txt ``` More about templates and search rules is at templates/de/list:member:generic:footer.txt and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: update_index

by Darren Smith

Holy cow I think that's exactly what the problem is. I will give that a try and let you know what happens! On Tue, Apr 3, 2018 at 10:50 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/03/2018 09:02 AM, Darren Smith wrote: > > Hello, > > > > If I'm reading the docs correctly, when we run manage.py update_index, it > > should be an incremental index of new emails that have been added since > the > > last time update_index was run - can anyone confirm that this is the > > expected behavior? Or is there another command line option that I am > > missing? > > > There are two ways to run update_index. > > Hyperkitty's update_index is incremental and is run by > > manage.py runjob update_index > > Running > > manage.py update_index > > runs haystack's update_index which with no options does a full update. Run > > manage.py update_index --help > > to see the options. The incremental 'manage.py runjob update_index' > should be run every minute by 'manage.py runjobs minutely' assuming cron > is running the periodic Django jobs, so running either update_index job > manually shouldn't be necessary > > > ... > > So...can anyone help with how to get the update_index to do only emails > > added since the last time the update_index was run? > > > manage.py runjob update_index > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 8 months

[MM3-users] Re: digests are created but not sent out

by "Jörg M. Schulz"

start fails when I use # The default language for this server. default_language: en [language.en] charset: utf-8 enabled: yes when I comment out the lines above, mailman starts. > Am 09.01.2019 um 20:53 schrieb Jörg M. Schulz <js(a)jslz.de>: > > and: When I put the stanza >>> [language.en] > into the mailman.cfg, the service doesn’t restart: > … > PermissionError: [Errno 13] Permission denied: '//var/templates' > > somehow the template path gets lost by defining this section. Possibly, somewhere the path to the .en / language templates must be set. How, where? > > > >> Am 09.01.2019 um 20:50 schrieb Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>>: >> >> Mark Sapiro wrote: >>> >>> You can change this for English by putting >>> >>> [language.en] >>> charset: utf-8 >>> >>> in your mailman.cfg. This works because us-ascii is a proper subset of >>> utf-8. >> >> >> I forgot to mention that there is a potential downside to the above. Because of the way the Python email library treats UTF-8 message bodies, list messages with UTF-8 bodies are sent with the body base64 encoded. This may or may not be an issue depending on whether you look at raw messages or perhaps grep mailboxes looking for things. >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> >

6 years, 11 months

[MM3-users] Re: Request for help with configuring "from" headers in mailman3 list

by Stephen Daniel

That worked! I apologize for needing to ask for help on this. I am very appreciative of how quickly and accurately my issues were resolved. On Thu, Jan 6, 2022 at 5:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/22 12:52 PM, Stephen Daniel wrote: > > > > Sendgrid requires that the "From:" address on any email reference an > > authenticated domain. > > > > In the old mailman2 implementation, emails sent by mailman are listed as > > > > From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org > > > > Reply-to: <human name> sender(a)senderdomain.com (the original email's > sender) > > > > Sendgrid would be happy with this, because LISTDOMAIN.org is a > > validated domain. > > > > However, in my mailman3 implementation, the From: header lists the > original > > email's sender. Sendgrid rejects this because the original email's > > sender's address is not one of the validated domains. > > > > How do I configure mailman3 to generate headers in the same style as the > > old mailman2 implementation? > > > In the list's Settings -> DMARC mitigations, set DMARC mitigation action > to Rrplace From: with list address and DMARC Mitigate unconditionally to > Yes. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 11 months

[MM3-users] Re: Getting rid of held messages from the command line

by Mark Sapiro

On 03/16/2018 09:01 AM, Aymeric Mansoux wrote: > > However, while I was testing this happily on a list that was not affected with the JSON error, I finally tested discard_held_messages() on one of the problematic list, and I get the exact same problem as when trying to view the moderation queue API: > >>>> discard_held_messages_queue('xxx(a)xxx.xxx') > Traceback (most recent call last): > File "<console>", line 1, in <module> > File "<console>", line 6, in discard_held_messages_queue > File "/usr/local/lib/python3.5/dist-packages/mailman/app/moderator.py", line 97, in handle_message > key, msgdata = requestdb.get_request(id) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/model/requests.py", line 120, in get_request > result.data_hash, expunge=False) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/model/pending.py", line 138, in confirm > value = json.loads(keyvalue.value) > File "/usr/lib/python3.5/json/__init__.py", line 319, in loads > return _default_decoder.decode(s) > File "/usr/lib/python3.5/json/decoder.py", line 339, in decode > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > File "/usr/lib/python3.5/json/decoder.py", line 355, in raw_decode > obj, end = self.scan_once(s, idx) > json.decoder.JSONDecodeError: Unterminated string starting at: line 1 column 1 (char 0) > > With that said, even though I cannot pass the discard action, I can export the queue without problem, so I will send you off-list a sample, because I am not sure what I should be looking for. Unfortunately, that didn't help. I was able to post all the messages in your sample to a test list and even with all the messages held, I could view them and discard them in postorius. This may not be too surprising as looking at the traceback, the exception is thrown in trying to delete the pending confirmation from the pending database. The issue is when a message is held an entry is made in the pending database with a confirmation token that can be used for example to approve or discard the message by email. There is an issue that affects MySQL databases only in that prior to the merge of <https://gitlab.com/mailman/mailman/merge_requests/333> values in the pendedkeyvalue table could be truncated (or exceptions thrown depending on MySQL settings). That appears to be the issue here. The fix was only merged in January and is not in Mailman 3.1.1. > Finally, is there another way to get rid of these messages? Are there consequences if I would use message_store.delete_message(message_id) instead of handle_message(m, req.id, Action.discard)? As I said, I think the issue is with the pendedkeyvalue table, not with the message itself. The table contains entries which are pickled versions of various things. A big issue is rule_misses. For one of your messages, the rule_misses list is ['dmarc-mitigation', 'no-senders', 'approved', 'emergency', 'loop', 'banned-address', 'member-moderation'] this gets pickled into b'\x80\x03]q\x00(X\x10\x00\x00\x00dmarc-mitigationq\x01X\n\x00\x00\x00no-sendersq\x02X\x08\x00\x00\x00approvedq\x03X\t\x00\x00\x00emergencyq\x04X\x04\x00\x00\x00loopq\x05X\x0e\x00\x00\x00banned-addressq\x06X\x11\x00\x00\x00member-moderationq\x07e.' which ultimately gets stored in the pendedkeyvalue table as a value for '_pck_rule_misses' which is '"\u0080\u0003]q\u0000(X\u0010\u0000\u0000\u0000dmarc-mitigationq\u0001X\n\u0000\u0000\u0000no-sendersq\u0002X\b\u0000\u0000\u0000approvedq\u0003X\t\u0000\u0000\u0000emergencyq\u0004X\u0004\u0000\u0000\u0000loopq\u0005X\u000e\u0000\u0000\u0000banned-addressq\u0006X\u0011\u0000\u0000\u0000member-moderationq\u0007e."' Which is longer than the VARCHAR(255) MySQL field for that value prior to <https://gitlab.com/mailman/mailman/merge_requests/333>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: mass subscribers disablement!?

by Christian Stalberg

After the first time where users were unsubscribed automatically, I added back one at a time all the subscribers who were unsubscribed. Now they have all been unsubscribed again automatically. They are valid working email addresses. How can I stop this behavior from occurring please? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 26, 2021 11:03 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!? On 10/26/21 5:14 AM, Christian Stalberg via Mailman-users wrote: > Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. > Is there a way to see via the web GUI which subscribers were disabled? > Correspondingly, can I re-enable delivery for them via the web GUI? Only one at a time. You could modify the shell session I posted previously to just display the members. ``` $ bin/mailman shell 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. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print('Delivery disabled by bounce for member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> exit() ``` Alternatively you can script some mailman commands as in ``` #!/bin/bash for list in `bin/mailman lists|sed '1d'`; do echo $list bin/mailman members --nomail bybounces $list done ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years

[MM3-users] Re: hidden list is hidden even to the owner

by Mohsen Masoudfar

As always: Thanks a lot! To answer your question, I am running 1.1.2-3 # apt search postorius python-django-postorius/bionic,now 1.1.2-3 all [installed,automatic] Web user interface to access GNU Mailman3 This is after a long fight with AWS and Redhat versions, I ended up installing the mailman3-full package on Ubuntu18. Installation was straight forward and easy, but it seems it is not easily possible to update/upgrade Postorius alone in this configuration, is it? Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, July 1, 2020 5:43 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: hidden list is hidden even to the owner [EXTERNAL EMAIL] On 7/1/20 2:05 PM, Abhilash Raj wrote: > > Which version of Postorius are you running? > > Newer version shows all the lists you are related to by default when you are logged-in. So, the ones you own, moderate, subscribe to. That's correct, but it's tricky. If as an owner of an unadvertised list, you go to a URL like https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp… you will see the unadvertised list(s) that you own as well as any that you are a member or moderator of. Likewise you will see the unadvertised list(s) you own at https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp… and if you are a member as well as owner of an unadvertised list, you will see it at https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp…. But (here's the tricky part) if you go to https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp…, you will not see any unadvertised lists, not even ones you own. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 5 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 7 Nov 2021, at 10:54 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: I wound up taking a different approach. I check for other references to the message in the message store and only delete the message if there are none. The fix is at https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs<https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs> Oh nice. That seems like a sensible solution. Thanks for tackling so quickly. I’ll do some testing today and roll it out once testing is complete. -- Mark Sapiro <mark(a)msapiro.net<mailto: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(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: attachment.png Content-Type: image/png Name: attachment.png Replaced multipart/alternative part with first alternative.

4 years, 1 month

[MM3-users] Re: Exception with processing subscription confirmation email

by Mark Sapiro

On 4/29/21 7:56 AM, Eric Broens wrote: > Hi, > > A new user tried to subscribe to a mailinglist, received the confirmation > mail, and replied to it. > > The subscriber is however not subscribed and remains listed in the "pending > confirmation" list. > > The following exception appears in the error.log. > > Does anyone knows how to resolve this? In the past we didn't experience any > issues and no changes but security updates have been installed. > > Apr 29 16:15:55 2021 (1581) deque: do_confirm_verify > > Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 69, in __next__ > > return step() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 356, in _step_send_confirmation > > raise StopIteration > > StopIteration Tracebacks like the above are normal and probably shouldn't be logged at all. > Apr 29 16:16:28 2021 (1490) Uncaught runner exception: Expecting ':' > delimiter: line 1 column 256 (char 255) > > Apr 29 16:16:28 2021 (1490) Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 173, in _one_iteration > > self._process_one_file(msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 266, in _process_one_file > > keepqueued = self._dispose(mlist, msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/runners/command.py" > , line 208, in _dispose > > mlist, msg, msgdata, parts, results) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/commands/eml_confir > m.py", line 54, in process > > mlist).confirm(token) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 578, in confirm > > workflow.restore() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 146, in restore > > data = json.loads(state.data) > > File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads > > return _default_decoder.decode(s) > > File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode > > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > > File "/usr/lib64/python3.6/json/decoder.py", line 355, in raw_decode > > obj, end = self.scan_once(s, idx) > > json.decoder.JSONDecodeError: Expecting ':' delimiter: line 1 column 256 > (char 255) > > Apr 29 16:16:28 2021 (1490) SHUNTING: > 1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfcc27dda5 This one is the issue. There was some problem with the user's confirmation reply. View the shunted message with the command ``` mailman qfile path/to/var/queue/shunt/1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfcc27dda5.pck ``` although that probably won't show anything wrong as it appears that the issue is with the saved workflow. You can get the token from the shunted message and then look at the database with something like ``` SELECT data FROM workflowstate WHERE token = '<the token>' ``` but I suspect the issue is because the database is MySQL or MariaDB, your Mailman core is older than 3.3.3 and your database server mode is such that data too long for column results in truncation, and the data in this case is truncated to 255 bytes. In Mailman 3.3.3, this column was changed from VARCHAR(255) to VARCHAR(510) for MySQL. As far as subscribing the user is concerned, you can in Postorius view the subscriptions waiting user confirmation and delete this one and then `mass subscribe` the user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Can't deliver mails in queue

by Mark Sapiro

On 5/19/21 10:22 AM, Nathanael Schneider wrote: > > I then created a completely new List which did not exists in mm2.1, > subscribed two addresses and sent myself an EMail. That one worked as > intended. I then deleted the whole broken list and created it cleanly, > added the same two people, sent an email and nothing. This seems strange. If I understand, you are essentially saying the two lists are the same. I.e., you created a completely new List which did not exists in mm2.1, and that one worked. Then you deleted the whole broken list and created it cleanly ... What was different between this cleanly created list and the completely new List? > May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb49b143780> > May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net > May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4974541d0> > May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net The fact that these are the only messages says that the attempt to send that message via smtp raised no exception as exceptions would have been logged, yet you say there's nothing in the maillog so there was no connect to Postfix. What are your settings for smtp_host: and smtp_port: in the [mta] section of mailman.cfg? ... > I have no clue what to do with this. I then turned the debug module > loglevel to debug. Also nothing useful. Just an endless list of > > [...] > May 19 18:17:29 2021 (7209) [outgoing] <function deliver at > 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> > May 19 18:17:29 2021 (7203) [ArchiveRunner] starting oneloop > May 19 18:17:29 2021 (7203) [ArchiveRunner] ending oneloop: 0 > May 19 18:17:29 2021 (7209) [OutgoingRunner] finishing filebase: > 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd > May 19 18:17:29 2021 (7209) [OutgoingRunner] doing periodic > May 19 18:17:29 2021 (7209) [OutgoingRunner] committing transaction > May 19 18:17:29 2021 (7209) [OutgoingRunner] checking short circuit > May 19 18:17:29 2021 (7209) [OutgoingRunner] ending oneloop: 1 > May 19 18:17:29 2021 (7209) [OutgoingRunner] starting oneloop > May 19 18:17:29 2021 (7209) [OutgoingRunner] processing filebase: > 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e > May 19 18:17:29 2021 (7209) [OutgoingRunner] processing onefile > May 19 18:17:29 2021 (7209) [outgoing] <function deliver at > 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> > [...] > > Which also tells me nothing I can understand. It says the message in queue entry 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd is handled but gets requeued as 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e which presumably is handled and requeued again ... > I have no clue what's > going wrong. (I've turned on debugging both on the original member list > and the reduced member list. Both hang on the first delivery they do). > If I restart mailman, the message gets correctly shunted as it is > interrupted mid-delivery. My maillogs don't register any activity beside > the listpost. Any ideas what I need to do to figure out what's not > working here or where the culprit could be? Not sure if it is related to > the mailinglist being in mailman2.1 before. I have no real understanding of why this isn't working. I don't think it's likely that it has to do with the mailing list being imported from MM 2.1, but I suppose it could be. How did you create and import the list? When you say you deleted the whole broken list and created it cleanly, what did you actually do? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Abhilash Raj

On Wed, Sep 18, 2019, at 8:14 AM, Mark Sapiro wrote: > On 9/18/19 3:32 AM, Henrik Rasmussen wrote: > > I am running maxking/mailman-*:0.2 (GNU Mailman 3.2.0 (La Villa Strangiato)). > > > > It looks like Mailman is not receiving (enough) mails, but are keps in the Postfix queue and I can't figure out why. > > > > I get a lot of "mail for [172.19.199.2]:8024 is using up 7841 of 7841 active queue entries" in the postfix container log (more postfix log at the buttom. > > > I know nothing about Docker containers and how they communicate with > each other, but Postfix is trying to deliver mail via lmtp to > [172.19.199.2]:8024. Mailman's lmtp runner should be running and > listening on port 8024. Either that is not the case or that port is not > exposed to Postfix on IP 172.19.199.2. Right, that is what I was wondering, you verify that by using telnet on the specified IP and Port (172.19.199.2:8024). `docker-compose ps` lists all the running containers, do you see all the containers running? You mentioned that Mailman is not receiving enough emails, do you get *any* emails from Mailman? I am trying to see if this is a perf problem or if Mailman's LMTP isn't reachable at all. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 2 months

[MM3-users] Re: Weekend releases

by Abhilash Raj

On Tue, Dec 10, 2019, at 8:27 AM, Mark Sapiro wrote: > On 12/10/19 2:58 AM, Paul Arenson wrote: > > Thank you. The setup I am using now has Hyperkitty 1.3.0 and I just wanted to confirm. Somewhere I thought I read there is a facility in the Hyperkitty archive interface to format text. Probably I misunderstood, but if there is such a facility, I am not seeing it. Maybe I am looking for something like Tiny Ice and thus can't find it. > > > Markdown rendering of message bodies in Hyperkitty is > <https://gitlab.com/mailman/hyperkitty/merge_requests/160>. This is > installed on <https://lists.mailman3.org/mailman3/> and > <https://mail.python.org/mailman3> but is not yet released. > To add more, if you look at the merge request, there are some pieces missing before it can be merged. Especially, a mechanism to opt-out on a per-list basis from this. While markdown is pretty nice to look at when you are dealing with certain mailing lists which communicates in plain text, it can be horrible to look at if the users aren't aware about markdown and/or the special markdown syntax. In practice, there is only so much we can do to render a random email as HTML using markdown syntax. Maybe I can get to it this holiday season and it can go out for interested folks in the next Hyperkitty release :) > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years

[MM3-users] Re: hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header

by Odhiambo Washington

On Thu, Dec 29, 2022 at 2:54 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/28/22 12:22, Odhiambo Washington wrote: > > On Wed, Dec 28, 2022 at 8:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 12/27/22 22:00, Odhiambo Washington wrote: > >>> I worke up to 959 such entries in my mailmanweb.log: > >>> > >>> ERROR 2022-12-27 22:49:57,732 82073 hyperkitty.views.mailman The > >>> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > >> ... > >>> > >>> What might have been the cause of this? > >>> > >> > >> Upgrading HyperKitty without upgrading mailman-hyperkitty. HyperKitty>= > >> 1.3.5 requires mailman-hyperkitty>=1.2.0. > > > Actually, HyperKitty>=1.3.5 with mailman-hyperkitty<1.2.0 produces a > different message so that isn't it. > > There is an issue with Apache. If you search the archives of this list > for the log message you'd find it, but see the last two posts in the > thread at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > But why these messages all of a sudden? Did you just change something? > I found a mismatch! MAILMAN_ARCHIVER_KEY != api_key A single quote character had sneaked in while copying the key over to the next file. I will watch what happens when the archiver is run next and whether I really need the ' WSGIPassAuthorization On'. Thank you very much as always. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Abhilash Raj

On Thu, Oct 26, 2017, at 06:39 PM, Mark Sapiro wrote: > On 10/26/2017 06:16 PM, Fabian A. Santiago wrote: > > > > > But in my testing, I replied to a subscription confirmation message and received back an undeliverable looping email error message from postfix. Any clues there you can offer? I can post to the list from any email added via the admin console. The test subscriber address was local to my server. From an outside address, same error. > > > This usually means that postfic is trying to deliver to an address and > the message already has a Delivered-To: header with that address. > > What are the headers of the "looping" message in the report? What are > the Postfix log messages related to that message? > > > > Once I registered the new email domain, I reverted my postfix config back to the default suggested by maxking's docker instructions. > > > > https://github.com/maxking/docker-mailman > > > I have essentially no knowledge of the docker container images, so I > can't be much help with issues specific to them. The Postfix integration in container images is basically just using regex instead of hash maps and everything else is same. I do remember atleast one other person facing a similar issue where Postfix wouldn't accept listname+token@domain addresses with our regex. I am thinking this is the same issue. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

8 years, 1 month

[MM3-users] Re: Deleting default "example.com" domain breaks everything

by Abhilash Raj

On Fri, Jul 16, 2021, at 12:12 PM, Mark Sapiro wrote: > On 7/16/21 11:31 AM, mcarter(a)corneredrats.com wrote: > > Hello. I'm new with v3 of mailman. > > Installed via aptitude on deb10. > > After I logged in as admin, I created my actual domain, as "example.com" was there by default. > > I then deleted example.com, and everything broke. > > The only site I had was still using example.com. > > How do I either a) restore example.com in config or CLI (as web UI is completely broken now), or b) move my one and only "Site 1" to the domain I created? > > > Try setting `SITE = 0` in your Django settings file. If that doesn't > work, try successively 1, 2, etc. One of these should work. Usually, example.com is always 1 and then it increases sequentially. So, if this is the first one you created, I'd try using 2. > > Also going back to your prior thread, you had > > > root@mail:/usr/share/mailman3-web# python manage.py createsuperuser > > Aside from the python/python3 issue, you should run any Mailman and > Django management commands as the Mailman user (probably `list` in your > case), not as root. See https://gitlab.com/mailman/mailman/-/issues/920 > and https://gitlab.com/mailman/mailman/-/issues/776. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 4 months

[MM3-users] Re: redirecting -bounces replies

by Mark Sapiro

On 6/26/25 11:37, Hirayama, Pat wrote: > > When I look at the domains in mailman-core, I see: > >>>> show_domains() > <Domain fhcrc.org> > <Domain fredhutch.org> > <Domain lists.fhcrc.org, , alias: lists.fredhutch.org> > <Domain lists.hanc.info, , alias: > > - owner: cit-sys-engineering(a)fredhutch.org This is part of the problem. The alias domain for a list should not be a real domain. Apparently, someone set this up so that mail to lists in the lists.fhcrc.org domain would go to the corresponding list in the lists.fredhutch.org domain. I think that may actually work, but you need more. In order to add recipients to the patest-bounces addresses, the recipient domains need to have an alias domain. In the cases below the domains lists.fredhutch.org and lists.hanc.info. E.g set an alias domain for lists.fredhutch.org to x.lists.fredhutch.org and for lists.hanc.info to x.lists.hanc.info. Then postfix_vmap will contain entries like > pattest(a)lists.fhcrc.org pattest(a)lists.fredhutch.org > pattest-bounces(a)lists.fhcrc.org pattest-bounces(a)lists.fredhutch.org > pattest-confirm(a)lists.fhcrc.org pattest-confirm(a)lists.fredhutch.org > pattest-join(a)lists.fhcrc.org pattest-join(a)lists.fredhutch.org > pattest-leave(a)lists.fhcrc.org pattest-leave(a)lists.fredhutch.org > pattest-owner(a)lists.fhcrc.org pattest-owner(a)lists.fredhutch.org > pattest-request(a)lists.fhcrc.org pattest-request(a)lists.fredhutch.org > pattest-subscribe(a)lists.fhcrc.org pattest-subscribe(a)lists.fredhutch.org > pattest-unsubscribe(a)lists.fhcrc.org pattest-unsubscribe@lists.fredhutch.orgpattest@lists.fredhutch.org > > pattest(a)lists.fredhutch.org pattest(a)x.lists.fredhutch.org > pattest-bounces(a)lists.fredhutch.org pattest-bounces(a)x.lists.fredhutch.org > pattest-confirm(a)lists.fredhutch.org pattest-confirm(a)x.lists.fredhutch.org > pattest-join(a)lists.fredhutch.org pattest-join(a)x.lists.fredhutch.org > pattest-leave(a)lists.fredhutch.org pattest-leave(a)x.lists.fredhutch.org > pattest-owner(a)lists.fredhutch.org pattest-owner(a)x.lists.fredhutch.org > pattest-request(a)lists.fredhutch.org pattest-request(a)x.lists.fredhutch.org > pattest-subscribe(a)lists.fredhutch.org pattest-subscribe(a)x.lists.fredhutch.org > pattest-unsubscribe(a)lists.fredhutch.org pattest-unsubscribe@x.lists.fredhutch.orgpattest@lists.fredhutch.org > > phtest(a)lists.hanc.info pattest(a)x.lists.hanc.info > phtest-bounces(a)lists.hanc.info pattest-bounces(a)x.lists.hanc.info > phtest-confirm(a)lists.hanc.info pattest-confirm(a)x.lists.hanc.info > phtest-join(a)lists.hanc.info pattest-join(a)x.lists.hanc.info > phtest-leave(a)lists.hanc.info pattest-leave(a)x.lists.hanc.info > phtest-owner(a)lists.hanc.info pattest-owner(a)x.lists.hanc.info > phtest-request(a)lists.hanc.info pattest-request(a)x.lists.hanc.info > phtest-subscribe(a)lists.hanc.info pattest-subscribe(a)x.lists.hanc.info > phtest-unsubscribe(a)lists.hanc.info pattest-unsubscribe@x.lists.hanc.infopattest@lists.hanc.info And I think postfix_lmtp will contain entries like > pattest(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-bounces(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-confirm(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-join(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-leave(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-owner(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-request(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-subscribe(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > pattest-unsubscribe(a)x.lists.fredhutch.org lmtp:[mailman-core]:24 > > phtest(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-bounces(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-confirm(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-join(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-leave(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-owner(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-request(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-subscribe(a)x.lists.hanc.info lmtp:[mailman-core]:24 > phtest-unsubscribe(a)x.lists.hanc.info lmtp:[mailman-core]:24 In any case you will then be able to add the additional recipient to the phtest-bounces(a)lists.hanc.info entry in postfix_vmap. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[MM3-users] Re: Moderation action "None" is misleading

by Markus Grandpré

Dear Mr Sapiro, dear Mr Turnbull, thank you very much for your reply. For clarification I like to change: > What versions of Mailman and Postorius are you using? * mailman3, v3.3.8-2~deb12u2 * mailman3-web, v0+20200530-2.1 * python3-django-mailman3, v1.3.9-1 * python3-django-postorius, v1.3.8-3 * python3-mailman-hyperkitty, v1.2.1-1 * python3-mailmanclient, v3.3.5-1 with Debian GNU/Linux 12 (bookworm). So the newest changes: > This is https://gitlab.com/mailman/postorius/-/issues/577 fixed in > Postorius 1.3.9 by https://gitlab.com/mailman/postorius/-/ > merge_requests/811 are not yet available on our system. Hopefully we won't have to wait too long with Debian as there is already a lot of confusion among some of our many list administrators as we only started using Mailman3 for production a few days ago. Best Markus Am 04.02.25 um 19:25 schrieb Mark Sapiro: > On 2/4/25 02:51, Markus Grandpré wrote: >> Dear List, >> >> I find the use of the term 'None' (or 'Kein' in the German >> translation; see attachments) in the 'Moderation action' column of the >> member list misleading, as the term suggests that no moderation action >> is applied to the respective member. >> >> However, this is not necessarily the case. If you check a member’s >> "Administration options / Moderation" setting, a moderation action, >> such as "Moderation" or "List default", may be in effect. > > This is https://gitlab.com/mailman/postorius/-/issues/577 fixed in > Postorius 1.3.9 by https://gitlab.com/mailman/postorius/-/ > merge_requests/811 > > See the UI changes at https://docs.mailman3.org/projects/postorius/en/ > latest/news.html#news-1-3-9 > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

10 months, 1 week

[MM3-users] Re: Migration from 2.1 to 3

by Mark Sapiro

On 12/27/19 6:54 AM, brunol(a)agro.uba.ar wrote: >> What do you mean by constantly appearing? Do you mean endlessly > repeating or that they just repeat a number of times equal to the number > of expected recipients of the post? > > Sorry, I meant endlessly repeating. > > This is a piece from debug after sending an email to the list from a recipient that does not need moderation: > > Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> > Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de264a8> > Dec 27 11:41:10 2019 (11468) [BounceRunner] starting oneloop > Dec 27 11:41:10 2019 (11468) [BounceRunner] ending oneloop: 0 > Dec 27 11:41:10 2019 (11473) Cannot connect to SMTP server 127.0.0.1 on port 25 This message is logged only once, but the issue occurs every time. deliver is getting a socket.error exception on its attempt to connect to the MTA. Thus, sending of this message fails and the message is requeued and the process repeats. Is an MTA listening on 127.0.0.1 on port 25? The only question is if we can't send this mail, how can we send the 'held for moderation' notices?. These are sent the same way. > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.0510046+6fe6039c1b0b65672aade3bfced1aca2fe8afa16 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.5784276+6f5454f4a57da4dc15912e789f0719be53c74616 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile > Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> > Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de26e10> > Dec 27 11:41:10 2019 (11470) [IncomingRunner] starting oneloop > Dec 27 11:41:10 2019 (11470) [IncomingRunner] ending oneloop: 0 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.5784276+6f5454f4a57da4dc15912e789f0719be53c74616 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.61572+a2844469514ead14dedcee020ad8e2a34036f8ef > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile > Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> > Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3de26f28> > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] finishing filebase: 1577457670.61572+a2844469514ead14dedcee020ad8e2a34036f8ef > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] doing periodic > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] committing transaction > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] checking short circuit > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] ending oneloop: 1 > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] starting oneloop > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing filebase: 1577457670.6512213+13fe7854257bb1a494f797f480cb10733bd440ac > Dec 27 11:41:10 2019 (11473) [OutgoingRunner] processing onefile > Dec 27 11:41:10 2019 (11473) [outgoing] <function deliver at 0x7f7c3de987b8>: <CAOwJ5NX+K3CORg9riHc2T1dbdKZLZojHT1MVs44Wd3SbTJju6A(a)mail.gmail.com> > Dec 27 11:41:10 2019 (11473) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f7c3dd44390> > Dec 27 11:41:10 2019 (11469) [CommandRunner] starting oneloop > Dec 27 11:41:10 2019 (11469) [CommandRunner] ending oneloop: 0 > > This is endlessly repeating with different filebase > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: How to delete large numbers of held messages

by lists＠g1fef.co.uk

Mark Sapiro wrote: > On 4/22/22 02:11, Chris via Mailman-users wrote: > > Mark Sapiro wrote: > > I suggest the following in mailman shell > > >> $ bin/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 > >> >>> from mailman.app.moderator import handle_message > >> >>> requestdb = IListRequests(m) > >> >>> for id, type in requestdb.held_requests: > >> ... if type == RequestType.held_message: > >> ... handle_message(m, id, Action.discard) > >> ... > >> >>> commit() > > > Thanks for the reply, unfortunately that gives an error: > > Traceback (most recent call last): > > File "<console>", line 1, in <module> > > TypeError: cannot unpack non-iterable _Request object > > Sorry, my mistake. > Try this: > $ bin/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 > >>> from mailman.app.moderator import handle_message > >>> requestdb = IListRequests(m) > >>> for req in requestdb.held_requests: > ... if req.request_type == RequestType.held_message: > ... handle_message(m, req.id, Action.discard) > ... > >>> commit() Perfect - thank you Chris

3 years, 7 months

[MM3-users] Re: Key Error when clicking on a list

by Mark Sapiro

On 6/19/20 9:02 AM, Jacob Bargery wrote: > I looked back and tried to see if this is related to the Filter_Vhost = true error. In the email log I received at the bottom where it lists settings I am seeing Filter_Vhost = false. So I am guessing it is not related I could be wrong though. > > I can see lists populated that have been created, but when I click to open them it immediately goes to page titled "Server Error" and reading "An error occurred while processing your request.". This is part of the email, I can include the rest with settings if that will help. > > > Internal Server Error: /mailman3/postorius/lists/testlist.groups.smccme.edu/ > > KeyError at /postorius/lists/testlist.groups.smccme.edu/ > 'file' As has been mentioned many times on this list, the KeyError at ... 'file' exception is not the issue. It is a result of Django encountering this issue in trying to log the real exception. > Request Method: GET > Request URL: http://groups.smccme.edu/mailman3/postorius/lists/testlist.groups.smccme.ed… You are trying to get the list view for the testlist.groups.smccme.edu list ant that causes: > Traceback: > > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner > 34. response = get_response(request) > > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response > 115. response = self.process_exception_by_middleware(e, request) > > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response > 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) > > File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in view > 71. return self.dispatch(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/postorius/views/generic.py" in dispatch > 65. return super(MailingListView, self).dispatch(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in dispatch > 97. return handler(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/postorius/views/list.py" in get > 252. 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 The above appears to be where the issue arises. The full code bit here is > if ('hyperkitty' in settings.INSTALLED_APPS and # noqa: W504 > 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 > self.mailing_list.archivers['hyperkitty']): > data['hyperkitty_enabled'] = True The condition `'hyperkitty' in self.mailing_list.archivers` is causing Postorius to try to get the archivers associated with this list, and that's where the 500 occurs. > File "/usr/lib/python3.8/_collections_abc.py" in __contains__ > 666. self[key] > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in __getitem__ > 151. return self._get(key) > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in _get > 90. return self.rest_data[key] > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in rest_data > 76. response, content = self._connection.call(self._url) > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py" in call > 99. raise HTTPError(url, response.status, content, response, None) this 500 return from Mailman core: > During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred: This "another exception occurred" is irrelevant. For more information on exactly what caused the 500 from core, you have to look in var/logs/mailman.log. There is presumably something wrong with that list's archivers configuration. This shouldn't happen, but without the error and traceback information from mailman.log, we don't know what the problem is. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Is there a way of recording bounce messages?

by Thomas Ward

Mark, As a person fluent in MS365 they are a catchall. The MS server tends to always accept the message. It then triggers a bounce after the fact because of the multilayered transit patterns MS365 uses for handing off messages. I know this because of custom mailing alert system integrations with MS365 not triggering SMTP transfer time alerts but receiving the bounces after MS365 has received the message and hands off to its edge transports to remote clients, then later sends a DSN. (I have spent three weeks digging on this for a FT Job task so I am unfortunately damned fluent in how MS365 processes SMTP to recipients that will decline or bounce...) MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. Thomas Sent from my Galaxy -------- Original message -------- From: Mark Sapiro <mark(a)msapiro.net> Date: 9/21/23 19:36 (GMT-05:00) To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Is there a way of recording bounce messages? On 9/21/23 15:01, Andrew Hodgson wrote: > Mark Sapiro <mark(a)msapiro.net> wrote: > >> Can you provide one of the bounce report messages and the corresponding bounce message from the MTA log. > > I only have the message I would get as the owner of the list that the delivery has been disabled, That's the one I'm interested in. If possible I'd like to see the actual raw message, not some MUAs rendering of it. > I don't have the original bounce message. One thing to note is the bounce messages coming in from Gmail are being generated by Office 365 (as that is the outbound smarthost for the Mailman server), so it may be due to the format of those NDRs why we aren't seeing the original bounce messages attached to the email. So as I understand it, Office 365 is sending the mail to the gmail recipient which is presumably rejecting the mail at SMTP with a 5xx status. Does Office 365 report the failure to Mailman with a failure status at SMTP time or later with an emailed DSN. If the former, there should be log messages in Mailman's smtp.log indicating the number of failures '$msgid post to $listname from $sender, $size bytes, $refused failures' and the reason for each '$msgid delivery to $recip failed with code $smtpcode, $smtpmsg'. Also, we create a fake DSN. See https://gitlab.com/mailman/mailman/-/blame/master/src/mailman/runners/outgo… If the latter we have the DSN from Office 365. In either case, the DSN should be attached to the notice. I don't know why it wouldn't be. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to teward(a)thomas-ward.net

2 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I got this error starting mailman service: [mailman@localhost ~]$ source env2Traceback (most recent call last): File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in create_server sock.bind(sa) OSError: [Errno 99] Cannot assign requested address During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/var/lib/mailman/env/bin/runner", line 11, in <module> sys.exit(main()) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/runner.py", line 198, in main runner.run() File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/runners/lmtp.py", line 242, in run self.lmtp.start() File "/var/lib/mailman/env/lib/python3.6/site-packages/aiosmtpd/controller.py", line 55, in start raise self._thread_exception File "/var/lib/mailman/env/lib/python3.6/site-packages/aiosmtpd/controller.py", line 35, in _run ssl=self.ssl_context)) File "/usr/local/lib/python3.6/asyncio/base_events.py", line 466, in run_until_complete return future.result() File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1047, in create_server % (sa, err.strerror.lower())) OSError: [Errno 99] error while attempting to bind on address ('192.185.51.89', 8024): cannot assign requested address What do you think? El lun., 24 jul. 2017 a las 17:47, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 03:31 PM, Rafael Mora wrote: > > I got this on maillog: > > > > > > > > [root@localhost log]# cat maillog > > > There's nothing in that log that shows any attempts by anything to > connect to Postfix. You have to look at logs from the processes you > think are trying to send mail and see what they're doing. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 4 months

[MM3-users] Re: Apache Conf

by Thomas G

I found ! Based on https://stackoverflow.com/questions/26848945/exclude-an-alias-from-virtualh… We have to exclude /static/ <VirtualHost *:80> ServerName mailing.hatlab.fr ErrorLog ${APACHE_LOG_DIR}/mailing.error.log CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined Alias /static/ /opt/mailman/static/ <Directory /opt/mailman/static/> Require all granted </Directory> ProxyPassMatch ^/static ! ProxyPass / http://localhost:8000/ ProxyPassReverse / http://localhost:8000/ </VirtualHost> Le ven. 19 oct. 2018 à 21:08, Thomas G <thomas82710(a)gmail.com> a écrit : > Same result with Alias "/static/" "/opt/mailman/static/" > > I have sometimes: > [Fri Oct 19 22:05:52.583841 2018] [proxy_http:error] [pid 8328:tid > 140435053815552] (104)Connection reset by peer: [client 1xxxxxxx1794] > AH01102: error reading status line from remote server localhost:8000 > [Fri Oct 19 22:05:52.583874 2018] [proxy:error] [pid 8328:tid > 140435053815552] [client 1xxxxxxx:51794] AH00898: Error reading from remote > server returned by /static/hyperkitty/libs/jquery/jquery-1.10.1.min.js > But it's not systematic. > > Alias seem to be ignored by the proxy. > > > Le ven. 19 oct. 2018 à 20:48, Mark Sapiro <mark(a)msapiro.net> a écrit : > >> On 10/19/18 12:17 PM, Thomas G wrote: >> > Hi tried both. >> > >> > Same result. >> > >> > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET >> /static/postorius/js/script.js >> > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) >> > Gecko/20100101 Firefox/60.0" >> >> >> What's in the apache error log? >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> >

7 years, 1 month

[MM3-users] Re: Cannot setup announce-only mailing list

by Abhilash Raj

On Thu, Jan 30, 2020, at 9:58 AM, Mark Sapiro wrote: > On 1/30/20 5:42 AM, Alberto Granzotto wrote: > > > > Of course, I want to keep this mailing list "read only" for members, and > > I want only selected people to post to that mailing list. > > > > Any idea on how to achieve that? > > > There is only one difference between the `Discussion` and `Announce` > list styles, and that is for an `Announce` list, the `allow_list_posts` > attribute is set to `False`. In turn, all that does is cause the > List-Post: header to be set to NO rather than the list posting address. > > There is a discussion at <https://wiki.list.org/x/4030685> of how to set > up an announce list for Mailman 2.1. Most of this translates > straightforwardly to Mailman 3, although not all the relevant settings > are exposed in Postorius. > > In short, you need to set this up manually using things like moderation > settings and custom templates for the welcome message. Mark, do you think we should make the actual announce-only style reflect these settings so folks don't have to manually set these after they create a announce-only list? I am not sure the reason behind these settings lacking for the current announce-only style. Are there situations where announce-only list would have different list setting? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 10 months

[MM3-users] Re: Slow and out-of-sequence delivery

by Mark Sapiro

On 12/16/22 13:18, Gregg Roberts wrote: > > Messages that I post to the forum have been taking as long as 48 hours > to come back to me. The issue is not new and AFAIK no one has been > messing with the settings. But the issue seems to have been becoming > more and more severe in recent weeks. This is a symptom of a backlogged out queue in Mailman. > Perhaps because of such delays, I also sometimes see responses to other > posts before I see the original post. It takes extra time to understand > the context when that happens. People's time gets wasted answering > questions that have already been answered without their knowledge. It's > just frustrating all around. > > The email address from which messages are sent is not in the list of > email addresses maintained in the hosting account cPanel. There seems to > be one by the name "relay" that is being used by Mailman. > > I actually don't know which version of Mailman is installed. I'm hoping > it's the more recent of the two options so I optimistically joined this > particular list. The Mailman provided with cPanel is Mailman 2.1, not Mailman 3. > The hosting service tech support can't help because they can't see the > forum email address or its logs. At least that's what they say. The hosting service only offers Mailman because it is part of cPanel. Unfortunately this is true of many cPanel based hosting services. They offer Mailman but are incompetent to support it. Your issue is a symptom of a backlogged out queue and it probably has nothing to do with your list. There will be only one Mailman instance on the cPanel host machine and it will be delivering messages for all the lists on all the virtual hosts supported by that machine. There are threads in the archives on the backlogged out queue issue, e.g. <https://mail.python.org/archives/list/mailman-users@python.org/thread/QGVWW…> and <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. There is also a FAQ article at <https://wiki.list.org/x/17892002>. > A contract tech support guy has suggested that it might solve a problem > if we started spending $100-$150 per month on a dedicated server. I > think that is a wrongheaded suggestion. If the organization had > thousands of members, it would make more sense. But throwing money at > the problem if something is simply not set up right, or some critical > file is corrupted, is not the right solution. Set the broken bone > correctly first, THEN inject stimulants and send the player back out > onto the field. :-) A dedicated server might help, but probably only because it would remove you from the impact of Mailman lists from other vhosts on the shared server. There are things the host can do to improve the situation, but only if they are competent in tuning Mailman and the outgoing MTA. If they are willing to work on this, they are welcome to post to mailman-users(a)python.org <https://mail.python.org/mailman3/lists/mailman-users.python.org/> and we will try to help, but you are at their mercy to fix this and your only recourse is to look for a different hosting service. If it's only for Mailman lists, see <https://wiki.list.org/COM/Mailman%20hosting%20services>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Hyperkitty no longer archiving

by Hirayama, Pat

> -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Tuesday, November 22, 2022 2:21 PM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Hyperkitty no longer archiving > > On 11/22/22 13:40, Hirayama, Pat wrote: > > > > There is only one uwsgi.ini file, and it is in the same directory as settings.py, > settings_local.py and wsgi.py > > > What is the content of that file? uwsgi.ini: [uwsgi] uwsgi-socket = :8000 chdir = /opt/mailman/mailman-suite/mailman-suite_project wsgi-file = /opt/mailman/mailman-suite/mailman-suite_project/wsgi.py harakiri = 60 master = true process = 4 threads = 4 uid = mail gid = mail attach-daemon = ./manage.py qcluster The referenced wsgi.py looks pretty vanilla: """ import os # import sys # import site # For some unknown reason, sometimes mod_wsgi fails to set the python paths to # the virtualenv, with the 'python-path' option. You can do it here too. # # # Remember original sys.path. # prev_sys_path = list(sys.path) # # Add here, for the settings module # site.addsitedir(os.path.abspath(os.path.dirname(__file__))) # # Add the virtualenv # venv = os.path.join(os.path.abspath(os.path.dirname(__file__)), # '..', 'lib', 'python2.6', 'site-packages') # site.addsitedir(venv) # # Reorder sys.path so new directories at the front. # new_sys_path = [] # for item in list(sys.path): # if item not in prev_sys_path: # new_sys_path.append(item) # sys.path.remove(item) # sys.path[:0] = new_sys_path from django.core.wsgi import get_wsgi_application os.environ.setdefault("DJANGO_SETTINGS_MODULE", "settings") application = get_wsgi_application() > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org Thanks! -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org

3 years

[MM3-users] Re: Message getting held due to max number of recipients and maximum message size

by Wong, Wesley

I can confirm that the list was set to 0 for max recipients and message size. In addition, I checked the base.py and the defaults are the ones in the message. If I went ahead and modified the settings in base.py, would this immediately to all existing lists in Mailman? wesley -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, September 22, 2023 1:04 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Message getting held due to max number of recipients and maximum message size On 9/22/23 11:37, Wong, Wesley wrote: > > Currently, the settings are set to 0 for both settings on the list so I am not sure where mailman is getting the default settings. Is this default hard coded somewhere in the Mailman core? The version of Mailman running is 3.3.6. This is very strange. Are you certain the list's settings are 0? Are there possibly two lists in different domains or otherwise similar names and you are looking at the wrong one? The only place where the defaults are set is in mailman/styles/base.py and this only affects the default settings for a new list. The values in the ``` Message has more than 10 recipients The message is larger than the 40 KB maximum size ``` messages come from the list's settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to wesley.wong(a)anderson.ucla.edu

2 years, 2 months

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 13:21, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/03/2017 10:42 AM, Rafael Mora wrote: > > > > I've found the MX records on my cpanel but how do I redirect the emails > > going to my list to my private server? > > > You have to configure the MTA that is the MX for the domain to relay the > mail to the Mailman server. > Our domain is: LABBRANDS.COM We have that domain config in a Hosgator hosting. The emails sent to labbrands.com go to our hosting, so how do I tell cpanel in hostgator hosting that the mails sent to the list ( mailing(a)labbrands.com) are redirect to the MTA (postfix) in my private server (we have static public IP address) ?? > > > > I still don't get it. What if I just suscribe the members and then send > the > > email to the suscribers the thing is that the email has to be received by > > mailman in order to resend it to the list suscribers right? > > > If all you want to do is send mail that you generate, you can use > > mailman inject > > to deliver the mail to Mailman on the local machine. The drawback of not > being able to receive mail from the outside is Mailman won't receive > bounce DSNs from remote servers. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 4 months

[MM3-users] Re: Apache+mod_wsgi issue

by Mark Sapiro

On 12/22/22 22:26, Odhiambo Washington wrote: > On Fri, Dec 23, 2022 at 9:21 AM Odhiambo Washington <odhiambo(a)gmail.com> > wrote: > >> And now I am having a problem with mod_wsgi. >> First, the URL displayed when I load the page looks bogus to me. >> While I expect the URL to be >> https://mm3-lists.kictanet.or.ke/mailman3/domains/, mod_wsgi give me >> https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - there is an >> extra /mailman3! See below: >> So I have; >> 1. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/ - working, >> or appears to. >> 2. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - working, >> or appears to. >> 3. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/bans/ - working, or >> appears to >> 4. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/users - working, or >> appears to >> 5. >> https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/kictanet.lists.kic… >> - This throws an exception error when I click "Manage Subscription". >> >> -> https://pastebin.ubuntu.com/p/RkKH793Jgw/ messages like these [Fri Dec 23 09:10:55.393386 2022] [wsgi:error] [pid 74857] [remote 197.232.81.246:14181] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailmanclient/restbase/connection.py", line 160, in call [Fri Dec 23 09:10:55.393390 2022] [wsgi:error] [pid 74857] [remote 197.232.81.246:14181] raise HTTPError(params.get('url'), response.status_code, [Fri Dec 23 09:10:55.393394 2022] [wsgi:error] [pid 74857] [remote 197.232.81.246:14181] urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} Indicate an uncaught exception in Mailman core. What's in mailman.log? >> And while I do not quite understand the error itself, there is also one >> particular line that I also saw that has left me baffled: >> [Fri Dec 23 08:53:18.290411 2022] [core:info] [pid 91236] [client >> 197.232.81.246:13865] AH00128: File does not exist: >> /usr/local/www/apache24/data/archives/list/ >> kictanet(a)lists.kictanet.or.ke/thread/VIHCC6MSXZSNHY7YPEJ3D2US4N7MHJEC/, >> referer: >> https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke This is because something is doing an HTTP GET for `/archives/list/kictanet(a)lists.kictanet.or.ke/thread/VIHCC6MSXZSNHY7YPEJ3D2US4N7MHJEC/` and the URL is not recognized as one handled by mod_wsgi so apache tries to get it from its DocumentRoot. mod_wsgi has to serve a number of URLs. Look in /opt/mailman/mm/urls.py for urlpatterns. You will probably see things like url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', admin.site.urls), url(r'^mailman3/', include('postorius.urls')), url(r'^archives/', include('hyperkitty.urls')), Those are all things that need to be handled by mod_wsgi In your apache config, you only have a WSGIScriptAlias for /mailman3. Thus paths need to be prefixed with /mailman3 in order to be handled by mod_wsgi. I'm not sure what is doing this prefixing, but without it paths that don't begin with /mailman3 don't work unless you also have things like WSGIScriptAlias /accounts /opt/mailman/mm/wsgi.py WSGIScriptAlias /admin /opt/mailman/mm/wsgi.py WSGIScriptAlias /archives /opt/mailman/mm/wsgi.py in your apache config. > I also need to add the fact that at the point where I am clicking "Manage > Subscription", the URL has changed to > https://mm3-lists.kictanet.or.ke/mailman3/archives/list/kictanet@lists.kict… > (just a single /mailman3). > Something is adding mailman3/ to URLs. In the above the URL should be https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k…, but an extra /mailman3 is added. The others are like https://mm3-lists.kictanet.or.ke/mailman3/lists/ and an extra /mailman3 is added. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I tested with python3 and got this: (env) [mailman@localhost mailman-suite_project]$ python3 manage.py migrate Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/var/lib/mailman/env/lib/python3.6/site-packages/django/core/management/__init__.py", line 363, in execute_from_command_line utility.execute() File "/var/lib/mailman/env/lib/python3.6/site-packages/django/core/management/__init__.py", line 337, in execute django.setup() File "/var/lib/mailman/env/lib/python3.6/site-packages/django/__init__.py", line 27, in setup apps.populate(settings.INSTALLED_APPS) File "/var/lib/mailman/env/lib/python3.6/site-packages/django/apps/registry.py", line 85, in populate app_config = AppConfig.create(entry) File "/var/lib/mailman/env/lib/python3.6/site-packages/django/apps/config.py", line 94, in create module = import_module(entry) File "/usr/local/lib/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 978, in _gcd_import File "<frozen importlib._bootstrap>", line 961, in _find_and_load File "<frozen importlib._bootstrap>", line 948, in _find_and_load_unlocked ModuleNotFoundError: No module named 'hyperkitty' Why does it say that hyperkitty is not installed? El vie., 21 jul. 2017 a las 14:37, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:33 PM, Rafael Mora wrote: > > > > I'm getting an error doing: > > > > (env) [mailman@localhost mailman-suite_project]$ python2 manage.py > migrate > > Traceback (most recent call last): > > File "manage.py", line 8, in <module> > > from django.core.management import execute_from_command_line > > ImportError: No module named django.core.management > > > Have you installed Django in your 'env' virtualenv? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 4 months

[MM3-users] Re: FILTER_VHOST fix - was: Postorius & multi domain

by Gelpi Andrea

Il 23/04/20 01:08, Mark Sapiro ha scritto: > On 4/22/20 11:52 AM, Mark Sapiro wrote: >> >> I'm currently working on a better fix. I'll post here on my progress. > > > I've got a tentative fix at > <https://gitlab.com/mailman/postorius/-/merge_requests/500/>. You can > see the changes there to the file src/postorius/views/list.py. > > This fix is limited in that it should enable FILTER_VHOST work in an > environment where there are domains with web host different from mail > host, but if there are multiple domains with the same web host but > differing mail hosts, going to that domain's Postorius lists view will > show all domains as if FILTER_VHOST is False. > > I.e. consider the following set of domains: > > mail host web host > example.com lists.example.com > example.net example.net > example.org lists.example.org > example.edu lists.example.org > > With the fix installed and FILTER_VHOST = True > > https://lists.example.com/postorius/lists/ will show only the > example.com lists > > https://example.net/postorius/lists/ will show only the example.net lists > > but https://lists.example.org/postorius/lists/ will show all lists, not > just the example.org and example.edu lists. > I saw the change in the file. As I'm not a programmer How can I test your fix? My system was installed via Debian 10 stable repository. I upgrade with testing repository postorius, django and mailmanclinet Postorius V 1.3.2 Django V. 2.2.12 Django filters V 2.1.0 Djanog mailman V 1.3.2 mailmanclient V 3.3.0 Thnak You -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

5 years, 7 months

[MM3-users] Re: Installation Questions [Installation}

by Arte Chambers

For other things like the systemd service and the postfix and web server configs, you need to do them as root (via sudo). Does this mean i need to add the mailman user as a sudoer? On Sun, Nov 3, 2024, 8:07 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/3/24 11:31, Arte Chambers via Mailman-users wrote: > > Hello everyone, > > > > I'm running Ubuntu 24.10 and following the Virtualenv instructions > > < > https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-mailman-u… > >. > > When creating the mailman user per the instructions I find that the > mailman > > user doesn't have sufficient permissions to do things later in the > > installation such as creating files in /etc. What steps should I take to > > ensure that the mailman user has the correct permissions to install the > > Mailman app. > > > We should probably cover this in the docs, but for /etc/mailman3, you > should do > ``` > sudo mkdir /etc/mailman3 > sudo chown mailman:mailman /etc/mailman3 > sudo chmod 755 /etc/mailman3 > ``` > Then you can create all the subordinate files as the mailman user. For > other things like the systemd service and the postfix and web server > configs, you need to do them as root (via sudo). > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to paul.m.robey(a)gmail.com >

1 year, 1 month

[MM3-users] Re: Internal Server Error: /hyperkitty/list/my@lists.domain.eu/pop-threads

by Mark Sapiro

On 2/22/21 8:26 AM, Marco Marinello wrote: > Dear Mark, > > thank you for your answer. > I can confirm my Hyperkitty works just fine for archiving messages. I can even confirm Hyperkitty can reach Mailman REST API. > I haven't touched the LOGGING configuration but here you go (can even confirm hyperkitty.log is filled correctly with logs): What I was trying to say is this KeyError at /hyperkitty/list/my(a)lists.domain.eu/pop-threads 'file' exception often occurs in messages sent by Django to site admins and is never actually relates to the real problem and should just be ignored. > In mailman.log, instead, it seems like there's some issue with PostgreSQL > > [2021-02-21 18:57:19 +0000] [11685] [ERROR] Error handling request /3.1/users/user(a)example.com > Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.6/site-packages/gunicorn/workers/sync.py", line 134, in handle > self.handle_request(listener, req, client, addr) > File "/opt/mailman/venv/lib64/python3.6/site-packages/gunicorn/workers/sync.py", line 175, in handle_request > respiter = self.wsgi(environ, resp.start_response) > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 274, in falcon.api.API.__call__ > File "falcon/api.py", line 269, in falcon.api.API.__call__ > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/rest/users.py", line 211, in on_get > okay(response, self._resource_as_json(self._user)) > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/rest/helpers.py", line 124, in _resource_as_json > resource = self._resource_as_dict(resource) > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/rest/users.py", line 130, in _resource_as_dict > user_id = self.api.from_uuid(user.user_id) > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/api.py", line 78, in from_uuid > return uuid.hex > AttributeError: 'NoneType' object has no attribute 'hex' > [21/Feb/2021:18:57:19 +0000] "GET /3.1/users/user(a)example.com HTTP/1.1" 500 0 "-" "-" I think this is the real issue. HyperKitty is trying to get the user information from core for user(a)example.com and this is throwing the AttributeError resulting in the 500. This is most likely some kind of database issue. at this point > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/rest/users.py", line 211, in on_get > okay(response, self._resource_as_json(self._user)) self._user is not None, but at this point > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/rest/users.py", line 130, in _resource_as_dict > user_id = self.api.from_uuid(user.user_id) user.user_id is None. If I were you, I would look at the database. First, I would find the entry in the address table. I.e., select user_id from address where email = 'user(a)example.com'; then the uid select uid from uid where id = <the user_id from above> I suspect there is no uid entry for this id. You might get more information from $ /opt/mailman/mm/bin/mailman shell 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. >>> um = getUtility(IUserManager) >>> usr = um.get_user('user(a)example.com') which I suspect will also throw an exception, but if not >>> usr.id should return the id found by select user_id from address where email = 'user(a)example.com'; and >>> usr.user_id should return the uiud which should not be None -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Multiple domain problem

by Odhiambo Washington

Are you by any chance doing redirection to https in your VHOSTS? For me I beg to see your VHOST configuration. Also is it absolutely necessary to hide your domain names? On Mon, Feb 13, 2023, 13:05 Lars Bjørndal <lars(a)lamasti.net> wrote: > Hi, Marik! > > I realized that I had two variables in settings.py where the domains is > listed, and one of them had a preceding https. > > I've now followed the documentation for configuring Apache here: > https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur…. > I want both domains to start mailman3 when contacting > example1.com/mailman3 and example2.com/mailman3. I have the sam > configuration in both virtualhost section in Apache. For > example1.com/mailman3, it works perfectly. For example2.com/mailman3 > however, the browser (elinks), reports Host not found: example2.commailman3 > e.g. without a slash after the domain name. What could cause this to happen? > > Thanks > Lars > > On Fri, Feb 10, 2023 at 11:59:02AM -0800, Mark Sapiro wrote: > > On 2/10/23 01:43, Lars Bjørndal wrote: > > > On Thu, Feb 09, 2023 at 02:05:09PM -0800, Mark Sapiro wrote: > > > > On 2/9/23 13:21, Lars Bjørndal wrote: > > > > > > > > > > If I connect to example2.com, the title is example2.com, without > the > > > > > preceding List index. And the body says Page not found. > > > > > > > > > > > > What's in the browser's address bar for that page? > > > > > > It's https://example2.com/mailman3/lists/ > > > > And when you get the Page not found, is it a browser 404 error or a > > Postorius error page? > > > > > > > > > > > What's in Postorius domains view? > > > > > > I realized that I have to change SIT_ID to 1 to be able to connect to > http://localhost:8000/. Then, when checking Domains, I have both domains > with different SIT_ID value (1 and 2). > > > > > > Why are you going to http://localhost:8000/? You should be able to see > the > > domain's view at https://example1.com/mailman3/domains/ or > > https://example1.com/mailman3/domains/ or by just clicking Domains in > > Postorius top nav bar. > > > > > > > Going to http://localhost:8000/admin and choosing Sites, I have both > domains listed. > > > > > > Again you should be able to go to https://example1.com/admin or > > https://example2.com/admin. If these don't work, you need to add > directives > > in your web server to proxy them to http://localhost:8000/admin > > > > -- > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > San Francisco Bay Area, California better use your sense - B. Dylan > > > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > This message sent to lars(a)lamasti.net > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 10 months

[MM3-users] Re: Hyperkitty attachments

by Eric Broens

Mark, thanks for the prompt reply. Most of the posts on one of the mailinglists, dedicated to astrophotography, have large pictures attached. It would be good to offload these from the database to a bigger HDD for space constraints (DB is running on SSD). I rather like to keep the occasional 'regular' attachments posted on the other mailinglists in the DB. Best regards, Eric -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, 10 December 2025 20:05 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Hyperkitty attachments On 12/10/25 1:24 AM, Eric Broens via Mailman-users wrote: > > Hyperkitty provides the possibility to store attachments on the disk > by the config parameter HYPERKITTY_ATTACHMENT_FOLDER. > > Is it possible to export attachments to disk if they are stored in the > DB, and have them linked into the archived mail? Yes, `django-admin attachments_to_file` does that. Note that depending on your installation the `django-admin` command might be named `mailmanweb` or `manage.py` or something else. > Is it possible to decide per mailinglist if attachments should be > stored in DB or on disk? No. > If not, I would like to request this feature. Can you explain your use case that makes this desirable? It seems to me that storing attachments in the DB or in the file system is a system administrative decision, and normally at least, attachments are only available to end users via the HyperKitty UI regardless of where they are stored. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ 4DBBE3B55RDUBAK26N2AR5XB6VMQMRWX/ This message sent to eric.broens(a)skynet.be

2 days, 3 hours

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Michael.Sanderson＠ubc.ca

Mark, thanks for your response. It is perhaps non-fatal, but we do have a different number of templates processed. This is from a successful run with django-allauth==0.57.0. Note the different count of templates from the “failed” processing and this one. (venv) [mailman@rubytears ~]$ mailman-web compress Compressing... done Compressed 2 block(s) from 124 template(s) for 1 context(s). Is this compression of web content that will served to clients? Compressed data would be preferred over non-compressed to decrease data volume, but non-compressed will be served if compressed isn’t available? Michael Sanderson > On Nov 7, 2023, at 7:46 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > [CAUTION: Non-UBC Email] > > On 11/7/23 16:26, Michael.Sanderson(a)ubc.ca wrote: >> Despite earlier comments that django-allauth 0.58.1 has been released to fix this issue (and presumably 0.58.2 would have the fix as well), there appears to still be an issue. As Odhiambo indicated with django-allauth==0.57.0, mailman-web compress completes without errors. With django-allauth 0.58.1 and 0.58.2, I still get >> (venv) $ mailman-web compress >> Compressing... Error parsing template socialaccount/signup.html: socialaccount/base.html >> done >> Compressed 2 block(s) from 78 template(s) for 1 context(s). > > > I don't think this is fatal, but I have reported it at https://github.com/pennersr/django-allauth/issues/3513 > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to michael.sanderson(a)ubc.ca

2 years, 1 month

[MM3-users] Re: mailman 3 adding extraneous /var/ to pid path?

by Abhilash Raj

On Thu, Sep 21, 2017, at 02:42 PM, Mark Sapiro wrote: > On 09/21/2017 01:29 PM, Andrew Hodder wrote: > > > > I keep getting around this by creating symlinks to the pid file and then > > the stop works, but it's getting silly. It seems like mailman just assumes > > CWD + /var/ + master.pid must be the location. Once I realized this, I > > found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since > > it'd then add /var/master.pid). But that seems a little nonsensical. > > > That is the normal expected behavior if devmode is enabled. Check your > configs for this. I don't think `devmode` has anything to do with this, it only disables sending out emails by accident and routes all emails to a pre-defined address. Haven't looked at the relevant portion of the source so I might be wrong. In the absence of any configuration file in pre-defined locations[1], Core will always generate a `var/` directory under $CWD with basic configuration and use it to track a running mailman instance (logs, db, pid file etc). Ideally, you should place your configuration file at one of the locations that it looks and specify a `[paths.custom]` directive in there to make sure it knows where to put everything. See [2] for more details. [1]: http://docs.mailman3.org/en/latest/config-core.html#configuring-mailman-core [2]: http://docs.mailman3.org/en/latest/config-core.html#configuring-filesystem-… > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

8 years, 2 months

[MM3-users] Re: templates

by Christian

In March when I started troubleshooting my lists, you stated: "Also, one other thing you might check. Do these non-working lists have templates defined in postorius, in particular, one for list:member:regular:footer, and if not, are there any in Mailman's var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that Mailman doesn't have permission to find and read?" There are no other templates listed in either Postorius nor in Mailman's var/templates (as I stated, I do not even lave a 'lists' subdirectory under Mailman's var/templates). My subscribers are not receiving message distributions from my lists, even while some of them are listed in the archives. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, May 4, 2023 10:58 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: templates On 5/4/23 10:33, Christian via Mailman-users wrote: > I'm having issues with my lists. For each list I have created a > template [ list:user:action:subscribe ]which has a prospective > subscriber have to consent to list rules before they are subscribed. > This template I created is listed in Postorius for each list. I have > noticed that there are no other templates listed in Postorius. Furthermore, there is no 'lists' > subdirectory under Mailman's var/templates/. When you set a template in Postorius it saves it in the postorius_emailtemplate table in the database and tells Mailman core to get the template from Postorius via a URI to a Postorius API. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ QIHCMEBWANR67HV3NKBK5MCQNSNZRF2A/ This message sent to csa(a)web-analysts.net

2 years, 7 months

[MM3-users] Re: new list not working

by Christian

Mail.log Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: connect from box.ecovillage.cc[45.79.28.18] Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: 11516101258: client=box.ecovillage.cc[45.79.28.18] Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: warning: header Subject: fifth test message from box.ecovillage.cc[45.79.28.18]; from=<christian(a)naturalintelligence.us> to=<redlatinleg(a)lists.ccalternatives.org> proto=ESMTP helo=<box.ecovillage.cc> Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: message-id=<033101d952d3$0fe82730$2fb87590$(a)naturalintelligence.us> Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: from=<christian(a)naturalintelligence.us>, size=3496, nrcpt=1 (queue active) Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: disconnect from box.ecovillage.cc[45.79.28.18] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Mar 9 22:03:30 zarathustra postfix/lmtp[27338]: 11516101258: to=<redlatinleg(a)lists.ccalternatives.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.02, delays=0/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: removed -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, March 9, 2023 2:39 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: new list not working On 3/9/23 14:32, Christian via Mailman-users wrote: > When I ran > > mailman members -r -n enabled redlatinleg(a)lists.ccalternatives.org > > I did receive a list of subscribers for the new list I created, not > just the owner or moderator. > > Upon closer examination, another of my longtime working lists is also > not working. Similar behavior as the new list I created in that I see > the message has been archived, but not distributed to the subscribers. What do your MTA logs show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ EOYMZXS4WPQGLDLVVWOGC67WY576665F/ This message sent to csa(a)web-analysts.net

2 years, 9 months

[MM3-users] Re: no access to Postorius web pages after upgrade

by Mark Sapiro

On 10/22/23 10:53, David Newman wrote: > Upgrading to MM3 3.39, Postorius 1.3.10, Hyperkitty, 1.3.8, > Django-mailman3 1.3.11, and Mailman-web 0.0.8 in a venv all seemed to go > OK. Mailman3 lists work as expected, and admins can log in via Django. > > However, any attempt to reach lists, domains, users, etc. now returns a > 404 Not Found error. All the Postorius stuff worked as expected before > the upgrade. > > In the nginx server logs, any Hyperkitty and Postorius URLs are now > appended to /opt/www/roundcubemail, which is this web server's root > directory but not the root for Mailman3 (I run Roundcubemail and MM3 on > the same server; don't judge me :-). > > Here is the nginx error, with obfuscation of client and server info: > > 2023/10/22 10:43:24 [error] 2264140#2264140: *135 > "/opt/www/roundcubemail/postorius/domains/index.php" is not found (2: No > such file or directory), client: 1.2.3.4, server: lists.example.com, > request: "GET /postorius/domains/ HTTP/2.0", host: "lists.example.com", > referrer: "https://lists.example.com/mailman3/listinfo" Here you are trying to get https://lists.example.com/postorius/domains/, but (see below) > And here are the relevant bits of the Nginx config. Again, this worked > before the upgrade. > > server { > > listen 443 ssl http2; > server_name lists.example.com; > root /opt/www/roundcubemail; > > # begin mailman3 stuff > > location /static/ { > alias /opt/mailman/web/static/; > } > > location /mailman3/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /archives/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /accounts/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > > proxy_set_header X-Forwarded-For $remote_addr; > } > location /admin/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /mailman/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /user-profile/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } Above you have defined proxying for the paths beginning with /mailman3/, /archives/, /mailman/ and others, but not /postorius/ or /hyperkitty/. Note that /mailman/ will get to Django, but probably won't work unless you have something like ``` path('mailman3/', include('postorius.urls')), ``` or possibly ``` re_path('mailman3?/', include('postorius.urls')), ``` in your urls.py (default mailman_web/urls.py) > Also, I'm not sure if it's relevant but after upgrading, the migrate > command throws a warning like this: > > (venv) mailman@mail10:~$ mailman-web migrate > System check identified some issues: > > WARNINGS: > account.EmailAddress: (models.W036) MariaDB does not support unique > constraints with conditions. > HINT: A constraint won't be created. Silence this warning if you > don't care about it. > account.EmailAddress: (models.W043) MariaDB does not support indexes on > expressions. > HINT: An index won't be created. Silence this warning if you don't > care about it. > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, > django_mailman3, django_q, hyperkitty, postorius, sessions, sites, > socialaccount > Running migrations: > No migrations to apply. This is an issue with MariaDB and MySQL. It can result in more processing because of the lack of an index or possibly a database operation succeeding that should fail because of the unsupported constraint, but these shouldn't affect operation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: spf/dkim/dmarc

by Christian

Using https://www.spf-record.com/ I have checked my SPF records which are reported as 'SPF check passed'. My DKIM also passes various test suites. Yet, Google is still rejecting mailman messages to any and all gmail users. I have even filled out their short form for delisting at https://support.google.com/mail/contact/bulk_send_new all to no avail. Example of block logfile message: May 18 12:53:11 lists postfix/smtp[28104]: C9D7A1005DA: to=<billb6951(a)gmail.com>, relay=gmail-smtp-in.l.google.com[142.250.138.27]:25, delay=0.69, delays=0.01/0.01/0.14/0.53, dsn=5.7.26, status=bounced (host gmail-smtp-in.l.google.com[142.250.138.27] said: 550-5.7.26 The MAIL FROM domain [lists.ccalternatives.org] has an SPF record 550-5.7.26 with a hard fail policy (-all) but it fails to pass SPF checks with 550-5.7.26 the ip: [192.46.218.224]. To best protect our users from spam and 550-5.7.26 phishing, the message has been blocked. Please visit 550-5.7.26 https://support.google.com/mail/answer/81126#authentication for more 550 5.7.26 information. p3-20020a056870868300b001926c1449a6si1393979oam.240 - gsmtp (in reply to end of DATA command)) Could the hard fail policy be implicated in the gmail rejection? Other than readdressing my server, is there anything else I can do? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, May 17, 2023 11:50 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: spf/dkim/dmarc On 5/17/23 07:20, Odhiambo Washington wrote: > > You can only have 1 SPF record. For a domain. But as Jeremy Stanley noted, mail.ccalternatives.org and lists.ccalternatives.org are different domains and it is fine for each to have its own spf record. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ WAUVS6WWYOYQBJGIDP3HK6L3NHM4RGHF/ This message sent to csa(a)web-analysts.net

2 years, 6 months

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Jered Floyd

You're welcome. Thank you for all your hard work making Mailman 3 happen at all! I think django_allauth integration is again stable, but for now I'm pinning 0.58.2 + this patch. I'll test again once there is another release notification, but since I rebuild by container image every 2-3 weeks I am getting exhausted by surprises... --Jered ----- On Dec 7, 2023, at 7:44 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 12/7/23 14:33, Jered Floyd wrote: >> >> FYI, The django-allauth author has proposed fixing both of these with an even >> simpler change, which is now upstream and queued for a future release. >> >> --Jered > > > Thank you again for your work on this. I can confirm that the patch > below fixes my issue with > https://msapiro.net/accounts/social/connections/ and SITE_ID = 0. > > >> --- a/allauth/socialaccount/adapter.py >> +++ b/allauth/socialaccount/adapter.py >> @@ -228,7 +228,10 @@ class DefaultSocialAccountAdapter(object): >> provider_to_apps = {} >> >> # First, populate it with the DB backed apps. >> - db_apps = SocialApp.objects.on_site(request) >> + if request: >> + db_apps = SocialApp.objects.on_site(request) >> + else: >> + db_apps = SocialApp.objects.all() >> if provider: >> db_apps = db_apps.filter(Q(provider=provider) | Q(provider_id=provider)) >> if client_id: > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

2 years

[MM3-users] Re: Mailman 3 - docker container - sync_members

by Abhilash Raj

On Tue, Oct 20, 2020, at 12:27 PM, Mark Sapiro wrote: > On 10/20/20 9:45 AM, holman(a)uw.edu wrote: > > I would like to populate list members via the Mailman 3 sync_members script. > > > > However, I am using Mailman 3 in docker containers and it doesn't appear to have this command. How are others completing this synchronization? > > > I'm not sure what version of Mailman core is in the Docker containers. > According to https://asynchronous.in/docker-mailman/NEWS.html, Mailman > core is docker version 1.1.1 released Aug 9 2017 which is about the time > of MM Core 3.1.0 which is quite old and has neither a `mailman > syncmembers` (introduced in core 3.3.2) command nor the older `mailman > members --sync` option (introduced in core 3.3.1). There are `rolling > releases` <https://asynchronous.in/docker-mailman/#rolling-releases> > which should have these. NEWS file is very outdated, I should remove it. The containers have latest released version if you are using the 0.3 tags and as Mark mentioned, `mailman members --sync` option should work. > > > > Searching this list I found a reasonable approach: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > Is there a different/preferred solution? > > > The script at > <https://gitlab.med.stanford.edu/irt-public/mailman-tools/-/blob/master/sync…> > seems fine. The alternative is to update your Docker container to one > including the appropriate `mailman` sub-command. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 1 month

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On Jun 9, 2020, at 1:23 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> On Jun 9, 2020, at 11:34 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >>>> ./mm3-admin: line 6: 702058 Killed django-admin $@ >>>> >>>> Now what? >>> >>> >>> Run it as user `list`. >> >> >> Same. > > > It appears that the reference to line 6 is line 6 of your mm3-admin file > which is the `django-admin $@` command. So that command is being killed > by the OS for some reason, probably out of memory. > > Try this instead. > > import pytz > import datetime > start = datetime.datetime(2020, 1, 1).replace(tzinfo=pytz.UTC) > end = datetime.datetime(2020, 2, 1).replace(tzinfo=pytz.UTC) > # These are examples. The args are year, month, day. > # Pick dates for start and end that overlap the start of this issue. > from hyperkitty.models import Email > emails = Email.objects.filter(date__range=(start,end)) > for email in emails: > if email.content.find('\u200b'*5) >= 0: > print('Found in ml {}, hash {}'.format( > email.mailinglist.name, > email.message_id_hash)) > > This will make a much smaller query set than all the emails and should work. I was just writing another email - I had a suspicion on this and I was right: this is the Linux OOM killer in action. Jun 9 13:15:32 mail kernel: [1051406.859205] Out of memory: Killed process 712833 (python3) total-vm:2351156kB, anon-rss:2274112kB, file-rss:2236kB, shmem-rss:4kB, UID:38 pgtables:4616kB oom_score_adj:0 Jun 9 13:15:32 mail kernel: [1051407.042975] oom_reaper: reaped process 712833 (python3), now anon-rss:0kB, file-rss:0kB, shmem-rss:4kB I set up a quick swapfile (there are 581,000 emails in this archive) and it came back with some hashes. I am tracking them down now. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 6 months

[MM3-users] Re: Adding Mass Subscribe custom template error

by Arte Chambers

Ok I did install using the https://docs.mailman3.org/en/latest/install/virtualenv.html I added ``` POSTORIUS_TEMPLATE_BASE_URL='https://www.example.com/' ``` to /etc/mailman3/settings.py and restarted mailman services However I'm still getting the same error from mailman.log ``` requests.exceptions.ReadTimeout: HTTPConnectionPool(host='localhost', port=8000): Read timed out. (read timeout=5) [29/Jan/2025:19:18:08 +0000] "POST /3.1/members HTTP/1.1" 400 128 "-" "GNU Mailman REST client v3.3.5" [29/Jan/2025:19:18:08 +0000] "GET /3.1/lists/ testing@list.louisvillecommunitygrocery.com/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5" [29/Jan/2025:19:18:08 +0000] "GET /3.1/lists/ testing(a)list.louisvillecommunitygrocery.com/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5" ``` Not sure if I'm editing the correct config file. Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Wed, Jan 29, 2025 at 1:27 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/29/25 09:41, Arte Chambers via Mailman-users wrote: > > Where can I find the setting > > ``` > > POSTORIUS_TEMPLATE_BASE_URL > > ``` > > It is in your Django settings. Where these are depends on your > installation, but these are usually in files named settings.py and > settings_local.py. > > If you installed following > https://docs.mailman3.org/en/latest/install/virtualenv.html the default > is in mailman_web/settings/mailman.py but you would override the default > in /etc/mailman3/settings.py > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to paul.m.robey(a)gmail.com >

10 months, 2 weeks

[MM3-users] Re: Bounces address spammed

by Enrique Terrazas

Thank you Mark! The requests are coming in via email. We were able to filter these out with the recommendation below. Blocking an entire domain is a bit extreme but I wanted to stop the bleeding. Can you, or someone on the list, point me in the the right direction as far as configuring postfix to protect against Spam campaigns? I’ve started reading through this document: http://www.postfix.org/BACKSCATTER_README.html But am not sure if this is where I should direct my efforts. Enrique On Feb 28, 2019, at 12:44 PM, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 2/28/19 9:15 AM, Enrique Terrazas wrote: Greetings, I hope everyone is having a good day. We have a highly visible list that is being spammed with join requests from spoofed addresses. Web or email? When the confirmation email is sent a bounce is received by the list owner. The count is in the 100’s of bounced emails/hour. We noticed they are all coming from one particular domain, this may help if we are able to filter/block the domain. What would be the best way to handle this? Is there a way to handle this granularly at the list level? If the requests are coming by email, you can block the domain in your MTA., E.g. with postfix in main.cf: header_checks = pcre:/etc/postfix/header_checks.pcre in /etc/postfix/header_checks.pcre: /^From:.*[@.]bad.domain\w/ DISCARD or /^From:.*[@.]bad.domain\w/ REJECT We don't accept mail from bad.domain. For web requests, adding a pattern like '^.*[@.]bad.domain$' to the lists "Banned addresses" might help. -- Mark Sapiro <mark(a)msapiro.net<mailto: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(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

6 years, 9 months

[MM3-users] Re: My Server is unable to connect to Mailman REST API few times

by Shashikanth Komandoor

Thank you Mark a lot. It worked awesome. You don't know how much you helped me. Thank you once again. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Sat, Sep 19, 2020 at 8:56 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/19/20 4:32 AM, Shashikanth Komandoor wrote: > > > > But I am trying to delete a list on an urgent basis. Because of which I > am > > getting the above said errors. I tried to delete > > through the interface, through curl command and through "mailman shell" > but > > nothing led me to a > > positive result. Is there any work around to delete the list ? > > What have you tried in Mailman shell? This should do it. > > $ 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 > >>> getUtility(IListManager).delete(m) > >>> commit() > > So should just > > $ mailman remove list.example.com > > What happens if you do those? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 2 months

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

by Mark Sapiro

On 2/10/25 13:45, Lieuallen, Thomas Otis via Mailman-users wrote: > Mark, > > Actually, this is saying cache_life under mailman: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/config/doc… > > There is a cache_lifetime under ‘dmarc’. You are correct. I was confused by the dmarc one. > I used your clue about the database to concoct my own solution… 😊. I edited the ‘expires_on’ values in the file_cache table in the database so the files were expired. > > It looks like the times in that table are UTC. > > I’m going to ratchet down my cache_life so anyone that is playing with templates doesn’t go bonkers (like me) with why their changes aren’t honored. I have a small site, so not much performance impact. That really shouldn't be necessary, but I think there is an issue in the code at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/template… which is intended to evict the cache entry for the previous template when a new one is set. If the previous template has a different uri from the one being set, e.g., a mailman:// uri is being replaced by a http(s):// Postorius uri the code will attempt to evict the Postorius uri which is not the cached value. This should not be an issue when just updating a template already in Postorius and should not be an issue when setting a Postorius template to replace one previously the default or in Mailman's var/templates directory as these normally don't have template table entries, but prior to Mailman 3.3.6, the `mailman import21` command would create template table entries for imported lists. This was https://gitlab.com/mailman/mailman/-/issues/988 fixed by https://gitlab.com/mailman/mailman/-/merge_requests/989 > Thank you for your help. You're welcome. I'm glad you solved it.

10 months

[MM3-users] Re: cannot import name 'parse_header' from 'django.http.multipartparser

by Stefan Bauer

Thank you Mark for your swift reply :) Am Do., 27. Feb. 2025 um 20:32 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 2/26/25 07:40, Stefan Bauer via Mailman-users wrote: > > Dear Users, > > > > i recently tried to upgrade to latest MM3 and followed this[1] steps. > > > > However > > > > (venv) $ mailman-web migrate > > > > fails with: > > > > from rest_framework import mixins, views > > File > "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/views.py", > > line 15, in <module> > > from rest_framework.request import Request > > File > "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/request.py", > > line 17, in <module> > > from django.http.multipartparser import parse_header > > ImportError: cannot import name 'parse_header' from > > 'django.http.multipartparser' > > > (/opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py) > > (venv) mailman@edmmal03$ vi > > > /opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py > > > > Could this be a broken dependency? > > > You have an incompatible configuration. > django.http.multipartparser.parse_header was removed in Django 4.2. See > https://docs.djangoproject.com/en/5.1/releases/4.2/#miscellaneous > > Your version of djangorestframework is incompatible with Django>=4.2. > Try in your venv > ``` > pip install --upgrade djangorestframework > ``` > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to cubewerk(a)gmail.com >

9 months, 1 week

[MM3-users] Re: Installing mailman 3

by Rafael Mora

For testing purpose I turned back to false the DEBUG var and everything started working fine with HyperKitty I don't understand... this is the trace when I click Login from Postorius to HyperKitty [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10950 [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css HTTP/1.1" 200 156657 What should I check? El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > find them: > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > > > > > Should I run any command to activate the CACHE dir? > > > You need to ensure you have a working sass compiler. As I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >, > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > Then you need to run commands like > > django-admin collectstatic --clear > django-admin compress > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 4 months

[MM3-users] Re: Migrating archives from Mailman21 to Mailman3

by Odhiambo Washington

On Tue, Sep 24, 2024 at 11:33 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/24/24 12:03, Odhiambo Washington via Mailman-users wrote: > > On Tue, Sep 24, 2024 at 7:38 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Yes. There is no requirement that archives have a matching list in > >> Mailman core. > > > > > > So the documentation at > https://docs.mailman3.org/en/latest/migration.html > > needs revision as it creates the impression that a matching list needs to > > be there: > > ``` > > $ python manage.py hyperkitty_import -l foo-list(a)example.com > > $var_prefix/archives/private/foo-list.mbox/foo-list.mbox > > ``` > > > Are you saying that the above quoted command is what gives that > impression? I don't see that `foo-list(a)example.com` is the name of the > list for the HyperKitty archive only and > `$var_prefix/archives/private/foo-list.mbox/foo-list.mbox` is the MM 2.1 > mbox. > > If you are saying something else gives that impression, what in > particular is that? > My thinking around the above was that `foo-list(a)example.com` refers to a Mailman list. But now I am beginning to think that it's only a listname for HyperKitty and the list doesn't necessarily have to exist in Mailman Core. Is that right? The fact that the command was referenced during the migration of an ACTUAL list is what created the impression (in my mind) that the list must also be a valid list for the Core. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 2 months

[MM3-users] Re: Handling of Mail from non-subscribers

by Peter Adebahr

On 5/9/20 2:13 AM, Mark Sapiro wrote: > On 5/8/20 5:08 PM, Peter Adebahr via Mailman-users wrote: >> On 5/9/20 1:55 AM, Mark Sapiro wrote: >> >>>> "Hold for moderation" has been set. >>> >>> Set in "Default action to take when a non-member posts to the list"? >> >> yep >> >> >>> >>> If that is the case, find the non-member in Users -> Non-Members and >> >> it does'nt show up there, "list has no nonmembers" > > > Look is var/logs/mailman.log for an error message with a SHUNTING > notation and a Traceback. Shunting seems to be ok: May 09 01:22:38 2020 (1235) SHUNTING: 1588980158.3151...... But immediately before I find the "module 'time' has no attribute 'clock'" which I remember from a thread a couple of days ago, though I cannot remember a solution when mm3 has not been installed from source but via apt-get. My core is V 3.2.2, core python 3.8.2, by the way. > > Also look in var/queue/shunt. You can examine messages you find there > with `mailman qfile`. > ah, learnt how to use that now: ... X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation ... <----- start object 2 -----> { '_parsemsg': False, 'dmarc': True, 'envsender': 'noreply(a)xyzzy-listen.de', 'lang': 'de', 'listid': 'xyzzy-listen.de', 'member_moderation_action': 'hold', 'moderation_reasons': ['The message is not from a list member'], 'moderation_sender': 'peter(a)xyzzy.de', 'original_size': 7640, 'received_time': datetime.datetime(2020, 5, 8, 23, 22, 37, 976364), 'rule_hits': ['nonmember-moderation'], 'rule_misses': [ 'dmarc-mitigation', 'no-senders', 'approved', 'emergency', 'loop', 'banned-address', 'member-moderation'], 'to_list': True, 'version': 3, 'whichq': 'in'} [----- end pickle -----] Does that help?

5 years, 7 months

[MM3-users] Re: Mailman Core 3.3.2 is now out

by Abhilash Raj

On Wed, Nov 25, 2020, at 1:58 AM, Mark Sapiro wrote: > On 11/22/20 1:04 AM, Torge Riedel wrote: > > Am 07.11.20 um 04:24 schrieb Abhilash Raj: > >> I missed it in the original email, but a full list of changes in this > >> version is present here: > >> > >> > >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > >> > > > > Hi, > > > > this link now points to 3.3.3, is there a chance to make this link more > > stable? Maybe > > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > > > Those links are created by Sphinx and as you note the fragments are not > stable. I don't know if it's possible to tell Sphinx via the .rst source > how to name the fragments. Maybe the best idea is to not use fragments > at all and just point to the document. I think I should keep in mind next time to use the #<heading-name> like `#3.3.2` pointed out by Torge, instead of `#id` (which is what I see when I hover over the Link in browser so I copied ;). You can specify explicit anchor name in .rst too, I think just adding a `.. _news-3.3.2` just above the heading will generate an anchor on the page with #news-3.3.2 (I haven't verified this but I think it will!) which links to the heading. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years

[MM3-users] Re: how to delete a list member using the Linux command line

by Mike Wertheim

Thanks! I'm on Debian 10, and the latest Mailman version that's available in the Debian package manager is 3.2.1. I really have no idea how packages get updated in the package manager. Do you know why Mailman 3.3.1 is not yet available in Debian's package manager? (Does someone on the Mailman project need to push it there? Or does someone on the Debian side need to pull it in?) On Fri, Jun 19, 2020 at 1:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/19/20 7:29 AM, Mike Wertheim wrote: > > I have Mailman 3.2.1 installed (on Debian Linux), using exim4 as the MTA. > > > > I have been trying to figure out how to use the Linux command line to add > > members to a list and delete members from a list, but am having trouble > > with deleting. > > The --delete option to `mailman members` was introduced in Mailman > 3.3.0. Your version doesn't have it. > > Note that as of the next (3.3.2) release, the --add, --delete and --sync > options to `mailman members` are deprecated in favor of new `mailman > addmembers`, mailman delmembers` and `mailman syncmembers` commands. > > It should be possible for you to install the current versions of all of > these without upgrading just by copying the `cli_*members.py` files from > <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/commands> > to the `mailman/commands/` directory in your current installation. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

5 years, 5 months

[MM3-users] Re: After server upgrade debian 11→12 and reinstalling everything in (venv), I got this error when accessing → mailman3/lists

by Stephen J. Turnbull

Mark Sapiro writes: > On 9/22/25 05:21, Wikinaut wrote: > > Mark, this is great news, a little bit like expected! > > Thanks again for clarifying the term "generic" here. It's helpful > > to have it for definition of both, "regular" and "digest". > > > > Is this documented somewhere? > > I don't think so. I thought I had seen it "somewhere", but I can't find it now. It should be here: https://docs.mailman3.org/projects/mailman/en/release-3.1/src/mailman/rest/…. See https://gitlab.com/mailman/mailman/-/issues/1243. Besides templates.html, this should be documented briefly in the forms for changing the generic, regular, and digest templates, something as simple as adding "if empty, falls back to generic:template" would do for the regular and digest specific templates, and "shadowed by regular:template and digest:template" for the generic template. Note that that is in the developer's documentation for the REST API. :-( We really need to reorganize the docs to be more discoverable for typical admins. > >I think, I need to create a wiki for mailman3. > We have a wiki at https://wiki.list.org/ for all versions of > Mailman. See the first paragraph at that page for info on obtaining > write access. But note that this is *not* appropriate for the wiki, which is more oriented to FAQs and news. Wikis are fine for formal documentation, but only if that's the ground truth. For better or worse, we chose not to do that. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 months, 2 weeks

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/24/20 2:10 PM, Ruth Ivimey-Cook wrote: > Mark, > >> You need to set hostname: in mailman.cfg to the actual external IP >> address of the Mailman host machine or to a name which resolves to that >> IP both internally and externally, and also set that host name/IP in the >> MAILMAN_REST_API_URL setting on the Postorius machine. > > I've done that, but there is no observed change in the browser (still > get same 404 error). > > Specifically, I reset hostname to be a newly-added CNAME of the actual > host address, and ensured that the 0.0.0.0 addresses were no longer there. OK, So setting hostname: to this CNAME which resolves to the external IP on the Mailman core host allows the REST interface to listen on that external interface and solves that issue without patching the rest runner. Correct? > A tcpdump now shows the GET of > > /3.1/domains/mailman-web.ivimey.org/lists&advertised=true&count=0&page=1 > > directed at mailman-core and the reply being 404 not found. > > The extract from core's mailman.log is now: > > [24/Jun/2020:20:41:11 +0000] "GET > /3.1/domains/mailman-web.ivimey.org/lists?advertised=true&count=0&page=1 > HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" > > And the entry for postorius in mailmansuite.log: > > ERROR 2020-06-24 21:41:11,191 13310 postorius Un-handled exception: > HTTP Error 404: {"title": "404 Not Found"} > Traceback (most recent call last): > File > "/opt/mailman3/lib/python3.6/site-packages/django/core/handlers/base.py", line > 113, in _get_response > response = wrapped_callback(request, *callback_args, > **callback_kwargs) > [snip] > File > "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/page.py", > line 37, in __init__ > self._create_page() > File > "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/page.py", > line 62, in _create_page > response, content = self._connection.call(self._build_url()) > File > "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", > line 116, in call > error_msg, response, None) > urllib.error.HTTPError: HTTP Error 404: {"title": "404 Not Found"} > > Note that the mailman-web.ivimey.org address is the newly-added CNAME of > greyarea-web1, mailman-core is likewise the CNAME of greyarea-post. > > There is nothing I can see in the other logs that looks out of the > ordinary. > > I guess this indicates that my earlier wondering if I had something left > over from a past install is dispelled, as that name didn't exist until > today. OK, but you still haven't reported whether you looked at the domains in Django. These are in the Django database on the Postorius server, and I don't know what's there, but if there is a domain there which is not known to core, that could cause this 404. Further if that domain is not fully qualified, something could just be appending the hostname: to it causing that name to be the one requested. Some of this is guesswork and possibly overreaching on my part, but I would like to be assured that there are no extraneous domains in Django's database. I wrote in the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > Go to your Django admin web UI and look at your Django Mailman 3 Mail > domains. This will be at a URL like > https://greyarea-web1.cam.ivimey.org/admin/django_mailman3/maildomain/ Have you done that? I want to help resolve this issue, but right now I want to rule out the possibility that there are domains known to Django that aren't known to core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: API access to Hyperkitty

by Abhilash Raj

On Tue, Feb 9, 2021, at 10:44 AM, Mark Sapiro wrote: > On 2/9/21 10:23 AM, Brian Carpenter wrote: > > Is it possible to download Hyperkitty's archives to a remote server via > > an API? Is there documentation that explains how to accomplish this task? > > > > > I don't think there is documentation, but if you look at the target of > any `download` button, it should be obvious. I.e. the link to download > the entire archive for this list is > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/export/… > > The `mailman-users(a)mailman3.org-2021-02.mbox.gz` part is the name of the > file to download to and the `-2021-02` part can be anything or nothing, > but the name must begin with the list posting address and end with > `.mbox.gz`. > > If the archive is large, this can time out in which case adjust `start` > and `end` to download it in pieces. Hyperkitty also has a traditional REST API, which can be used to ingest archives on a different server that doesn’t necessarily want to deal with mboxes. The documentation comes with Hyperkitty and is typically available at “/api” in Hyperkitty. So something like this on our server: https://lists.mailman3.org/archives/api/ There is also a “HTML” version where you can actually browse through the API like a webpage. It returns Json/XML/txt when you ask for it. The above page should have the details. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 10 months

[MM3-users] Re: Set member.moderation_action via REST API as part of message approval?

by Mark Sapiro

On 3/3/25 14:27, Andy Matthews wrote: > We're using Mailman 3.3.9. > > Entity<Form> data = Entity.entity(form, MediaType.APPLICATION_FORM_URLENCODED_TYPE); > response = getTarget().path("lists/" + listId + "/config").request().method("PATCH", data); You are patching the list's config and with that patch you are replacing the old value of `accept_these_nonmembers` with the new, not appending the new value. You would need to retrieve the existing value, update it and PATCH that. However, as you know, that setting is deprecated and exists only to support the regexp and @list type of entries. For explicit email addresses, the intent is to create a nonmember and set the nonmember's moderation_action to `defer` - you normally don't want `accept` because that bypasses all the subsequent checks such as administrivia, implicit-dest, max_recipients, max_size, , no_subject, etc. > The result of these two API calls is that both the subscribers and nonmembers properties of the mailing list are updated to include the new email (let's call it abc(a)123.com) The user can immediately send another email which is not held for moderation. The issue comes when a different nonmember sends an email and is approved (let's call it xyz(a)789.com) For some reason this blows out the "always accept" status of user abc(a)123.com and requires their email to be approved again. > > After some research I believe this is because the `accept_these_nonmembers` property has been deprecated (which seems valid because that property remains an empty array). Additional reading seems to indicate that we can now set `moderation_action` on each individual user which supercedes the mailing list's `default_nonmember_action` property (in our case it is `Action.hold`). That is correct, and that is the intended way to deal with nonmember moderation. > The docs indicate that I should be able to submit a patch request to update the moderation action for any user: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > > But it requires the user ID. And when trying to get the user_id for a nonmember it appears that it is not returned by the API. The following call: > `/3.0/addresses/abc(a)123.com` > > returns > ``` > { > "email": "abc(a)123.com", > "original_email": "abc(a)123.com", > "registered_on": "2025-03-03T19:18:35.169703", > "self_link": "https://0.0.0.0:8001/3.0/addresses/abc@123.com", > "http_etag": "\"92c44d0b3b323450f3576e6352acb59b4cc5d6f0a\"" > } > ``` > So I'm not sure how I would be able to update this particular record without a member or user id. > > So, all that said, I'm looking for information on how to do one of the following. > > 1. When submitting a user's email to the `accept_these_nonmembers`, is there a way to indicate that the `member.moderation_action` should be a specific value? No. You can put the email in the appropriate *_these_nonmembers, but that does only that. It doesn't affect the nonmember's moderation_action, nor does it create a nonmember if there isn't one already, but if there is a nonmember with non-None moderation_action, that action takes precedence over *_these_nonmembers. > 2. Retrieve a nonmember record and have it include a member or user id that I can use to explicitly update the `member.moderation_action` value? You must be able to set a nonmember's moderation_action via REST. (The docs may need updating.) Postorius does it, so it can be done, but I don't offhand know the endpoint and I'm leaving the country for vacation tomorrow and don't have time to research it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Re: How to identify the exact reason behind the shunting of the mails ?

by Shashikanth Komandoor

Thank you Mark, Then I will try to upgrade the version Thank you once again. On Fri, Jun 18, 2021 at 8:01 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/18/21 6:48 AM, Shashikanth Komandoor wrote: > > Dear Mark, > > > > FYI, I observed this issue with the postfix that receives the > > mails from the previous MTA and hands it over to the mailman. But I fixed > > at postfix by upgrading it to the version postfix 3. > > > > But still Mailman is not able to understand Hindi (Indian > local > > language) in which language the display names of the email ids are there. > > > > So, now what to do at Mailman so that it can also understand > > local languages or any work around or other alternate solutions for these > > sort of cases. > > > As noted in my reply at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > the issue is a Mailman bug which is fixed in the next release. It has to > do with the fact that the display names are RFC 2047 encoded and not the > particular encoding. > > Actually, the fix at > https://gitlab.com/mailman/mailman/-/merge_requests/841 depends on > https://gitlab.com/mailman/mailman/-/merge_requests/652 which was > released in Mailman 3.3.2. A complete patch for versions < 3.3.2 is > attached. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 5 months

[MM3-users] Re: User settings triggers error

by Mark Sapiro

On 6/16/20 12:18 PM, Mark Dadgar wrote: > On Jun 16, 2020, at 11:47 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py" in call >>> 99. raise HTTPError(url, response.status, content, response, None) >> >> And gets a 500 from core. >> >> >>> During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred: >> >> >> Which we aren't interested in. >> >> The next step is to look in core's mailman.log to see what the rest call >> was and the exception and hopefully traceback the caused the 500 response. > > > Here’s what’s logged during that error: > > Jun 16 12:16:54 2020 (1326) 127.0.0.1 - - "GET /3.1/users/mark(a)pdc-racing.net HTTP/1.1" 200 432 > Jun 16 12:16:54 2020 (1326) REST request handler error: > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1245, in _execute_context > self.dialect.do_execute( > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 581, in do_execute > cursor.execute(statement, parameters) > psycopg2.errors.UndefinedFunction: operator does not exist: text = uuid > LINE 4: WHERE "user"._user_id = '05dcbeb4-b784-45eb-96f8-6f9e4b7ab6c... > ^ > HINT: No operator matches the given name and argument types. You might need to add explicit type casts. > > > The above exception was the direct cause of the following exception: > > Traceback (most recent call last): > File "/usr/lib/python3.8/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 218, in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 232, in falcon.api.API.__call__ > File "falcon/api.py", line 229, in falcon.api.API.__call__ > File "falcon/api.py", line 582, in falcon.api.API._get_responder > File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 131, in find > attribute = getattr(resource, name, MISSING) > File "/usr/lib/python3/dist-packages/mailman/rest/users.py", line 203, in _user > return user_manager.get_user_by_id(user_id) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/lib/python3/dist-packages/mailman/model/usermanager.py", line 94, in get_user_by_id > if users.count() == 0: > File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3630, in count > return self.from_self(col).scalar() > File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3355, in scalar > ret = self.one() > File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3325, in one > ret = self.one_or_none() > File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3294, in one_or_none > ret = list(self) > File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3367, in __iter__ > return self._execute_and_instances(context) > File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3392, in _execute_and_instances > result = conn.execute(querycontext.statement, self._params) > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 982, in execute > return meth(self, multiparams, params) > File "/usr/lib/python3/dist-packages/sqlalchemy/sql/elements.py", line 287, in _execute_on_connection > return connection._execute_clauseelement(self, multiparams, params) > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1095, in _execute_clauseelement > ret = self._execute_context( > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1249, in _execute_context > self._handle_dbapi_exception( > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1476, in _handle_dbapi_exception > util.raise_from_cause(sqlalchemy_exception, exc_info) > File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 398, in raise_from_cause > reraise(type(exception), exception, tb=exc_tb, cause=cause) > File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 152, in reraise > raise value.with_traceback(tb) > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1245, in _execute_context > self.dialect.do_execute( > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 581, in do_execute > cursor.execute(statement, parameters) > sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedFunction) operator does not exist: text = uuid > LINE 4: WHERE "user"._user_id = '05dcbeb4-b784-45eb-96f8-6f9e4b7ab6c... > ^ > HINT: No operator matches the given name and argument types. You might need to add explicit type casts. > > [SQL: SELECT count(*) AS count_1 > FROM (SELECT "user".password AS user_password, "user".id AS user_id, "user".display_name AS user_display_name, "user"._user_id AS user__user_id, "user"._created_on AS user__created_on, "user".is_server_owner AS user_is_server_owner, "user"._preferred_address_id AS user__preferred_address_id, "user".preferences_id AS user_preferences_id > FROM "user" > WHERE "user"._user_id = %(user_id_1)s) AS anon_1] > [parameters: {'user_id_1': UUID('05dcbeb4-b784-45eb-96f8-6f9e4b7ab6cb')}] > (Background on this error at: http://sqlalche.me/e/f405) > Jun 16 12:16:54 2020 (1326) 127.0.0.1 - - "GET /3.1/users/05dcbeb4b78445eb96f86f9e4b7ab6cb/addresses HTTP/1.1" 500 59 > Jun 16 12:16:54 2020 (1326) REST request handler error: > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1245, in _execute_context > self.dialect.do_execute( > File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 581, in do_execute > cursor.execute(statement, parameters) > psycopg2.errors.UndefinedFunction: operator does not exist: text = uuid > LINE 4: WHERE "user"._user_id = '05dcbeb4-b784-45eb-96f8-6f9e4b7ab6c... > ^ > HINT: No operator matches the given name and argument types. You might need to add explicit type casts. This looks like another manifestation of the issue reported at https://gitlab.com/mailman/django-mailman3/-/issues/35 and https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… If you are running django-mailman3 1.3.3 and haven't upgraded to django-mailman3 1.3.4, see the above list post for a workaround. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Problems after upgrading from bullseye to bookworm

by Thomas Ward

FYI I updated my workaround on the linked issues on Gitlab to reflect this. Technical Note that this may not apply after the PDM backend updates which are in the works to not normalize metadata (which causes this problem). I have not tested a fresh setup yet since the issue was first identified but it is possible the issue is easily resolved once updated versions of these flufl libraries land in PyPI with the pdm backend fixes in place for the build envs of those libraries. Sent from my Galaxy -------- Original message -------- From: Mark Sapiro <mark(a)msapiro.net> Date: 6/26/23 16:23 (GMT-05:00) To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Problems after upgrading from bullseye to bookworm On 6/26/23 12:35 PM, Ken Alker wrote: > I'm brand new to this, so take this with a grain of sale, but, I had a similar problem a few days ago, however, mine was "flufl.i18n>=3.2". Perhaps the same thing is happening with flufl.lock (but that didn't bite me). > > I solved my problem by following this: <https://gitlab.com/mailman/mailman/-/issues/1085> and, ultimately modifying "$VENV_ROOT/lib/$PYVERSION/site-packages/mailman-3.3.8.egg-info/requires.txt" per that thread (see <https://gitlab.com/mailman/mailman/-/issues/1085#note_1442207929> by Thomas Ward section called "The WORKAROUND"). Maybe you need to do the same thing, but for flufl.lock. Yes, the same issue now affects flufl.lock as well as flufl.i18n. You will need to change both flufl.lock->flufl_lock and flufl.i18n->flufl_i18n. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to teward(a)thomas-ward.net

2 years, 5 months

[MM3-users] Re: Avoiding non-members to be saved.

by Mark Sapiro

On 8/7/21 4:55 AM, Stephen J. Turnbull wrote: > Guillermo Hernandez (Oldno7) via Mailman-users writes: > > > Yesterday I had a problem with a private list. A spammer sent a mail > > forging one address that was a non-member (in fact was an "accept this > > no subscriber mails" from mailman 2.1 import) with very bad intentions > > and it was distributed. > > If you upgrade from Mailman 2 to Mailman 3, the accept_these_nonmembers > list for each list is grandfathered into the Mailman 3 list (from > rules/moderation.py): > > # Check the '*_these_nonmembers' properties first. XXX These are > # legacy attributes from MM2.1; their database type is 'pickle' and > # they should eventually get replaced. > for action_name in ('accept', 'hold', 'reject', 'discard'): > legacy_attribute_name = '{}_these_nonmembers'.format( > action_name) > > > There were no list of "accept this non members" in the Postorius > > config > > If there is no such list in Postorius, I would guess that some > developer thought "OK, this is a legacy feature and I'll get back to > it when we move it to the proper database" (unfortunate, but most of > us have open-subscription member-posts-only lists, and the current > workflow seems to work well, so this feature may not be so salient). Moderation in MM 3 works as follows: Is poster address a member. If so apply the member's moderation action, else Does poster address appear or match a pattern in the legacy (accept|hold|reject|discard)_these_nonmembers (first match in that order). If so, apply the appropriate action, else If the poster address is not a non-member, add it as a nonmember and apply the default nonmember moderation. > > I think it is solved now (deleting all and putting to hold just the > > non-members addresses that I would want to pass messages on) > > This should not be necessary, unless there were pre-approved addresses > that are no longer appropriate. But Mailman can't know that! The import21 process imports *_these_nonmembers by adding any regexps to the corresponding MM 3 *_these_nonmembers and adding any addresses as nonmembers with the appropriate moderation action. > > The fact is that any sender address of mails sent to the list is saved > > as a "non member", and it make me nervous as it will grow despite it is > > a legitimate message or not. This is the way MM 3 works. The only reason *_these_nonmembers exists in MM 3 is to support the legacy regexps from MM 2.1. For non-regexp addresses the address is a nonmember with the appropriate moderation action. I actually find this convenient. When a nonmember posts spam to a list and that spam is held, I discard the spam in Postorius and at the same time set the nonmember's moderation action to discard so I never see any more from that address. Also, when someone who I recognize as a list member posts from an alternate nonmember address, I can accept that post and set the nonmember address moderation action to default processing. > As far as I can see there is no other rule except that legacy rule > (and the rule that accepts all posts, which is rarely used) that will > accept a post from nonmembers. As I note above, nonmembers and members alike have a moderation action which can be any of Hold, Reject (with notice), Discard (no notice), Accept (without any further checks), Default Processing (continue with additioal checks) or the list's default action for (non)members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: New year releases!

by Mark Sapiro

On 1/4/23 13:54, Dan Caballero wrote: > I'm attempting this upgrade in my test environment which is a Docker container with Python 3.9.10 virtual environment. I was able to upgrade all the Python requirements but when I run mailman-web migrate I get an error. It seems related to the mailman-web package. See output below. > > > "(mailmanve) mailman@1d0e3a230c94:/var/www/mailman-www$ mailman-web migrate > Traceback (most recent call last): > File "/opt/mailmanve/bin/mailman-web", line 33, in <module> > sys.exit(load_entry_point('mailman-web==0.0.6', 'console_scripts', 'mailman-web')()) > File "/opt/mailmanve/lib/python3.9/site-packages/mailman_web/manage.py", line 37, in main > execute_from_command_line(sys.argv) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line > utility.execute() > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/__init__.py", line 440, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 402, in run_from_argv > self.execute(*args, **cmd_options) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 448, in execute > output = self.handle(*args, **options) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 96, in wrapped > res = handle_func(*args, **kwargs) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/commands/migrate.py", line 97, in handle > self.check(databases=[database]) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 475, in check > all_issues = checks.run_checks( > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/checks/registry.py", line 88, in run_checks > new_errors = check(app_configs=app_configs, databases=databases) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/checks/urls.py", line 14, in check_url_config > return check_resolver(resolver) > File "/opt/mailmanve/lib/python3.9/site-packages/django/core/checks/urls.py", line 24, in check_resolver > return check_method() > File "/opt/mailmanve/lib/python3.9/site-packages/django/urls/resolvers.py", line 494, in check > for pattern in self.url_patterns: > File "/opt/mailmanve/lib/python3.9/site-packages/django/utils/functional.py", line 57, in __get__ > res = instance.__dict__[self.name] = self.func(instance) > File "/opt/mailmanve/lib/python3.9/site-packages/django/urls/resolvers.py", line 715, in url_patterns > patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module) > File "/opt/mailmanve/lib/python3.9/site-packages/django/utils/functional.py", line 57, in __get__ > res = instance.__dict__[self.name] = self.func(instance) > File "/opt/mailmanve/lib/python3.9/site-packages/django/urls/resolvers.py", line 708, in urlconf_module > return import_module(self.urlconf_name) > File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1030, in _gcd_import > File "<frozen importlib._bootstrap>", line 1007, in _find_and_load > File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 680, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 850, in exec_module > File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed > File "/var/www/mailman-www/urls.py", line 20, in <module> > from django.conf.urls import include, url > ImportError: cannot import name 'url' from 'django.conf.urls' (/opt/mailmanve/lib/python3.9/site-packages/django/conf/urls/__init__.py)" In Django 3.1 django.conf.urls.url was a deprecated alias to django.urls.re_path and in Django 4.0 it was removed. See, e.g. <https://docs.djangoproject.com/en/3.2/ref/urls/> and <https://docs.djangoproject.com/en/4.0/ref/urls/>. However, the above Traceback doesn't identify which module contains the from django.conf.urls import include, url import. If I look through our sources, I only find this import in mailman-suite/mailman-suite_project/urls.py as an example. You need to look at your urls.py files. Try something like grep -r 'from django.conf.urls import include, url' /opt/mailmanve/lib/python3.9/site-packages/ to find which module contains that import. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I have installed rubygem-sass and added the config to settings.py previously and even executed this command: # Copy all the static files to one single location. $ python2 manage.py collectstatic I tested the commands you suggested and this is what I got: (env2) [mailman@localhost mailman-suite_project]$ pwd /var/lib/mailman/mailman-suite/mailman-suite_project (env2) [mailman@localhost mailman-suite_project]$ django-admin collectstatic --clear No Django settings specified. Unknown command: 'collectstatic' Type 'django-admin help' for usage. El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > find them: > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > > > > > Should I run any command to activate the CACHE dir? > > > You need to ensure you have a working sass compiler. As I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >, > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > Then you need to run commands like > > django-admin collectstatic --clear > django-admin compress > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 4 months

[MM3-users] Re: 'Failed adding message' error when migrating a list from mailman2 to mailman3

by Prasanth Nair

Thank you, Mark. Kind regards, Prasanth On Thu, 14 Oct 2021 at 19:17, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/14/21 9:04 AM, Stephen J. Turnbull wrote: > > Prasanth Nair writes: > > > > > *2%Failed adding message <mailman.2.1593699619.32248>: 'ascii' codec > can't > > > encode character '\ufffd' in position 252: ordinal not in > range(128).* > ... > > > I ran the check_hk_import script before migrating and it was not > > > giving any error. > > > > In order to catch this kind of error, the check script would have to > > pretty much do the import but throw it away. > > > The check_hk_import script > <https://www.msapiro.net/scripts/check_hk_import> is designed to detect > and report conditions which would cause the django hyperkitty_import > process to abort and stop processing the mbox. It doesn't catch errors > like the above, but these are non-fatal and just cause the offending > message to be skipped. > > As Steve says, the Message-ID was reported so find it in the mbox and if > you want it in the archive, extract it from the mbox, fix it and then > just rerun the import with just that message as input[1] and a > --since=1970-01-01 option. > > Note the issue could be in a header, but also could be in a body part > implicitly or explicitly declared as charset="us-ascii". > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 1 month

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Odhiambo Washington

I'll create the merge request. On Sat, Jan 28, 2023, 21:49 Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/28/23 09:39, Odhiambo Washington wrote: > > Now that you have mentioned > > > https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/install/v…, > , > > please show me how to import it, edit. Then I can submit a diff. > > Alternatively, I'd love to be given access to edit that document (and the > > edit can be reviewed before getting published) to make it easy to follow > by > > someone with zero python background. > > I am willing to invest some time in improving it for laymen. > > > There are multiple ways to proceed. The simplest is to just download > > https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/install/v… > (there's a download button on that page), edit that and post the edited > file somewhere where we can get it to look at. > > The better way is more complex. That way is for you to create a personal > project space at https://gitlab.com/users/sign_up and clone the > mailman/mailman-suite-doc project into your personal space and edit it > there and then create a merge request to merge your edits into the > mailman/mailman-suite-doc project. GitLab documentation is at > https://gitlab.com/help > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 10 months

[MM3-users] Re: Hyperkitty Text/Markdown/HTML

by Mark Sapiro

On 9/8/25 15:38, Sam Darwin via Mailman-users wrote: > > Or, the more the topic is discussed, I see there are two parts. Hyperkitty rendering is one of them. The other being to find a way to sanitize HTML of outgoing emails. If you want to accept HTML in posts, you should ensure that only trusted users can post. This is good practice anyway to avoid spam on the lists. Then you don't have to be too concerned about malicious HTML. >> I was asking if you envisioned that a text/html part outside of a multipart/alternative part would cause mailman to create a text/plain alternative and package it with the text/html part in a multipart/alternative part. But if that was not your intent, OK. > > I hadn't thought about that situation. > > Maybe it is relevant after all. And then, you said that you are not interested in doing that. It might need to be investigated along with these other features. Not sure. You can currently convert HTML to plain text, but that replaces the HTML. I understand you want both so your users have the option of seeing one or the other depending on MUA settings, but I don't see a demand for a feature like that. >> The issue is not in the plain text converted from the HTML by Mailman's Convert html to plaintext feature. The issue is in the text/plain alternative created by Yahoo when a message is composed as "rich text" and created by Yahoo as multipart/alternative. Were you looking at that text/plain alternative part from Yahoo., i.e. what you see in the outgoing mail if Collapse alternatives is Yes. > > The list's settings are Collapse alternatives=Yes and Convert html to plaintext=YES. Standard "plain" URLs are ok, but I was just now able to replicate some sort of problem. Using the yahoo toolbar, a fully HTML hyperlink with an href and name failed to render in plain text. It resulted in just plain text without appearing as a "link". If you are saying it resulted in the URL being rendered in the text/plain alternative as a text string, that is not what I see. I just composed a message from Yahoo to a non-yahoo address. I created the message in Yahoo's HTML editor. It simply said "Hi mark. Here's a link." after which I pasted today's Google Doodle link. In the resultant message the HTML part rendered as Hi mark. Here's a link. Google Search where "Google Search" was the above link I had pasted and this was also followed by a Google Search graphic which was also the same link. However the text/plain part in its entirety (minus my signature) was > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: quoted-printable > > Hi mark. Here's a link. Google Search > > |=20 > |=20 > | |=20 > Google Search > > > | > > | > > | > > > > The display text "Google Search" was in the text plain part, but the text of the link itself appeared nowhere in the text/plain part > interesting... The future plan would be to set all filtering to NO. All MIME parts delivered. But then, what if a plain-text version is missing somehow. Then the message will contain only the HTML. But if you do that, malicious HTML and missing plain text will be the least of the things to be concerned about. All sorts of malicious malware can be attached to email in other than HTML parts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

[MM3-users] Re: cannot bind to lmtp host address through lmtp port(OSError: [Errno 99] error while attempting to bind on address: cannot assign requested address)

by Mark Sapiro

On 10/18/22 11:28, Paul Ssekamatte via Mailman-users wrote: > i have successfully set up mailman3 instance by following the guide at https://gitlab.com/mailman/mailman-suite-doc/blob/master/source/install/vir… and from this mailing list. > my setup uses an alias domain i.e the mail server is different from the lists server. That is not what alias domains are for. You do not want an alias domain. > I have successfully created an alias domain and mailing list through Postorius but I keep getting this error in syslog. > OSError: [Errno 99] error while attempting to bind on address ('xxx.xx.xx.xx', 8024): cannot assign requested address. > Even when I change the port number, I still get the same error > Kindly assist. First, remove the Alias Domain from your domains. > here is my mailman.cfg config > [paths.here] > var_dir: /opt/mailman/mm/var > > [mailman] > layout: here > site_owner: postmaster(a)mail.example.com > > [database] > class: mailman.database.postgresql.PostgreSQLDatabase > url: postgres://mailman:#passwd@localhost/mailman > > [archiver.prototype] > enable: yes > > # For the HyperKitty archiver. > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg > > [shell] > history_file: $var_dir/history.py > > [mta] > verp_confirmations: yes > verp_personalized_deliveries: yes > verp_delivery_interval: 1 > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: mail.example.com The above is wrong. You want the default lmtp_host: 127.0.0.1 > lmtp_port: 8024 > smtp_host: mail.example.com smtp_host should be the mail server, not the list host. Is it? > smtp_port: 25 > configuration: python:mailman.config.postfix These next 3 do not belong in mailman.cfg. They are Postfix main.cf settings: > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no and this next one is a Mailman 2.1 mm_cfg.py directive and is not for Mailman 3. > POSTFIX_STYLE_VIRTUAL_DOMAINS= ['example.com'] > > /etc/mailman3/settings.py file is as follows not relevant for this issue. > /etc/postfix/main.cf is as follows > smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) > biff = no > append_dot_mydomain = no > readme_directory = no > compatibility_level = 2 > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination > alias_maps = hash:/etc/aliases > alias_database = hash:/etc/aliases > mydomain = example.com > myhostname = lists.example.com > mydestination = $myhostname, localhost.$mydomain, localhost > relayhost = mail.example.com > myorigin = $mydomain > mynetworks = 127.0.0.0/8, 10.0.0.0, 192.0.0.1, [::ffff:127.0.0.0]/104 [::1]/128 > mynetworks_style = subnet > mailbox_size_limit = 4096000000 > #message_size_limit = 2048000000 > recipient_delimiter = + > inet_interfaces = all > #inet_protocols = all > inet_protocols = ipv4 > unknown_local_recipient_reject_code = 550 > owner_request_special = no > virtual_mailbox_domains = example.com You probably don't want this, at least not if the mailman server is example.com > virtual_mailbox_base = /var/vmail > virtual_uid_maps = static:20000 > virtual_gid_maps = static:20000 > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/opt/mailman/mm/var/data/postfix_lmtp > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains > virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap and you don't want this virtual_alias_maps. > postfix domains as follows: > lists.example.com example.com > > postfix lmtp as follows: > testlist(a)lists.example.com lmtp:[mail.example.com]:8024 > testlist-bounces(a)lists.example.com lmtp:[mail.example.com]:8024 > testlist-confirm(a)lists.example.com lmtp:[mail.example.com]:8024 The host in lmtp: is the Mailman server. > postfix vmap as follows: > testlist(a)example.com nmutest(a)lists.example.com > testlist-bounces(a)example.com nmutest-bounces(a)lists.example.com > testlist-confirm(a)example.com nmutest-confirm(a)lists.example.com You don't want that at all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

Looking at the code in gitlab it looks like it wasn’t merged until 1.3.6: https://gitlab.com/mailman/postorius/-/blob/1.3.6/src/postorius/urls.py#L53 But it’s not in 1.3.5: https://gitlab.com/mailman/postorius/-/blob/1.3.5/src/postorius/urls.py#L49 Thats ok, I’m going to 1.3.6 in a few days so that should solve my issue. -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:39 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 10/31/21 7:27 PM, Simon Coggins wrote: > Oops sorry I hit send to soon. If I try to go > to /lists/listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests> > <http://listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests>> I get a 404, it > looks like unsubscription_requests > <http://listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests>> isn’t in my > urls.py list for Postorius? It should be. It was added by https://gitlab.com/mailman/postorius/-/commit/0aba874cae15b1baae2839dca57d3…<https://gitlab.com/mailman/postorius/-/commit/0aba874cae15b1baae2839dca57d3…> -- Mark Sapiro <mark(a)msapiro.net<mailto: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(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

4 years, 1 month

[MM3-users] Re: Link to account

by Lars Bjørndal

Thanks a lot. Maybe I've done a mistake, it doesn.t work. At the bottom of /etc/mailman3/settings.py I have: ROOT_URLCONF = 'urls' `cat /etc/mailman3/urls.py` [...] urlpatterns = [ path( '', RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), ), path('lists/mailman3/', include('postorius.urls')), path('lists/archives/', include('hyperkitty.urls')), path('lists/', include('django_mailman3.urls')), path('lists/accounts/', include('allauth.urls')), path('lists/admin/', admin.site.urls), ] In Apache config for the domain, I now have: <IfModule mod_proxy.c> ProxyPreserveHost On ProxyPass "lists/mailman3" "http://127.0.0.1:8000/lists/mailman3" ProxyPass "lists/archives" "http://127.0.0.1:8000/lists/archives" ProxyPass "lists/accounts" "http://127.0.0.1:8000/lists/accounts" ProxyPass "lists/admin" "http://127.0.0.1:8000/lists/admin" ProxyPass "lists/user-profile" "http://127.0.0.1:8000/lists/user-profile" </IfModule> Restarted mailmanweb, httpd and mailman3. If I go to list.punktskriftutvalget.no/mailman3/, I get a 404 Not Found response in browser. So what's wrong, do you think? Thanks Lars On Tue, Apr 11, 2023 at 10:52:47AM -0700, Mark Sapiro wrote: > On 4/11/23 10:46, Lars Bjørndal wrote: > > Hi, list! > > > > On one of my sites, I want to have all Mailman3 links to go under > > /mailman3. Even though, the Login link goes to a URL like: > > > > https://list.punktskriftutvalget.no/accounts/login/ > > > > How can I ensure it goes to > > https://list.punktskriftutvalget.no/mailman3/accounts/login/ > > > See this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to lars(a)lamasti.net

2 years, 8 months

[MM3-users] Re: [External Email] Re: Mailman2 CLI commands for Mailman3

by Dave Hall

Mark, Thank you for your reply. This will help greatly in adapting to this new (to me) version. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu 607-760-2328 (Cell) 607-777-4641 (Office) On Wed, Oct 5, 2022 at 12:00 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/5/22 07:53, Dave Hall via Mailman-users wrote: > > Hello. > > > > Sorry if this is an old topic. I'm in the process of migrating from 2.1 > to > > 3.2. In my use case one of the advantages of Mailman 2.1 vs services > like > > Google Groups has been the ability to manage lists from the command line. > > Things like using sync_members to update the list for a committee when > the > > membership of the committee is updated one a year, or like using > > find_members and remove_members to remove a user from all mailing lists > > when they leave the organization. Even the ability to script mailing > list > > creation. > > > > So far I haven't found these commands in Mailman3. I hope there is a > plan > > to add these soon. > > They are there. In MM 3, the command line commands are all subcommands > of the `mailman` command. See `mailman --help` where you will see > subcommands including `syncmembers`, `findmember` and `delmembers`. Note > that prior to 3.3.2 there were no `addmembers`, `delmembers` and > `syncmembers` subcommands, but there were `modes` of the `mailman > members` command that would accomplish these functions. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 2 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Mark Sapiro

On 12/13/20 7:11 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > 1.Regarding the repeated access of /archives/api/mailman/urls seems to be related to mailman not being able to open port 25. > This is weird because other mails have been distributed. > The mailman log shows:Dec 12 22:16:48 2020 (1471) ACCEPT: < message id > > Dec 12 22:16:52 2020 (1474) Cannot connect to SMTP server localhost on port 25 That message is in response to a socket.error exception in attempted delivery. It is logged only once until there is a successful delivery, but the message keeps being retried. > webserver logs:<host > - - [12/Dec/2020:22:16:50 +0100] "GET /archives/api/mailman/urls ?mlist=...&key=*** HTTP/1.1" 200 64 "-" "python-requests/2.25.0" > <host > - - [12/Dec/2020:22:16:52 +0100] "GET /archives/api/mailman/urls?mlist=...&msgid=< message id >&key=*** HTTP/1.1" 200 105 "-" "python-requests/2.25.0" > This last entry is repeated forever (until I stop the mailserver for a few minutes, but later on this happens again for other mails too). Those GETs are part of normal message processing. As I said, they result from core handlers asking HyperKitty for the URL at which the message will be archived so they can add that URL to the Archived-At: header and maybe to a message header or footer. Presumably the one that keeps repeating is the one message/message-id that is throwing the socket.error and being continuously retried. I would stop Mailman and move that one .pck or .bak file out of Mailman's var/queue/out/ directory and then start mailman. You can then examine the queue entry with `mailman qfile` and maybe see what the issue is. > 2..Regarding the mails on the archive page, for most of the lists it is solved now. So probably one of the periodic jobs fixed that.The mailinglist which showed 0 participants 0 subscribers, does show now 0 participants 66 discussions.I have checked the member tables, and the members for this mailinglist are included there. OK. > 3.What I notice now too is that the hourly runjobs tasks don't seem to finish.I would have to check what they exactly do. Can I somehow activate logging for these? > mailman 300042 300016 1 08:00 ? 00:09:18 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 302158 302149 2 09:00 ? 00:09:10 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 304513 304506 2 10:00 ? 00:09:38 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 308631 308620 3 11:00 ? 00:09:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 312847 312832 3 12:00 ? 00:09:15 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 317343 317332 4 13:00 ? 00:09:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 320079 320072 7 14:00 ? 00:09:08 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 322618 322610 13 15:00 ? 00:08:54 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 325205 325198 84 16:00 ? 00:06:56 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings /opt/mailman/venv/bin/django-admin runjobs --list will show you what the jobs are. The hourly jobs are new_lists_from_mailman, thread_starting_email and update_index. The one running long is almost certainly update_index. I would stop running the hourly jobs until you have successfully updated the search index for all lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Mail configuration

by Bill Christensen

Though not a perfect solution, setting an SPF in your DNS will help. Enter something along the lines of: v=spf1 include: mailServerDomainName.com ip4:<old_IP_Address> ip4:<new_IP_address> ~all (obviously, change the generic entries to real values, and use IP6 addresses if appropriate. ) On Tue, Mar 27, 2018 at 6:34 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 03/27/2018 03:43 PM, Stephen J. Turnbull wrote: > > > > My feeling is that you want to ask on Postfix channels, since I don't > > see a good reason to involve Mailman itself in what is really a task > > for the MTA. Mailman was deliberately designed to not know anything > > about outgoing mail except a host and port to send to. > > > Which brings up the point I've been meaning to post for days but it > keeps slipping off the back burner and falling on the floor. > > I can think of a couple of ways to hack the code in Mailman 2.1 to > select a different outgoing MTA by list. It can also be done in Mailman > 3 by having separate MTA configs per list, but I can't give you a recipe > off hand. > > But, the way I would do this is what you are presumably doing anyway. > That is have separate Mailman installations on the old and new server. > Then you can move the lists incrementally and gradually. Then all you > need is a transport map in Postfix on the old server to route mail to > the new server for the already moved lists, and then finally update DNS > after all the lists are moved. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 4 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Odhiambo Washington

On Mon, Jan 23, 2023 at 11:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/23/23 12:17, Odhiambo Washington wrote: > > On Mon, Jan 23, 2023, 23:09 Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> It's actually trying to create fulltext_index, so clearly it's not > >> looking at the fulltext_index that you are. If you are following > >> https://docs.mailman3.org/en/latest/install/virtualenv.html you > probably > >> need to specify the path in /etc/mailman3/settings.py as in, e.g. > >> ``` > >> HAYSTACK_CONNECTIONS['default']['PATH'] = > >> '/opt/mailman/mm/var/fulltext_index' > >> > > > > Doesn't this follow the same rules of getting the settings.py from > gitlab? > > > I don't understand. Can you be more specific? > > Note that when following > https://docs.mailman3.org/en/latest/install/virtualenv.html you create > /etc/mailman3/settings.py and it contains > ``` > from mailman_web.settings.base import * > from mailman_web.settings.mailman import * > ``` > to establish a base set of settings that can be augmented or overridden > in /etc/mailman3/settings.py. mailman_web.settings.mailman in turn contains > ``` > HAYSTACK_CONNECTIONS = { > 'default': { > 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', > 'PATH': "fulltext_index", > ``` > which is a relative path for fulltext_index and may need to be set to an > absolute path. > Mi Mark, I have read this page - https://docs.mailman3.org/en/latest/install/virtualenv.html and further - https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-config - without clicking any external links. I still don't see the HAYSTACK_CONNECTIONS in the settings.py included on that page. I am missing something obvious, no? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Abhilash Raj

On February 27, 2019 11:53:34 PM PST, Danil Smirnov <danil(a)smirnov.la> wrote: >Hi Mark, > >Actually all this stuff happens inside the container after it's started >and >initialized without errors. I didn't amend the image anyhow. > >Also I have the configuration based on docker-compose.yaml provided in >the >repository which works just fine for mailman-web image. > >The very same config with postorius image (+ UWSGI_STATIC_MAP param) >fails >with 500 error... > >Now answering your questions: > >ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > >> do you have django-q in INSTALLED_APPS in your Django settings and >what >> is set for Q_CLUSTER? >> > >I've checked settings.py inside the container and I haven't found any >of >the mentioned configurations there. > >Does the manage.py that's being run here point to the right >settings.py? >> > >No clue. > >Also I wonder why we have some Hyperkitty-related cronjobs in non-HK >configured image? > >https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… Because I am a dum dum ;-) Will work on removing those crons and stuff. Would be nice if you opened an issue on Github so that I don't forget. >Danil > > > >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. >Dylan >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> >_______________________________________________ >Mailman-users mailing list -- mailman-users(a)mailman3.org >To unsubscribe send an email to mailman-users-leave(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

6 years, 9 months

[MM3-users] Re: nginx configuration on a multitasking server

by David Newman

On 12/22/21 8:50 PM, Mark Sapiro wrote: > On 12/22/21 7:54 PM, David Newman wrote: >> On 12/22/21 7:29 PM, Mark Sapiro wrote: >> >>> This looks like a uwsgi issue as discussed at >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >>> although that's with apache and not nginx so it may not be. >> >> If I'm reading the thread correctly, it's Apache workarounds to an >> underlying Debian issue, so I agree it may not apply with nginx. > > > I think you're correct that it doesn't apply to nginx, but the symptom > is not the same. It is not a Debian issue per se. It is an Apache change > that got installed with a Debian update, but the underlying issue is > with Apache. See > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > >> There are 260 files named 'urls.py' under /opt/mailman, mostly for >> socialaccount stuff. >> >> Where does that change go? All files? Or just this one: >> >> /opt/mailman/venv/lib/python3.9/site-packages/postorius/urls.py > > > Not that one. The one whose content looks like > https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py. It > is probably in the same directory as your Django settings. On my system that file lives here: /opt/mailman/venv/lib/python3.9/site-packages/mailman_web/urls.py But the error persists after this addition and restarting MM3 and mailmanweb and nginx: url(r'^mailman/', include('postorius.urls')), There is this 404 error in uwsgi.log: [pid: 73356|app: 0|req: 3/3] 127.0.0.1 () {48 vars in 1544 bytes} [Wed Dec 22 21:13:48 2021] GET /mailman/admindb/listname => generated 5328 bytes in 14 msecs (HTTP/1.0 404) 6 headers in 197 bytes (1 switches on core 0) If this is a uwsgi issue, is there something else to tweak with that? Thanks dn > >

3 years, 11 months

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/16/19 9:22 PM, Paul Arenson wrote: > In my test of the two forms of signup, I am getting these unexpected results. Is it my settings or is something weird within the program itself? > > 1) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > > 2) Choose "You can also subscribe without creating an account. If you wish to do so, please use the form below" > > 3) Then I have to approve it. They get "Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org You have to approve it or the user has to confirm her email address? Maybe you have to approve it because the lists Subscription Policy is Moderate. > 4) But I have to approve it.I assume this is because they do not yet have a real account. And they should be listed as a NON MEMBER? No. They will be a member, they just will not have a Django account that they can log in to. > 5) But even when they sign up here: https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… they get an email from my provider (NOT MY LIST????) as follows: > > "Hello from mailman3.emwd.com! You're receiving this e-mail because user iCloud has given yours as an e-mail address to connect their account. > To confirm this is correct, go to https://list.tokyoprogressive.org/accounts/confirm-email/MTE3:1iA44k:E7w7xh… Thank you from mailman3.emwd.com! mailman3.emwd.com" Because when you create a Django account, you have to confirm your email address. > 6) And this is where it gets weird. If they send from their email program and get the welcome (Welcome to the "Discuss" mailing list! > To post to this list, send your email to: discuss(a)list.tokyoprogressive.org You can unsubscribe or make adjustments to your options via email by > sending a message to....... I then get a notice: > > "Your mail to 'discuss(a)list.tokyoprogressive.org' with the subject test notice Is being held until the list moderator can review it for approval. The message is being held because: The message is not from a list member" What is Message Acceptance -> Default action to take when a member posts to the list ? You get the notice or the user gets the notice? > 7) While if they send FROM THE interface it goes through. > > 8) What I am confused about. > > Signing up for an account should make them a member, right? Subscribing should make them a non member, no? Signing up for an account is just signing up for a Django account. You can sign up for an account and log in and then subscribe to the list. Subscribing makes one a member whether or not you subscribe from a logged in account or subscribe without creating an account. > But here it seems that both make them a non member. If an address which is not a member posts to the list, that address becomes a non-member. This is the only way other than being explicitly added by an admin that an address becomes a non-member. > And worse, someone with an account sending from the Interface has their message get through while the same person sending from an email program has me get a notice that a non member is trying to post. If by sending from the interface, you mean posting via hyperkitty, the user must have an account and be logged in to do that. Your "same person" may have multiple entities within Mailman, possibly subtly different email addresses, one of which is a member and one of which isn't. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Recommended way to backup a mailman3 instance

by Abhilash Raj

On Mon, Apr 13, 2020, at 9:40 AM, Mark Sapiro wrote: > On 4/13/20 3:22 AM, Andrew Hodgson wrote: > > > > I was working round my own backup strategy a few weeks ago as I discussed earlier on this list. One thing I found when the directory structure that Mailman Core uses is that the lists directories do not get re-created when Mailman Core starts if they don't already exist. Is this something that should happen, and when would those directories get created? Every other directory did get re-created. > > > > In my case I was moving from a Dockerised installation to one using venvs, and as the directories from the Docker installation were empty as there hadn't been any postings for a few days, I didn't transfer those over. I created the list directories myself and everything carried on. > > > These var/lists/<list-id>/ directories hold the digest.mmdf files which > are mailboxes containing the messages for the next digest. A list post > will be added to the digest.mmdf file which will be created if > necessary, but if the var/lists/<list-id>/ directory doesn't exist, the > create will fail. > > Thus, the var/lists/<list-id>/ directories need to exist. Normally, they > are created when the list is created so they need to be part of a backup. If they are empty, perhaps the digest creation process should just re-create them instead of failing to create/send digests? We don't really need the directory structure to exist. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 7 months

[MM3-users] Re: Issue converting table charset to utf8mb4 on mysql

by Helio Loureiro

Ok. Thanks for the clarification. Just a heads up: something went wrong. Very wrong. I had to revert the database to the last backup. But not on mailman3. It was on mailman3web. Apparently things got really bad after I converted tables django_q_ormq and hyperkitty_sender. After that hyperkitty got into cyclical crashes. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Sun, 24 Mar 2024 at 01:24, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/23/24 12:14, Helio Loureiro wrote: > > > So the question is whether it is possible to change the types in this > table. > > > > MariaDB [mailman3]> desc pendedkeyvalue; > > +-----------+----------------+------+-----+---------+----------------+ > > | Field | Type | Null | Key | Default | Extra | > > +-----------+----------------+------+-----+---------+----------------+ > > | id | int(11) | NO | PRI | NULL | auto_increment | > > | key | varchar(255) | YES | MUL | NULL | | > > | value | varchar(20000) | YES | MUL | NULL | | > > | pended_id | int(11) | YES | MUL | NULL | | > > +-----------+----------------+------+-----+---------+----------------+ > > 4 rows in set (0.001 sec) > > > > key and value are varchar. Can any of them be changed to text instead? > > Perhaps even both? > > > I wouldn't bother. The keys and values in the pendedkeyvalue table > should all be OK as latin1. That's why that table wasn't included in the > migration at > > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/database/alemb… > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to helio(a)loureiro.eng.br >

1 year, 8 months

[MM3-users] Re: HyperKitty Question

by Samir Faci

Sorry about this, I had a draft ready to go sitting there for the past few hours. I stand corrected. I'm not sure what combinations of factors fixed this but it's all good now. base_url: https://lists.domain.org/hyperkitty/ worked. I have an archive and about 50 emails of me talking to myself while testing all this out. Thank you for all the help Marc and everyone else on the list. -- Samir Faci On Mon, May 4, 2020 at 7:36 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/4/20 6:11 PM, Samir Faci wrote: > > > > I have nginx running with multiple website being serviced from the same > > server. > > > > I updated the config where port 80 gets redirected to SSL. > > > > I tried setting mailman3-hyperkitty.conf to both: > > > > base_url: http://localhost/hyperkitty> base_url: > https://lists.domain.com/hyperkitty/ > > > > Either should be OK, possibly dependent of your nginx config. > > > But neither seem to be working. Does hyperkitty require traffic to be > > going over port 80? > > > No. https should work. Can you go to > https://lists.domain.com/hyperkitty/ in a browser? > > Do you have api_key: set in mailman3-hyperkitty.conf and is it set to > the same value modulo quotes as MAILMAN_ARCHIVER_KEY in your Django > settings. > > Note the value needs to be quoted in > > MAILMAN_ARCHIVER_KEY = 'the_value' > > and not in > > api_key: the_value > > because the former is a Python string and the latter is a config value. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thank you Samir Faci https://keybase.io/csgeek

5 years, 7 months

[MM3-users] Re: RDS CA changes

by Hirayama, Pat

Thanks, Mark. That's what it looked like to me, but I wanted someone with more expertise / experience to weigh in. Have a great day! Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, August 12, 2024 10:49 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: RDS CA changes CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 8/12/24 10:23, Hirayama, Pat wrote: > > As near as I can tell from reading the Mailman 3 docs, and looking at my mailman.cfg and settings_local.py ... I don't know that Mailman 3 is using certificate verification for the PostgreSQL connection. At least, I can't see anything in those configuration files that suggest this. Does anyone know if this is the case – or which configuration file I should look at to verify? Will my Mailman 3 be ok if the DBAs go ahead and update the certificates on their end? There are two places where the database access is defined. They are the [database] section in mailman.cfg and the DATABASES definition in Django's settings. I don't see a way in either of these to specify TLS for the connection, possibly it is set on the PostgreSQL side. In any case, I don't think there'd be any issue if the DBAs go ahead and update the certificates on their end. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailm… Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma… This message sent to phirayam(a)fredhutch.org

1 year, 4 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Hi Mark, Any suggestions over my earlier email? I am waiting for your reply. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Oct 27, 2020 at 1:16 PM Shashikanth Komandoor < shashikanth.komandoor(a)gmail.com> wrote: > Hi Mark, > > Thank you for your help. I have traced the versions of > different components of mailman 3. I am downloading through GIT LAB because > I need to modify the code according to my organization's requirements like > to add SMS notifications when a mail is waiting for pending approval and so. > > With your help, I have found out the commits I am using in my > environment. I got them using the way you suggested "git log". That may be > helpful for you to help dummies like me. > > *### Mailman Core Version ###* > > *commit 437cb49ffc29ef8960ef26d18bd883ed5aa61ded* > *Merge: 98cf97b 0bca998* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Thu Oct 15 14:02:36 2020 -0700* > > * Merge branch 'template' into 'master'* > > * Clarify the posting instruction in the list welcome message.* > > * See merge request mailman/mailman!723* > > *### django-mailman3 Version ###* > > *commit d9e675e5cc1b966f9cd02b2e492649972f8ddc40* > *Merge: ea2b33a c091e43* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 00:40:51 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use GHCR for the CI image* > > * See merge request mailman/django-mailman3!108* > > *### Hyperkitty Version ###* > > *commit 36f43466763c2686cf4d69c982ea64b956c30939* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Mon Oct 5 04:54:44 2020 +0000* > > * Use GH registry to pull CI image.* > > *### Mailmanclient Version ###* > > *commit aaa529808e2d61899f90509da4ea802a70d2c8ff* > *Merge: ff39dd8 8670751* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 01:09:32 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use GHCR for the CI image* > > * See merge request mailman/mailmanclient!130* > > *### Mailman Hyperkitty Version ###* > > *commit 87db8b03cc4ceba8ef8eafedeaaf11f99f2e50e0* > *Merge: 35ff801 04deff5* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Fri Jun 19 18:15:57 2020 +0000* > > * Merge branch 'fix_25' into 'master'* > > * Add a test for the presence of surrogates in the stringified message.* > > * Closes #25* > > * See merge request mailman/mailman-hyperkitty!7* > > *### Mailman-suite Version ###* > > *commit 3b8780f26d544cb333970eae43ccffc7e34314aa* > *Merge: 74e7927 4463b31* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Sat May 30 00:32:40 2020 +0000* > > * Merge branch 'doc_mb4' into 'master'* > > * Added comment about OPTIONS = {'charset': 'utf8mb4'} to settings.py.* > > * See merge request mailman/mailman-suite!8* > > *### Postorius Version ###* > > *commit 02e3183c3cd9e069d8d886426b76b08504ea5e1e* > *Merge: 61242d2 321310c* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 00:43:14 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use the GHCR registry for CI image.* > > * See merge request mailman/postorius!549* > > I have removed only mailmanclient and re-cloned it from gitlab and > ran the python setup.py develop command. But still the same error. > > Is there anything else I can do to get rid of that error. > > Thanks in advance. > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_6854939421424022049_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On Tue, Oct 27, 2020 at 6:56 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 10/26/20 6:10 PM, Shashikanth Komandoor wrote: >> > >> > How to find out the versions of the each and every component >> > of the mailman 3 like mailman core, mailmancilent, postorius, >> > hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, >> > after installation? >> >> >> cd to the directory in which you cloned the gitlab project for the >> component and do `git log` >> >> >> > If I am running an old mailmanclient or older version of any >> > other mailman component, please suggest how to upgrade either one or >> > multiple components based on the requirement. Is there any link that >> > would help me to upgrade ? >> > >> > I have used the >> > link https://docs.mailman3.org/en/latest/devsetup.html to install the >> > mailman 3 components. I expected that the procedure followed in this >> > link would install the latest versions of the mailman 3 components. >> > Please correct me if I am wrong. Is there any latest version >> > compatibility table ? >> >> >> If you installed each of mailman, mailmanclient, django-mailman3, >> postorius and hyperkitty according to instructions like >> >> $ cd ~/mailman >> $ git clone https://gitlab.com/mailman/mailmanclient.git >> >> Then set up mailmanclient: >> >> $ cd mailmanclient >> $ python setup.py develop >> $ cd .. >> >> from that document, you should have the latest version. If that is the >> case, `git log` in the mailmanclient directory should begin like >> >> commit aaa529808e2d61899f90509da4ea802a70d2c8ff (HEAD -> master, >> origin/master, origin/HEAD) >> Merge: ff39dd8 8670751 >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Thu Oct 15 01:09:32 2020 +0000 >> >> Merge branch 'fix-ci' into 'master' >> >> Use GHCR for the CI image >> >> See merge request mailman/mailmanclient!130 >> >> commit 8670751caff689733751ef323ef521c4a3fa1237 >> Author: Abhilash Raj <raj.abhilash1(a)gmail.com> >> Date: Wed Oct 14 17:36:58 2020 -0700 >> >> Use GHCR for the CI image >> >> commit ff39dd8f03a820f442f2251553c444370df3b914 >> Merge: 80ebed4 76d44e1 >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Fri Aug 7 19:35:05 2020 +0000 >> >> Merge branch 'invite' into 'master' >> >> Add support for inviting an email address to join a list. >> >> See merge request mailman/mailmanclient!129 >> >> or if you did this before Oct 15, maybe it starts with >> commit ff39dd8f03a820f442f2251553c444370df3b914 >> >> The particular commit you need for your issue is >> >> commit 86eb0da3cdb48e253b0d36138ab7cf91259a7583 >> Merge: c8dcb1e 28d1c3a >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Sat May 16 08:02:21 2020 +0000 >> >> Merge branch 'held-count' into 'master' >> >> Add a new get_held_count() API to get a count of held messages. >> >> See merge request mailman/mailmanclient!122 >> >> >> >> Note that unless you intend to do actual development of Mailman 3, you >> should be following >> <https://docs.mailman3.org/en/latest/install/virtualenv.html> rather >> than <https://docs.mailman3.org/en/latest/devsetup.html>. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > > -- > Thanks & Regards, > Shashi Kanth.K > 9052671936 > > > > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 1 month

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

I have run the below commands for sure: $ cd mailmanclient $ python setup.py develop And as you have suggested, I navigate to mailmanclient directory and ran the git log to provide you the version output. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 12:12 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/27/20 11:08 PM, Shashikanth Komandoor wrote: > > Thank you Mark for your response. > > > > All the mentioned versions of all the components are taken from my > > currently running system only in which I am facing the issue. > > Did you run > > $ cd mailmanclient > $ python setup.py develop > > as it says at <https://docs.mailman3.org/en/latest/devsetup.html> > > I do not understand exactly how the various components are installed in > your installation, so I can't tell you what is wrong, but the version of > mailmanclient that gives you the AttributeError: 'MailingList' object > has no attribute 'get_requests_count' is not the one whose latest commit is > > ### Mailmanclient Version ### > > commit aaa529808e2d61899f90509da4ea802a70d2c8ff > Merge: ff39dd8 8670751 > Author: Abhilash Raj <maxking(a)asynchronous.in maxking(a)asynchronous.in> > Date: Thu Oct 15 01:09:32 2020 +0000 > > Merge branch 'fix-ci' into 'master'* > > Use GHCR for the CI image* > > See merge request mailman/mailmanclient!130* > > because that one won't have this error. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 1 month

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

Thanks for your prompt reply.To import the config and archives I ran the commands as outlined in Migrating from Mailman 2.1 to Mailman 3 — Mailman Suite 3.3 documentation : mailman import21 foo-list(a)example.com /path/to/mailman2/foo-list/config.pck python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox After running these commands the archives became available for most of the mailinglists. I didn't run the Django admin command with arguments "update_index_one_list" to build the indices for each mailinglist seperately. After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. Best regards,Eric On Sunday, December 13, 2020, 12:12:46 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 2:33 PM, Eric Broens via Mailman-users wrote: > Today I have migrated about 30 mailinglists from mailman 2.1 to mailman 3.3.2 & Hyperkitty 1.3.3. > Although no error responses were given when importing the 2.1 pck files, and neither for importing the archives, for about half of the mailinglists the hyperkitty webpage doesn't show any subscribers, nor archived emails. > The imported members and other settings are correctly shown in the postorius page. > Is there anything that I can verify why the archive is not shown on the hyperkitty page?The hyperkitty_email database table does contain the emails. Did you specify --no-sync-mailman when you ran hyperkitty_import? If so did you run the django sync_mailman job when you finished importing? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years

[MM3-users] Re: Cron error

by Mark Sapiro

On 10/25/20 6:14 AM, Gordon Dickens wrote: > Hi Mark, and other helpful souls, > This cron error continues to occur at 12AM several times each week > but not each day > .Here is the output from the error message that is sent to the mailman3 > admin: > > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 216, in lo > ck > os.link(self._claimfile, self._lockfile) > FileExistsError: [Errno 17] File exists: '/var/lib/mailman3/locks/dbcreate.lck|s > lc.mailhub4u.com|19728|1804933663424130229' -> '/var/lib/mailman3/locks/dbcreate > .lck' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/bin/mailman", line 11, in <module> > load_entry_point('mailman==3.2.1', 'console_scripts', 'mailman')() > File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ > return self.main(*args, **kwargs) > File "/usr/lib/python3/dist-packages/click/core.py", line 716, in main > with self.make_context(prog_name, args, **extra) as ctx: > File "/usr/lib/python3/dist-packages/click/core.py", line 641, in make_context > self.parse_args(ctx, args) > File "/usr/lib/python3/dist-packages/click/core.py", line 1089, in parse_args > rest = Command.parse_args(self, ctx, args) > File "/usr/lib/python3/dist-packages/click/core.py", line 940, in parse_args > value, args = param.handle_parse_result(ctx, opts, args) > File "/usr/lib/python3/dist-packages/click/core.py", line 1477, in handle_pars > e_result > self.callback, ctx, self, value) > File "/usr/lib/python3/dist-packages/click/core.py", line 96, in invoke_param_ > callback > return callback(ctx, param, value) > File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in init > ialize_config > initialize(value) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 218, in > initialize > initialize_2(propagate_logs=propagate_logs) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 177, in > initialize_2 > config.db = getUtility(IDatabaseFactory, utility_name).create() > File "/usr/lib/python3/dist-packages/mailman/database/factory.py", line 50, in > create > with Lock(os.path.join(config.LOCK_DIR, 'dbcreate.lck')): > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 334, in __ > enter__ > self.lock() > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 248, in lo > ck > elif self._read() == self._claimfile: > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 442, in _r > ead > with open(self._lockfile) as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/dbcreate > .lck' > > Then, the contents of the /var/lib/mailman3/locks directory is as > follows: > > -rw-rw---- 1 list list 80 Oct 25 00:00 > 'dbcreate.lck|slc.mailhub4u.com|19728|1804933663424130229' > -rw-rw---- 2 list list 78 Oct 26 2020 master.lck > -rw-rw---- 2 list list 78 Oct 26 2020 > 'master.lck|slc.mailhub4u.com|25024|3254783301248355113' > > I have since removed the file > 'dbcreate.lck|slc.mailhub4u.com|19728|1804933663424130229'. > . > Also, I had previously changed the permissions on the > /var/lib/mailman3/locks directory to give universal read/write > permissions:: > > drwxrwxrwx 2 list list 4096 Oct 25 08:11 locks > > Also, as user = list, I am able to create, edit and delete files in > that directory which really doesn't make any sense because mailman3 is > alsoÂ running as user = list when it creates the Permission denied > error. > Does anybody have an idea as to what is going on here and how to fix > it? The FileExistsError is possibly due to some kind of race condition between two `mailman` commands. Are you perhaps running both `mailman digests --periodic` and `mailman notify` via cron at midnight each night? If so, try running one if them a minute later. The permissions error is on reading the lock file itself. I don't understand what is causing that, but I doubt permissions on the locks directory are involved. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Help with some 'withlist' configuration changes

by Mark Sapiro

On 6/23/21 6:30 AM, David Partain via Mailman-users wrote: > Hi, > > Firstly, a repeat that I have a relatively broken (and soon to be fixed, I hope) installation of mailman3 based on Ubuntu 18.04 distrib packages (3.1.1-9) that stumbles along by me dealing with a bunch of things by hand that I hope'll go away once I'm up to the current version. > > In this set-up, I get a fair number of items shunted. Since I have this wonky version where stuff isn't always exposed in the web interface, I have to fix these things by hand. An example is that something gets shunted because of too many recipients, where I do: > > sudo -u list mailman withlist somemailmanlist > m.max_num_recipients = 0 > commit() > sudo -u list mailman unshunt > > I've managed to find a number of these, such as m.max_message_size, m.require_explicit_destination, and m.administrivia. There is some other issue here as these things should only cause a message to be held, not shunted. Some exception is being thrown in the process of holding the messgage, and thaty is the real issue. What are the tracebacks in Mailman's mailman.log for these shunts? > My questions are undoubtedly foolish, but here goes: > > 1. Is there any way to print the entire 'm' structure? If so, I'd perhaps be able to figure out the answers to my other questions. dir(m) or maybe you want >>> for x in dir(m): ... if not x.startswith('_'): ... print(f'{x}: {m.__getattribute__(x)}') ... > 2. Is there a way for me to correct the following shunt-ing issues with 'withlist'? I've been unable to figure out how... > > a. 'moderation_reasons': [ 'Message has no subject'] / 'rule_hits': ['no-subject'] > > b. Some things get caught as 'rule_hits': ['nonmember-moderation']. However, if I look in the (web-based) config, it shows that non-members should be accepted but the messages are shunted nonetheless. I don't know what to look for in 'm' or how I might clear these messages. As I note above, these things are reasons to hold the message. The shunting occurs because something is going wrong in the holding process. Find the errors and tracebacks in Mailman's mailman.log to see what the real issue might be. > 3. I have no idea what these are telling me to do about digest messages. Suggestions? This is the entire info I get from 'mailman qfile': > > ------------------------------------------------------snip snip---------------------------------------------- > [----- start pickle -----] > <----- start object 1 -----> > > <----- start object 2 -----> > { '_parsemsg': False, > 'digest_number': 457, > 'digest_path': '/var/lib/mailman3/lists/somelist/digest.31.457.mmdf', > 'lang': 'en', > 'listid': 'somelistid', > 'version': 3, > 'volume': 31, > 'whichq': 'digest'} > [----- end pickle -----] > ------------------------------------------------------snip snip---------------------------------------------- That is telling you there was in issue in sending the digest, the mailbox for which is /var/lib/mailman3/lists/somelist/digest.31.457.mmdf. Unshunting that will retry sending that digest. > 4. I have some that have 'rule_hits': [] (it's empty) but are shunted nonetheless. I can't see anything weird other than one of the messages has a utf-8 subject. Any ideas? > > 5. Some messages that were sent to -request addresses (e.g., subscribe messages, confirm, approve messages) are being shunted. What should I do with these? You need to find the errors in the log and figure out what the underlying issue is. I'm guessing it's a permissions issue, possibly because of having at one time rum `mailman start` as root causing files to be created and owned by root and not be readable/writable by the Mailman user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Christian

I followed instructions provided here. Well, I rebooted the server and I'm getting the same error again at the web page of "Mailman REST API not available. Please start Mailman core." I again found locks in /opt/mailman/mm/var/locks . Once I removed them I could start mailman. Perhaps I made a boo boo. I want mailman to start without locks upon reboot. Help! (thanks) -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, February 12, 2025 1:12 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman REST API not available. Please start Mailman core. On 2/12/25 12:05, Christian via Mailman-users wrote: > That worked. > > Now on > https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-m > ailman > -automatically it says > > "Pay attention to the config file output above and make sure that you > see /etc/mailman3/mailman.cfg there. If the config path is different, > you should make sure to create a new config file at > /etc/mailman3/mailman.cfg and re-run the command." > > Well...mailman info yields > > GNU Mailman 3.3.5 (Tom Sawyer) > Python 3.7.3 (default, Mar 23 2024, 16:12:05) [GCC 8.3.0] config file: > /opt/mailman/mm/mailman.cfg db url: > postgres://mailman:5DqTHnv8hUQSdd@localhost/mailman > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ REST credentials: > restadmin:restpass > > Should I create a new config file at /etc/mailman3/mailman.cfg ? You can, but the easiest thing is just replace the line Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" in /etc/systemd/system/mailman3.service with Environment="MAILMAN_CONFIG_FILE=/opt/mailman/mm/mailman.cfg" -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ NYAIOPZ3PLQCPT3QPLLRKMOUY52UORBM/ This message sent to csa(a)web-analysts.net

10 months

[MM3-users] Re: Congrats on the instructions for installation on ubuntu, what about migration?

by Bill Oliver

Thanks. I'll think on that. My tables have a different prefix, so I'll have to remember where to change those config files... billo On Wed, 2024-10-09 at 13:18 -0700, Mark Sapiro wrote: > On 10/8/24 5:45 PM, Bill Oliver wrote: > > > > Is there a tutorial/instructions on migrating data from an old > > system > > to a new one? It's actually not the end of the world if I don't > > get > > all the old emails transferred, but I'd like to get the email > > addresses > > of the participants moved over easily... I believe that I set it > > up > > in 2020, but did not do any version upgrades since then... > > > There's no explicit doc, but there are some posts in the archives of > this list, e.g. > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/me > ssage/FTIC47FPQER5FLR4IW4CGI7JB6ALKIX4/>. > > The easiest scenario is if you want to migrate everything. You just > dump > the database on the old server and load it on the new one using the > database manager's tools. > > If you only want to move some, but not all lists, it's more > complicated, > but possibly the easiest thing is to migrate everything and then > delete > the unwanted lists and their archives from Postorius and HyperKitty. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. > Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to billo(a)billoblog.com

1 year, 2 months

[MM3-users] Re: Performance issues with Mailman 3

by Wong, Wesley

I can confirm the settings on the old Mailman 2.1 setup had "VERP_DELIVERY_INTERVAL=0" set. In Mailman 3, I had copied the configuration from an example with the following defined for the mta: verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 I'll disable it and see how things go on it. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, October 7, 2022 5:19 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Performance issues with Mailman 3 On 10/6/22 15:08, Wong, Wesley wrote: > Hi, I am having some performance problems with Mailman 3 (version 3.3.5) when it sends out a lot of messages to people. We recently migrated from our old Mailman 2.1.x system to Mailman 3.x about 3 months ago. We host about 350 lists with membership counts varying between 10 to 1500 members on some of the lists. I noticed that outbound messages from Mailman to our outbound SMTP are getting delayed up to an hour when Mailman is processing a lot of messages going to lists. I suspect the difference is your Mailman 3 instance has full VERP enabled and your Mailman 2.1 instance did not. I.e., In MM 2.1, you did not override the default `VERP_DELIVERY_INTERVAL = 0` in mm_cfg.py, but in MM 3 you have `verp_delivery_interval: 1` in the `mta` section of mailman.cfg. > I was wondering if there are good performance tuning tips to be considered for Mailman 3 (i.e. OS, database and/os Mailman Core). I am running the setup on a VM. Here is my configuration for VM and OS: Search the Titles for `performance` at https://wiki.list.org/. The articles you find are all written for MM 2.1, but you're really dealing with the MTA and the issues are the same for MM 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 2 months

[MM3-users] Re: Welcome message issue

by Mohsen Masoudfar

Thank you Mark! You are helpful as always. I am running: Postorius Version 1.1.2 That explains the issue. Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 22, 2024 5:38 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Welcome message issue [EXTERNAL EMAIL] On 10/22/24 13:34, Mohsen Masoudfar wrote: > Good afternoon > I have an issue with welcome message. > > A list owner is requesting to update the welcome message for only one of their lists. They are requesting to change the default text and insert additional URLs pointing to sites related to their list. > I know there is a URI field that you may include a web page. But this doesn't work and gets ignored. If you are referring to the `uri` field in the template table this should work if the `name` is `list:user:notice:welcome` and the `context` is the list_id of the target list. > - is there a mailman cli option to update the default template for a single list? There is no specific cli option. A site admin can address this by creating a custom template at Mailman's var/templates/lists/LIST_ID/LC/list:user:notice:welcome.txt where LIST_ID is the desired lists ID and LC is the preferred language. The list owner can create a custom list:user:notice:welcome template via Postorius. > > I couldn't find it in WUI. Do you mean GUI? If so, since at least Postorius 1.2.0 there has been a `Templates` choice in the second level nav in the lists view. > I reviewed all parameters and variables of the list and couldn't find one that might be related to it. > > We are running an old version of Mailman 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

1 year, 1 month

[MM3-users] Re: Different Mail Domain Cause Key Error

by Mark Sapiro

On 4/21/20 1:10 PM, Brian Carpenter wrote: > > Ok. The first thing however is did I miss a step? Not really. The problem is FILTER_VHOST = True doesn't work for web hosts that aren't email hosts. > Here is the complete error that is sent to me via email as superuser: > > > Internal Server Error:/mailman3/lists/ > > KeyError at/mailman3/lists/ > 'file' > > Traceback: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/exception.py" > in inner > 34. response = get_response(request) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/base.py" > in _get_response > 115. response = > self.process_exception_by_middleware(e, request) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/base.py" > in _get_response > 113. response = wrapped_callback(request, > *callback_args, **callback_kwargs) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py" > in list_index > 755. paginator_class=MailmanPaginator) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in paginate > 71. objects = paginator.page(page_num) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in page > 46. number = self.validate_number(number) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/paginator.py" > in validate_number > 48. if number > self.num_pages: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/functional.py" > in __get__ > 80. res = instance.__dict__[self.name] = self.func(instance) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/paginator.py" > in num_pages > 97. if self.count == 0 and not self.allow_empty_first_page: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/functional.py" > in __get__ > 80. res = instance.__dict__[self.name] = self.func(instance) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in count > 56. return self.function(count=0, page=1).total_size > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py" > in _get_list_page > 751. advertised=advertised, mail_host=mail_host, > count=count, page=page) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/client.py" > in get_list_page > 181. return Page(self._connection, url, MailingList, count, page) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/page.py" > in __init__ > 37. self._create_page() > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/page.py" > in _create_page > 62. response, content = self._connection.call(self._build_url()) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/connection.py" > in call > 112. error_msg, response, None) > > *During handling of the above exception (HTTP Error 404: {"title": "404 > Not Found"}), another exception occurred:* The above 404 is the underlying problem. In the traceback above we see that /opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py at line 751 calls client to get the view for lists for this host. The full code is def _get_list_page(count, page): client = get_mailman_client() advertised = not request.user.is_superuser mail_host = request.get_host().split(":")[0] if ( getattr(settings, 'FILTER_VHOST', False)) else None return client.get_list_page( advertised=advertised, mail_host=mail_host, count=count, page=page) The issue is the FILTER_VHOST = True setting is broken. This is <https://gitlab.com/mailman/postorius/-/issues/394> The broken code tries to get the lists for the domain in the requesting URL which here is the web_host but the web_host has no lists. This is a complicated issue. See the whole comment thread in the issue where I am trying to mentor someone to a fix, but he apparently has given up. The issue is we don't have a method for retrieving lists by web host. It is simple enough to get all the email hosts associated with a web host, but what do we do if that's more than one email host. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Apple Mail encoding again

by Rainer Herbst

On Mi, 20 Apr 2022 10:01:55 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/20/22 07:54, Rainer Herbst wrote: >> Dear all, >> >> my first post was to optimistic - the user tested some other >>combinations and when he tries to send a signed HTML mail, the server >>again refuses to accept it with "Diagnostic-Code: smtp; 501 Message >>has defects". >> >> The user suggested that the problem is caused by a line containing >>only "-- " somewhere in the text, but I can not confirm this. >> >> Please find enclosed the refused mail (anonymized). > > That message has no defects. > ``` > >>> import email > >>> from mailman.email.message import Message > >>> txt = b""" (the testmail-abgelehnt.txt contents) """ > >>> msg = email.message_from_bytes(txt, Message) > >>> msg.defects > [] > >>> > ``` > Maybe I have deleted to much when anonymizing the message... I tested the whole message and it gave me: >>> msg.defects [InvalidMultipartContentTransferEncodingDefect()] Than I reduced the message content. The minimal message that provoked the defect is attached. When I delete line 12 ("Content-Transfer-Encoding: quoted-printable") from the message, the defect disapears. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. >Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 ----------------------------------------------------------------------------------------------- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/x-pkcs7-signature Name: smime.p7s

3 years, 7 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Thu Oct 13, 2022 at 6:03 AM WAT, Onyeibo Oku wrote: > On Wed, 12 Oct 2022 17:52:47 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: > > Thanks Eggert and Sapiro. > > > > > As Eggert suggests, see > > https://docs.mailman3.org/en/latest/install/virtualenv.html and > > follow that. > So far, this has been an interesting exercise. Mailman3 (core) is running but not Hyperkitty and Postorious. My setup is different though. I am running a system-wide instance of uwsgi. At the moment, uwsgi is serving a website. It is running in Emperor-tyrant mode. Hence, it can serve multiple django projects. I only need to add the relevant .ini file at /etc/uwsgi.d/ and it spawns a service for that. I have added mailman3.ini (taken from the suggested page above) into the /etc/uwsgi.d/ directory. This is what "systemctl status uwsgi" says: Oct 31 06:57:18 mail.server.tld uwsgi[20676]: [uWSGI] getting INI configuration from mailman3.ini Oct 31 06:57:18 mail.server.tld uwsgi[20676]: unable to find logger file Oct 31 06:57:18 mail.server.tld uwsgi[20261]: Mon Oct 31 06:57:18 2022 - [emperor] curse the uwsgi instance mailman3.ini (pid: 20676) Oct 31 06:57:21 mail.server.tld uwsgi[20261]: Mon Oct 31 06:57:21 2022 - [emperor] removed uwsgi instance mailman3.ini Oct 31 06:58:30 mail.server.tld uwsgi[20684]: [emperor-tyrant] dropping privileges to 973 972 for instance mailman3.ini Oct 31 06:58:30 mail.server.tld uwsgi[20684]: *** has_emperor mode detected (fd:9) *** Oct 31 06:58:30 mail.server.tld uwsgi[20684]: [uWSGI] getting INI configuration from mailman3.ini Oct 31 06:58:30 mail.server.tld uwsgi[20684]: unable to find logger file Oct 31 06:58:30 mail.server.tld uwsgi[20261]: Mon Oct 31 06:58:30 2022 - [emperor] curse the uwsgi instance mailman3.ini (pid: 20684) Oct 31 06:58:33 mail.server.tld uwsgi[20261]: Mon Oct 31 06:58:33 2022 - [emperor] removed uwsgi instance mailman3.ini It is not finding the logger file. The other django project on this machine is running fine. I can confirm that the logger plugin is installed. I must be missing something. Regards Onyeibo

3 years, 1 month

[MM3-users] Re: Have postgresql in the mailman.cfg file but sqlite shows in the mailman info command

by Mark Sapiro

On May 29, 2024 12:50:00 PM EDT, Keith Christian <keith1christian(a)gmail.com> wrote: > >Uncommented class and url: >class: mailman.database.postgresql.PostgreSQLDatabase ><<<---------------------------------------- >url: postgresql://mailman:MYPASSWORD@localhost/mailman ><<<---------------------------------------- > > >Now I get a stack trace from "mailman info" > >(venv) [mailman3@localhost-live ~]$ mailman info >Traceback (most recent call last): > File "/opt/mailman3/venv/bin/mailman", line 33, in <module> > sys.exit(load_entry_point('mailman==3.3.9', 'console_scripts', 'mailman')()) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", >line 1157, in __call__ > return self.main(*args, **kwargs) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", >line 1077, in main > with self.make_context(prog_name, args, **extra) as ctx: > File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", >line 943, in make_context > self.parse_args(ctx, args) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", >line 1644, in parse_args > rest = super().parse_args(ctx, args) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", >line 1408, in parse_args > value, args = param.handle_parse_result(ctx, opts, args) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", >line 2400, in handle_parse_result > value = self.process_value(ctx, value) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", >line 2362, in process_value > value = self.callback(ctx, self, value) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/bin/mailman.py", >line 95, in initialize_config > initialize(value) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/core/initialize.py", >line 228, in initialize > initialize_1(config_path) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/core/initialize.py", >line 122, in initialize_1 > mailman.config.config.load(config_path) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", >line 145, in load > self.push(filename, user_config.read()) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", >line 150, in push > self._config.push(config_name, config_string) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", >line 582, in push > confs = self._getExtendedConfs(conf_name, conf_data) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", >line 615, in _getExtendedConfs > _parser_read_file(parser, StringIO(conf_data), conf_filename) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", >line 49, in _parser_read_file > parser.read_file(f, source) > File "/usr/lib64/python3.9/configparser.py", line 718, in read_file > self._read(f, source) > File "/usr/lib64/python3.9/configparser.py", line 1085, in _read > raise MissingSectionHeaderError(fpname, lineno, line) >configparser.MissingSectionHeaderError: File contains no section headers. >file: '/opt/mailman3/mailman.cfg', line: 14 ><<<---------------------------------------- >'class: mailman.database.postgresql.PostgreSQLDatabase\n' > > >Here is the complete mailman.cfg file: > > 1 # /etc/mailman3/mailman.cfg > 2 # [paths.here] > 3 # var_dir: /opt/mailman/mm/var > 4 # > 5 # [mailman] > 6 # layout: here > 7 # # This address is the "site owner" address. Certain >messages which must be > 8 # # delivered to a human, but which can't be delivered to a >list owner (e.g. a > 9 # # bounce from a list owner), will be sent to this address. >It should point to > 10 # # a human. > 11 # site_owner: user(a)example.com > 12 # > 13 # [database] > 14 # class: mailman.database.postgresql.PostgreSQLDatabase > 15 # url: postgresql://mailman:MYPASSWORD@localhost/mailman > 16 # > 17 # [archiver.prototype] > 18 # enable: yes > 19 # > 20 # # For the HyperKitty archiver. > 21 # [archiver.hyperkitty] > 22 # class: mailman_hyperkitty.Archiver > 23 # enable: yes > 24 # configuration: /etc/mailman3/mailman-hyperkitty.cfg > 25 # > 26 # [shell] > 27 # history_file: $var_dir/history.py > 28 # > 29 # [mta] > 30 # verp_confirmations: yes > 31 # verp_personalized_deliveries: yes > 32 # verp_delivery_interval: 1 > 33 # If you uncomment any of the lines in this config, you must also uncomment the preceding section header, line 13 in this case. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

1 year, 6 months

[MM3-users] Re: bounce handling in mm3 available?

by Stefan Bauer

Hi Mark, thank you. We are running 3.1.1-9. So to get you right, this version only records the bounces in database and nothing more? No disabling of users etc. Stefan Am Mo., 24. Jan. 2022 um 23:32 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 1/24/22 05:20, Stefan Bauer wrote: > > Hi, > > > > what happens with bounce-mails that are processed by mailmans postfix > > instance? > > > What Mailman core version? Prior to 3.3.1, bounce events were recorded > in the bounceevent table but not otherwise processed. Subsequent to > that, they are scored if recognized and what notices are sent depends on > list settings. > > > > Jan 24 10:46:03 l01 postfix/lmtp[8432]: DF4AE600623: > > to=<company-newsletter-bounces(a)lists.company.tld>, > > relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0.01/0/0.01, > > dsn=2.0.0, status=sent (250 Ok) > > > > But the list-owner does not get any notification, nor do i see any > > bounce-information in the pistorious-gui. > > What are you expecting to see in Postorius? All you can see is if a > member's delivery status is Disabled by Bounces. Things like Bounce > score are not available in Postorius. > > What notices are sent depends on the settings in the Bounce Processing > section in Postorius. For example, if your message logged by postfix was > spam to the <company-newsletter-bounces(a)lists.company.tld> address that > is not recognized as a DSN and `Forward unrecognized bounces` is > Discard, the message will be silently discarded. > > Also, if that message was a non-fatal, message-delayed type of DSN, it > will be ignored. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 10 months

[MM3-users] Re: Disabled by bounce

by tlhackque

On 02-Feb-23 16:43, Mark Sapiro wrote: > On 2/2/23 04:54, Danil Smirnov wrote: >> Hi Mark >> >> On Wed, Feb 1, 2023 at 9:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >>> Yes and no. If 'Bounce info stale after' is set to 3d and no bounces >>> for >>> a user are received in a 3 day period, the user's bounce score is not >>> immediately reset, but it will be reset (to 1) the next time a >>> bounce is >>> received for the user. I.e., it is effectively the same thing unless >>> you >>> are looking at the user's bounce score which doesn't change until the >>> next bounce. >>> >> >> Isn't this a bug? We are now showing users' bounce scores on the Members >> page and this would be misleading. Is it difficult from internals >> perspective to have the bounce score reset immediately? > > > Yes, it is not difficult, but it's a lot of processing. It would > require something like a task runner task to periodically look at each > row in the member table and if the bounce score is > 0, find the > associated list's bounce_info_stale_after and if last_bounce_received > + bounce_info_stale_after < now, reset the score. > > Consider a site like mail.python.org that at this moment has 79024 > rows in the member table and 7531 of those have bounce_score > 0. > That's a lot of processing, and is it really an issue to show a > non-zero bounce score that's stale? > There's a middle ground. Seems like the sort of thing to do daily. Loose consistency would be good enough. Waiting for the next bounce - which on a low traffic list could be a long time coming - does seem difficult to explain that to users. A daily update seems easier to explain.

2 years, 10 months

[MM3-users] Re: Mails are stuck in Mailman Pipeline Queue

by Mark Sapiro

On 3/26/22 21:01, Shashikanth Komandoor wrote: > > But the below trace back is observed during mailman service stopping: This doesn't say much ... ...> Mar 27 09:01:22 2022 (5864) Uncaught runner exception: > Mar 27 09:01:22 2022 (5864) Traceback (most recent call last): > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 173, in _one_iteration ... > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 114, in signal_handler > raise RunnerInterrupt > mailman.interfaces.runner.RunnerInterrupt > Mar 27 09:01:22 2022 (5864) SHUNTING: 1648351882.6693938+ > c2e6ed709646a7680c73059b52d2f0451836e591 > Mar 27 09:01:22 2022 (5864) digest runner exiting. Above, digest runner was interrupted in processing and shunted the message it was working on. and below, pipeline runner was interrupted in processing and shunted the message it was working on. > Mar 27 09:01:22 2022 (5860) Uncaught runner exception: > Mar 27 09:01:22 2022 (5860) Traceback (most recent call last): > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 173, in _one_iteration > self._process_one_file(msg, msgdata) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 266, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/runners/pipeline.py", > line 37, in _dispose > process(mlist, msg, msgdata, pipeline) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/pipelines.py", > line 50, in process > handler.process(mlist, msg, msgdata) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/ > mailman/handlers/member_recipients.py", line 84, in process > for member in mlist.regular_members.members > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/ > mailman/handlers/member_recipients.py", line 83, in <genexpr> > recipients = set(member.address.email > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/roster.py", > line 239, in members > yield from self._get_members(DeliveryMode.regular) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/roster.py", > line 226, in _get_members > if member.delivery_mode in delivery_modes: > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/member.py", > line 205, in delivery_mode > return self._lookup('delivery_mode') > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/member.py", > line 167, in _lookup > pref = getattr(self.address.preferences, preference) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/attributes.py", > line 287, in __get__ > return self.impl.get(instance_state(instance), dict_) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/attributes.py", > line 723, in get > value = self.callable_(state, passive) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/strategies.py", > line 760, in _load_for_state > session, state, primary_key_identity, passive > File "<string>", line 1, in <lambda> > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/strategies.py", > line 850, in _emit_lazyload > session.query(self.mapper), primary_key_identity > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/ext/baked.py", > line 603, in _load_on_pk_identity > setup, tuple(elem is None for elem in primary_key_identity) The above says the runner was doing a database lookup. This may be a coincidence or there may be some database locking issue that underlies the issue with the pipeline runner. > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 114, in signal_handler > raise RunnerInterrupt > mailman.interfaces.runner.RunnerInterrupt > Mar 27 09:01:22 2022 (5860) SHUNTING: 1648351882.8537986+ > 9bf59cb23a71a4bae65536bfdbec0abb261adaa0 > Mar 27 09:01:22 2022 (5860) pipeline runner exiting. I suggest doing the following assuming your Mailman database is not sqlite3 (if it is, just do step 2): 1) Stop mailman core and maybe other mailman services too. 2) Assuming the two shunted messages are still in Mailman's shunt queue, run `mailman unshunt` to unshunt them. If there are more shunted messages, inspect them with `mailman qfile` to see if you want them, They may be spam. 3) Restart your database server. 4) Start Mailman core and any other stopped services. Also, look in the database server logs for any issues. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Extract posts into mbox file

by Abhilash Raj

On Sat, Apr 18, 2020, at 9:45 AM, Mark Sapiro wrote: > On 4/17/20 10:23 PM, Andrew Bernard wrote: > > Where are the posts stored in the database? What tables? How would on go about exporting them into mbox format for the complete set? > > > It depends on which archiver(s) if any are enabled for the list. > > For the prototype archiver, messages are archived in Maildir format, > <https://en.wikipedia.org/wiki/Maildir>, in the directory > var/archives/prototype/<list-address>/ > > For Hyperkitty, messages are stored in the database in the > hyperkitty_email table and non-plain text parts are in the > hyperkitty_attachment table, but you don't need to know that because in > any HyperKitty view, i.e. a message view, a thread view, a threads by > month view ot an all threads view, there is a button to download all the > messages in that view as a gzipped .mbox file. Emails from Hyperkitty are also available via a REST API endpoint. The documentation for it isn't much but you can build URL patterns by looking at: https://lists.mailman3.org/archives/api/ As Mark above mentioned, you are also able to get an mbox file downloaded via API. I wrote a small python utility to download archives from Hyperkitty to a local Maildir: https://gitlab.com/mailman/hksync But it is also possible to sync to a local mbox if need be. The tool just needs to be extended a little. Although, if the need is to *only* have a mbox or maildir, you should avoid having the complicated Hyperkitty setup and instead use the prototype archiver that Mark mentioned above. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 7 months

[MM3-users] Re: installing mailman3 core

by Abhilash Raj

On Fri, May 29, 2020, at 8:36 AM, Mark Sapiro wrote: > On 5/29/20 7:49 AM, Ralf Wiegand wrote: > > https://docs.mailman3.org/en/latest/install/install.html > > > > I was following this "official" page. There is no word on "pip install > > mailman" as an alternate choise? > > > > There is also a reference in regards to "Virtualenv Installation > > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…>, > > recommended for Production" ... why is this recommended? Does the "pip > > install mailmail" install a production environment I can trust? > > > I didn't write that page, but I think it is saying that for production, > installing in a virtualenv is preferred over installing globally, and > not that it is necessarily preferred over installing a Docker container > or a distro package. Should we edit the wording to signify something else? I guess the definition of production varies a lot. While many would prefer distro packages to use in their sites, some others want the latest bug-fixed version. Debian picks up their packages from PyPI too, but they verify the signatures on packages, which `pip` doesn't. So, from a strict security point of view, Debian might be slightly better, but with the lack of a proper Web Of Trust in PyPI, the value of the signature depends on how much you trust my signing key. > > However, if you actually read the Virtualenv Installation document, you > will see under Installing Mailman Core > <https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…> > it says to install Mailman core via `pip install mailman` in the > virtualenv. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 6 months

[MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails - Hyperkitty - CERT Issue

by Willie Castillo

The issue started right after the site's CERT expired. The CERT expired on 7/8/25. This is what's in the log... Jul 16 15:19:45 2025 (3777209) Connection to HyperKitty failed: HTTPSConnectionPool(host='XXX.com', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/urls?mlist=jmats-versions%40XXX.com (Caused by SSLError(SSLCertVerificatio nError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1000)'))) The CERT has been updated but the 7/25 message is not archived still. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, July 28, 2025 8:10 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [NON-INTERNAL] [MM3-users] Re: Missing Archived emails - Hyperkitty - CERT Issue CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 7/28/25 13:07, Willie Castillo wrote: > I tried with a new post and still, not showing the messages from July 25th in the Archive. There must be a way to force the archiving of the messages from July 25th. > > List metrics > > Created at March 25, 2016, 11:15 a.m. > Last post at July 25, 2025, 12:01 p.m. > Digest last sent at July 25, 2025, 12:01 p.m. > Volume 135 Did the new post get archived? If so, why is last post at still July 25, 2025? If no, why not. The post must go to the archiver to cause the queue to be processed. If the post was archived and the July 25 messages are still queued, what's in Mailman's mailman.log. There should be error messages and tracebacks indicating the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://urldefense.us/v3/__https://lists.mailman3.org/mailman3/lists/mailma… Archived at: https://urldefense.us/v3/__https://lists.mailman3.org/archives/list/mailman… This message sent to willie.castillo(a)caemilusa.com

4 months, 2 weeks

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

On 1/8/22 12:31 PM, Michael Heseltine wrote: > Hi Mark, Stephen, > in fact, there isn't anything running on port 8000, even though I added the service description files under "/lib/systemd/system" as detailed in the HowTo. > > Looking at "journalctl -xe", both the "gunicorn" and the "qcluster" service run into errors i don't understand: > > (qcluster) >> Jan 08 21:22:23 lists.mydomain.com systemd[1]: qcluster.service: Start request repeated too quickly. >> Jan 08 21:22:23 lists.mydomain.com systemd[1]: qcluster.service: Failed with result 'exit-code'. >> -- Subject: Unit failed >> -- Defined-By: systemd >> -- Support: http://www.ubuntu.com/support >> -- >> -- The unit qcluster.service has entered the 'failed' state with result 'exit-code'. >> Jan 08 21:22:23 lists.mydomain.com systemd[1]: Failed to start HyperKitty async tasks runner. >> -- Subject: A start job for unit qcluster.service has failed >> -- Defined-By: systemd >> -- Support: http://www.ubuntu.com/support >> -- >> -- A start job for unit qcluster.service has finished with a failure. >> -- >> -- The job identifier is 734836 and the job result is failed. This isn't your immediate problem, but it is an issue. The above isn't too informative. What do you get if you run /opt/mailman/mm/bin/django-admin qcluster manually? > (gunicorn) >> Jan 08 21:24:58 lists.mydomain.com systemd[1]: gunicorn.service: Failed with result 'exit-code'. >> -- Subject: Unit failed >> -- Defined-By: systemd >> -- Support: http://www.ubuntu.com/support >> -- >> -- The unit gunicorn.service has entered the 'failed' state with result 'exit-code'. >> ...skipping... >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/bin/gunicorn", line 14, in> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: sys.exit(gunicorn.app.wsgiapp.run()) >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: WSGIApplication("%(prog)s [OPTIONS] [APP_MODUL> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: super().run() >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: Arbiter(self).run() >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: self.halt(reason=inst.reason, exit_status=inst> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: self.stop() >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: time.sleep(0.1) >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: self.reap_workers() >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: raise HaltServer(reason, self.WORKER_BOOT_ERRO> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: gunicorn.errors.HaltServer: <HaltServer 'Worker fa> >> Jan 08 21:24:58 lists.mydomain.com systemd[1]: gunicorn.service: Main process exited, code=exited, statu> >> -- Subject: Unit process exited >> -- Defined-By: systemd >> -- Support: http://www.ubuntu.com/support >> -- >> -- An ExecStart= process belonging to unit gunicorn.service has exited. >> -- >> -- The process' exit code is 'exited' and its exit status is 1. It would help to see the full traceback, not truncated at the right. You can scroll the display to the right with the right arrow key or just find the messages in /var/log/syslog. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Is there a way of recording bounce messages?

by Mohsen Masoudfar

I'm dealing with the same issue. Upon reviewing the logs, I've noticed a significant number of bounced emails for a particular mailing list. Gmail users have reported not receiving emails. I haven't been able to locate the "munge from" information. My current setup is using Mailman 3.1.1. I read it has been introduced in 3.2. The Question is what to do with Mailman 3.1.1, if the upgrade is not an option. I get in the logs messages like below with several Queue-ids: Sep 25 09:03:55 localhost postfix/smtpd[26692]: 147583E927: client=a14-93.smtp-out.amazonses.com[54.240.14.93] Sep 25 09:03:55 localhost postfix/cleanup[26696]: 147583E927: message-id=<0100018acb94b326-fdf39193-144e-4fdc-8faf-0d3df54eb4ee-000000(a)email.amazonses.com> Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: from=<>, size=24934, nrcpt=1 (queue active) Sep 25 09:03:55 localhost postfix/lmtp[26697]: 147583E927: to=<listname-bounces@servername>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: removed Mohsen ________________________________ From: Andrew Hodgson <andrew(a)hodgson.io> Sent: Friday, September 22, 2023 7:47 AM To: Andrew Hodgson <andrew(a)hodgson.io>; Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Is there a way of recording bounce messages? [EXTERNAL EMAIL] Hi. Seems other people have had this on Office365 when I searched the specific error. I have enabled VERP now on probes and all list messages so lets see if that improves things. Thanks. Andrew. -----Original Message----- From: Andrew Hodgson <andrew(a)hodgson.io> Sent: Friday, September 22, 2023 12:22 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org Subject: [MM3-users] Re: Is there a way of recording bounce messages? Mark Sapiro <mark(a)msapiro.net> wrote: >On 9/21/23 17:30, Thomas Ward wrote: >> >> MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). >> >> If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. >It appears however that Mailman does recognize the DSN returned by MS365 as the user's delivery is being disabled by bounce. The issue is whatever DSN is returned to the list-bounces address is not attached to the notice sent to the list owner about the disable and it should be. Ok guys the plot thickens. Yesterday using the Mailman Shell I unbounced all the users on that list. We had a couple of messages yesterday and I also enabled the From munging for all messages sent to the list partway through those messages coming to the list. This morning we got all Gmail users bounced again, with no NDR attached to the message. However on one of the messages the NDR was attached, and so I'm going to send that to Mark separately. It looks like the NDR included the information for all the bouncing messages though, and that is probably because Mailman sends the messages to all users in one SMTP transaction. The message returned from Google was: user(a)gmail.com 9/22/2023 9:44:55 AM - Server at PAVPR08MB9257.eurprd08.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError' 9/22/2023 9:24:03 AM - Server at gmail-smtp-in.l.google.com (142.250.27.27) returned '421 4.4.2 Connection dropped due to SocketError' Thanks. Andrew. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to andrew(a)hodgson.io _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

2 years, 2 months

[MM3-users] Re: mass subscribers disablement!?

by Christian Stalberg

Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. Is there a way to see via the web GUI which subscribers were disabled? Correspondingly, can I re-enable delivery for them via the web GUI? Thank you in advance. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, October 22, 2021 5:51 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!? On 10/22/21 2:07 PM, Christian Stalberg via Mailman-users wrote: > I added the additional hosts to ALLOWED HOSTS in settings_local.py and > mailman is distributing mail to subscribers again. However, I then > received many emails of valid users subscriptions being disabled. What > would cause that? Did you just upgrade Mailman core from a version <=3.3.0 to one >=3.3.1? If so, see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U 5ZW6X5QLQRXUOMD2DN77CYCOLKVMUXJ/ > Can subscriber management be done via command line? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/do cs/commands.html for description of the available mailman subcommands. If you are interested in re-enabling delivery for members whose delivery is disabled by bounce, you can do this fairly easily in an interactive `mailman shell` session. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/do cs/shell.html Something like the following session: $ bin/mailman shell 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. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... print('Re-enabled delivery for bouncing member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> commit() >>> exit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 1 month

[MM3-users] Re: DMARC Munging

by Allan Hansen

Mark, et al., I have entered a ticket at gitlab. Thanks. Is there a way for me to make this change to the From header munging until it is implemented in the production version? I made MM2 do the munging using such a change on your recommendation and it has worked. Our installation is from source, which might make it possible/easier? I have played a lot with the wrapping option and have come to the conclusion that it will not work. In some cases, the Apple Mail client for the desktop simply did not display the internal message, while iOS worked fine. The header munging is safer. Yours, Allan Hansen allan_hansen(a)icloud.com > On Jan 26, 2020, at 22:32 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 1/26/20 4:43 PM, Allan Hansen wrote: >> All, >> The munged From: header in MM3 still says >> 'name' via ‘listname’ <‘listaddress’> >> This caused me and my subscribers a lot of grief in MM2: >> Some mail clients use the first part up to the From for future key-ahead for new email to ’name’, hiding the address, so what they think is a personal message for ’name’, instead goes to the entire list. Red faces all around. >> Stephen Thurnbull earlier suggested further munging by replacing the list address in the From: header like this: >> 'name' via ‘listname’ <‘whoopsieaddress’> >> Which will return an automated reply explaining the issue. I like this option. How can I get that in? > > > You can file an issue at <https://gitlab.com/mailman/mailman/issues>. That will at least get it on the table, but there are no guarantees as to if/when it would be implemented. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 10 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

I just notice in the webserver logfile, the same request for the same mlist, msgid and key several times per second for about 3 hours now: "GET /archives/api/mailman/urls?mlist=....&msgid=...&key=... HTTP/1.1" 200 105 "-" "python-requests/2.25.0" The request seems to originate from the server where the mailman suite is installed Best Regards,Eric On Sunday, December 13, 2020, 01:54:54 AM GMT+1, Eric Broens via Mailman-users <mailman-users(a)mailman3.org> wrote: The settings - Archiving, are not different from the ones that do show the messages:"Private Archives" selected, and Active archivers "hyperkitty" also selected. I was trying to find out how the hyperkitty page gets the mails from the database, and if I can start from there.Or maybe something is not completely correct in the database tables. Best Regards,Eric On Sunday, December 13, 2020, 01:27:53 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote: > After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. I agree, that won't make the mails available on the webpage. If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still. What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years

[MM3-users] Re: How to fix: [Django] ERROR (EXTERNAL IP)

by Jigme Datse

On Fri, 1 Nov 2024 12:29:56 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/31/24 21:18, Jigme Datse wrote: > > On Thu, 31 Oct 2024 20:07:00 -0700 > > Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> What's in Django's logs? > >> > > > > Attached logs (I hope that works). A couple are currently empty? > > > I suspect the django_q error is because you need to run `django-admin > migrate`[1], but it isn't responsible for your inability to get list > pages. > > Again, what's in Django's logs? These are not the uwsgi logs. If you > don't know where they are, look in your Django settings in the > LOGGING definition for the filename setting for the file handler. > > [1] The actual name of the Django admin command may be > `django-admin`, `python manage.py` or something else depending on how > Mailman web is installed. > Thank you, A couple of things, running django-admin complains about: Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.). which *that* error gets replaced by: django.core.exceptions.ImproperlyConfigured: settings.DATABASES is improperly configured. Please supply the ENGINE value. Check settings documentation for more details. with the command: python venv/lib/python3.12/site-packages/mailman_web/manage.py migrate which *might* be the wrong manage.py but other than the change with the migrate command, without it looks to throw the same output. The Django log was at that time empty it's now attached (larger than I'd like). It does seem like some configuration isn't quite working. Maybe *badly* not working with some change that happened. It's not a huge deal, this is more a "fun project" for me. This part of it isn't so much fun.

1 year, 1 month

[MM3-users] Re: Upgrade

by Darren Smith

Nice...spoke too soon. Mailman info works, but when attempting to start mailman I'm now getting this: Traceback (most recent call last): File "/opt/mailman3/conda/bin/mailman", line 11, in <module> sys.exit(main()) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 676, in main _verify_python3_env() File "/opt/mailman3/conda/lib/python3.6/site-packages/click/_unicodefun.py", line 118, in _verify_python3_env 'for mitigation steps.' + extra) RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult http://click.pocoo.org/python3/for mitigation steps. This system lists a couple of UTF-8 supporting locales that you can pick from. The following suitable locales where discovered: aa_DJ.utf8, aa_ER.utf8, aa_ET.utf8, (followed by a bijillion others) -Darren On Mon, Apr 16, 2018 at 11:25 AM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > Boy howdy did that work... > > Thanks! > > > On Mon, Apr 16, 2018 at 11:22 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 04/16/2018 10:12 AM, Darren Smith wrote: >> >> > "/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/ >> engine/strategies.py", >> > line 160, in create >> > engineclass.__name__)) >> > TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), >> > using configuration PGDialect_psycopg2/QueuePool/Engine. Please check >> that >> > the keyword arguments are appropriate for this combination of >> components." >> > >> > Anyone able to point me where to go to look for a solution for this? >> >> >> You need to update SQLAlchemy to >= 1.2 for this, but there is another >> issue that requires at least 1.2.3 (current is 1.2.6) >> >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > >

7 years, 7 months

[MM3-users] Re: Messages attached to probe messages

by Mark Sapiro

On 7/12/22 12:36 AM, Bjoern Franke via Mailman-users wrote: > Hi, > > some time ago I started a discussion where I wrongly assumed that probe > messages were sent accidentally from example.com > > Some digging showed now that the sender of the probe messages are > correct, but the attached messages seem to be wrong. > > An attached example for bouncing messages was: > > From: Mailman <mailman(a)example.com> > To: Mailman Bounces <mailman-bounces(a)example.com> > Subject: SMTP Delivery Failure > Message-ID: <165577237837.35.8042057157021349872@mailman-core> > Date: Tue, 21 Jun 2022 00:46:18 +0000 > Message-ID-Hash: TOJ7WDT3TXWOEHZB4USRUOPZUW7BEATI > X-Message-ID-Hash: TOJ7WDT3TXWOEHZB4USRUOPZUW7BEATI > > Mail to bjo(a)schafweide.org failed at outgoing SMTP > > Error code: 554 > Error message: b'5.7.1 Spam message rejected' That's a fake DSN created by Mailman's outgoing runner. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoi…. There will be nothing in Mailman's smtp.log regarding receipt of this message because this message is not received via SMTP, but see below. It is created when the outgoing runner gets a 5xx refusal and the runner calls the bounce processor directly with this fake DSN to process this refusal as a bounce. > I took a look into the logs and found no example.com, but: > > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) handling connection > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'LHLO mail.ffnw.de' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'MAIL > FROM:<yzvotmm(a)forestanes.mom> SIZE=293338' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) sender: > yzvotmm(a)forestanes.mom > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'RCPT > TO:<vorstand(a)lists.ffnw.de>' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) recip: > vorstand(a)lists.ffnw.de > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'DATA' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'QUIT' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) connection lost > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) Connection lost during > _handle_client() The above is the receipt of the post whose delivery to some recipients failed. > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > response exception: (554, b'5.7.1 Spam message rejected') > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > response exception: (554, b'5.7.1 Spam message rejected') > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> smtp to > vorstand(a)lists.ffnw.de for 6 recips, completed in 0.7157599925994873 > seconds > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> post to > vorstand(a)lists.ffnw.de from vorstand(a)lists.ffnw.de, 294362 bytes, 6 > failures > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to foo(a)stadel.info failed with code 554, b'5.7.1 Spam message > rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to abc(a)ffnw.de failed with code 554, b'5.7.1 Spam message > rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to def(a)ffnw.de failed with code 554, b'5.7.1 Spam message > rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to xyz(a)ffnw.de failed with code 554, b'5.7.1 Spam message > rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to bjo(a)schafweide.org failed with code 554, b'5.7.1 Spam > message rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to blabla(a)osnabrueck.freifunk.net failed with code 554, b'5.7.1 > Spam message rejected' > Jun 21 00:46:49 2022 (35) > <165577240769.30.3077851374384466408@mailman-core> smtp to > vorstand(a)lists.ffnw.de for 1 recips, completed in 0.5507137775421143 > seconds The various messages like > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to bjo(a)schafweide.org failed with code 554, b'5.7.1 Spam > message rejected' are logged by the outgoing runner when it receives a 5xx reject and creates a bounce with a fake DSN. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: To what extent can mailman 3 handle images and html?

by Mark Sapiro

On 10/20/19 2:11 AM, Paul Arenson wrote: > Hi > > The other day I attempted to send a message from my mail client (Apple computer, Mail program, html--well, what they call Rich Text). While a user was able to send a message previously that contained an image, I was unsuccessful. It should be the same as Mailman 2.1. What are your settings for content filtering. In Postorius the only thing exposed are Settings -> Alter Messages -> Filter content, Collapse alternatives and Convert html to plaintext. If this Filter content Yes, content is filtered according to the other two settings and MIME parts may be removed according to the list settings filter_types, pass_types, filter_extensions and pass_extensions. These settings exist in core, but aren't exposed in Postorius. For a new MM3 list these settings are empty, but for a list imported from Mailman 2.1, they are set according to the corresponding MM 2.1 settings. I suspect in your case the issue is Filter content and Collapse alternatives are both Yes. Or perhaps the issue is HyperKitty's rendering of the message > As well, links were weird. > > LINKS > ===== > Because My wordpress often has a Japanese URL and they can become very long, I tried both the URL as is and embedded (made a clickable html link). > > URL > === > So while I typed > https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis.... > > It came out double as > > https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... > <https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... > (The full link was truncated with ... at the end, and the link appeared twice with the second instance preceded by "">") I think the doubling is due to your MUA. The truncation of the displayed link in HyperKitty is expected, but the link itself should reference the full URL. > The embedded one did not come out embedded buy showed the text like this: > Alternate link: 多摩川河川敷に男性の遺体、増水した川に流されたか > <https://www.tokyoprogressive.org/%e5%a4%9a%e6%91%a9%e5%b7%9d%e6%b2%b3%e5%... What do these look like in the message received from thge list as opposed to HyperKitty? > QUESTION 1: Is there a preferred way to write links, or will there always be problems with the mail clients? > (Even the web archive shows this problem though): > > https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… See what this looks like at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > See the top item Homeless man drowns in river during Typhoon and what I mean. The first of those 3 links actually works. The other two don't work because the Japanese characters have been encoded as hex values by your MUA (which may be HyperKitty if you are posting via HyperKitty. To answer your question, you can just type the URL as you did above in your thread link, or you can surround it with angle brackets as I did in my message link. If you don't use angle brackets, it should be surrounded by whitespace to avoid ambiguity. See <https://www.rfc-editor.org/rfc/rfc3986#appendix-C> > IMAGE > No image appears though one was added inline. > > And, as I said, a user was previously able to add one. I do not know how she did it. I also posted it to my web site instead of the newsletter for unrelated reasons. But there was an image (Originally got a warning the message was held because the attachment or something). > > So are there guidelines one whether/how to attach an image so that it makes it? Are you posting via email or HyperKitty? If by email, I suspect the issue is Filter content and Collapse alternatives are both Yes. If by HyperKitty you can only post plain text. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

DEBUG var True: [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10950 [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css HTTP/1.1" 200 156657 DEBUG var False: [02/Aug/2017 16:46:46] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10001 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/d6cbfc945441.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 [02/Aug/2017 16:46:46] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > find them: > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > > > > > Should I run any command to activate the CACHE dir? > > > You need to ensure you have a working sass compiler. As I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >, > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > Then you need to run commands like > > django-admin collectstatic --clear > django-admin compress > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 4 months

[MM3-users] Re: Bulk delivery status change?

by Stephen Daniel

OK. Ran the script. No errors while running it, but when I look at the users through Postorius GUI, they still show as 'Disabled by Bounces' ?? On Sun, Nov 10, 2024 at 11:42 AM Stephen Daniel <swd(a)pobox.com> wrote: > Thanks all! I will use these pronto. > > On Sun, Nov 10, 2024 at 11:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: >> > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: >> > >> >> Mistakes were made, and for while every single outbound email bounced. >> >> I've fixed the mistakes, but now in my largest and most active email >> list, >> >> every single user's delivery status is "Disabled by Bounces". >> >> >> >> Is there a way to bulk fix this? Or do I have to go into each user, >> one at >> >> a time, and fix them? >> > >> > Please see this thread: >> > >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> The script in that post does all lists. For a single list see >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> but note that the command line >> ``` >> $ shell -l list(a)example.com >> ``` >> should be >> ``` >> $ mailman shell -l list(a)example.com >> ``` >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> Archived at: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> This message sent to swd(a)pobox.com >> >

1 year, 1 month

[MM3-users] Re: where to configure max_days_to_hold on MM3 GUI interface?

by Shashikanth Komandoor

Hello Mark, Thanks for helping me for moving ahead in my project. Troubling you again, I would like to put another request at you. As per your suggestion, I am trying to configure my list configuration through REST API for specially the parameter like max_days_to_hold as it is not available through interface and I am following the official links of mailman 3 i.e https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/listconf.html But I am getting "name is not defined" sort of errors as below: *>>> dump_json('http://localhost:9001/3.0/lists/ <http://localhost:9001/3.0/lists/>','ant(a)example.com/config <http://ant@example.com/config>',dict(display_name='My List'),'PATCH')Traceback (most recent call last): File "<stdin>", line 1, in <module>NameError: name 'dump_json' is not defined>>>* Actually I am new to REST API but hope this is the only issue that is preventing me to go ahead. Could you please help me by saying how should I handle this so that I should be able to configure *max_days_to_hold* of a list or multiple ? On Wed, Jan 29, 2020 at 11:20 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/28/20 8:42 PM, Shashikanth Komandoor wrote: > > > > But I could see that parameter value configurable on MM2 GUI > > interface in General Options but I don't see the same on the MM3 GUI > > interface. > > > There are many core settings not (yet) exposed in Postorius. > max_days_to_hold. is one of them. It can be set via `mailman shell` or > via the REST API > < > https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/rest.html#re… > >. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 10 months

[MM3-users] Re: Problem creating list members using REST API

by Stephen Daniel

I can give you a program written in Go. Would that be helpful? On Tue, Jan 18, 2022 at 6:49 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/18/22 2:11 PM, Stephen Daniel wrote: > > The REST API documentation is a bit informal. As someone who is not > > familiar with mailman, and who doesn't know python, they are a bit of a > > slog. > > > Agreed. I guess we sort of assume that people dealing directly with the > REST API are familiar with both. > > > > It might be worth seeing if the code can be enhanced to allow the boolean > > values to be sent in using JSON booleans as well as JSON strings. > > > I think here we only have to deal with the REST API because other uses > of as_boolean are all on strings that come from config files. We can't > modify as_boolean directly, as it is part of a third party dependency > and is intended to be used with config files, not JSON objects, but I > think something like this will do it. > ``` > --- a/src/mailman/rest/helpers.py > +++ b/src/mailman/rest/helpers.py > @@ -249,6 +249,8 @@ class GetterSetter: > """ > if self.decoder is None: > return value > + if self.decoder is as_boolean and isinstance(value, bool): > + return value > return self.decoder(value) > > > > ``` > Perhaps you could try to test that. > > I just created https://gitlab.com/mailman/mailman/-/issues/970 for this. > It would help me in fixing this if you could provide a small piece of > your code that throws the error. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 10 months

[MM3-users] Re: Emergency Moderation

by Abhilash Raj

On Sun, May 24, 2020, at 11:34 AM, Mark Sapiro wrote: > On 5/24/20 10:59 AM, Allan Hansen wrote: > > In the MM3 settings there is an option to ‘Hold for moderation’ when members or non-members post to the list. > > I use that for the same cases where in MM2 I switched a list to ‘Emergency Moderation.’ > > > If you imported your MM 2.1 lists with `mailman import21`, `emergency` > was set appropriately for the imported list and should be working to > hold posts regardless of other settings. > > > > My own current top-of-the-list issues: > > > > A bug: Moderators can’t see/edit the list of members even when allowed to by list setting. > > The visibility issue is <https://gitlab.com/mailman/postorius/-/issues/369>. > > Editing membership beyond what could be done via the admindb interface > (i.e. clearing a moderated poster's mod flag) was never allowed for a > moderator in MM 2.1. > > In MM 3, a moderator can set a member's moderation when handling a held > post. Do you think a non-owner moderator should be able to make other > changes to a member? > > > > A feature request: Member changing email address on all lists he/she belongs to, without involving moderators. > > > This is <https://gitlab.com/mailman/postorius/-/issues/399> and we're > working on it. Another way to achieve this request, without needing the Preferred Address route is to simply Patch the Member resource with the new address, which wouldn't trigger the full subscription workflow and would have the extra advantage of having the same delivery_mode and preferences. I created: https://gitlab.com/mailman/postorius/-/issues/425 to track this issue. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 6 months

[MM3-users] Re: installing mailman3 core

by Mark Sapiro

On 5/29/20 7:41 AM, Ralf Wiegand wrote: > Mark - What is the difference between to two install methods? What are > my pros and cons? Installing from the GitLab repository will get the latest development version, however, you can also install from this repository via pip and pick a tag or commit to install <https://pip.pypa.io/en/stable/reference/pip_install/#git> `pip install mailman3` will install the latest released version. As of this writing, that's 3.3.1, so ``` pip install mailman3 ``` and ``` pip install git+https://gitlab.com/mailman/mailman@3.3.1 ``` should give the same result although the former installs from PyPI and the latter from GitLab. The advantage to installing the latest version from GitLab is you get features and fixes that haven't been released yet. The disadvantage is you might get new bugs, although the servers that support this list and all the Mailman 3 @python.org lists are generally running the latest GitLab versions, so any serious issues will be quickly found and fixed. > I have been using this: > >>>>> > > |# Note: if we are using a dedicated postgresql database server, all > postgresql changes need to be done on the actual postgresql server.| > |>>>| > |sudo yum install postgresql-server postgresql-contrib| > |sudo postgresql-setup initdb| > |sudo systemctl start postgresql| > |sudo systemctl enable postgresql| > |sudo -u postgres psql -c ||"SELECT version();"| > |sudo useradd -c ||"Mailman User"| |-s /bin/bash -m mailman| > |sudo -u postgres create role mailman;| > |sudo -u postgres createdb -O $USER mailman| > |sudo -u postgres psql -c ||"grant all privileges on database mailman to > mailman;"| > |sudo -u postgres psql -c ||"ALTER ROLE mailman WITH PASSWORD > 'secret123';"| > |sudo -u postgres psql -c ||"ALTER ROLE "||mailman||" WITH LOGIN;"| > |sudo echo ||"listen_addresses = '*' "| |>> > /var/lib/pgsql/10/data/postgresql.conf| > |sudo echo ||"# The user mailman will be able to access all databases > from a trusted location (any) without a password"| |>> > /var/lib/pgsql/data/pg_hba.conf| > |sudo echo ||"host all mailman 0.0.0.0/0 > trust"| |>> /var/lib/pgsql/data/pg_hba.conf| > |sudo systemctl restart postgresql| > |sudo ss -nlt | grep 5432| > |<<<| > |sudo yum install python36* --skip-broken -y| > |# check make sure you have both versions| > |sudo python --version| > |Python 2.7.5| > |sudo python3 --version| > |Python 3.6.8| > |sudo pip3 install psycopg2-binary| > |sudo chown mailman.mailman /opt/mailman| > |sudo chmod 755 /opt/mailman| > |# NOTE: The first initial mailman3 core setup has to be done manually.| > |# This is a important step to ensure the user "mailman" will run the > actual mailman3 application and not root.| > |# switch to user mailman| > |mailman# cd /opt/mailman| > |mailman# git clone https:||//gitlab.com/mailman/mailman.git| This gets the head of the GitLab master branch. > |mailman# cat <<EOT >> /opt/mailman/mailman/src/mailman/config/mailman.cfg| > |[devmode]| > |enabled: yes| > |recipient: root@localhost| > |[webservice]| > |hostname: localhost| > |port: 8001| > |show_tracebacks: yes| > |use_https: yes| > |[mta]| > |incoming: mailman.mta.postfix.LMTP| > |outgoing: mailman.mta.deliver.deliver| > |lmtp_host: localhost| > |lmtp_port: 8024| > |smtp_host: localhost| > |smtp_port: 25| > |[database]| > |class||: mailman.database.postgresql.PostgreSQLDatabase| > |url: postgres:||//mailman:secret123@<IP-ADDRESS or FQDN>/mailman| > |EOT| > |mailman# python3.6 -m venv venv-3.6| > |>>| > |mailman# source venv-3.6/bin/activate| > |(venv-3.6) [mailman@empire mailman]$ cd mailman| > |(venv-3.6) [mailman@empire mailman]$ python setup.py develop| > |(venv-3.6) [mailman@empire mailman]$ mailman info| > |<<| > | > | > | > | > |So I was told I don't have to do this, I can just simple do (rhel7) > | > |yum install pyhton3| > |pip install mailman| This gets the latest release from PyPI Other than that, you still have to do the configuration and install some dependencies as in the first method. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Log rotation

by Darren Smith

Well, that is certainly a wealth of information from you two, thanks a ton! I've got a few things to try now. I'm going to have to look up the retry runner to see if that might help when we have to shut things down. I'll let you know what I find... On Tue, Apr 10, 2018 at 5:41 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/10/2018 03:39 PM, Abhilash Raj wrote: > > Yes, this is a known thing and the reason for it is that the SIGTERM > isn't delivered till the process wakes up next time. We can have the > process sleep for a smaller amount of time to fix this, but then it would > mean that it will be running much more often. > > > > It is the Retry runner, which has sleep_time set to 15m. I don't know if > you want to retry very often, like 2min or 5min, but you can change it by > adding the following snippet to your mailman.cfg > > > A long time ago (in a galaxy far away) Mailman 2.1 had a global > DELIVERY_RETRY_WAIT setting. This setting had been ineffective for > years, relying instead on the retry runner's sleep time. > > In 2.1.26, for what turned out to be a probably spurious reason, I made > DELIVERY_RETRY_WAIT effective again, although the retry runner still > sleeps for 15 minutes. > > We could implement something similar in MM 3 to allow the retry runner > to have a much shorter sleep time without actually retrying the delivery > that often. The down side of that is even though we aren't retrying > delivery each time the runner wakes up, we are dequeueing and requeueing > the message each time and this would have a file system impact. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 8 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 8 Nov 2021, at 11:11 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: Simon Coggins wrote: > On 7 Nov 2021, at 10:54 am, Mark Sapiro <mark(a)msapiro.netmailto<mailto:mark@msapiro.netmailto>:mark@msapiro.net<mailto:mark@msapiro.net>> wrote: > I wound up taking a different approach. I check for other references to > the message in the message store and only delete the message if there > are none. The fix is at > https://gitlab.com/mailman/mailman/-/merge_requests/932/diffshttps://gitlab…<https://gitlab.com/mailman/mailman/-/merge_requests/932/diffshttps://gitlab…> > Oh nice. That seems like a sensible solution. Thanks for tackling so quickly. I’ll do some testing today and roll it out once testing is complete. I made a small change to defend against 'impossible' situations. See https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs<https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs> Thanks for the heads up. I did a bunch of testing with the original patch and was happy with it so we’re running that in prod now. How far off is 3.3.6? Just working out if I apply this slight change or wait for the full release. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: attachment.png Content-Type: image/png Name: attachment.png Replaced multipart/alternative part with first alternative.

4 years, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Can we modify the docs? Ok, I'm going to add that config to main.cf and test Thank you El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 09:36 AM, Rafael Mora wrote: > > > > Postfix <http://www.postfix.org/>: To setup Postfix, add the following > > configuration to master.cf: > > > > # Support the default VERP delimiter.recipient_delimiter = > > +unknown_local_recipient_reject_code = 550owner_request_special = > > notransport_maps = > > hash:/path-to-mailman/var/data/postfix_lmtplocal_recipient_maps = > > hash:/path-to-mailman/var/data/postfix_lmtprelay_domains = > > hash:/path-to-mailman/var/data/postfix_domains > > > > > > I added that config at the bottom of the master.cf file and did a > 'postfix > > reload' and I got this error message: > > > > [root@localhost ~]# postfix reload > > /usr/sbin/postconf: fatal: file /etc/postfix/master.cf: line 129: bad > field > > count > > postfix/postfix-script: fatal: cannot execute /usr/sbin/postconf! > > > First of all, in a report such as this, it would really help if you > reported what is actually in master.cf in the vicinity of line 129. > > However, that said, the doc is wrong. The lines should be added to > main.cf, not master.cf. See > <https://gitlab.com/mailman/mailman-suite-doc/issues/14>. > > Also, what you post above is quite garbled. It is not clear what you > meant, but the lines to add should be > > > # Support the default VERP delimiter. > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no > transport_maps = > hash:/path-to-mailman/var/data/postfix_lmtp > local_recipient_maps = > hash:/path-to-mailman/var/data/postfix_lmtp > relay_domains = > hash:/path-to-mailman/var/data/postfix_domains > > > and should not be wrapped as in your post. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 4 months

[MM3-users] Re: Badsignature on uwsgi-error.log

by Helio Loureiro

Hi Mark, Thanks for your response. I found what the issue was. I actually misspelled hyperkitty as hyPperkitty on the url. So the error on mailman-hyperkitty.cfg was: base_url: http://localhost:8000/hypperkitty/ I moved to: base_url: http://localhost:8000/hyperkitty/ and it was solved. Problem was the wrong link was getting a generic page from Django instead of error. And it was failing to do the parsing probably, which was taking wrongly as key mistake. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Thu, 21 Mar 2024 at 01:13, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/20/24 14:25, Helio Loureiro wrote: > > Hi, > > > > I keep receiving a lot of errors like this: > > > > --- Logging error --- > > Traceback (most recent call last): > ... > > > "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", > > line 55, in unsign > > raise BadSignature('Signature "%s" does not match' % sig) > > django.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" > > does not match > ... > > > > The api_key on mailman-hypperkitty.cfg, SECRET_KEY and > MAILMAN_ARCHIVE_KEY > > on setting.py are the same. > > > Of those three, the api_key on mailman-hypperkitty.cfg and > MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a Django > thing and has nothing to do with the others. See > https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key > > If you changed it, that's the issue. If you know what it was previously, > you could set the previous value in SECRET_KEY_FALLBACKS, see > https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to helio(a)loureiro.eng.br >

1 year, 8 months

[MM3-users] Re: Hyperkitty issue(s)

by Mark Sapiro

On 5/27/20 2:24 PM, Bryan Loniewski wrote: > Hello -- > > I'm stuck trying to integrate Hyperkitty. I see the following errors in mailman.log and mailmansuite.log respectively: > > <snipped> > [2020-05-27 16:42:11 -0400] [5140] [ERROR] Error handling request /3.1/lists/bry_test4.lists-test.rutgers.edu/archivers > Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 134, in handle > self.handle_request(listener, req, client, addr) > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 175, in handle_request > respiter = self.wsgi(environ, resp.start_response) > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 274, in falcon.api.API.__call__ > File "falcon/api.py", line 269, in falcon.api.API.__call__ > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 406, in on_get > for archiver in archiver_set.archivers > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 407, in <dictcomp> > if archiver.system_archiver.is_enabled> File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/model/mailinglist.py", line 587, in system_archiver > raise AssertionError('Archiver not found: {}'.format(self.name)) > AssertionError: Archiver not found: hyperkitty I've been looking at the code, and I think this can occur if the mailing list has a configured archiver which is no longer known in mailman.config.config.archivers. I.e., the list has hyperkitty as an archiver, but hyperkitty is no longer configured as an archiver in Mailman. > and > > <snipped> > Traceback (most recent call last): ... > KeyError: 'file' This traceback is useless. All it says is a Django logging error occurred in trying to log the real exception. The interesting one is immediately before this in the log. > Note that I've kinda followed the Virtualenv route along with using Mark's helpful webpage re: his experiences. > > Some relevant? config files... > > mailman.cfg: > > <snip> > [archiver.prototype] > enable: yes > > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg > <snip> That looks good. > mailman-hyperkitty.cfg: > [general] > base_url: https://a_real_domain/mm3/hyperkitty > api_key: <movealong> > > I can provide additional conf file setups if warranted? I am curious (and perhaps this is in fact the issue) why when I run mailman conf I don't see the archiver.hyperkittty section even though its in the mailman.cfg file? I don't either and I don't know why., For example on lists.mailman3.org ``` mailman conf|grep [[]archiver [archiver.mail_archive] class: mailman.archiving.mailarchive.MailArchive [archiver.mail_archive] clobber_date: maybe [archiver.mail_archive] clobber_skew: 1d [archiver.mail_archive] configuration: python:mailman.config.mail_archive [archiver.mail_archive] enable: no [archiver.mhonarc] class: mailman.archiving.mhonarc.MHonArc [archiver.mhonarc] clobber_date: maybe [archiver.mhonarc] clobber_skew: 1d [archiver.mhonarc] configuration: python:mailman.config.mhonarc [archiver.mhonarc] enable: no [archiver.prototype] class: mailman.archiving.prototype.Prototype [archiver.prototype] clobber_date: maybe [archiver.prototype] clobber_skew: 1d [archiver.prototype] configuration: changeme [archiver.prototype] enable: yes ``` doesn't show hyperkitty and neither does ``` mailman conf -k enable [archiver.mail_archive] enable: no [archiver.mhonarc] enable: no [archiver.prototype] enable: yes ``` but ``` /mailman conf -s archiver.hyperkitty [archiver.hyperkitty] class: mailman_hyperkitty.Archiver [archiver.hyperkitty] clobber_date: maybe [archiver.hyperkitty] clobber_skew: 1d [archiver.hyperkitty] configuration: /opt/mailman/mm/deployment/mailman-hyperkitty.cfg [archiver.hyperkitty] enable: yes ``` So I don't think this per se is the issue. > Any suggestions? Try ``` mailman shell May 28 00:35:47 2020 (15162) patched 1/1 modules (sqlalchemy) 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. >>> from mailman.config import config >>> list(config.archivers) [<mailman.archiving.mhonarc.MHonArc object at 0x7fdd9ccff6a0>, <mailman.archiving.mailarchive.MailArchive object at 0x7fdd9ccffac8>, <mailman.archiving.prototype.Prototype object at 0x7fdd9ccffb38>, <mailman_hyperkitty.Archiver object at 0x7fdd9ccffe80>] >>> ``` Does yours list hyperkitty? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Help on removing moderators

by Mark Sapiro

On 3/4/20 6:26 AM, sean_sullivan(a)rhoworld.com wrote: > > However, if I try and bring that in as a function that can be used with mailman withlist, I am consistently getting errors, and being that I am not very experienced in python, it has me scratching my head to say the least. > > from mailmanclient import Client You do not need to use mailmanclient with shell/withlist. mailmanclient is Python bindings for REST API functions. When you are under `mailman shell` (or `mailman withlist`, a synonym for `mailman shell`) you are working within mailman core and it's just extra baggage to use mailmanclient/REST. > from mailman.interfaces.member import MemberRole, AlreadySubscribedError > from mailman.testing.helpers import subscribe Here again, mailman.testing.helpers is to provide certain functions used in doctests. You don't need that with mailman shell. > addresses = ['test1(a)example.com', 'test2(a)example.com', 'test3(a)example.com'] > > client = Client('http://localhost:8001/3.1', 'restadmin', 'restpass') > > def set_owners(mlist): > > for email_addr in addresses: > try: > member = subscribe(mlist, '', email=email_addr, role=MemberRole.owner ) See below. > print (member) > except AlreadySubscribedError as err: > print (err) > > def remove(mlist): > my_list = client.get_list(mlist) > # print(my_list.fqdn_listname) > # for email_addr in addresses: > # my_list.remove_owner(email_addr) > > The errors I am getting are: > > ./bin/mailman withlist -r set_owners.remove -l it-test-b(a)lists.rhoworld.com > Traceback (most recent call last): > File "./bin/mailman", line 8, in <module> > sys.exit(main()) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 764, in __call__ > return self.main(*args, **kwargs) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 717, in main > rv = self.invoke(ctx) > File "/opt/mailman3/lib/python3.6/site-packages/mailman/bin/mailman.py", line 68, in invoke > return super().invoke(ctx) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 1137, in invoke > return _process_result(sub_ctx.command.invoke(sub_ctx)) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 956, in invoke > return ctx.invoke(self.callback, **ctx.params) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 555, in invoke > return callback(*args, **kwargs) > File "/opt/mailman3/lib/python3.6/site-packages/click/decorators.py", line 17, in new_func > return f(get_current_context(), *args, **kwargs) > File "/opt/mailman3/lib/python3.6/site-packages/mailman/commands/cli_withlist.py", line 293, in shell > r = call_name(dotted_name, m, *run_args) > File "/opt/mailman3/lib/python3.6/site-packages/mailman/utilities/modules.py", line 70, in call_name > return named_callable(*args, **kws) > File "/opt/mailman3/bin/set_owners.py", line 24, in remove > my_list = client.get_list(mlist) > File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/client.py", line 347, in get_list > 'lists/{0}'.format(fqdn_listname)) > File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call > error_msg, response, None) > urllib.error.HTTPError: HTTP Error 404: 404 Not Found > > > So, I am wondering, is it possible to do something like this or am I completely misunderstanding the documentation, and why do I get a 404 here, when in the shell everything works as expected. I know I must be missing something, but cannot for the life of me figure out what that is. Any help would be greatly appreciated. Here's what you want with addresses as arguments so you can save this as set_owners.py and run things like. $ bin/mailman shell --run set_owners -l list.example.com \ test1(a)example.com test2(a)example.com test3(a)example.com' and $ bin/mailman shell --run set_owners.remove -l list.example.com \ test1(a)example.com test2(a)example.com test3(a)example.com' > from mailman.app.membership import add_member, delete_member > from mailman.interfaces.member import MemberRole, AlreadySubscribedError > from mailman.interfaces.subscriptions import RequestRecord > > def set_owners(mlist, *addresses): > for email_addr in addresses: > try: > record = RequestRecord(email_addr) > member = add_member(mlist, record, role=MemberRole.owner) > print (member) > except AlreadySubscribedError as err: > print (err) > > def remove(mlist, *addresses): > for owner in mlist.owners.members: > if owner.address.email in addresses: > owner.unsubscribe() -- 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: Debian Package Install - Ownership and Permissions

by Dave Hall

On Fri, Apr 7, 2023 at 5:47 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/7/23 13:43, Odhiambo Washington wrote: > > On Fri, Apr 7, 2023 at 8:09 PM Andreas Schamanek < > > as2020+github(a)fam.tuwien.ac.at> wrote: > >> > >> I am running MM2 und 3 in parallel without problems, I do have a > >> special MTA setup though (Sendmail). Can't speak for Postfix etc.. > >> > > > > Your setup can handle list1(a)domain1.name via MM2 and MM3, > simultaneously, > > right? :-) > > It is possible to have an MM2 `list1` and an MM3 `list1(a)domain1.name` > simultaneously on the same server, but what is the MTA going to do with > incoming mail to `list1(a)domain1.name`. I suppose it could deliver it to > both MM2 and MM3, but I don't see any practical use case for this. > > I run Exim4 on my servers so I can comment from this perspective. Exim had a concept of 'routers' which are stacked and processed in order of appearance. There is a router for MM2 and one for MM3 that pick off incoming mail based on whether the email address matches a list name. WIth this setup, you could have the same list name in both MM2 and MM3, but it would go to whichever router appears first and the second one would never see it. So I have the MM3 router first, and as I migrate my lists from MM3 the email for those lists no longer gets to MM2. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to kdhall(a)binghamton.edu -- Dave Hall Binghamton University kdhall(a)binghamton.edu 607-760-2328 (Cell) 607-777-4641 (Office)

2 years, 8 months

[MM3-users] Re: Broken web UI after upgrade

by Odhiambo Washington

On Sat, Dec 17, 2022 at 9:22 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/16/22 21:47, Odhiambo Washington wrote: > > On Fri, Dec 16, 2022 at 11:17 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> I suggest you run > >> ``` > >> django-admin collectstatic --clear --noinput --verbosity 2 > >> > > > > The output is here: https://pastebin.ubuntu.com/p/qkR2bDYv3G/ > > > > > > > >> django-admin compress --verbosity 2 > >> > > > > The output of the above is here: > https://pastebin.ubuntu.com/p/T7jQPrs3JX/ > > > Those look OK. > > I suggest you look at ownership and permissions. > I doubt it's about ownership and permissions given the fact that I have even done "chown -R mailman.mailman /opt/mailman" just for the kicks. > > ``` > find /opt/mailman/mm/static/ -not -user mailman > find /opt/mailman/mm/static/ -not -perm -u+rw > find /opt/mailman/mm/static/ -type d -not -perm -u+x > ``` > and the same on > /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ > root@list:/home/wash# find /opt/mailman/mm/static/ -not -user mailman root@list:/home/wash# find /opt/mailman/mm/static/ -not -perm -u+rw root@list:/home/wash# find /opt/mailman/mm/static/ -type d -not -perm -u+x root@list:/home/wash# find /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ -not -user mailman root@list:/home/wash# find /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ -not -perm -u+rw root@list:/home/wash# find /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ -type d -not -perm -u+x root@list:/home/wash# Yielded nothing - perms and ownership are all okay. > If the above doesn't reveal anything substantial, then let me know and I > > can bump up the verbosity. > > > I don't know if --verbosity 3 will reveal anything or not. You could try. > I did check, but the output looks the same as when it's set to 2. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

[MM3-users] Re: Starting new thread in Postorius -> disappears

by Thor Atle Rustad

I go with the workaround from Cameron Smith: sudo docker-compose exec mailman-web ./manage.py runjobs yearly makes messages appear However, there was "something" else that caused my messages not only NOT to show up in Hyperkitty, but also caused them not to be sent in the first place. I believe the reason was wrong subdomain in SERVE_FROM_DOMAIN in docker-compose.yaml. 2017-11-22 0:38 GMT+01:00 Mark Sapiro <mark(a)msapiro.net>: > On 11/21/2017 01:53 AM, Thor Atle Rustad wrote: > > I have had this working before, so I guess it's a simple setup error. > > > > When I send a message from the Postorius interface, it is neither sent > out > > or stored. I briefly see this message: "Your reply has been sent and is > > being processed.", and then nothing happens. > > > I assume you mean HyperKitty. Postorius has no facility for posting > messages to a list. > > > > I have installed maxking's docker-mailman and copied my old setup with > > basic stuff like passwords and such. The only new thing is that I'm now > > running in userspace by putting in /etc/subuid and subguid: > > > When you post from HyperKitty, HyperKitty creates a > django.core.mail.EmailMessage() instance and calls it's send() method > which causes Django to send the message to the list address. It then has > to be received and processed by Mailman the same as any email post > before it will appear in the archive. > > Are you running with DEBUG = True. If so, Hyperkitty won't send the mail. > > If DEBUG = False and normal posting is working, perhaps there is some > Postfix issue in delivery of the message from Django to Mailman. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years

[MM3-users] Re: at the finish line of mailman3 docker, but can't sign in.

by Abhilash Raj

On Fri, Jul 30, 2021, at 11:01 AM, Mark Sapiro wrote: > On 7/30/21 10:47 AM, bob B wrote: > > > > Basically once I have docker installed, and mailman3 up and no lists are available, How do I setup or/and sign in as admin? > > > I'm not sure what the actual command would be do run the django-admin > interface in the docker image, but from below, it looks like it's > `mailman-web`. Run `mailman-web createsuperuser` to create an admin ID. Container images don't support mailman-web command yet, it has to be ported to use the mailman-web command. You can run commands with `docker exec -it mailman-web ./manage.py <command>`. For creating the superuser, you can run[1] [1]: https://asynchronous.in/docker-mailman/web.html#running Although, if you have set the MAILMAN_ADMIN_EMAIL, that command should have already run in the setup process. You want to figure out the email sending process. Although, you can create a second admin and set the password for it and login using that using the command mentioned at [1]. > > > > Also In docker how can I test sending mail? the command "mailman-web sendtestemail youremailid@domain" from the mailman-web container does not work. You can run docker exec -it mailman-web ./manage.py sendtestemail youremailid@domain > > This command tries to send the mail via SMTP to localhost port 25. > > > > How can I make sure my containers can send and receive mail? > > > The MTA should be listening on port 25 and that need to be visible in > the mailman-web container. See > <https://asynchronous.in/docker-mailman/#setting-up-your-mta> > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 4 months

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/17/19 6:39 PM, paul(a)arenson.org wrote: > > A) Thoughts before summarizing tests. > 1) I had originally thought of making archives only for subscribers to give them the benefit of posting from the archives directly and being able to find stuff more like a forum (email is always hard to follow). Anyone logged in to an account can post from Hyperkitty. Their post is treated the same as if they posted by email. > 2) But in retrospect it seems people can get an idea what the list is about from free access. So that is now what I have. OK > 3) On the other hand, it is a bit confusing that a non member can post from the archives without realizing that they need to register, with my settings I can moderate and decide if I want to add him or her to the list based on whether that is spam or not. So ok. A non-member is a non-member. A post from a non-member is handled according to "Default action to take when a non-member posts to the list" unless that non-member has a Moderation action other than List Default. > B) THE TESTS > I was testing too many variables so, to simplify things, I made my settings as follows > > 1) Subscription—> Confirm > > 2) Message Acceptance—> Default processing (so only members may post) > > 3) Testing Procesure > I added people three ways—> To do that I created 3 unique addresses to see if they can send and receive by email. > > > 3a) subscribe without creating an account—from here (bottom) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > > 3b) Subscription / Unsubscription from same page, navigate to Login and again navigate to signup > Comment 1: Confusing because even after creating an account, they are not subscribed to the list. Maybe it makes sense if a person has many lists, but I only have this one. It does not say clearly that one has to subscribe after creating an account. I understand it's not totally explicit, but it says "To subscribe or unsubscribe from this list, please log in first. If you have not previously logged in, you may need to set up an account with the appropriate email address." To me the implication is once you have created an account, you have to come back, log in and subscribe. What do you want it to say? > Comment 2: The other thing is that it does not show my domain but that of mailman3.emwd.com <http://mailman3.emwd.com/>. Talk to Brian (emwd) > 3c) Mass Subscribe by me. Which is what I intend for my 600 users from another list company. > Comment This worked fine. > > > C) Summary > 1) I have been thinking of having an account as a good way to get users used to using the archives as a way to confirm current and past topics (as opposed to keeping track by email. But it seems I need to tell them to BOTH subscribe AND create an account. Am I thinking about it the wrong way? That's correct. They need an account and they need to subscribe that account to the list. > 2) When a person wants to unsubscribe, they go to discuss-request(a)list.tokyoprogressive.org <mailto:discuss-request@list.tokyoprogressive.org> with subject bline help. > > a) Isn’t there a better way to unsubscribe by email? email to discuss-leave(a)list.tokyoprogressive.org (or discuss-unsubscribe(a)list.tokyoprogressive.org) Or you can login, go to https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… and click the big red unsubscribe button. > b) And how about a way to remove their account itself? Log in and click the dropdown at the upper right, select Account and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/ and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/delete -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: How to use the "recipient_delimiter" postfix parameter with Mailman3?

by Pierre Malard

Ok, thanks for the documentation. But as Mailman uses this functionality for its own processing of emails, if I leave it to be used for another processing, Mailman will no longer work correctly... Ok, that means I'm going to forbid the use of the escape character when processing mailing lists. > Le 12 avr. 2022 à 16:37, Mark Sapiro <mark(a)msapiro.net> a écrit : > > On 4/12/22 01:56, Pierre Malard via Mailman-users wrote: >> Hi, >> We are using the « recipient_delimiter » parameter with our Postfix server as « _ ». >> Visibly, Mailman have it’s own mail configuration because it doesn’t work know. >> Is it a way to conserv this Postfix functionality? > > > Mailman by default expects the recipient delimiter to be `+`. There are various settings in the [mta] section of mailman.cfg that allow you to change this. These are documented along with default settings at lines 812 - 898 of https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Pierre Malard Responsable architectures système GeoSUD IRD - UMR Espace-Dev - UMS CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « Les utopies ne sont souvent que des vérités prématurées » Alphonse de Lamartine |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 8 months

[MM3-users] Re: Apache Conf

by Abhilash Raj

On Fri, Oct 19, 2018, at 12:17 PM, Thomas G wrote: > Hi tried both. > > Same result. > > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) > Gecko/20100101 Firefox/60.0" And, you have verified that the files exist at `/opt/mailman/static` on your host? > > > Le ven. 19 oct. 2018 à 18:59, Mark Sapiro <mark(a)msapiro.net> a écrit : > > > On 10/19/18 10:29 AM, Guiseppin Thomas wrote: > > > Hi, > > > Currently, I use a nginx configuration for mailman. It's work perfectly. > > > > > > I tried to do the same with Apache, but the statics files are not > > > delivered (404). > > ... > > > <VirtualHost *:80> > > > ServerName mailing.ddd.fr > > > > > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log > > > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined > > > > > > <Location /static/> > > > Alias "/opt/mailman/static/" > > > </Location> > > > > > > <Location /> > > > ProxyPass http://localhost:8000/ > > > ProxyPassReverse http://localhost:8000/ > > > ProxyPreserveHost On > > > </Location> > > > </VirtualHost>/ > > > > > > In Apache, location > > <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not > > appropriate for resources in the file system. > > > > Try > > > > Alias /static/ /opt/mailman/static/ > > > > not within a location block. > > > > -- > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj (maxking)

7 years, 1 month

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< mailman-users(a)mailman3.org>) escribió: > I think you're confused. > > You already have mail.labbrands.com set up as the MX record for > labbrands.com. And it has an A record with the same address as your > webserver. > I'm working with the hostgator mailserver, we are not running a local mailserver. As suggested I added an A record like this: [image: image.png] Is it correct? is it redirecting to my Ip so I can redirect it to my postfix/mm3 server? > > So if you're getting e-mail on that domain, there's another e-mail > server running on that IP address. You can't have 2 servers on port > 25. In that case, as has been noted before, you'll need to setup a > relay in that server, not a firewall redirect. Depending on your MTA, > you would need to relay to your internal server. And make sure your > firewall setup allows your MTA to do this. > > We can see it's EXIM: > > telnet mail.labbrands.com 25 > Trying 192.185.51.89... > Connected to mail.labbrands.com (192.185.51.89). > Escape character is '^]'. > help > 220-gator4137.hostgator.com ESMTP Exim 4.87 #1 Thu, 03 Aug 2017 15:47:48 > -0500 > 220-We do not authorize the use of this system to transport unsolicited, > 220 and/or bulk e-mail. > 214-Commands supported: > 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP > quit > 221 gator4137.hostgator.com closing connection > Connection closed by foreign host. > > Or, consolidate all your e-mail to one server - which is a lot easier to > manage unless you have a really big operation. Postfix is probably the > right choice, but requires more setup. > > Although Mailman3 configuration is not well documented (as you've > discovered), you may want to get help from someone with more general > network and mail experience. You're now into territory that is, as > Simon indicated, not Mailman-specific. > > On 03-Aug-17 16:28, Rafael Mora wrote: > > El jue., 3 ago. 2017 a las 15:26, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > > > >> On 08/03/2017 01:22 PM, Rafael Mora wrote: > >>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) > >> escribió: > >>>> You need to forward port 25 for SMTP mail delivery and if you want the > >>>> web UI (Postorius and HyperKitty) accessible from the outside, port 80 > >>>> for http and/or port 443 for https > >>>> < > >>>> > >> > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >>>>> . > >>> I mean for incoming mail redirected from my hostgator hosting, because > >> when > >>> I suscribe an email address MM3 sends a confirmation email, so I have > to > >>> reply to be suscribed to the list. > >> > >> As I said, for mail delivery you need to forward port 25 to the Mailman > >> server. > >> > > Ok so I'll redirect in my zentyal firewall the port 25 to my local > centos7 > > with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > > > > > >> > >> -- > >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > >> San Francisco Bay Area, California better use your sense - B. Dylan > >> _______________________________________________ > >> Mailman-users mailing list > >> mailman-users(a)mailman3.org > >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >> > > -- > This communication may not represent my employer's views, > if any, on the matters discussed. > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 4 months

[MM3-users] Re: Mailman, etc. upgrade woes and persistent bugs

by Mark Sapiro

On 2/11/21 10:22 PM, hansen(a)rc.org wrote: > I just had my Mailman suite upgraded. When it got started, I starting receiving messages that hundreds of subscribers to the lists had been disables, including several of the list moderators. This version started supporting bounce processing, but how in the world was this upgrade allowed to act on bounces that were being collected PRIOR to enabling bounce processing?? I'm sorry about that. It's too late now, but the avoidance is discussed at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. > I got many angry emails, messages and phone calls asking what was going on, as they were bona fide list members. I was very surprised myself. > > I then looked at several of the disabled accounts, but the subscription info page in Postorius had no information about whether an account was enabled or disabled. Why is this not displayed???. The members can't see if their account is enabled. Is this another example of the disconnect between Mailman and Postorius? If the user has a Django account, she can see all that info at (e.g. for this list) <https://lists.mailman3.org/mailman3/accounts/subscriptions/> She gets there from `Mailman settings` in the dropdown under her user name. She can also get there via the `Manage Subscription` button on the list's Info page. That takes her to `List-based preferences` for the list. Any setting not selected there is inherited from the Address-based preferences or Global Mailman preferences > Further, even after the upgrade, the moderators still cannot access the list memberships even though all the lists are set to allow that. I would have asked the moderators to do this if this access bug had been fixed, but they can't get there. You've already reported this at <https://gitlab.com/mailman/postorius/-/issues/462>, and it's been previously reported at <https://gitlab.com/mailman/postorius/-/issues/369>. > As a result of these bugs, after consulting with Brian, who helped with the upgrade, I spent many hours re-enabling the several hundred accounts that had been disabled. I had to go through each email notification to find the address of a disabled account, then find the list, then the member, in Postorius, and finally enable the account (at which time Postorius DID show the enabled status). I'm sorry you had to go through this. The potential issue and the avoidances should be better documented. Unfortunately, they aren't. > Please, can the next upgrade include these very basic fixes/enhancements, which I requested a long time ago: > > a. The ability of moderators to see the list membership (a bug). As I note above, this is a known issue. We are a small project with very feew core developers, all of whom are volunteers. There is a merge request at <https://gitlab.com/mailman/postorius/-/merge_requests/423> which purports to fix <https://gitlab.com/mailman/postorius/-/issues/369>, but as you can see from the comment thread, it is not complete and the author has apparently disappeared. If you would like to take it over and address the deficiencies, we would welcome that. > b. The ability of members to change their addresses for all lists they are subscribed to. Users can add addresses to their account and can then change their subscribed address at (again, e.g. for this list) <https://lists.mailman3.org/mailman3/accounts/list-options/mailman-users.mai…> (Get there via the `Manage Subscription` button on the list's Info page.) If one is subscribed to lists via their `primary` address, one can go to `E-mail Addresses` in their account settings and make a new address `primary` and that will change all their subscriptions. > and further, now: > > c. That when members go to look at their subscription info, they can actually see the settings. They can if they go to `Mailman settings` in the dropdown or the `Manage Subscription` button on the list's Info page and look at all the tabs. -- 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: [EXTERNAL] Re: Database deadlock when trying to delete a member.

by Simon Coggins

After making that change and doing some testing. So far I’ve not had any issues and the sync are working as expected now. -Simon From: Mark Sapiro <mark(a)msapiro.net> Date: Wednesday, 24 March 2021 at 4:10 am To: "mailman-users(a)mailman3.org" <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member. On 3/22/21 9:53 PM, Simon Coggins wrote: > Ok after bit tracking I’ve worked out that the bouncer is dangling transactions when it’s sending warning messages. When https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> is called and it get to update last_warn_sent it does the following in the DB: > > 2021-03-23 14:42:50.622 AEST [11693] LOG: statement: UPDATE member SET last_warning_sent='2021-03-23T04:42:50.622015'::timestamp, total_warnings_sent=1 WHERE member.id = 169331 > > But it never COMMITs this transaction. So all write operations are now hung waiting for the transction to be closed as the member record has been modified. As a test I added config.db.commit() after https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> and restarted. And my mailman syncmembers worked perfectly and I didn’t have any hangs it correctly removed everyone it should have. In the database logs I can see the COMMIT. > > I’m pretty sure this is not the right spot for a config.db.commit() but hopefully this helps point to what might be going wrong. Thank you for all the research on this. It is extremely helpful. Instead of adding a commit after line 277 please try adding the @transactional decorator to the send_warnings_and_remove method at line 210 @transactional @dbconnection def send_warnings_and_remove(self, store): I think that is the proper fix. Let us know if that works. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

4 years, 8 months

[MM3-users] Re: Apple Mail encoding again

by Rainer Herbst

Dear all, as the original poster, I have asked the user to send a test mail through our mailman3 system (docker image maxking/mailman-core:0.4.2) and the mail passed. The user is now on Apple Mail 16, maybe that does the trick. Please find enclosed the anonymizied mail source. Best regards and thanks for caring even if the problems seems to affect only a small number of users! Rainer On Fr, 15 Apr 2022 09:03:41 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/14/22 21:33, Stephen J. Turnbull wrote: >> >> Whether we *want* to do that depends on how much trouble that causes >> for our main constituency (list and site admins), and whether we can >> provide discoverable documentation of the problem. My take is that >> this seems to be an extremely rare problem, and at least some MUAs >>are >> able to read the message, so we should let it through. > >First, we are not silently dropping this message. We are rejecting it >at LMTP time so the sender should be notified. > > Then the broader question is should we accept all messages with >defects, almost all of which are spam, or only certain defects and >which ones. > > I note that Apple has now released Mail 16 so maybe they've fixed >this. My macs are still on Big Sur, so I can't test this. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. >Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 ----------------------------------------------------------------------------------------------- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/x-pkcs7-signature Name: smime.p7s

3 years, 7 months

[MM3-users] Re: Uncaught runner exception

by Wolfgang Bock

Hello Mark, thanks for your hint. Postfix is runnig as mta on my machine. I tested port 25 with swaks ->mail to user on server: localhost port 25 -> everything fine Mailman is configured with localhost for incoming and outgoing mails. After stopping mailman3, deleting all files in the queue directories, restart mailman3 I sent a test-mail /var/log/mailman3/mailman.log Apr 07 12:08:23 2020 (28198) Master started Apr 07 12:08:24 2020 (28206) out runner started. Apr 07 12:08:24 2020 (28202) command runner started. Apr 07 12:08:24 2020 (28203) in runner started. Apr 07 12:08:24 2020 (28200) archive runner started. Apr 07 12:08:24 2020 (28201) bounces runner started. Apr 07 12:08:24 2020 (28210) retry runner started. Apr 07 12:08:25 2020 (28208) rest runner started. Apr 07 12:08:25 2020 (28212) digest runner started. Apr 07 12:08:25 2020 (28205) nntp runner started. Apr 07 12:08:26 2020 (28211) virgin runner started. Apr 07 12:08:26 2020 (28207) pipeline runner started. Apr 07 12:08:26 2020 (28204) lmtp runner started. Apr 07 12:09:19 2020 (28203) ACCEPT: <000f01d60cc4$96c9a8d0$c45cfa70$@[domain]> Apr 07 12:09:21 2020 (28206) Cannot connect to SMTP server localhost on port 25 I have no idea what to do for solving my problems. Regards from Hamburg Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Montag, 6. April 2020 23:50 An: Wolfgang Bock <mailinglisten(a)wbock.de> Betreff: Re: [MM3-users] Re: Uncaught runner exception On 4/6/20 2:44 PM, Wolfgang Bock via Mailman-users wrote: > Thank you Steven for your reply! > > I Set smtp_server to port 25 and got a "Cannot connect ro SMTP Server > on port 25", the former error message didn't show again. > > As I see port 25 is reseved for postfix. So I have to fiddle out how > mailman3 could also use this port for sending mails out. .... You need an MTA for Mailman to deliver its mail to. Normally this will be Postfix, sendmail, Exim, etc running on localhost and listening on port 25. Do you have such an MTA running on localhost? Note, Mailman does not directly send mail to end recipients. It only delivers mail to an outgoing MTA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Setting up on ubuntu server 22.04

by Kyriakos Terzopoulos

Thanks Mark, That seemed to work: (venv) mailman@hestia:~/venv$ mailman info GNU Mailman 3.3.8 (Tom Sawyer) Python 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:XXXXXXXXXXXXX>@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: XXXXX:XXXXXX Now, off to handle other issues like nginx, exim4, etc. I will search or create another thread for this if I'm stuck. It would be nice to somehow update the documentation for https://docs.mailman3.org/en/latest/install/virtualenv.html. Thank you all for your efforts. *Kyriakos* On Wed, 4 Oct 2023 at 03:44, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/3/23 06:00, Kyriakos Terzopoulos wrote: > > > > However, I cannot find the mailman/setup.py anywhere in order to patch > it, > > since the installation was done through pip from here: > > > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > > > Maybe I can try upgrading python from 3.10 to 3.11 and re-install > > > Upgrading Python won't help. There is currently an incompatibility issue > when following > https://docs.mailman3.org/en/latest/install/virtualenv.html because that > doc is based on the head of the GitLab branch, but `pip install > mailman3` installs the 3.3.8 released version of core and the latest > 6.1.0 version of importlib_resources and these are incompatible. > > There are two ways to fix this. > > The easy way is to downgrade importlib_resources in your venv with > ``` > pip install importlib_resources\<6.0 > ``` > The slightly more complex way is to upgrade mailman core to 3.3.9b1 from > GitLab with > ``` > pip install -U git+https://gitlab.com/mailman/mailman.git > ``` > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to kyriakos.terzopoulos(a)gmail.com >

2 years, 2 months

[MM3-users] Re: UnpicklingError on mailman lists command

by Bryan Loniewski

$ /opt/mailman/mm/bin/mailman version GNU Mailman 3.3.2 (Tom Sawyer) So, I'm running > 3.2. Any other advice on debugging the truncated data? ________________________ Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator ________________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, August 2, 2021 10:06 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: UnpicklingError on mailman lists command On 8/2/21 4:15 PM, Bryan Loniewski wrote: > Hi all -- > > $ /opt/mailman/mm/bin/mailman lists > Traceback (most recent call last): ... > File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/commands/cli_lists.py", line 78, in lists > for mlist in list_manager.mailing_lists: > File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/model/listmanager.py", line 100, in mailing_lists > MailingList._list_id).all() > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3246, in all > return list(self) > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 101, in instances > cursor.close() > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 69, in __exit__ > exc_value, with_traceback=exc_tb, > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 178, in raise_ > raise exception > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in instances > rows = [proc(row) for row in fetch] > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in <listcomp> > rows = [proc(row) for row in fetch] > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 589, in _instance > populators, > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 726, in _populate_full > dict_[key] = getter(row) > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/sql/sqltypes.py", line 1708, in process > return loads(value) > _pickle.UnpicklingError: pickle data was truncated This is probably https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co… which was fixed in Mailman 3.2.0 by https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…. What version are you running? If your version is 3.2.0 or greater, it could be one of the other issues with MySQL/MariaDB truncating data. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

4 years, 4 months

[MM3-users] Re: Rejecting held emails

by Darren Smith

Mark, You're quite right, I meant Discard. Thanks for the clarification. I hope to be able to pull a fix in for this in the near future. :) -Darren On Thu, Apr 26, 2018 at 10:14 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/26/2018 08:43 AM, Darren Smith wrote: > > > > We recently had a phishing message make it through our spam filters and > > arrive at a mailing list. The good news is that since it was not from a > > list member it was in the held message queue. > > > > I was able to find the message in the var/messages directory by searching > > for a keyword in the subject. However, after rejecting the message from > > Postorius, the message doesn't seem to be removed from the var/messages > > directory. > > > Do you mean Reject and not Discard? Phishing/Spam should never be > "rejected" for backscatter reasons. Reject should only be used for > somehow inappropriate posts from known people. > > > > Is this expected behavior? I know that infosec people won't be too happy > > about a phishing email sitting around on our disk. (Infosec guys are > > notoriously paranoid. :) ) > > > > Is there some sort of cleanup process that would remove these messages? > If > > not, does this pose an issue where over time disk usage will creep up? > This > > could be a pretty significant problem if that is the case. > > > It's not the behavior I would "expect", but it is the way it currently > works, and yes, all your concerns are valid. This is > <https://gitlab.com/mailman/mailman/issues/257> which I just edited to > note that in addition to not removing the pending db entry, the message > isn't removed either. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 7 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Kelly Close

Thanks for those clarifications Mark. -- K. Kelly Close, P. E. Senior Project Manager | Water Rights Engineer | Technology Team Lead Office: 303-455-9589 Direct: 303-867-7665 Kelly.Close(a)LREwater.com LREWATER.COM 1221 Auraria Parkway Denver, CO 80204 **CONFIDENTIALITY NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you. On Tue, Jun 16, 2020, 7:51 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/16/20 5:03 PM, kelly.close(a)lrewater.com wrote: > > I resolved this myself with a search that turned up a 2018 post from > Mark that suggested typing "mailman aliases" to create the > hash/alias/lookup table/file things in /var/lib/mailman3/data (that's where > they are on Ubuntu 18.04). I looked in that folder and sure enough it was > empty so I typed "sudo mailman aliases" which did indeed create the 4 > things that needed to be there: > > postfix_domans > > postfix_domains.db > > postfix_lmtp > > postfix_lmtp.db > > > > But, they were owned by root:root and everything else under that > /ver/lib/mailman3 folder is owned by "list" so I took a guess changed the > ownership on the 4 files to list:list. > > Because that's how you ran it. Run > > sudo -u list mailman aliases. > > > > Seems to have worked! I was perplexed about why I had to do this though > because these were created automatically last time I did this, but I > figured that out too. > > > Current `mailman start` should create the aliases. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

5 years, 5 months

[MM3-users] Re: Postorius password resets

by Andrew Hodgson

Mark Sapiro wrote: >On 10/15/20 9:24 PM, Andrew Hodgson wrote: >> Mark Sapiro wrote: >> >>> On 10/14/20 11:11 AM, Andrew Hodgson wrote: >> >>>> I am having an issue with our system where password resets are giving the users an email with a http://localhost:8000 URL. I have made sure settings in settings_local.py (and even settings.py) are as follows: >>>> >>>> POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.hodgsonfamily.org' >> >>> This is not relevant. >> >> Does it need resetting back to http://localhost:8000? Not if it works. Most likely either one is OK, but localhost:8000 avoids a DNS lookup an proxying through the web server. Ok I have reset this value now. >>>> However emails are still coming through with the wrong URL. >> >>> I'm not sure offhand, but it's either domains in Postorius or sites in the django admin UI. >> >> I've checked both and cannot see any errors (I just have the one site lists.hodgsonfamily.org) and nothing is empty which seems as though it needs filling in. >What's in `sites` and what's in `Mail domains` in the django admin UI https://lists.hodgsonfamily.org/admin/django_mailman3/maildomain/: <Mailman domain lists.hodgsonfamily.org> https://lists.hodgsonfamily.org/admin/django_mailman3/maildomain/1/change/ Site: lists.hodgsonfamily.org Mail domain: lists.hodgsonfamily.org https://lists.hodgsonfamily.org/admin/sites/site/1/change/ Domain name and display name: lists.hodgsonfamily.org >and what's in Web Host in the Postorius domains view - in particular, if you have Postorius 1.3.3, what's the SITE_ID, and what's SITE_ID in settings(_local).py. https://lists.hodgsonfamily.org/postorius/domains/ Mail Host Description Alias Domain Web Host lists.hodgsonfamily.org lists.hodgsonfamily.org (lists.hodgsonfamily.org) SITE_ID = 1 Site ID is 1 in settings.py (not overridden in settings_local.py) > Also, when you go to the archive UI, whats the domain at the top left of the pages. Lists.hodgsonfamily.org I have overridden the following settings relating to this in settings_local.py: USE_X_FORWARDED_HOST = True ALLOWED_HOSTS = [ 'localhost', 'lists.hodgsonfamily.org' ] Settings.py is from the latest commit from the Mailman Suite Gitlab project. Thanks for helping me with this. Andrew.

5 years, 1 month

[MM3-users] Re: Template Ignored?

by Stephen Daniel

Fixed the POSTORIUS_TEMPLATE_BASE_URL. Doesn't fix the issue. I've been playing with wget, and no matter what I put, I keep getting a 404 error. So: this works: wget -O wget.out --user restadmin --password restpass ' http://localhost:8001/3.1/lists/list.example.com' but this does not (404 error): wget -O wget.out --user restadmin --password restpass ' http://localhost:8001/3.1/templates/list/list.example.com/list:user:notice:… ' Is there a way to list all templates? Or all templates for a list? On Thu, Feb 17, 2022 at 12:34 PM Stephen Daniel <swd(a)pobox.com> wrote: > That pulls a 404 error. Thanks for the hint. I will investigate. > > On Thu, Feb 17, 2022 at 11:49 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 2/17/22 08:04, Stephen Daniel wrote: >> > Mailman3 people -- >> > >> > I created a new list, and used postorius to create a template for " >> > list:user:notice:welcome". I then used the mass subscription feature to >> > add myself to the list, having checked "pre-confirmed", "pre-approved", >> and >> > "pre-verified". >> > >> > I received a welcome message that appears to be the default welcome >> > message. It certainly wasn't what I put into my template. >> > >> > Any suggestions on how I get mailman to use my template? Things I >> might be >> > doing wrong? >> >> >> What is your setting for POSTORIUS_TEMPLATE_BASE_URL? If you create a >> full URL by appending >> `/api/templates/list/list.example.com/list:user:notice:welcome` >> <http://list.example.com/list:user:notice:welcome> to that >> where `list.example.com` is the actual list_id of your list, and go to >> that URL, what do you get? >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> >

3 years, 9 months

[MM3-users] Re: hyperkitty failed to create a thread

by Abhilash Raj

On Thu, Feb 14, 2019, at 11:51 AM, Danil Smirnov wrote: > Thank you very much for the quick fix, Mark and Abhilash! > > Abhilash, could you include the fix into the "latest" version of > mailman-web container please? They are nightly builds, if the fix was merged and the CI went through, they should already be in there. > > Btw I wasn't able to find a changelog of Mailman docker images anywhere and > 'Releases' page in Github is quite outdated too... Is there any other > place I should check? I have admittedly been too busy to write release notes, but the recent releases have seen not too much changes other than version bumps for the included Mailman packages. > > Danil > > вт, 12 февр. 2019 г., 4:06 Mark Sapiro <mark(a)msapiro.net>: > > > On 2/11/19 9:47 AM, Danil Smirnov wrote: > > > > > > What could be a reason of HyperKitty failing to create a thread from > > > chained emails? > > > > > > For example, see "RECENTLY ACTIVE DISCUSSIONS" on page > > > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/ > > > > > > "Openvpn and Network mapping" discussion displayed as five threads > > instead > > > of only one... > > > > > > Any ideas how to improve HyperKitty ability to detect threaded messages? > > > > > > Thanks for the report. > > > > The MR at <https://gitlab.com/mailman/hyperkitty/merge_requests/125> > > will fix this. > > > > -- > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 9 months

[MM3-users] Re: Notifying owners of membership changes but not moderators

by Perry Kollmorgen

Thanks Mark. So, I have python scripts which do the adding of nonmembers and moderators. For the nonmember script I needed to add something so that the nonmembers can send, i.e the moderaction_action = 'defer' This is my code for nonmembers: mailing_list.add_role('nonmember', nonmember.email, display_name=nonmember.display_name) list_member = mailing_list.get_nonmember(nonmember.email) list_member.moderation_action = 'defer' list_member.save() For the code for moderators it currently only adds them: mailing_list.add_moderator(moderator.email, display_name=moderator.display_name) Would I need to add something similar which sets a delivery_status for the moderator added ? Cheers, Perry ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, 27 November 2024 2:16 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Notifying owners of membership changes but not moderators On 11/26/24 4:54 PM, Perry Kollmorgen wrote: > > Is there any way to have these only for Owners ? No. Essentially all admin notices are sent to LISTNAME-owner@DOMAIN and that in turn resends to owners and moderators. There are no controls to restrict this to only owners and not moderators, however it doesn't send to those with delivery disabled, so you could do something like this in `mailman shell` ``` $ mailman shell -l LIST_ID 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_ID mailing list >>> for moderator in m.moderators.members: ... moderator.preferences.delivery_status = DeliveryStatus.by_moderator ... >>> commit() ``` This will not affect the delivery status of the user's role as list member. This is not available in Postorius and also, the moderator can't set the delivery_status for their moderator role either, only for their member role. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to pcjkollmorgen(a)hotmail.com

1 year

[MM3-users] Re: MM3 templates

by Odhiambo Washington

On Thu, Feb 16, 2023 at 9:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/15/23 23:42, Odhiambo Washington wrote: > > On Thu, Feb 16, 2023 at 10:26 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > > In my case, I had the exact same files in the two paths and the > > list:user:action:subscribe.txt was still not used in my tests. > > Why? > > > I don't know why? What's the content of the template table in the database? > ``` > SELECT * FROM template; > ``` > root@localhost [mailmansuite]> SELECT * FROM template; Empty set (0.03 sec) > I have now created the directory: > > mkdir -p /opt/mailman/mm/var/templates/domains/lists.kictanet.or.ke/en/ > > And I have placed the same files in there. Gearing up for a test to see > if > > the template will be used this time around. > > > That's just wasting space. If you're putting the exact same templates in > site/, domains/ and lists/, you might just as well delete the ones in > domains/ and lists/ and Mailman will use the ones from site/. > Well, space is cheap these days. > >> 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. > >> > > > > It wasn't a template per se. It was the regular nondigest msg_footer from > > MM2. > > > import21 imports the nondigest msg_footer, makes certain adjustments for > Mailman3 compatibility and stores it as a template in the > var/templates/lists/<list-id>/<lc>/ directory, however if it was the MM > 2.1 default msg_footer, it won't be stored as a template and the MM3 > default list:member:generic:footer template will be used. > And what I am seeing is that the default list:member:generic:footer template is what is showing up in all posts. To my chagrin though. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Ryan McClung

I do see the output of the script and it shows the mailing lists being created. If you put "${VARIABLE}"@domain.com it outputs correctly. Also, to that end, the output of lists changes depending on which directory I am in which makes 0 sense. On Tue, Jul 31, 2018 at 3:27 PM Ryan McClung <rmcclung(a)afilias.info> wrote: > I do see the output of the script and it shows the mailing lists being > created. If you put "${VARIABLE}"@domain.com it outputs correctly. > > On Tue, Jul 31, 2018 at 3:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 07/31/2018 07:04 AM, Ryan McClung wrote: >> > Scratch that. Ran with the corrected script and getting the following: >> > [root@mailman3(stg) archives]# mailman lists >> > No matching mailing lists found >> > >> > Any thoughts? >> >> This >> >> > for DIR in $DIRS; do mailman create "${DIR}"; mailman import21 "${DIR}"@ >> afilias.info "${DIR}"/config.pck; >> >> is still wrong. The list name for mailman create needs to be fully >> qualified as in >> >> > for DIR in $DIRS; do mailman create ${DIR}(a)afilias.info; mailman >> import21 ${DIR}(a)afilias.info ${DIR}/config.pck; >> >> (Do you look at the output from your script?) >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > > -- > > Ryan McClung > Systems Administrator @ Afilias Canada > A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 > <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> > W. www.afilias.info > T. +1.416.646.3304 x4186 > -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

7 years, 4 months

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Abhilash Raj

On Wed, 9 Aug 2017 15:45:48 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/09/2017 02:35 PM, Abhilash Raj wrote: > > Hi, > > > > On Wed, 9 Aug 2017 13:42:20 -0700 > > Mark Sapiro <mark(a)msapiro.net> wrote: > [...] > > > > I wasn't aware that Core needed cron jobs too, is that true for 3.1 release as > > well? > > > It's only that one and whether it's needed or not depends on list > configuration. The list has attributes digest_send_periodic and > digest_size_threshold. When a post is received it is added to the list's > digest mbox, and if that causes the size of the mbox to reach > digest_size_threshold K bytes, a digest is sent. Additionally, if > digest_send_periodic is true, a digest is sent periodically whether or > not it has reached digest_size_threshold. > > However, the sending of periodic digests depends on cron running > something periodically to actually trigger the sending. Can this be done using the REST API? If not, maybe we should do that so that Postorius can take of the periodic tasks? I am thinking mostly about the container images because the mailman-core container runs nothing else other than Core. I'd have to another cron for this which isn't a lot of overhead but since mailman-web container already has periodic tasks, it would be great if I could trigger it from there. > > Note: I've just looked at the code and there seems to be an issue with > using 'mailman digests --send' to send the periodic digests. It appears > that if a list's digest mbox has any messages, 'mailman digests --send' > will send a digest even if digest_send_periodic is false. I've just > reported <https://gitlab.com/mailman/mailman/issues/384> for this issue. Also, it seems that Postorius doesn't have any way to set `digest_send_periodic` and only has a setting to set the max_threshold for the digest. I opened another issue (https://gitlab.com/mailman/postorius/issues/211) to add this feature. -- thanks, Abhilash Raj

8 years, 4 months

[MM3-users] Re: Missing whitespace in postfix_vmap after mailman genaliases

by Wolfgang Bock

Dear Mark, I am running mailman3 (version 3.2.1) on debian buster. Created yesterday a Test mailinglist and faced the same problem in postmapping postfix_vmap again. Is the debian buster version of mailman3 not uptodate?? Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Sonntag, 20. September 2020 00:43 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Missing whitespace in postfix_vmap after mailman genaliases On 9/19/20 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > after creating a new list I got the following errormessage: > > mailman aliases -> postmap: warning: > /var/lib/mailman3/data/postfix_vmap, > line 17: expected format: key whitespace value > > /var/lib/mailman3/data/postfix_vmap > # AUTOMATICALLY GENERATED BY MAILMAN ON 2020-09-19 07:44:34 .... > xxxxxxxxxxx(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-bounces(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-bounces(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-confirm(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-confirm(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-join(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-join(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-leave(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-leave(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-owner(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-owner(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-request(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-request(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-subscribe(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-subscribe(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-unsubscribe(a)lists.xxxxxxxxxxxxxxxx.dexxxxxxxxxxx-unsubscri > be@xxx > xxxxxxxxxx.de > > The last line in the left part contains 48 chars. It isn't clear what you really have, but I'm guessing that in each case except the last, what you show as two lines is actually a single line with whitespace between and the last line has no whitespace. This is <https://gitlab.com/mailman/mailman/-/issues/651>, fixed in Mailman 3.3.1 by <https://gitlab.com/mailman/mailman/-/merge_requests/576>. > I solved the problem by adding a whitespathe last line has no > whitespace.ce in the last line and I made a new postmap for postfix_vmap. > > But it would be better to solve the problem by changing the genaliases > process in the next update. Already fixed and released in the last update. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 2 months

[MM3-users] Re: Using the API to create nonmembers with a different moderation action than the list default

by Perry Kollmorgen

Oh great, that will be very useful when it is ready. It is easy for standard users to maintain a list which can be used also for sending access to other lists, particularly when nested. This along with the extra URL variables for use in templates look handy also. I already have added some URLs to our templates manually however if we expand to other domains it would save on some updating of templates. Usually, I would look to merge in useful PRs to my own branch of the source code used in production however with the use of docker this time around it isn't quite as easy. Likely not too difficult, but it might be good to wait too. Regards, Perry ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, June 8, 2024 3:59:46 AM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Using the API to create nonmembers with a different moderation action than the list default On 6/6/24 11:36 PM, Perry Kollmorgen wrote: > Hi, > > My next challenge is to script the setup of a bunch of nonmembers who have a moderation action of accept (or maybe defer) whilst the list itself has a nonmember action of hold. > > This is due to a relatively heavy use of nested lists, and have a fair number of people who might possibly send to all lists, and are important enough they wouldn't want to be manually allowed each time even if it only once. Note that beginning with Mailman 3.3.10 (not yet released) you can put things like @list2@example.com in accept_these_nonmembers of list1(a)example.com to accept posts from non_members who are members of list2(a)example.com. See https://gitlab.com/mailman/mailman/-/merge_requests/1154 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to pcjkollmorgen(a)hotmail.com

1 year, 6 months

[MM3-users] Re: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Shashikanth Komandoor

Thank you Mark. What you have said is right.. I found a list with two "hyperkitty" records in the listarchiver in the database. I had removed the list and recreated it and now I found it is working fine. The recreated list is having only one record. After searching the links you provided I found there is just a work around but not the precaution to be taken for not getting the duplicate record. Can you say what might be the reason for this duplication? If I need to provide any details, please let me know. On Fri, Jul 24, 2020 at 11:50 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/24/20 10:34 AM, Shashikanth Komandoor wrote: > > Hi Team, > > > > Today, I found an error message like "Multiple rows were found > > for one_or_none()" when a hold message is approved for a list. Until > > yesterday the mails were accepted and delivered fine. > > > We have seen this issue before. See > <https://gitlab.com/mailman/mailman/-/issues/657>. There are also > multiple threads on it in the archive, e.g., > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > >. > > We don't know how it happens, but the issue is that the `listarchiver` > table in the database has multiple `mhonarc` entries for the same > `mailing_list_id`. > > You can see the problem with the query > > select * from listarchiver where name = 'mhonarc'; > > There will be two entries with the same `mailing_list_id` and deleting > one of them will fix this and you can run `mailman unshunt` to reprocess > the shunted messages. > > The above referenced issue contains a script that can be run to remove > the extra entry. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 4 months

[MM3-users] Re: Mailman 3, postfix domains, and postgresql cannot authenticate user

by Keith Christian

Odhiambo, Yes, trying to. Mark, I'll review your suggestions. Thanks. On Wed, Jul 3, 2024, 12:52 Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/3/24 09:22, Keith Christian via Mailman-users wrote: > > > --------------------------------------------------------------------------- > > First issue:Postfix v3.5.8 on RHEL 8. > > The below is from journalctl -xe: > > > --------------------------------------------------------------------------- > > Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or > > directory > > > > I manually created the var_dir: /opt/mailman3/mm/var directory > > specified in the mailman.cfg file. > > How do I find out how to populate the postfix_domains.db files, and > > the postfix_lmtp.db file? > > > The `mailman aliases` command generates the postfix_domains and > postfix_lmtp files and calls the configured postmap_command (default > /usr/sbin/postmap) to create the .db files. `mailman start` also > generates these files by default. > > > > > --------------------------------------------------------------------------- > > Second issue: Postgresql authentication. > > PostgreSQL v10.23. > > > --------------------------------------------------------------------------- > > I have this in the active mailman3.cfg file, where xxxxxxxxxx is the > > same complex password in the mailman3 config file: > > url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 > > > I don't think you should have two /mailman3 at the end > > the form is `postgresql://user:password@host:port/database_name` The > default port is 5432. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to keith1christian(a)gmail.com >

1 year, 5 months

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Eric Broens

Hi Mark, I can't find any log entry which indicate a problem with this subscription request. The _request table does not contain a request for the specific mailinglist, but I am not sure if subscription requests are included in this table. The token is found in the pended table: +-----+------------------------------------------+---------------------+ | id | token | expiration_date | +-----+------------------------------------------+---------------------+ | 115 | 4d6b4b11266c7332684c5a492eb3f92c531f761b | 2031-01-04 16:17:38 | +-----+------------------------------------------+---------------------+ These are the relevant entries in the pendedkeyvalue table: +------+--------------+-------------------------------------+-----------+ | id | key | value | pended_id | +------+--------------+-------------------------------------+-----------+ | 1130 | type | subscription | 115 | | 1131 | list_id | "********************" | 115 | | 1132 | email | "***********************@*********" | 115 | | 1133 | display_name | "" | 115 | | 1134 | when | "2021-01-06T16:17:38" | 115 | | 1135 | token_owner | "moderator" | 115 | +------+--------------+-------------------------------------+-----------+ Can I workaround this problem for this specific subscriber by adding entries in the _request table, and if so what do I need to add? Thanks in advance, Eric On Friday, January 15, 2021, 11:42:47 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 1/14/21 3:43 PM, Eric Broens via Mailman-users wrote: > Hi Mark, > The link that shows the subscription request pending approval is as follows: 'https://<host_url>/postorius/lists/<listname>.<domain>/subscription_requests' > > The link behind the accept button is as follows. 'https://<host_url>/postorius/lists/<listname>.<domain>/handle_subscription_request/4d6b4b11266c7332684c5a492eb3f92c531f761b/accept' > > I have checked if there is already a subscription with that email address, but that's not the case. I don't know why that would 404 unless the token 4d6b4b11266c7332684c5a492eb3f92c531f761b didn't exist, but since it came from a "current" view, it should be good. I have seen occasional issues where two moderators attempt to handle the same request in close succession - i.e. both get the pending request and try to handle it and the second fails because the request is gone, but that appears not to be the case here. You might check the web server logs, the Django log and Mailman's logs to see if there is any more of a clue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 10 months

[MM3-users] Re: Help with fresh debian install

by Mark Sapiro

On 10/3/19 5:17 PM, Mark Dadgar wrote: > > I brought up a fresh install of Mailman3 via the current Debian package alongside my current 2.1 setup (installed and updated from source since 2002) on Ubuntu 18.04 LTS. > > Importing lists from 2.1 has been a real problem. > > I am trying to import a list with no archives to keep it simple while I prove out the process. If I run the mailman import21 comment as my user, I get the following errors: > > — > mark@mail:/tmp$ mailman import21 announce(a)pdc-racing.net ./announce-config.pck > Traceback (most recent call last): > File "/usr/bin/mailman", line 11, in <module> > load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() > File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in main > initialize(config_path) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 189, in initialize > initialize_2(propagate_logs=propagate_logs) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 152, in initialize_2 > mailman.core.logging.initialize(propagate_logs) > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 157, in initialize > _init_logger(propagate, sub_name, log, logger_config) > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 110, in _init_logger > handler = ReopenableFileHandler(sub_name, path_abs) > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 50, in __init__ > self._stream = self._open() > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 53, in _open > return codecs.open(self.filename, 'a', 'utf-8') > File "/usr/lib/python3.6/codecs.py", line 897, in open > file = builtins.open(filename, mode, buffering) > PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' This is the issue. I don't know how the Debian packages do this, but I recommend having a 'mailman' user that owns everything and running commands as that user. > Error in atexit._run_exitfuncs: > Traceback (most recent call last): > File "/usr/lib/python3.6/logging/__init__.py", line 1945, in shutdown > h.flush() > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 56, in flush > if self._stream: > AttributeError: 'ReopenableFileHandler' object has no attribute '_stream' This is due to the prior permissions error. > If I run it as root, it runs for a long time but spews a HUGE stream of these errors to /var/log/mailman3/mailman.log: If there are a lot of members to add, that can take a long time. The current version of import21 has a progress thermometer for this. > — > Oct 03 17:08:48 2019 (19118) Skipping and preserving unparseable message: 1570147727.3029191+80f1cc4d18f54868ad6162e8e41e52567185e983 > Oct 03 17:08:49 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' > Oct 03 17:08:49 2019 (19118) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration > msg, msgdata = self.switchboard.dequeue(filebase) > File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue > with open(filename, 'rb') as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' First, I don't know what these messages are. Normally import21 doesn't send any mail. I'm guessing it's trying to send 'you are subscribed' notices to the users, but it shouldn't be doing this. All these files should wind up in Mailman's var/queue/bad/ directory with a .psv extension. You should be able to examine them with the 'mailman qfile' command. Whatever they are, the error comes from virgin runner so import21 should have actually succeeded. Did it import the list? > It also dumps some mail footer templates into the template directory that are owned by root, which seems … incorrect? It makes a weak effort at converting the list's msg_footer and digest_footer into MM 3 templates in templates/list/<list-id>/<list-lang>/. These are owned by root in your case because you ran import21 as root. > Any thoughts on what’s going wrong here? It looks like this may be an issue with the Debian package, at least the sending of messages part. As for the rest, the Debian package should install stuff as a Mailman user, perhaps 'mailman' or 'list', and you should be running all commands as that user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: How to identify the exact reason behind the shunting of the mails ?

by Shashikanth Komandoor

Thank you Mark for your immediate response. The below are the tracebacks I could find in the mailman log. *Jun 17 19:04:08 2021 (8642) Uncaught runner exception: sequence item 0: expected str instance, Header foundJun 17 19:04:08 2021 (8642) Traceback (most recent call last): File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/handlers/avoid_duplicates.py", line 59, in process addrs = getaddresses(msg.get_all(header, [])) File "/usr/lib64/python3.6/email/utils.py", line 112, in getaddresses all = COMMASPACE.join(fieldvalues)TypeError: sequence item 0: expected str instance, Header foundJun 17 19:04:08 2021 (8642) SHUNTING: 1623936848.367641+4753f8127953071ddcabfe828ebe72fcf04d0ae2* In the shunt file, I see something like this as below in CC while To is good: *Cc: =?unknown-8bit?q?=22Support_Zimbra=22_=3Csupport-zimbra=40nic=2Ein=3E=2C?= =?unknown-8bit?b?ICLgpLbgpLDgpKYg4KSu4KS+4KSl4KWB4KSwIC0gU2hhcmFkIE1hdGh1ciIgPHN1cHBvcnQtdmFqcmFAc3VwcG9ydGdvdi5pbj4s?= =?unknown-8bit?b?ICLgpLDgpL7gpJzgpYfgpLYg4KS44KS/4KSC4KS5IC0gUmFqZXNoIFNpbmdoIiA8cmFqc0BuaWMuaW4+LA==?= =?unknown-8bit?b?ICJTYWJ5YXNhY2hpIENob3VkaHVyeSIgPHNhYnlhQG5pYy5pbj4sIG1haWxhZG1pbkBuaWMuaW4s?= =?unknown-8bit?b?ICJNUklUVU5KQVkgS1VNQVIiIDxta0BuaWMuaW4+LCAiQmhyaWd1IEt1bWFyIiA8YmhyaWd1QG5pYy5pbj4s?= =?unknown-8bit?b?ICJPbSBQcmFrYXNoIiA8b3AubmhxQG5pYy5pbj4sICJIYXJpaGFyYW4gTSIgPGhhcmloYXJhbi5tQGdvdi5pbj4s?= =?unknown-8bit?b?ICJQaGlzaGluZyBQaGlzaGluZyIgPHBoaXNoaW5nQG5pYy5pbj4sICJpbmNpZGVudCIgPGluY2lkZW50QG5pYy5pbj4s?= =?unknown-8bit?b?ICJNYW5hdiBSYWtoZWphIiA8bWFuYXYucmFraGVqYUBuaWMuaW4+?=* Also, I came to know that two of the recipients in CC block have their mail ID display name in their local language. While I am not sure, I doubt if it could be the issue of getting shunted. Please confirm and suggest any solution. On Thu, Jun 17, 2021 at 8:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/17/21 6:56 AM, Shashikanth Komandoor wrote: > > > > Is there any chance to find out the reason for shunting of the > > mails through any means ? > > > > > Look in Mailman's var/logs/mailman.log for the tracebacks associated > with the shunted messages. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 5 months

[MM3-users] Re: lmtp runner not starting

by Guillermo Hernandez (Oldno7)

El 1/4/23 a las 21:14, Mark Sapiro escribió: > On 4/1/23 12:00, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> El 1/4/23 a las 20:44, Mark Sapiro escribió: >>> ... >>> lmtp runner did not start because at some point it had died and >>> restarting Mailman won't restart a runner that died and was marked >>> to not restart. >>> >>> You need to stop Mailman and make sure when mailman is stopped that >>> there are no files in mailman's var/locks/ directory (remove any >>> that are there) and then start Mailman and lmtp runner should start. >>> >> I stopped mailman and removed all that was in there (there were many >> locked registers). Restarted mailman, and it shows the same error >> that in my previous mail. >> >> Now there is two new locked files, one (master.lck) which its content >> is the name of the other file. And the second one has the same content: >> >> master.lck|www.proteccion-civil.eu|9389|7022761192045613065 > Sorry, I sent my previous mail, and then received this > > Those are the master lock that prevents Mailman core from starting > when it is running. They should not be removed unless Mailman core is > stopped. Everytime I deleted that files I previously have stopped mailman, yes > >> will try deleting the content of var/locks and restarting the server > > If you had completely stopped Mailman core and then started it, lmtp > runner should have started. What are the complete log messages from > mailman.log following the start? > I sent them before > What does `mailman conf -s runner.lmtp` show? > Here it is: root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg conf -s runner.lmtp" [runner.lmtp] class: mailman.runners.lmtp.LMTPRunner [runner.lmtp] instances: 1 [runner.lmtp] max_restarts: 10 [runner.lmtp] path: [runner.lmtp] sleep_time: 1s [runner.lmtp] start: yes -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 8 months

[MM3-users] Re: Single-Sign-out for List member

by Abhilash Raj

On Thu, Aug 13, 2020, at 10:04 AM, Mark Sapiro wrote: > On 8/13/20 6:21 AM, w.schoener(a)alp.dillingen.de wrote: > > > > So I would like to ad a link in the footer of every message, with which every receiver/member can sign out of the newsletter with one click. > > It does not seam to be possible, to put this into effect with mailman 3. > > Does anybody have any hints, how to create a link, and when this link is called, the user is signed out of the newsletter. > > > You can set the list's unsubscription_policy to open and set the link as > a mailto: to the list-leave address, but that still requires a second > click to send the mail. > > The solution is to create a web based CGI script which is called with a > URL like > <https://example.com/unsub_script/list.example.com/user@example.net> and > have that script invoke the appropriate `mailman` command to remove the > member from the list. Beginning with Mailman 3.3.2, this would be If this is one-click, can't this URL be hit by anyone trying to remove the user from any MailingList without any auth or anything? > > mailman delmembers -l list.example.com -m user(a)example.net -g > > to remove the member and send a goodbye message. In older Mailman, it > would be something like > > echo user(a)example.net | mailman members -x - list.example.com > > I understand you may have a legal requirement do do this, but these > "one-click - no user confirmation" links are a bad idea because usera > will reply to a list post or forward it and not remove the link and > userb will receive usera's reply and click usera's unsubscribe link > either maliciously or thinking it will unsubscribe userb. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 4 months

[MM3-users] Re: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 4:16 PM, maszap(a)tin.it wrote: > Hi > My mail.log > > Jul 13 01:15:12 gamelia postfix/smtpd[1973]: connect from localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/smtpd[1973]: 276C0C202B7: client=localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/cleanup[1975]: 276C0C202B7: message-id=<20200712231512.1546.30031(a)mail.pratico.work> > Jul 13 01:15:12 gamelia opendkim[726]: 276C0C202B7: DKIM-Signature field added (s=mail2020, d=pratico.work) > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: 276C0C202B7: from=<admin(a)pratico.work>, size=586, nrcpt=2 (queue active) > Jul 13 01:15:12 gamelia postfix/smtpd[1973]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > Jul 13 01:15:12 gamelia postfix/smtpd[1978]: connect from localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/smtpd[1978]: C3A57C20D52: client=localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/cleanup[1975]: C3A57C20D52: message-id=<20200712231512.1546.30031(a)mail.pratico.work> > Jul 13 01:15:12 gamelia opendkim[726]: C3A57C20D52: DKIM-Signature field added (s=mail2020, d=pratico.work) > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: C3A57C20D52: from=<admin(a)pratico.work>, size=1610, nrcpt=2 (queue active) > Jul 13 01:15:12 gamelia postfix/smtpd[1978]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=2 data=1 quit=1 commands=6 > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia amavis[1566]: (01566-01) Passed CLEAN {RelayedInbound}, [127.0.0.1]:36322 <admin(a)pratico.work> -> <admin(a)pratico.work>,<info@pratico$ > Jul 13 01:15:12 gamelia postfix/smtp[1976]: 276C0C202B7: to=<admin(a)pratico.work>, orig_to=<max(a)pratico.work>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.76, $ > Jul 13 01:15:12 gamelia postfix/smtp[1976]: 276C0C202B7: to=<info(a)pratico.work>, orig_to=<max(a)pratico.work>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.76, d$ > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: 276C0C202B7: removed > Jul 13 01:15:12 gamelia dovecot: lmtp(1980): Connect from local > Jul 13 01:15:12 gamelia dovecot: lmtp(admin(a)pratico.work)<1980><wZyjNoCZC1+8BwAA0Fextg>: sieve: msgid=<20200712231512.1546.30031(a)mail.pratico.work>: stored $ > Jul 13 01:15:12 gamelia dovecot: lmtp(info(a)pratico.work)<1980><wZyjNoCZC1+8BwAA0Fextg:2>: sieve: msgid=<20200712231512.1546.30031(a)mail.pratico.work>: stored$ > Jul 13 01:15:12 gamelia postfix/lmtp[1979]: C3A57C20D52: to=<admin(a)pratico.work>, relay=mail.pratico.work[private/dovecot-lmtp], delay=0.13, delays=0.09/0.0$ > Jul 13 01:15:12 gamelia postfix/lmtp[1979]: C3A57C20D52: to=<info(a)pratico.work>, relay=mail.pratico.work[private/dovecot-lmtp], delay=0.13, delays=0.09/0.01$ > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: C3A57C20D52: removed > Jul 13 01:15:12 gamelia dovecot: lmtp(1980): Disconnect from local: Client has quit the connection (state=READY) > Jul 13 01:15:16 gamelia dovecot: imap-login: Login: user=<admin(a)pratico.work>, method=PLAIN, rip=173.249.18.220, lip=173.249.18.220, mpid=1983, TLS, session$ > Jul 13 01:15:16 gamelia dovecot: imap(admin(a)pratico.work)<1983><IiFCv0aqJoyt+RLc>: Logged out in=297 out=5915 deleted=0 expunged=0 trashed=0 hdr_count=11 hd$ The issue here is the message is being delivered to Dovecot via LMTP rather than to Mailman via LMTP. See this thread <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. > sudo mailman conf -s logging.smtp > > [logging.smtp] datefmt: %b %d %H:%M:%S %Y > [logging.smtp] every: $msgid smtp to $listname for $recip recips, completed in $time seconds > [logging.smtp] failure: $msgid delivery to $recip failed with code $smtpcode, $smtpmsg > [logging.smtp] format: %(asctime)s (%(process)d) %(message)s > [logging.smtp] level: info > [logging.smtp] path: smtp.log > [logging.smtp] propagate: no > [logging.smtp] refused: $msgid post to $listname from $sender, $size bytes, $refused failures > [logging.smtp] success: $msgid post to $listname from $sender, $size bytes With these settings, posts should be logged. They aren't because no mail is delivered to Mailman at all. The Mail that local users receive doesn't come from the list. It comes from Dovecot. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Edit archived email? Is it possible?

by Prasanth Nair

Hi Mark, Thank you for your help. Let me try this. Kind regards, Prasanth On Tue, 28 Sept 2021 at 18:03, Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/28/21 6:02 AM, Prasanth Nair wrote: > > Hello, > > > > Does anyone know how to edit an archived email in Mailman3? It is > possible > > in Mailman2 ( > > > https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M… > ). > > Is there any option similar to this in Mailman3? > > > In some sense the process is the same but possibly even simpler in > Mailman 3. You need to modify the underlying data which requires > appropriate access to the server. > > In Mailman 3, the data are in the hyperkitty_email table in Mailman's > database. You can get the Message-ID hash from the URL to the archived > message, e.g. for the message to which I'm replying, the URL is > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have > access, you can do database queries like > ``` > SELECT subject, content FROM hyperkitty_email WHERE message_id_hash = > '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; > ``` > and > ``` > UPDATE hyperkitty_email SET content = '<new content>' WHERE > message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; > UPDATE hyperkitty_email SET subject = '<new subject>' WHERE > message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; > ``` > If the message has attachments, they are in the hyperkitty_attachment > table and can be referenced by `email_id` which is the corresponding > `id` from the hyperkitty_email entry. > > You can also do similar things via `django-admin shell`. E.g. > ``` > $ django-admin shell > Python ... > (InteractiveConsole) > >>> from hyperkitty.models.email import Email > >>> x = > Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA') > >>> print(x[0].content) > ``` > but this requires some knowledge of HyperKitty's models and Django's ORM. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 2 months

[MM3-users] Re: What to backup?

by Alain Kohli

Thank you, that's perfect! For anyone that might stumble upon this, I had to make two minor adjustments to automate it. import os msg_ids = {} lm = getUtility(IListManager) ms = getUtility(IMessageStore) for mlistin lm.mailing_lists: requestdb = IListRequests(mlist) for rqin requestdb.held_requests: key, msgdata = requestdb.get_request(rq.id) if msgdata['_request_type'] !='held_message': continue msg = ms.get_message_by_id(key) msg_ids[(msg['Message-ID-Hash'])] =True for root, dirs, filesin os.walk('/docker/var/messages'): for filein files: if not msg_ids.get(file, False): msg = ms.get_message_by_hash(file) # It happened to me that msg was 'None' if msg: ms.delete_message(msg['Message-ID']) # I couldn't run it with '--run' and if you pipe it into 'mailman shell' # I needed this or the loop above wouldn't execute. pass On 5/27/19 6:22 AM, Mark Sapiro wrote: > On 5/26/19 3:07 PM, Mark Sapiro wrote: >> You could modify the above to write the list to a file and then wrap the >> whole thing in a shell script which would make the list and then do >> something like >> >> for f in `find var/messages -type f`;do >> n=`cut -d / -f5 <<<$f` >> for keep in `cat list` ;do >> k=0 >> if [ $n == $keep ] ;then >> k=1 >> break >> fi >> done >> if [ $k -eq 0 ]; then >> rm $f >> fi >> done > Actually, I thought about it a bit more, and I decided that arcane shell > script was a bit obscure and it would be easier to just do it in Python. > Plus, you can properly delete the message that way. > > A complete script for `mailman shell` is like > > import os > msg_ids = {} > lm = getUtility(IListManager) > ms = getUtility(IMessageStore) > for mlist in lm.mailing_lists: > requestdb = IListRequests(mlist) > for rq in requestdb.held_requests: > key, msgdata = requestdb.get_request(rq.id) > if msgdata['_request_type'] != 'held_message': > continue > msg = ms.get_message_by_id(key) > msg_ids[(msg['Message-ID-Hash'])] = True > > for root, dirs, files in os.walk('path/to/var/messages'): > for file in files: > if not msg_ids.get(file, False): > msg = ms.get_message_by_hash(file) > ms.delete_message(msg['Message-ID']) > >

6 years, 6 months

[MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member.

by Simon Coggins

Thanks I’ll give that a try. Also in my tracing of the code I noticed https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/interfaces/dat… it starts with a single quote and ends with triple quotes so the single quote is never terminated. -Simon From: Mark Sapiro <mark(a)msapiro.net> Date: Wednesday, 24 March 2021 at 4:10 am To: "mailman-users(a)mailman3.org" <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member. On 3/22/21 9:53 PM, Simon Coggins wrote: > Ok after bit tracking I’ve worked out that the bouncer is dangling transactions when it’s sending warning messages. When https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> is called and it get to update last_warn_sent it does the following in the DB: > > 2021-03-23 14:42:50.622 AEST [11693] LOG: statement: UPDATE member SET last_warning_sent='2021-03-23T04:42:50.622015'::timestamp, total_warnings_sent=1 WHERE member.id = 169331 > > But it never COMMITs this transaction. So all write operations are now hung waiting for the transction to be closed as the member record has been modified. As a test I added config.db.commit() after https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> and restarted. And my mailman syncmembers worked perfectly and I didn’t have any hangs it correctly removed everyone it should have. In the database logs I can see the COMMIT. > > I’m pretty sure this is not the right spot for a config.db.commit() but hopefully this helps point to what might be going wrong. Thank you for all the research on this. It is extremely helpful. Instead of adding a commit after line 277 please try adding the @transactional decorator to the send_warnings_and_remove method at line 210 @transactional @dbconnection def send_warnings_and_remove(self, store): I think that is the proper fix. Let us know if that works. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

4 years, 8 months

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Thomas Ward

I was able to instantiate the class AND get the expected three objects from it - pre_hook, post_hook, and resource. >>> from mailman_customizations.hooks import MailmanCustomizations >>> instance = MailmanCustomizations() >>> dir(instance) ['__class__', '__delattr__', '__dict__', '__dir__', '__doc__', '__eq__', '__format__', '__ge__', '__getattribute__', '__gt__', '__hash__', '__implemented__', '__init__', '__init_subclass__', '__le__', '__lt__', '__module__', '__ne__', '__new__', '__providedBy__', '__provides__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', 'post_hook', 'pre_hook', 'resource'] I know Abhilash Raj is probably well versed in this from statements made elsewhere, so I've added them in the CC field. Abhilash Raj, any ideas? Thomas -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 24, 2023 10:36 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler? On 10/24/23 3:56 PM, Thomas Ward via Mailman-users wrote: > > When I DO NOT have the module loaded in the configuration, `mailman > shell` works. Since that was functional, I went into the shell and > executed this: > > > from mailman_customizations.hooks import MailmanCustomizations > > This worked fine, but obviously importing the class doesn't > necessarily > *activate* the class. So something is up with how I'm *supposed* to > activate the plugin in the config, and we know that it's visible to > Mailman in its shell, but it can't autoload it. I'm past the limit of my knowledge here and only stabbing in the dark, but what happens after you import it. Can you instantiate it, e.g. ``` instance = MailmanCustomizations() dir(instance) ``` I'm not saying this should succeed, just that it may possibly provide useful information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to teward(a)thomas-ward.net

2 years, 1 month

[MM3-users] Re: digests are created but not sent out

by "Jörg M. Schulz"

when I use the lines below, the templates are looked for in //var. When I comment them out, the location is correct: /var/lib/mailman3/ (debian buster standard) . The user list has full access. The folder is empty. See mailman.cfg: [mailman] # This address is the "site owner" address. Certain messages which must be # delivered to a human, but which can't be delivered to a list owner (e.g. a # bounce from a list owner), will be sent to this address. It should point to # a human. site_owner: help(a)elternserver.de # This is the local-part of an email address used in the From field whenever a # message comes from some entity to which there is no natural reply recipient. # Mailman will append '@' and the host name of the list involved. This # address must not bounce and it must not point to a Mailman process. noreply_address: noreply # The default language for this server. default_language: en [language.en] charset: utf-8 enabled: yes [language.de] description: German charset: iso-8859-1 enabled: yes > Am 09.01.2019 um 21:12 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/9/19 12:02 PM, "Jörg M. Schulz" wrote: >> start fails when I use >> >> >> # The default language for this server. >> default_language: en >> [language.en] >> charset: utf-8 >> enabled: yes >> >> when I comment out the lines above, mailman starts. > > > And in what section is this put? I.e. if the last preceding section > header is not [mailman], the default_language: en is in a section where > it doesn't belong. > > Or are you saying that you had set the server default_language to > something other than 'en' and the above is intended to change it to > 'en'. In that case, look at var/templates/en and ensure it and > subordinates are user:group list:list > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 11 months

[MM3-users] Re: Disabled by bounce

by Allan Hansen

Mark, I can see your argument here, but if a 'Disabled by bounce' subscription is enabled, it would require just looking at that particular subscription and set the bounce count to 0, so that the next bounce (before staleness) does not disable it again. __ Yours, Allan On 2/2/23, 13:44, "Mark Sapiro" <mark(a)msapiro.net> wrote: On 2/2/23 04:54, Danil Smirnov wrote: > Hi Mark > > On Wed, Feb 1, 2023 at 9:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> Yes and no. If 'Bounce info stale after' is set to 3d and no bounces for >> a user are received in a 3 day period, the user's bounce score is not >> immediately reset, but it will be reset (to 1) the next time a bounce is >> received for the user. I.e., it is effectively the same thing unless you >> are looking at the user's bounce score which doesn't change until the >> next bounce. >> > > Isn't this a bug? We are now showing users' bounce scores on the Members > page and this would be misleading. Is it difficult from internals > perspective to have the bounce score reset immediately? Yes, it is not difficult, but it's a lot of processing. It would require something like a task runner task to periodically look at each row in the member table and if the bounce score is > 0, find the associated list's bounce_info_stale_after and if last_bounce_received + bounce_info_stale_after < now, reset the score. Consider a site like mail.python.org that at this moment has 79024 rows in the member table and 7531 of those have bounce_score > 0. That's a lot of processing, and is it really an issue to show a non-zero bounce score that's stale? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: mailman-users(a)mailman3.org <https://lists.mailman3.org/archives/list/<a href=>/message/ERW6LLR3VIJHUS5ECDA7A2P53WD7ZZEB/">https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to hansen(a)rc.org

2 years, 10 months

[MM3-users] Re: digests are created but not sent out

by "Jörg M. Schulz"

When I remove the offending special character from the footer, digests are sent out perfectly. So, for international use, we have to wait for the language template system to be ready … By the way: Thank you for your continuing work with this marvellous piece of software. > Am 09.01.2019 um 19:16 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/9/19 9:33 AM, "Jörg M. Schulz" wrote: >> But, also in mailman log. >> Uncaught runner exception: 'ascii' codec can't encode character '\xdf' in position 157: ordinal not in range(128) >> Jan 09 12:24:06 2019 (17491) Traceback (most recent call last): >> File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration >> self._process_one_file(msg, msgdata) >> File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/lib/python3/dist-packages/mailman/runners/digest.py", line 324, in _dispose >> mime = mime_digest.finish() >> File "/usr/lib/python3/dist-packages/mailman/runners/digest.py", line 185, in finish >> footer = MIMEText(footer_text.encode(self._charset), >> so the footers may not contain special characters. >> Will review this one. > > > in the above, self._charset is the character set of the lists > preferred_language. The footer can't contain characters not in the > character set of the list's preferred_language. For English (en) this is > us-ascii. For German (de) it is iso-8859-1. These are artifacts from > Mailman 2.1 > > You can change this for English by putting > > [language.en] > charset: utf-8 > > in your mailman.cfg. This works because us-ascii is a proper subset of > utf-8. > > For other languages, a change like this might require recoding of > templates and/or a message catalog, but since we don't currently ship > any non-English templates or message catalogs, that is moot at the moment. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 11 months

[MM3-users] Re: Hyperkitty on Debian 12

by Markus Grandpré

Dear Mr Sapiro, thank you very much for your help. The required command is: # mailman-web hyperkitty_import \ -l mailman21-migration-test-04(a)mailman.uni-konstanz.de \ /var/mailman21/testlist.mbox Due to the following warnings, I still have to customize Hyperkitty: django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. ... Can you give me another hint? As Linux admin I installed the packages mailman and mailman-web that were offered to me under Debian 12. Although during the installation of the packages user "list" was created, I cannot use it: # su - list This account is currently not available As with Mailman 2.1, I will probably have to continue working with Mailman3 as root. Too bad that there is no documentation for Debian admins like me, who don't want to dive too deep into the python framework. Or have I overlooked something? Best regards, Markus Am 25.03.24 um 18:56 schrieb Mark Sapiro: > On 3/25/24 07:58, Markus Grandpre wrote: >> Dear list members, >> >> when following the instructions to migrate list archives from >> Mailman21 to Mailman3 (see [1]), I face the following problem: >> >> # python3 manage.py hyperkitty_import -l mailman21-migration-test-04 >> /var/mailman21/testlist.mbox >> python3: can't open file '/var/mailman21/manage.py': [Errno 2] No such >> file or directory >> >> and have no clue, where to find the right <manage.py> file. The command > > > This depends on how you installed Mailman 3. You may or may not want > `python3 manage.py` at all. The required command could be something like > `django-admin` or `mailman-web`. > > Also the `#` prompt indicates you may be running as root. Mailman > related commands should be run as the Mailman user (could be `mailman` > or `list` or ... depending again on how you installed Mailman). Running > as root can create files owned by root that later can't be read by the > Mailman user. > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

1 year, 8 months

Search results for query "sapiro"