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

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

by Mark Sapiro

On 4/18/20 3:26 AM, Andrew Hodgson wrote: > > In my situation I noticed the directories weren't created very quickly as my Exim config looks for the list directories to identify whether that address exists. I don't know how Postfix does the aliasing but for my case it would make sense to get the directories created as soon as possible, not sure if the digest handler would be soon enough or not. The directory is created when the list is created and should always be there if the list is there. The idea behind <https://gitlab.com/mailman/mailman/-/issues/699> is only to correct a situation where the directory for a list is absent because it was deleted or the server was restored from a backup that didn't contain it. -- 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: Extract posts into mbox file

by Mark Sapiro

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. -- 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: Hyperkitty shows "<" as <

by Mark Sapiro

On 4/5/23 07:39, Andreas Schamanek wrote: > > The function that handles it is escapeemaillinks() in > templatetags/hk_generic.py (at line 111 in my version). > > Adding `.replace("&","&")` to the return value fixes the rendering > of email addresses (at least for me). escapeemaillinks(text) searches text for strings like <a href="mailto:user@example.com>xxx</a> and replaces them with user(a)example.com thus replacing everything from `<a href=` through `</a>` with just the email address with `@` replaced by `(a)` However, text is the whole message body, so what you are doing is just replacing `&` with `&` in the message body, but only when escapeemaillinks(text) is invoked. Also, this is all changed in HyperKitty 1.3.5 with the addition of optional markdown rendering. -- 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: export/import list?

by Mark Sapiro

On 8/22/23 2:38 PM, Dave McGuire wrote: > > I'm moving from sqlite3 to postgres; I can handle that migration. But > I'm also moving from Mailman 3.1.1 to 3.3.8; do you (or anyone else) > know of any schema changes? I spot-checked the first few and they > looked the same, but before going through all of them I figured I'd just > ask here. Schema changes are handled automatically by alembic. The migrations are defined in /mailman/database/alembic/versions/. Your current version is is stored in the database in the alembic_version table. When Mailman core is started, all migrations from your current version to the latest version will be applied to bring your database up to date. I.e., you don't need to be concerned about schema changes upon upgrade. They are handled automatically. -- 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: Held messages not delivered after approval

by Mark Sapiro

On 8/5/25 02:06, Krinetzki, Stephan wrote: > Aug 05 10:21:05 2025 (217986) Cannot connect to SMTP server localhost on port 25 > > The last error is a very often in the mailman.log: That's a misleading message. It's been improved by https://gitlab.com/mailman/mailman/-/merge_requests/1362, however usually the underlying issue is inability to access a header or footer template when decorating the message. This in turn is most likely caused by some template(s) in Mailman's var/templates/ directory being owned by `root` or some other non-mailman user and not readable by the Mailman user which in turn most likely results from running `mailman import21` as root. Bottom line - check that all sub-directories and files in Mailman's var/templates/ directory are searchable and readable 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

7 months, 2 weeks

[MM3-users] Re: Sanity check of upgrade procedure

by Mark Sapiro

On 10/26/22 17:30, David Newman wrote: > > OK, thanks. Before getting to mistune, this command, run as mailman in a > venv: > > pip install -U mailman postorius django-mailman3 hyperkitty mailman-web > uwsgi Mailmanclient > > produced this error: > > .. > > Attempting uninstall: mailman-web > Found existing installation: mailman-web 0.0.6.dev9+gc606169 > Uninstalling mailman-web-0.0.6.dev9+gc606169: > Successfully uninstalled mailman-web-0.0.6.dev9+gc606169 > ERROR: Could not install packages due to an OSError: [Errno 13] > Permission denied: 'WHEEL' > Check the permissions. > > The command also said I needed to upgrade pip. Doing that produced a > similar error. > > How to resolve this error? Thanks again. Was the venv initially created as the `mailman` user? Maybe sudo chown mailman:mailman /path/to/venv will fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: MM2 -> MM3 Migration: listinfo page

by Mark Sapiro

On 3/9/23 02:49, Odhiambo Washington wrote: > > I'd rather not touch the MM2.1 domain because references have been made to > it in publications. > What I am struggling with is the listinfo.html file: > ``` > https://lists.kictanet.or.ke/mailman/listinfo/kictanet > ``` > I am struggling to add reference to the MM3 subscription link user the > " Subscribe to KICTANet by filling out the following form:" > The HTML code to insert there beats me :) Where you have ``` Subscribe to KICTANet by filling out the following form:<br> ``` replace that with ``` Subscribe to KICTANet <a href="https://example.com/mailman3/lists/kictanet@example.com>here</a><br> ``` where https://example.com/mailman3/lists/kictanet@example.com is the URL to the Mailman3 list's info page. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Pkl files with ".last" extension

by Mark Sapiro

On 7/12/24 2:20 PM, Keith Christian via Mailman-users wrote: > In the MM2 to MM3 migration project I'm involved with, I see files with > names like config.pkl.last along with config.pkl. > > Is there a special reason for the ".last" extension and if so, what is it? A Mailman 2.1 list has possibly as many as 4 configuration files. - config.pck (not pkl) is the current list configuration. - config.pck.last is the immediately prior configuration used in case config.pck is corrupt or missing. In addition there may be config.db and config.db.last files. These only exist if the list predates MM 2.1 and should be removed because they're old and could be used as a fallback if both config.pck and config.pck.last are missing or corrupt. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Too Many From Headers

by Mark Sapiro

On 11/16/25 08:08, dap1--- via Mailman-users wrote: > I am getting mail bounced from yahoo and gmail smtp servers with this message: > > 554: Message not accepted due to failed RFC compliance. Too many From headers. See https://senders.yahooinc.com/smtp-error-codes#rfc-compliance-failures > > What would cause mailman to build too many from headers when distributing email? It appears the from address is repeated 5 times in the from field. I'm guessing it is something in my configuration but what and where? I don't think Mailman can do this. Maybe it's something in fetchmail that's doing it. It's not clear what you are saying. Is it one From: with the address repeated 5 times or is it 5 From: headers?. Either way, I don't think it's Mailman. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: using SSH/TLS with external MTA

by Mark Sapiro

On 7/28/24 06:26, Roland Giesler via Mailman-users wrote: > On 2024/07/28 00:39, Mark Sapiro wrote: >> >> What do you see in Mailman's smtp.log and in the mail.log on the mail >> server? > > The smtp log is in syslog... The smtp.log I refer to is Mailman's smtp.log which is in Mailman's var/logs/ directory. > I think I see what's going on here. The mail is being sent from > postorius(a)giesler.za.net and there is no log entry on > box2.gtahardware.co.za that shows this logon attempt. So it seems it's > not going to that server, but rather to the local postfix. > > A mail was sent to root on the localhost with the following content: > > Return-Path: <root(a)giesler.za.net> > X-Original-To: root@localhost > Delivered-To: root@localhost > Received: from mailman.fast.za.net (localhost [IPv6:::1]) > by mailman.localdomain (Postfix) with ESMTP id 2174A120A5B > for <root@localhost>; Sun, 28 Jul 2024 13:11:03 +0000 (UTC) > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: quoted-printable > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: > /accounts/login/ > From: root(a)giesler.za.net > To: root@localhost > Date: Sun, 28 Jul 2024 13:11:03 -0000 > Message-ID: <172217226313.2150.10895652368679013629(a)mailman.fast.za.net> > > Internal Server Error: /accounts/login/ > > SMTPRecipientsRefused at /accounts/login/ > {'roland(a)giesler.za.net': (454, b'4.7.1 <roland(a)giesler.za.net>: Relay > acce= > ss denied')} This is mail from django-allauth, not from Mailman. Your settings in mailman.cfg do not affect how this mail is sent. See https://docs.djangoproject.com/en/5.0/topics/email/#smtp-backend for the Django settings for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Moderating posts via email

by Mark Sapiro

On 10/26/2017 02:21 PM, Dmitry Makovey wrote: > > after which we've used above password trying to approve messages > following the steps outlined above. > > What are we doing wrong, or where to look for further information? Are you replying to the outer message or to the message in the attached message/rfc822 part that contains the If you reply to this message, keeping the Subject: header intact, ... text? You don't actually have to 'reply' to anything, but your message with the 'Approved: password' actual header or first body line must be sent To: the list-request address with Subject: confirm <token> (possibly preceded by 'Re: ' or similar. If you reply to the attached message/rfc822 message, it should work. If you reply to the outer message it won't work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

[MM3-users] Re: Template Ignored?

by Mark Sapiro

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

4 years, 1 month

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

by Mark Sapiro

On 12/14/22 08:15, Odhiambo Washington wrote: > After upgrading MM3 and running all the post-update tasks and even > re-indexing all the posts, I have ended up with a somehow "broken" > hyperkitty. > The archives display on a browser six, to say the least. > The site is public, so I can share the link: https://list.rc.org/archives/ > > What should I do in order to fix this? > Are you asking about the lack of style or the "No archived list yet."? The former indicates an issue in your web browser with accessing the `static` directory or an issue with the django admin collectstatic or compress commands. I don't know about the latter - could it be because all the archives are private and I'm, not logged in? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

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

by Mark Sapiro

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

2 years, 8 months

[MM3-users] Re: Any possible way to reduce robot spam accounts?

by Mark Sapiro

On 7/20/23 20:42, Franklin Weng wrote: > > Thank you. When I set it in my settings_local.py, I clicked register > and got an error: > > ModuleNotFoundError at/accounts/signup/ > No module named 'django_mailman3.views.user_adapter' > > (In the document the path is /etc/mailman3/settings.py but I installed > it with Debian packages so I guess the path is somewhat different, and I > thought setting in setting_local.py should work too. It seems work > since it gave me the error above.) > > Do I have to install something else? Or disable some other options? What is the version of django_mailman3 in your Debian package? As it says in the FAQ article, "You would need django-mailman3 >= 1.3.6 for these settings to work." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Mailman issues after re-boot

by Mark Sapiro

On 9/29/23 12:53, paulrubin37(a)gmail.com wrote: > > When I tried to use mailman-web I get this error: > > django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE This is because you have django-allauth>=0.56. If your django-mailman3 version is <=1.3.9 you can downgrade django-allauth with ``` pip install django-allauth\<0.56 ``` Or you can find where in your django settings MIDDLEWARE is defined and add ``` 'allauth.account.middleware.AccountMiddleware', ``` to the list, however if you have a /etc/mailman3/settings.py like the one at https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… the imports from mailman_web.settings.base, you need to add the following to /etc/mailman3/settings.py ``` x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x ``` Note either downgrade django-allauth or update MIDDLEWARE, but not both. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Different (official?) documentations available - what is the correct one?

by Mark Sapiro

On 2/14/19 9:12 AM, Torge Riedel wrote: > Hi, > > I've found two different documentations: > > http://docs.mailman3.org/en/latest/index.html > > https://mailman.readthedocs.io/en/latest/README.html > > Where the first one looks to me like the official documentation (when > looking at the URL), the second one looks more up-to-date. > > Is there a reason behind it? They are both part of the official docs. The first is the overview of the entire documentation suite. The second is the documentation for Mailman core. The link in the first bullet item, 'Mailman Core - the mailing list manager core (required)' actually is to <https://mailman.readthedocs.io/en/latest/> which is another name for <https://mailman.readthedocs.io/en/latest/README.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: join via webform

by Mark Sapiro

On 6/19/19 4:50 AM, mailman3(a)malevil.cc wrote: > Is there a simple possibility to join a mailinglist besider writing a mail to list-join(a)example.com? I know you can register and then join a list, but thats only possible for public lists It is also possible for unadvertised lists. You can go to `lists/list@domain` and subscribe even though the list is not advertised. > and I would like to have such a very simple webform for a specific list where you just enter your email address and then get the confirmation mail. I guess there was something like this with mailman2 You can do this by having your web form do the subscription via the REST API. See <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/rest.html> and <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/membership.h…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Moderation not working?

by Mark Sapiro

On 11/24/20 2:53 PM, peter(a)chubb.wattle.id.au wrote: > > The only think I noticed after trawling through all the configs is > there was no moderator address set up. In Mailman 2.1 that meant the > list owner would be asked to moderate. I've added a couple of > addresses to see what happens next Held message notices, both immediate if set and summary (assuming the appropriate cron is active) are sent to all owners and moderators. This is the same for MM 3 and MM 2.1. > For other lists on the same mailman instance I *am* seeing moderation > requests for non-member postings --- but they had explicit moderator > addresses configured. The explicit moderators should not make any difference. Plus, a message being held and an owner/moderator notice of the held message are two separate things. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/27/22 05:22, Stephan Krinetzki wrote: > > I think there is a communication problem in the chain: > > apache -> uwsgi -> mailmancore/API ->database > > but i can't dig deeper there. Let me know if i should provide more details or logs It seems that this part of the chain apache -> uwsgi -> mailmancore/API is not experiencing delay. It is involved with every Postorius request, most of which seem to have no issues. It is only this one piece mailmancore/API ->database that seems to have an issue and only with this one DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX query. However, like you, I have no idea as to what you could do further to debug this. -- 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: Emergency moderation and clearing out a lot of held messages

by Mark Sapiro

On 11/11/22 10:23, Stephen J. Turnbull wrote: > > The two database configuration is not really a recommendation. I > suppose the practice derives from an abundance of caution, as there > are concepts like "User" that must be implemented in somewhat > different ways across components (core doesn't authenticate users, > while Postorius's primary function is authentication of users). I > myself would worry that there might be name collisions among tables, > which would cause mayhem, but that's probably excessive. FWIW, the Mailman3 installations at both mail.python.org and lists.mailman3.org use a single database and with the exception of Mailman core's tables and Postorius' `template` table, tables are prefixed with application names like `auth`, `django_` and `hyperkitty_`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: WSGI: gunicorn and uwsgi

by Mark Sapiro

On 6/9/19 3:18 AM, andrew.bernard(a)gmail.com wrote: > Using the Ubuntu 19 packages for all the mailman suite, uwsgi is the Python WSGI server included. I have now switched over to a full build from current source from gitlab, following Mark Sapiro's excellent instructions. Thank you. > It would appear that the current code has the use of gunicorn built in. Is gunicorn the preferred way now to run the mailman Django apps? Is it worth spending time converting everything to use uwsgi, or should I go with the flow and use gunicorn? The "built-in" gunicorn is used only by core to provide the REST API interface. This replaced the former standard library wsgiref module to improve performance. It is completely independent of whatever WSGI server you use for Django. > What are the advantages of gunicorn over uwsgi? I can't comment intelligently on that. For a long time I used Graham Dumpleton's mod_wsgi with Apache for wsgi support, mostly for MoinMoin. I have no experience with uwsgi. When I set up MM 3 on lists.mailman3.org, the server was already using nginx so I arbitrarily chose gunicorn for that. On mail.python.org I started using mod_wsgi, but at one point there was an issue due apparently to an SSL library mismatch following an upgrade, but before the cause was recognized, I switched to gunicorn to get things up. On a third server I manage, I use mod_wsgi for MoinMoin which is Python 2.7. I found setting up both Python 2.7 and Python 3 versions of mod_wsgi on the same server to be daunting, so I went with gunicorn for Mailman 3 on that server too. My choices of gunicorn over uwsgi were an initial arbitrary choice followed by familiarity for subsequent choices. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

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

by Mark Sapiro

On 2/5/20 9:55 AM, Shashikanth Komandoor wrote: > > With the above script I am able to set the value of max_days_to_hold as > required but how to check manually and make my held messages discarded > automatically which are after the specified period configured for > max_days_to_hold. > > If I am able to do it manually I can be confident to take in to production > so that the held messages after a specific period would not be appeared > under "held messages" tab. I'm really not sure what you are looking to do, but I can tell you that while the max_days_to_hold list attribute exists and can be set, the actual discarding of held messages older than max_days_to_hold is not implemented. Thus the setting currently does nothing. -- 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: New messages not being archived

by Mark Sapiro

On 7/15/21 11:28 AM, Sarah H wrote: > I have, it just ends up printing out the pages html in the error message after: > > </html> > Jul 14 10:52:31 2021 (471314) Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message > raise ValueError(result.text) > ValueError: > ... I'm interested in what's before that in the log. I.e., the message that says HyperKitty failure on <the url>: <the returned data> (<the http status>) Or, is there some redirect in your web server that is maybe redirecting `http` to `https` and returning some `3xx` status? We really need to see the status from the above message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: slow restart time for mailmanweb

by Mark Sapiro

On 12/28/21 1:07 PM, David Newman wrote: > Debian 11.2, Mailman 3.3.5, Python 3.9.2, MariaDB 10.5.12-0+deb11u1 > > On a Debian system running MariaDB, mailman3 restarts quickly but > mailmanweb takes about 90 seconds: > > root@myhost # time systemctl restart mailmanweb > > real 1m30.156s > user 0m0.013s > sys 0m0.000s > > The daemon.log has a timeout error: > > Dec 28 12:16:01 myhost systemd[1]: Stopping GNU Mailman Web UI... > Dec 28 12:16:03 myhost uwsgi[409333]: [uWSGI] getting INI configuration > from /etc/mailman3/uwsgi.ini > Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: State > 'stop-sigterm' timed out. Killing. ... > Dec 28 12:17:31 myhost systemd[1]: Stopped GNU Mailman Web UI. It looks to me like the timeout is in stopping, not starting. What happens if you separately systemctl stop mailmanweb and systemctl start mailmanweb -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Mark Sapiro

On 2/18/22 01:55, Élodie BOSSIER via Mailman-users wrote: > Thank you for your response Mark, > > With Mailman 2.1, the lists were split on their webpage respectively. > How could I do same with Mailman 3.3.3 (Tom Sawyer) please ? > > My domain table SQL have this result : > id, mail_host, description, alias_domain > 1, ml.franceserv.fr, NULL, local.ml.franceserv.fr > 2, ml.viticreation.fr, NULL, local.ml.viticreation.fr If you go to https://example.com/mailman3/domains/ (the Domains view in Postorius) you will see at least two entries, one with Mail Host ml.franceserv.fr and one with Mail Host ml.viticreation.fr. What are the Web Host entries for these? You should have two separate site entries in the django_site table (https://example.com/admin/sites/site/) for these domains. -- 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: Odd behavior: "Invalid" list destinations result in mail routing loop w/ SMTP relay in line

by Mark Sapiro

On 12/6/23 11:11, Thomas Ward via Mailman-users wrote: > See, that's the oddness. There appears to be SOME weird mail loop here > where $ORIGIN (MS365/Exchange) hands it once, then there's > back-and-forth between SMTPPROXY and Mailman. IT's really odd how it > behaves, and I have no explanation for it. > > Right now I'm away from the office where this happens, but when I'm back > there I'll grab logs from both sides. > > > Thomas > > On 12/5/23 17:54, Mark Sapiro wrote: >> On 12/5/23 10:08, Thomas Ward via Mailman-users wrote: >>> We use a multi-hop SMTP system to go from the inside of our network >>> out to the Internet at the domain test.lists.example.com. >>> >>> The setup is this way for ingress: >>> >>> {EXTERNAL} -> MS365 (relay/antispam) -> MS On-Prem (via 365 >>> Connector) -> Mailman for delivery to listserv Presumably the EXTERNAL to MS365 SMTP transaction includes MAIL FROM: <user(a)example.com> RCPT TO: <invalid(a)test.lists.example.com> It seems that somewhere in the path to Mailman this is getting changed to MAIL FROM: <invalid(a)test.lists.example.com> so the outbound DSN is sent to invalid(a)test.lists.example.com instead of user(a)example.com. The question is which one of the MTAs in the path is doing this and why. But even more mysterious is the fact that the DSN from Mailman should be sent with MAIL FROM: <> so when it's undeliverable, no further DSN is sent. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

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

by Mark Sapiro

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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: MM3 gateway errors and frequent reboot needs

by Mark Sapiro

On 4/19/20 1:21 PM, hansen(a)rc.org wrote: > We have had to reboot the list server almost every week and wonder if there is something leaking and eating up resources. I does not appear to be memory, though. The server is slow to respond (could be because it's overseas) and then after some time we get intermittent gateway errors and finally we cannot access the lists online because of the gateway errors. It appears to me that the issue is with Postorius, but I could be wrong. Do files get closed after opening? Are we alone having such issues? We are not seeing an issue like this on either lists.mailman3.org (this list) or mail.python.org (at the moment 118 @python.org Mailman 3 lists) What are you seeing in web server logs? -- 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: pending subscriptions lost?

by Mark Sapiro

On 3/14/22 09:18, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > this is with "Postorius Version 1.2.4" (as installed by the mailman3 > Debian package). The Debian packages are OK for people who want to install things via a package manager, but they are quite out of date. Something like the following in `mailman shell` can do it. ``` >>> # Cutoff date delete pended subscriptions older than this >>> cutoff = '2022-03-01' >>> pendings = getUtility(IPendings) >>> # Prior to Mailman core 3.3.5 need to explicitly delete workflow >>> wfm = getUtility(IWorkflowStateManager) >>>for token, data in pendings.find(pend_type='subscription'): ... if data['token_owner'] != 'subscriber': ... continue ... if data['when'] >= cutoff: ... continue ... pendings.confirm(token, expunge=True) ... # for MM < 3.3.5 ... wfm.discard(token) ... >>> commit() ``` -- 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: How to hide sender completely

by Mark Sapiro

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

2 years, 10 months

[MM3-users] Re: Internal Server Errors in mailmanweb.log

by Mark Sapiro

On 1/22/26 00:53, Washington Odhiambo via Mailman-users wrote: > On Thu, Dec 25, 2025 at 10:46 AM Washington Odhiambo <odhiambo(a)gmail.com> > wrote: > > For some reason, my mailmanweb (I am using Gunicorn) has been misbehaving > lately. > The last change I ever made to my MM3 installation is when I applied the > patch mentioned in this thread. > The misbehavior manifests in the Postrorius web UI becoming inaccessible, > much as mailmanweb is running. It looks like all the logged errors result from an attempt to export a thread from HyperKitty. Is it this export that precipitates the issue? I.e, can you access Postorius first thing after a clean start of mailman web? If so, is it only when you try to export a thread from HyperKitty that the issues start? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 3 weeks

[MM3-users] Re: 3rd Party Account is not working

by Mark Sapiro

On 2/16/21 4:46 AM, Matthew Alberti wrote: > I think each plugin has to be configured separately, such as with an API key from each service. For what it's worth, this list supports 4 Oauth2 providers, Google, Facebook, Github and Gitlab. 3 of these require stuff in Django's settings ``` SOCIALACCOUNT_PROVIDERS = { 'google': { 'SCOPE': ['profile', 'email'], 'AUTH_PARAMS': {'access_type': 'online'}, }, 'facebook': { 'METHOD': 'oauth2', 'SCOPE': ['email'], 'FIELDS': [ 'email', 'name', 'first_name', 'last_name', 'locale', 'timezone', ], 'VERSION': 'v2.12', }, 'gitlab': { 'SCOPE': ['read_user'], }, } Additionly, each requires creation of an app with the provider and addition of the app and its keys in the Django admin UI at socialaccount/socialapp/. See <https://django-allauth.readthedocs.io/en/latest/providers.html> for more info on setting up specific providers. -- 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: mailman3 admin from mailman2 & File location questions

by Mark Sapiro

On 11/4/21 6:58 AM, bob B wrote: > Sorry i did some more digging and for question 2 I found: > > "By default, HyperKitty stores the email attachments in the database. If you would rather have them stored on the filesystem, you can set the HYPERKITTY_ATTACHMENT_FOLDER configuration value to a directory." That only refers to attachments, not to the message headers and body. > So unless I am missing something, I no longer need a big drive on my mailman3 install (Like i did on mailman2) cause everything is being stored in the database That is correct for HyperKitty by default, but not for the prototype archiver. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Of course the prototype archiver can be disabled and maybe is in your case. -- 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: File in /var/lib/mailman3/queue/bounces/

by Mark Sapiro

On 12/11/21 6:29 PM, Andreas Barth wrote: > > in my local installation there is a file in > /var/lib/mailman3/queue/bounces/ since a couple of days. Any hint how > to get rid of it? 'mailman unshunt' doesn't do it, but also, it's in > queue/bounces and now queue/shunt. I suspect the issue is that bounce runner is not running. If you grep Mailman's mailman.log for `bounces` I suspect you will see that it has died and not restarted. You may or may not find additional information in the log as to why it died, but in any case restarting Mailman should start everything again. The master should restart it when it dies, but this is https://gitlab.com/mailman/mailman/-/issues/898 for which we don't have a satisfactory fix. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 6/11/24 6:47 AM, Marcus Bautze via Mailman-users wrote: > i found: > > python3-django-hyperkitty 1.3.7-1 > python3-mailman-hyperkitty 1.2.1-1 > mailman3-full 3.3.8-2~deb12u1 These versions should be OK and your other settings seem OK. I suspect that the issue may be nginx not forwarding the Authorization: header from mailman_hyperkitty. Your nginx config posted at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… seems a bit off. If you compare that to https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… you'll see you are missing a `location /static/` directive and you've included `proxy_hide_header upgrade;`. I'm not sure why you have this. I don't see why ngnix would be dropping the Authorization: header , but you might try adding `proxy_pass_header "Authorization";` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: User cannot reset password

by Mark Sapiro

On 8/11/24 11:27, Greg Newby wrote: > > 1. Will the new (Django) and imported (Postorius) usernames automatically > be matched to the same email address? > > The goal is for someone to use the web-based front end to manage their > migrated subscriptions. Yes, The user creates an account with one of their MM 2.1 email addresses and adds any other MM 2.1 addresses to that account. That account will be associated with all their list subscriptions. > 2. How can I customize the email that went to users who selected "Forgot > password?" ( > > You are receiving this email because you, or someone else, tried to access > an account with email > > > I didn't find that string in the source code. It comes from Django-allauth. See allauth/templates/account/email/unknown_account_message.txt -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Relay Access Denied

by Mark Sapiro

On 7/22/25 9:47 AM, jkoral(a)luc.edu wrote: > > Error before changing main.cf: > 2025-07-20T22:14:30.381945-05:00 lstprdls01 postfix/smtpd[3713490]: NOQUEUE: reject: RCPT from unknown[10.18.3.105]: 454 4.7.1 <joetest(a)lists.luc.edu>: Relay access denied; from=<jkoral(a)luc.edu> to=<joetest(a)lists.luc.edu> proto=ESMTP helo=<DM1PR04CU001.outbound.protection.outlook.com> > > Error after adding F5 IP to mynetworks: > 2025-07-22T11:27:13.885111-05:00 lstprdls01 postfix/smtp[174935]: AB1C11C0229: to=<joetest(a)lists.luc.edu>, relay=lists.luc.edu[147.126.1.184]:25, delay=0.16, delays=0.11/0.01/0.04/0, dsn=5.4.6, status=bounced (mail for lists.luc.edu loops back to myself) > > Any help would be greatly appreciated. Is Postfix configured per https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… What is the output from `postconf -n`? What is the content of Mailman's var/data/postfix_lmtp? In particular, are the domains of the list addresses lists.luc.edu and not listservnew.luc.edu? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 3 weeks

[MM3-users] Re: problem with Python's stdlib email module

by Mark Sapiro

On 6/5/23 14:59, Peter Münster wrote: > On Mon, Jun 05 2023, Mark Sapiro wrote: > >> Basically, all over. > > Thanks. I would like to find out, which function is responsible for the > modification of the body, before filling a bug report. > Unfortunately I don't have any experience with Python, so any help is > highly appreciated. > My idea is to add "print(message)" at the places, that you mentioned. > Where would I find the output then? You don't want to use print statements. All those modules do logging to various logs so they pretty much all import logging. Then you add something like ``` dlog = logging.getLogger('mailman.debug') ``` near the beginning of the module and then add things like ``` dlog.info(msg.as_bytes()) ``` to write the message to debug.log. However, I would not proceed in that way. I would start by putting the raw problem message as it comes to mailman in a file and then use `mailman shell` do to things like ``` >>> import email >>> import smtplib >>> from mailman.email.message import Message >>> with open('path/to/message/file', 'rb') as fp: ... msg = email.message_from_binary_file(fp, Message) ... >>> ``` to create the message object, and then do something like ``` >>> conn = smtplib.SMTP() >>> conn.sendmail(from_addr, to_addrs, msg) ``` to send the message to to_address and see if it has the added lines. Or maybe just ``` >>> print(msg.as_bytes()) ``` to see if that has the added lines. It may be necessary to do things like ``` >>> msg['Message-ID-Hash'] = 'aaaaa' ``` to add a header to create 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, 9 months

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

by Mark Sapiro

On 10/25/2017 01:08 PM, Fabian A. Santiago wrote: > Hello, > > I have mm3 up and running via docker (courtesy of maxking/docker-mailman) but when i send an email to my test list, it bounces back claiming user unknown. it states: > > <"lmtp:[172.19.199.2]:8024"@>: unknown user: > "lmtp:[172.19.199.2]:8024" > > looking at the email source, it seems as though the message is trying to be delivered to: > > Final-Recipient: rfc822; "lmtp:[172.19.199.2]:8024"@<my email server's FQDN> > Original-Recipient: rfc822;test123@<my list's email domain> > > all of various alias transport maps are defined in postfix's main.cf. not sure where to go from here. does anyone have any clues? For the docker image, the tables have to be defined in Postfix as regexp: tables. Are they? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

[MM3-users] Re: postorius configuration of the from-part

by Mark Sapiro

On 11/12/19 2:27 PM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > can someone give me an advice how I can configure in the > postorius-menues the view of the from-part of my list-member like in > this mailinglist: > > Wolfgang Bock_via Mailman-users_ <mailman-users(a)mailman3.org> The above is the result of Settings -> DMARC Mitigatations -> DMARC mitigation action = "Replace From: with list address" You can apply that to only messages From: a domain the publishes a DMARC policy of reject or quarantine or to all messages depending on DMARC Mitigate unconditionally. > case 1 reply goes to the list or to the member > case 2 reply goes only to the list The DMARC Mitigatations settings are independent of the various reply settings on the Alter Messages tab. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: New messages not being archived

by Mark Sapiro

On 7/8/21 8:35 AM, Sarah H wrote: > > When trying to add a new thread via the hyperkitty interface I can see the email go through the maillog, I get the email with the entered content and everything else works, it just doesn't add a new thread to the archive. What if anything is in Mailman's var/archives/hyperkitty/spool/ directory? Do you have something like ``` [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg ``` in your mailman.cfg? Do you then have ``` [general] base_url: ... api_key: ... ``` in the mailman-hyperkitty.cfg file and is base_url set to a url tha accesses hyperkitty and is api_key set to the same value as the MAILMAN_ARCHIVER_KEY is your Django settings - quoted in settings but not in mailman-hyperkitty.cfg, i.e., ``` api_key: xxx MAILMAN_ARCHIVER_KEY = 'xxx' ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: New messages not being archived

by Mark Sapiro

On 7/12/21 1:40 PM, Sarah H wrote: > I took a look at the pickle files, this last one didn't have the archive locations but another had > > Archived-At: <> > List-Archive: <> > > as well, so it looks like it's not being passed properly to the archive location? Messages in the spool were not successfully delivered to HyperKitty[1] and will be retried each time there is a new post. There should be log messages in mailman.log about the failures. Likely issues are problems with the base_url or api_key settings in mailman-hyperkitty.cfg [1] It doesn't matter if they originated from HyperKitty or elsewhere. Messages originating as replies or new threads from HyperKitty are posted to Mailman core for processing and only archived when core sends them back to HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Email discard

by Mark Sapiro

On 4/1/23 08:33, qro(a)xs4all.nl wrote: > Hi > > I have a good working mailman3 list server with 3 mailing lists. > 2 of them work OK, but 1 has a little odd behaiver > > If a non member send an email it will discard while the setting in /postorius/lists/list.name.nl/settings/message_acceptance shows Hold for moderation > > A snip from var/mailman3/mailman.log > Apr 01 10:48:32 2023 (49342) DISCARD: <4359976d-d4bb-9b30-0901-c842aa1fecb3(a)xs4all.nl>; ['The message is not from a list member'] > > Changing and saving a other choice makes no difference. > > Where can I look more to find a solution? (in mysql?) In Postorius, find the nonmember in the Users->Non-Members list. Does that nonmember have a moderation action of discard. Also, what's in Postorius->Settings->Message Acceptance->Discard these non-members? -- 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: Postorius -owner messages

by Mark Sapiro

On 6/15/23 13:47, ssehi--- via Mailman-users wrote: > > They'd like to disable owner delivery for themselves, and I'd like to not make the change for them using the shell every time I get one of their requests. We have a Postorius front end set up and working, but it doesn't appear that disabling delivery using the List-based preferences in the Postorius interface stops those Owner communications. Is there a way to allow users to disable that natively in Postorius? No. In Postorius you can set the delivery status for members and non-members, but you can't set it for owners or moderators. Owners and moderators do have a delivery_status which will control whether they receive notices sent via the listname-owner address, but it is not exposed or settable in Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: customized welcome message

by Mark Sapiro

On 12/7/23 03:01, Nils wrote: > Hi, > > I've created a template "The notice sent to a member when they are > subscribed to the mailing list.". > When I subscribe to the list, I don't get the message I've created. > Instead I get a plain text message, containing the html source of the > parent domain. These messages are sent with `Content-Type: text/plain`. Any html included in a template will be rendered as plain text. I.e., you can't include html in templates. > When I try to change the value of Settings > Automatic Responses > URI > for the welcome message in postorius frontend, I always get this error > message: I see no URI setting in Postorius Settings > Automatic Responses. What Postorius version is this? Any local mods? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Hiding the "subscribe without creating an account"

by Mark Sapiro

On 7/10/24 7:36 PM, Ben Sturmfels via Mailman-users wrote: > > Is there a configuration option that does this, or was it a custom change made in > the templates? Was the change made to reduce fake registrations? Did it work? It was added in Postorius 1.3.9. See the UI section at https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 Yes, the change was made in an attempt to reduce fake registrations. We haven't really studied it's effectiveness. It seems to help somewhat, but it also seems that bots may already have a template to POST so removing it from the UI is not a complete solution. There is also a lot of email to innocent third parties and non-existent addresses from attempts to register them for an account. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: footer template priority

by Mark Sapiro

On 6/19/25 15:42, Sam Darwin via Mailman-users wrote: > It takes time to figure out a new feature. I see what is happening. :-) Or, merely one step further. > > After a template is stored in the DB you can remove POSTORIUS_TEMPLATE_BASE_URL because the value is cached in the DB. That explains the caching. > > Next, without POSTORIUS_TEMPLATE_BASE_URL, it assumes http://localhost:8000/mailman3/ . On our server this is not correct, because it's listening on a unix socket, as well as 80 and 443, but not 8000. Actually, it assumes whatever the default is which might be `http://localhost:8000`. See https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/settings/m…. It's Postorius that adds the /mailman3/... when setting the template table entry. If that is not correct for your server, you need to set the correct value in settings.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

[MM3-users] Re: upgrading Mailman

by Mark Sapiro

On 10/1/25 11:02, Christian Stalberg via Mailman-users wrote: > I am operating an old platform. I am currently running GNU Mailman Core > version 3.3.5, API version 3.1, Python Version 3.7.3, on Debian 4.19.316-1 > > What version of Mailman 3 is current and what is the recommended server > please? Are there upgrade instructions available? Please do not hijack threads. When posting a new topic compose a new message, not a reply to an unrelated post. The current released version of Mailman core is 3.3.10 and it requires Python >= 3.9. If you are asking about upgrading Debian Mailman packages, that's a question for Debian. There is information on upgrading at https://docs.mailman3.org/en/latest/upgrade-guide.html. You can install Mailman in a virtualenv following the instructions at https://docs.mailman3.org/en/latest/install/virtualenv.html. You can do this and keep your existing database. -- 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: Setting up From: field as list address

by Mark Sapiro

On 11/24/19 11:54 PM, Steven Maddox wrote: > Hi folks, > > I'm trying to configure our mailman3 lists (via postorious) in a way > that'll mean they'll behave in the way way that I've witnessed on > another 3rd party list (one running mailman2). > > This is where (when receiving a message from the list) the From: is the > list itself, and the person who actually sent it bizarrely appears as a > CC:, for example... > > From: Steven Madox via Shropshire LUG <shropshire(a)mailman.lug.org.uk> > Subject: [Shropshire LUG] Whatever > To: shropshire(a)mailman.lug.org.uk > CC: s.maddox(a)lantizia.me.uk Go to Settings -> DMARC Mitigations and set DMARC mitigation action to "Replace 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

6 years, 3 months

[MM3-users] Re: list footer web customization procedure

by Mark Sapiro

On 11/29/21 8:13 PM, Philippe B wrote: > I am new to Mailman 3 and I've been reading all the documentation that I could find, but I haven't been able to figure out how a list owner can use the web interface to customize the footer that appears at the end of each e-mail from the list. > > We're actually after something much simpler (in theory), which is to eliminate the built-in footer altogether for some of our lists. > > Could someone share the instructions for doing that? Thanks. In Postorius go to the Templates tab for the list, click New Template, then in the Name dropdown select [list:member:regular:footer], leave the Data box empty and Save. Do the same for [list:member:digest:footer] if you want to eliminate that one too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: How to stop minutely mails about readme_renderer

by Mark Sapiro

On 5/22/22 08:10, Stephen J. Turnbull wrote: > Axel Rau writes: > > > /usr/local/py_venv/mailman_33/lib/python3.9/site-packages/readme_renderer/markdown.py:44: > > UserWarning: Markdown renderers are not available. Install > > 'readme_renderer[md]' to enable Markdown rendering. > > warnings.warn(_EXTRA_WARNING) > > > > I installed cmarkgfm 0.8.0 in my venv, > > Why did you do that? Is it something in our documentation? It is required by readme_renderer. Can you activate your venv, run python and successfully ``` import cmarkgfm from cmarkgfm.cmark import Options as cmarkgfmOptions ``` If you can't do either, cmarkgfm is not properly installed in the venv. If you can do the first, but not the second, there is a compatibility issue between readme_renderer and cmarkgfm 0.8.0. Try ``` pip install cmarkgfm==0.6.0 ``` which works in my installations -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Apache proxy error messages.

by Mark Sapiro

On 6/15/23 11:42, Mark London wrote: > I have two users who are getting a proxy error message when they try to connect her our mailman server: > Proxy Error > The proxy server received an invalid response from an upstream server. > The proxy server could not handle the request > Reason: Error reading from remote server > Apache/2.4.52 (Ubuntu) Server at lists.psfc.mit.edu > Has anybody else in an errorlike this before? > One person manage to get around this by going in incognito mode on the browser. Does that make any sense? What are you proxying to? I.e., uwsgi, gunicorn or ?? You might find something in its logs. In any case, if the same URL worked in incognito mode and switching wasn't just a coincidence, it's a browser issue, possibly related to cookies. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: two signatures on sent mail?

by Mark Sapiro

On 6/19/25 08:33, STR via Mailman-users wrote: > Hi, I am a very non-savvy mailman list user. I am trying to set up a list via cPanel but when I send emails there are two signatures. One is my usual signature and the other, below, is appended by Mailman and includes an http link to a non-existent page on my website. How do I strip the auto signature, just leaving my own? > > I use Mailman via cPanel on two separate hosting accounts. One works fine and this new one attaches the list address. I can't see what I did differently with the first! Please see https://wiki.list.org/DOC/Mailman%20and%20CPanel That said, if you can go to the standard Mailman web admin UI, go to Non-digest options and ensure msg_footer is completely empty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

[MM3-users] Re: Hyperkitty CPU usage

by Mark Sapiro

On 4/26/19 11:14 AM, Alain Kohli wrote: > I see loads of "A string literal cannot contain NUL (0x00) characters." > messages, but I haven't found missing messages in the archives yet. Not > sure how that could be related, though. Apart from that I don't see > anything unusual. The other jobs (quarter_hourly, hourly, etc.) seem to > run and finish normally. Did you upgrade from a Python 2.7 version of HyperKitty to a Python 3 version? The Haystack/Whoosh search engine databases are not compatible between the two and "A string literal cannot contain NUL (0x00) characters." is the symptom. You need to run 'python manage.py clear_index' or just remove all the files from the directory defined as 'PATH' under HAYSTACK_CONNECTIONS in your settings file (normally 'fulltext_index' in the same directory that contains your settings.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: Mailman3 on Debian 10

by Mark Sapiro

On 1/30/20 8:24 AM, Bala Mutyam wrote: > Hi Mark, > > Thanks for the update and I managed to resolve the errors on the UI. > > I have 2 more questions about the mailman3. > > 1) how to create Mailing Lists? You can create lists with the `mailman create` command lint tool or via Postorius as a superuser. > 2) super user login is not working even with correct login credentials and giving me - The username and/or password you specified are not correct. How did you create the super user? You should do it with the django admin createsuperuser command. > 3) Password Reset Email urls and email confirmation web pages giving me - This site can't be reached error. If this is an error from your browser, there is something wrong with the host portion of the URL. -- 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: 500 Internal Server Error on specific list pages

by Mark Sapiro

On 7/30/20 12:13 PM, Johnny Cison wrote: > > I asked the person who was making changes at the time what was done and she > indicated that she had approved an email being held (from a non-list > member) and then added a user to the list. Not sure which of those created > the issue. Thank you for asking. I'll take a look at the flow of those actions. The code basically won't add a duplicate entry. It checks if there is one and only adds if there isn't, so it has to be some kind of race condition, possibly caused by inadvertently double-clicking a button or link. (I have a mouse with a bouncy switch that sometimes double-clicks on its own if I'm not careful.) -- 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: OS upgrade - anything to take care of?

by Mark Sapiro

On 5/13/21 7:25 AM, Torge Riedel wrote: > > today I upgraded one of two servers from Ubuntu 18.04 to 20.04 and - > besides some minor config updates - postfix & dovecot worked well > afterwards. > > So I am very optimistic that the upgrade of the second server from 18.04 > to 20.04 will also work fine. But the second server is running MM3 > (installed in venv) and I saw that on upgrade Python 3.8 is installed. > > Is there anything I have to take care of? Anything to do / change in venv? The venv will still run whatever Python it was built with. That's what virtualenvs are for - to isolate the software therein from external changes. You shouldn't need to do anything in the venv for Mailman to continue. -- 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: Remove old bounces in bouncedir

by Mark Sapiro

On 3/9/22 00:58, Stephan Krinetzki wrote: > Hello all, > > our Mailman3 has over 7GB of bounces in its bouncedir. I noticed that some messages there are already over 3 years old. Now my question: Is there a way to remove the old bounces? I don't know what you mean by bouncedir. If you are referring to the bounceevent table in the database, it would be OK to remove all the entries for which `processed` is True. If you are referring to messages in Mailman's bounces queue, if these are not processed and removed within 15 minutes of arrival, Mailman's bounce runner is not running. If you are referring to bounce messages in the message store (var/messages/), there have been issues with those not being removed, but Mailman core >= 3.3.5 should clean those up. -- 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: Footer from templates not working - DB issue?

by Mark Sapiro

On 9/21/22 05:10, chris(a)mehl.one wrote: > Hi, > > I am running Mailman3 on Debian 11 with Apache and MariaDB. Single installation. > > When I edit a footer from the WebUI templates, it doesn't show in the messages. How is Mailman installed? If from the Debian packages, this may be a Debian issue, and you should contact Debian for assistance. > Could it be an issue with the related DB? If so - what do I need to change? I can't say without more info. Is the default footer added to messages? What do you get from the db query ``` SELECT * from template WHERE name = 'list:member:regular:footer'; ``` Assuming that returns a row with context of the list id, what is the uri and can you retrieve it? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: customized welcome message

by Mark Sapiro

On 12/7/23 12:46, Nils wrote: > I didn't try to include html. > It completely ignored the template I've created and sent the html source > of the parent domain. Which seems totally random to me. How and to what did you set the URL for the template? What does the database query SELECT uri FROM template WHERE name = 'list:user:notice:welcome'; show? >> I see no URI setting in Postorius Settings > Automatic Responses. What >> Postorius version is this? Any local mods? > It's Postorius Version 1.2.4 installed through the mailman3-web package > for ubuntu focal (https://packages.ubuntu.com/focal/mailman3-web) This is very old. Current Postorius is 1.3.10. 1.2.4 is from February 2019. The Debian/Ubuntu packages are out of date. We recommend installing via the doc at 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

2 years, 3 months

[MM3-users] Re: MM2 to MM3 Archives Loading

by Mark Sapiro

On 11/22/24 11:02, Joshua Bushe wrote: > Unsure where these hide inactive or hide private boxes are located. Looked through all settings. They are at the top of the main Hyperkitty overview page. E.g. like https://lists.mailman3.org/archives/ > Nothing strange in Django's logs. > > Only thing I've noticed is that when i look at my listing. It has the list name then it says "inactive". Not sure if or how to change that to something else? `inactive` means no posts in the last 30 days. However, from your original post, I thought your issue was that you couldn't see the lists. What are the urls of the page with the issue and the page that shows your list as `inactive` (you can replace the host name with example.com if you wish). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Current status and issue deleting Archives in Mailman3

by Mark Sapiro

On 11/2/21 11:50 AM, bob B wrote: > So I am teaching myself to fish, and see that it is actually django-admin, so that is in > mailman-web? (in docker) > > But i get this: > > $ docker exec -it mailman-web /bin/bash > bash-5.0# django-admin shell > Python 3.8.10 (default, May 6 2021, 06:30:44) > [GCC 9.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models import MailingList > Traceback (most recent call last): ... > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: 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. Do what it says. I.e. run DJANGO_SETTINGS_MODULE=path/to/settings; django-admin shell -- 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: django-allauth failures, but only for some users (independent of browser?)

by Mark Sapiro

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

2 years, 3 months

[MM3-users] Re: Hyperkitty error - not archiving

by Mark Sapiro

On 7/26/25 10:55 AM, Odhiambo Washington via Mailman-users wrote: > Another thing I have seen, inside /etc/mailman3/ > root@list:/etc/mailman3# ls -al > total 40 > drwxr-xr-x 3 mailman mailman 4096 Jul 26 10:52 . > drwxr-xr-x 110 root root 12288 Jul 26 07:17 .. > -rw-r--r-- 1 mailman mailman 948 Jul 25 02:48 mailman.cfg > -rw-r--r-- 1 mailman mailman 352 Oct 25 2023 mailman-hyperkitty.cfg > drwxr-xr-x 2 mailman mailman 4096 Jul 26 03:11 __pycache__ > <===== Is the presence of this directory expected? > -rw-r--r-- 1 mailman mailman 4971 Jul 26 03:10 settings.py > -rw-r--r-- 1 mailman mailman 863 Jul 25 04:14 uwsgi.ini Yes, in any directory that contains .py files, when those files are imported, a corresponding compiled byte code .pyc file is placed in a __pycache__ directory. This is normal Python 3 behavior. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 3 weeks

[MM3-users] Re: Your Dashboard

by Mark Sapiro

On 2/11/20 1:27 PM, Allan Hansen wrote: > > Our site has over 50 lists and several moderators are responsible for multiple lists. In addition to a dashboard like described here I would like to have a ‘comment’ field next to each request, so tha the moderator can keep track of the status of each. Our approval process involves multiple steps. > > Time to visit gitlab? GitLab is the one place for feature requests for Mailman 3/Htperkitty/Postorius. Things requested in list posts get lost and forgotten. That said, the more specific you can be in a request, the better. I.e., if you want a dashboard, what do you want on it for, e.g., the site admin, a user who may or may not be an owner of a couple of lists, a moderator of a couple more and a member of still others. -- 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: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 3:53 PM, maszap(a)tin.it wrote: > Hi, > > I added the line to the main.cf file > > owner_request_special = no > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = hash:/var/lib/mailman3/data/postfix_lmtp > relay_domains = hash:/var/lib/mailman3/data/postfix_domains > > In my log MTA mail.warn I get: > Jul 13 00:44:56 gamelia postfix/trivial-rewrite[8317]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains What's in your mail.log for a message to and from the list? > I check > my /var/log/mailman3/smtp.log > but is empty If Mailman is sending any mail at all, there should be entries in smtp.log unless the log level is higher than info. What does mailman conf -s logging.smtp show? -- 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: DMARC - was: Disable user registration

by Mark Sapiro

On 3/20/21 4:00 PM, mailman3(a)digicrime.com wrote: > My understanding was that DMARC is merely a superset of DKIM+SPF along with some other policies. I have that set up on some of my domains. The weird part is that DKIM and SPF both passed, but DMARC was failing - I didn't realize it can happen but apparently it can: https://dmarcian.com/how-can-spfdkim-pass-and-yet-dmarc-fail/ Your reference explains it. DMARC requires a valid SPF or DKIM sig with a domain which "aligns" with the domain of the From: address. Your valid SPF and DKIM signature from your domain will not be enough for DMARC to pass because your domain won't "align" with the From: domain. "align" is a technical term defined in RFC 7489. This is what ARC (RFC 8617) is trying to address. -- 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: Migration of archives from Sympa to MM3

by Mark Sapiro

On 2/28/22 10:53, Tom Fillmore wrote: > > Moving existing lists to MM3 looks doable the archives are a different story. Has anyone ever migrated archives from Sympa to MM3? Mailman can import archives where the messages are in a Unix format mbox file. It appears sympa can export archives as a zip file containing monthly files of messages <https://sympa-community.github.io/manual/customize/archives.html>. If these files are in Unix mbox format, HyperKitty's hyperkitty_import function can import them directly, either individually or concatenated. If not, they would need to be processed to add Unix `From ` lines and possibly make other changes. In any case, the mbox to be imported should be checked for unescaped `From ` lines in message bodies with a script such as the one at <https://www.msapiro.net/scripts/cleanarch3>. -- 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: Detectors and Bounces

by Mark Sapiro

On 8/5/22 11:12, summersan(a)nclack.k12.or.us wrote: > > Thank you for refocusing the issue in terms of the "large numbers of bounces", too. > > Here is what I have in `mailman.cfg` for the `[mta]` section: > > `[mta]` > `verp_confirmations: yes` > `verp_personalized_deliveries: yes` > `verp_delivery_interval: 1` > > Does this help narrow down the problem any further? Not really. You need to see why you are getting these bounces. What's in Mailman's bounce.log? Are bouncing users getting their delivery disabled? What are your list(s) `Bounce Processing` settings. In particular, if you set all the `Notify owner ...` settings to `Yes` and `Forward unrecognized bounces` to either `List Admins` or `Site Admin`, what do you see? Also, if there are queued bounces in `/opt/mailman/mm/var/queue/bounces`, you can examine them with `/opt/mailman/mm/bin/mailman qfile` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Twitter OAuth2

by Mark Sapiro

On 12/26/22 06:14, Odhiambo Washington wrote: > I'd like to integrate Twitter OAuth as part of the Social Accounts in my > setup. > I have gone through > https://django-allauth.readthedocs.io/en/latest/providers.html#twitter, but > cannot find the config options to add to my settings. > Does someone have a config block setting for "SOCIALACCOUNT_PROVIDERS =" ? The last I looked into using Twitter as an OAuth2 provider, which was some time ago, it would not work because Twitter would not provide the user's email address via OAuth2. Possibly this could work if the user's name was her Twitter handle. As far as SOCIALACCOUNT_PROVIDERS is concerned, you don't need anything. You just need to create your OAuth2 app and provide the keys via the Django admin SOCIAL ACCOUNTS interface. See https://django-allauth.readthedocs.io/en/latest/providers.html#twitter-oaut… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: IndexError in archiving queue

by Mark Sapiro

On 3/16/23 04:13, Jacob Sievert via Mailman-users wrote: > Hello, > > it seems I have forgotten where I can kick an email out of the archiving > queue as it produces this error in a loop. > Might one of you know where I can do that? > Thanks in advance. The underlying error is a bogus Message-ID header in the message. We have observed cases of Message-IDs like Message-ID: <[d1e99408882e4aed93b0df4c1c28dfa3-JFBVALKQOJXWILKNK4YVA7COOVDWK5D4IVWWC2LMKB2WE3DJONUGK4T4IV4G6U3NORYA====(a)microsoft.com]> where the `[` and `]` are the problem. See the report at https://gitlab.com/mailman/mailman/-/issues/732 and fix for that at https://gitlab.com/mailman/mailman/-/merge_requests/1099 I would like to see the headers of the message in your case. To answer your question, the offending message is queued in Mailman's var/archives/hyperkitty/spool/ directory and can be examined with Mailman's `mailman qfile` command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Mark Sapiro

On 10/19/23 12:30, Wikinaut wrote: > Now I wanted to start uwsgi, after having setup everything as documented but I got in the error log this: > > ModuleNotFoundError: No module named 'allauth.account.middleware' As it says at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… "Note either downgrade django-allauth or update MIDDLEWARE, but not both." Now you have added 'allauth.account.middleware.AccountMiddleware' to MIDDLEWARE and downgraded django-allauth<0.56. You can either do ``` pip install --upgrade django-allauth ``` or remove ``` x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x ``` from /etc/mailman3/settings.py. Either will do, but DO NOT DO BOTH. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Removing a moderator via the REST API

by Mark Sapiro

On 11/15/24 06:38, Andy Matthews wrote: > > Given a list address of announce(a)bar.com, and a subscriber of andy(a)bar.com, the API endpoint would be: > ``` > 'lists/announce.bar.com/moderator/andy@bar.com' > ``` > > Is that correct? Yes. > One question, I think I assumed that removing a user from the list would also cascade to remove any roles that user may have had. So we're currently POSTing to `lists/announce.bar.com/roster/member`, and I was expecting that to also remove the moderator role. But it sounds like it would require an extra call to explicitly remove them as moderator? Yes, member, nonmember, owner and moderator roles are all separate. removing a user from one of those roles has no effect on any other role the user might have. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Cannot Install Web UI

by Mark Sapiro

On 10/23/25 11:57, dap1--- via Mailman-users wrote: > OK, so gnuicorn is easier to install and set up. However, it has its own glitch not in the docs. I'm getting the following error trying to start web: > > gunicorn[42860]: !!! > !!! WARNING: configuration file should have a valid Python extension. This is just a warning and can be ignored. > gunicorn[42860]: !!! > gunicorn[42860]: Error: Error: '/opt/mailman/mm/var/logs/error.log' isn't writable [PermissionErr> > > The docs say to use conf but I think the error implies it should be py. In addition I'm guessing I have to change the log and access file names to something like gunicorn.error.log. The access.log and error.log names are correct. They should be owned by `mailman` and your /etc/systemd/system/mailmanweb.service should include User=mailman -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: hyperkitty threads by month question

by Mark Sapiro

On 7/25/24 11:20, Bryan Fields wrote: > Sorry for the delay, I was on some travel last week. > > On 7/19/24 7:30 PM, Mark Sapiro wrote: >> That URL gives me as server error. What's in the Django (mailman-web) >> logs for that? > > I did notice hitting a 500 error on occasion, sometimes it works. I just tried it twice more and got the error both times. > When this happens, I get an email error below. This is really wierd. See below. >> Are you running all the Django periodic jobs and is qcluster running? > > Ok, the docs said that qcluster service wasn't needed under uWSGI > https://docs.mailman3.org/en/latest/install/virtualenv.html#automatically-s… > qcluster does appear to be running: Right, you don't need to create a separate service for it with our recommended uWSGI configuration because uWSGI runs it, but it does need to run. ... > line 88, in reverse > return resolver._reverse_with_prefix(view, prefix, *args, **kwargs) > File > "/opt/mailman/venv/lib/python3.10/site-packages/django/urls/resolvers.py", line 828, in _reverse_with_prefix > raise NoReverseMatch(msg) > > Exception Type: NoReverseMatch at > /archives/list/nanog(a)nanog-mm3.keekles.org/ > Exception Value: Reverse for 'hk_archives_with_month' with keyword > arguments '{'year': 999, 'mlist_fqdn': 'nanog(a)nanog-mm3.keekles.org', > 'month': 12}' not found. 2 pattern(s) tried: > ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/(?P<year>\\d{4})/(?P<month>\\d\\d?)/$', 'hyperkitty/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/(?P<year>\\d{4})/(?P<month>\\d\\d?)/$'] > Raised during: hyperkitty.views.mlist.overview It appears to be trying to get the threads for December, 999. What do these queries show? SELECT * FROM hyperkitty_thread WHERE EXTRACT(year FROM date_active) < 1000; SELECT id FROM hyperkitty_email WHERE EXTRACT(year FROM date) < 1000; -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mark Sapiro

On 9/18/20 12:48 PM, Phil Stracchino wrote: > On 2020-09-18 15:32, Mohsen Masoudfar wrote: >> Hi, >> >> I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped. > > > Assuming that this works roughly the same in mm3 as it does in mm2, you > can set max_message_size in your list configuration. It defaults to 40; > units are KB. Yes, and you can set it to zero for "unlimited", but even if that is a satisfactory workaround, the much more interesting question, at least to me, is why does the message "disappear". -- 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: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Mark Sapiro

On 10/19/23 11:48, Wikinaut wrote: > > I was "_forced_" :-) to install that in one of the very first steps of the documentation. https://docs.list.org/en/latest/install/virtualenv.html#installing-mailman-… > > What I suggest is: > > I will (try to help) to fix the documentation, so that it also can work for mysql. > Please, I am willing to help. It seems to me that adding a sentence following "This will install latest release of Mailman Core, and Python bindings for Postgresql database." such as "If you are using a different database manager, do not install psycopg2-binary." would suffice. What do you think? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

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

by Mark Sapiro

On 07/30/2018 07:37 AM, Ryan McClung wrote: > GNU Mailman 3.2.0 (La Villa Strangiato) > Python 3.6.5 (default, Apr 10 2018, 17:08:37) > [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] > config file: /opt/mailman/var/etc/mailman.cfg > db url: sqlite:////opt/mailman/var/data/mailman.db > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > > Shortly after I run an import on a bunch of lists they all disappear. > [root@mailman3(stg) mailman]# mailman lists > No matching mailing lists found > > I have 30+ lists. Does the 'mailman lists' command invoke the identical 'mailman' file as the 'mailman import21' command that did the imports. And how did you create the lists before importing them? We have done several imports of 2.1 lists to <https://mail.python.org/mm3/mailman3/> and have never seen an issue like this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

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

by Mark Sapiro

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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Moderation emails

by Mark Sapiro

On 3/3/21 7:59 PM, peter(a)chubb.wattle.id.au wrote: > > The third part is another message/rfc822 part that says, > If you reply to this message, keeping the Subject: header intact, > Mailman will discard the held message. The 'this message' in that text refers to the message in the message/rfc822 part. I know it's confusing, but it's been that way since Mailman 2.1.0. That said, it should be fixed. It should at least say "If you reply to this attached message part, not the outer message, keeping ...". It also refers to an Approved: header with the list password, and there is no list password. There is a moderator_password which works in this context, but it is rather obscure. Not only that, but it doesn't work anyway. See <https://gitlab.com/mailman/mailman/-/issues/631> and <https://gitlab.com/mailman/mailman/-/issues/169> -- 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: Using Header filters

by Mark Sapiro

On 8/13/21 10:55 AM, Mohsen Masoudfar wrote: > Hi, > > I wonder if it is possible using the "Header filters" option to filter for a specific word to push the message to Moderation? You can use Header filters to hold for moderation any messages that have a header matching a pattern. The pattern match is unanchored and case insensitive so for example to hold for moderation any message which contains the string `word` or `Word`, etc. anywhere in the Subject: you would create a Header Filter with Header = subject, Pattern = word and Action = Hold for moderation. If you want to match only the word `word` and not things like `foreword` and `wordless`, you'd use a pattern like (^|\W)word(\W|$). See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…> and <https://docs.python.org/3/library/re.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, 7 months

[MM3-users] Re: Whitelist in mailman3: How to allow only ~400 e-mail senders in a file whitelist to send to a list?

by Mark Sapiro

On 8/3/25 13:52, Wikinaut wrote: > In mailman2, it was quite handy to place "@whitelist" into the field sender/accept_these_nonmembers, when such a file has been set up. > > How can I (per list or programmatically) define the ~400 e-mail senders to be allowed to send to my about 30 lists? > And, yes, I already searched for a solution of this problem, but could not find any. This feature was added in Mailman core 3.3.10. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… https://gitlab.com/mailman/mailman/-/issues/794 https://gitlab.com/mailman/mailman/-/merge_requests/1154 and documented in postorius 1.3.13. See https://gitlab.com/mailman/postorius/-/issues/589 https://gitlab.com/mailman/postorius/-/merge_requests/938 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 2 weeks

[MM3-users] Re: localhost[::1] said: 550 Requested action not, taken: mailbox unavailable

by Mark Sapiro

On 10/26/2017 11:30 PM, Bjoern Franke wrote: > > Oct 27 08:24:58 srv20 postfix/lmtp[2981]: 8798E40979: > to=<admin(a)lists.ffnw.de>, relay=localhost[127.0.0.1]:8024, delay=0.51, > delays=0.43/0.02/0.02/0.03, dsn=5.0.0, status=bounced (host > localhost[127.0.0.1] said: 550 Requested action not taken: mailbox > unavailable (in reply to end of DATA command)) This may be a Mailman bug. I'll look further when I have time. The message above says that Postfix tried to deliver the message to Mailman's lmtp runner and the runner said there was no such list. I'm guessing that there may be confusion between the admin@... list address and a listname-admin@... address. If this is the case, it means there is a bug which would affect any lists named 'admin', 'bounces', 'confirm'. 'join', 'leave', etc. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

[MM3-users] Re: Change settings via mailman shell

by Mark Sapiro

On 3/6/19 1:32 AM, kk(a)eco.cept.org wrote: > I am trying to find a way to set some parameters on the lists from a shell script. One specific parameter - max_message_size is not presented through the REST interface apparantly, and i found a way to set this with mailman shell command. Continuing this path i seem not to be able to set any other parameters like this: > m.archive_policy = 'never' You can't set archive_policy to a string. it has to be set to an attribute of mailman.interfaces.archiver.ArchivePolicy i.e. from mailman.interfaces.archiver import ArchivePolicy m.archive_policy = ArchivePolicy.never See <https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/archives…> > m.subject_prefix = '' > m.dmarc_mitigate_action = 'munge_from' Likewise dmarc_mitigate_action is an attribute of mailman.interfaces.mailinglist.DMARCMitigateAction See <https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/dmarc-mi…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Strange URL in error message

by Mark Sapiro

On 7/14/24 9:14 AM, waps(a)tantalus.jena.thur.de wrote: > (Debian 12) > > I have the problem that the hyperkitty archive is empty. The file /var/log/mailman3/mailman.log show sometimes the message > > urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='www.XXXXX-project.demailman3', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/archive (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fa48b43a910>: Failed to establish a new connection: [Errno -2] Name or service not known')) > > (there is a slash missing between 'project.de' and 'mailman3'). My goal is, of course, to have an running archive. But I think the error message could be a hint about the reason) It appears that your setting for base_url in mailman-hyperkitty.cfg is missing the slash. I.e., it is http://www.XXXXX-project.demailman3/ and should be http://www.XXXXX-project.de/mailman3/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 10/2/24 20:33, jkoral(a)luc.edu wrote: > Not sure if this means anything. This is the log from old server after trying to send. I edited the FQDN and IP though. Any thoughts? I think it may be the configuration of postfix on the new server though. > > Oct 2 22:26:59 listservls01 postfix/smtp[139911]: B1FD27ED: to=<test(a)listservnew.example.com>, orig_to=<olivertest(a)lists.luc.edu>, relay=listservnew.example.com[x.x.x.x]:25, delay=0.01, delays=0/0/0.01/0, dsn=4.4.2, status=deferred (lost connection with listservnew.example.com[x.x.x.x] while receiving the initial server greeting) The message is deferred. Postfix will keep trying for maximal_queue_lifetime (default 5 days). Possible causes are a firewall on the new server blocking port 25 connects or some postfix misconfiguration on that server. Can that server receive mail at all? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Confirm and Moderate Unsubscribe Requests

by Mark Sapiro

On 10/21/20 8:53 AM, Brian Carpenter wrote: > If you set the unsubscription policy to confirm then moderate for a list > and someone unsubscribes, they receive a confirmation request. That is > good. They respond to it. That is also working fine. However the list > owner/moderator than gets a request to approve the unsubscribe request > and well, unless I am missing something, I don't see an interface to > handles such requests via Postorius. This is <https://gitlab.com/mailman/postorius/-/issues/332>. > How does one handle an unsubscribe request that requires moderator > approval? I'm not sure at this point, I can look further later, but if the notice to the admin has a token, it might work to send a `confirm <token>` command to the list-request address. Otherwise, don't moderate unsubscription requests. -- 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: High memory usage

by Mark Sapiro

On 2/16/22 00:18, Philip Colmer wrote: > Thank you for the replies from Mark and Stephen. > > One of the reasons why Prasanth & I are concerned with this specific system > is because the first time memory usage crept up, it got to the point where > oomkiller stepped in and, as is usual for that particular mechanism, one of > the processes it killed was sshd, thus removing access to the system :(. I > know that oomkiller can be tuned to stop it killing processes like sshd but > it will, nevertheless, start killing *some* processes if it sees an out of > memory situation. It sounds like there is a memory leak somewhere. This is an issue with some versions of Python. I know both Python 3.10.2 and 3.9.10 were released ahead of schedule to fix this. See https://bugs.python.org/issue46347 -- 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: Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )

by Mark Sapiro

On 1/9/23 05:31, Johannes Rohr wrote: > > Thanks! I assume, there is a reason why this cannot be easily > implemented, else it would have been. Asking because I know a number of > people would make extensive use of this in MM2. The actual implementation is probably not difficult, but it's more than just handling things like `@list_id` in *_these_nonmembers. It also requires developing appropriate unit tests, updating REST and `mailman import21` to accept the syntax and documentation updates at least for Postorius Settings -> Message Acceptance -> * these non-members. That adds up to a significant amount of work. I recognize it's a significant regression for some, but we are a small, all volunteer project and can't do everything. A well crafted merge request would certainly be accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by Mark Sapiro

On 11/18/24 23:13, mark(a)suburbia.org.au wrote: > - Modified second test user to "Hold for moderation" in Members list. Noted the Moderation was set to "List default" before changing it to "Hold for moderation" The actual value is None, but Postorius displays/sets that as List default. >> If that is true, I can only think that at the time of that post, >> settings weren't as they are now. > > I think for now I will have to assume that's the case, until the next email can be readied against the proper list. If you hear nothing further, assume that this was all based on some random quirk (by humans or machines). I'll update if it happens again. Thank you for doing the test. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: mailman addmember/syncmember commands print undecoded UTF-8 [ADD] or [DEL] mail addresses in its messages like "[ADD] =?utf-8?q?John_=....."

by Mark Sapiro

On 8/6/25 04:44, Wikinaut wrote: > Dear Mark, > > the problem has not gone. Now, in production during regular list upgrades, I got one member with 2(two) entries, one regularly encoded, the other double-escaped (can we call that so?). I'm interested in exactly what is done to produce these entries. Are you running `mailman syncmembers` or `mailman addmembers`? If so what is the input file that produces this. You can send it to me off list. > If you send me your private address, I can send you a screenshot. You can email me off list at the address in this and all my other posts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/8/25 13:25, dap1--- via Mailman-users wrote: > Same as before. > > <venv> $ mailman info > GNU Mailman 3.3.10 (Tom Sawyer) > Python 3.12.3 (main, Aug 14 2025, 17:47:21) [GCC 13.3.0] > config file: /opt/mailman/var/etc/mailman.cfg And is /opt/mailman/var/etc/mailman.cfg now a symlink to /etc/mailman3/mailman.cfg? If not, make it so. If it is you could try rm /opt/mailman/var/etc/mailman.cfg cp /etc/mailman3/mailman.cfg /opt/mailman/var/etc/mailman.cfg > db url: sqlite:////opt/mailman/var/data/mailman.db > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass > > It is getting late here so I probably won't get back to this until tomorrow. Thanks for your help and sorry for being a PITA. We want to help. The only pain is when you don't provide requested information. -- 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: Difficulties setting up MM3 with Postfix MTA in Docker Environment: Invalid EHLO domain name & Authentification as lists.local

by Mark Sapiro

On 10/21/18 4:51 AM, Niklas Frühauf wrote: > > To me it seems like mailman is trying to authenticate as “lists.local” or “mail.local” or “localhost” to postfix (which of course isn’t working), then issues a EHLO/HELO to postfix which is not a FQDN. If the MTA requires authentication, you need to set smtp_user: and smtp_pass in the 'mta' section of mailman.cfg. By default, these are empty which means Mailman will not attempt to authenticate to the MTA for outgoing smtp. The actual connection to the MTA is via Python's smtplib. See <https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/authenticatio…> and <https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/connection.ht…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

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

by Mark Sapiro

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

7 months, 3 weeks

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

by Mark Sapiro

On 7/31/25 10:38, Odhiambo Washington via Mailman-users wrote: > > In one response, he mentioned that "Other mailinglists on the same host are > doing fine. Even a 1:1 copy of the list works - only the original list does > not work". > Does it mean that "the issue is in the outgoing runner" only for a single > list? So far we have not determined what the issue is. Until we do, we don't know in which module it is. It could be in outgoing runner involving something in the list's configuration or membership that isn't in the "1:1 copy" or it could be something to do with the message itself. It could even be an OS error such as "out of memory" due to the large number of list members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 3 weeks

[MM3-users] Re: Issue with Held Messages

by Mark Sapiro

On 08/19/2016 10:39 PM, Jean-Luc Wasmer wrote: > On 2016-08-19 17:58, Mark Sapiro wrote: >> On 08/17/2016 09:17 PM, Jean-Luc Wasmer wrote: >>> >>> No matter what action I set for member posts (Hold for moderator, >>> Reject) they are always delivered. >> >> >> I don't know why this would be. Perhaps the member's moderation is set >> to Accept immediately - you can see this on ther member's options page >> in Postorius when logged in as a list owner. > > Apart from "Mode of Delivery" that is set to "Regular" for the user, > none of the following attributes are set: > > Mail Delivery > Receive own posts to the list > Receive acknowledgement mails > Conceal address from the subscriber list > Avoid duplicate copies of messages If you look at the user's options when logged in as a list owner, you should see an additional "Administration options" section below those with a "Moderation" setting. What is that set to? ... > By the way, I didn't mention before but in Settings | Message > Acceptance, the "Acceptable aliases:" box contains "[]". When I try to > Save changes after modifying something, I gut "An error occured: []" in > the yellow banner (instead of "The settings have been updated."). What happens if you clear the Acceptable aliases box before saving? ... >> This is apparently <https://gitlab.com/mailman/mailmanclient/issues/10> >> fixed by <https://gitlab.com/mailman/mailmanclient/merge_requests/16> > > Any ETA when this will be pushed to "mailman-bundler"? I expect bundler will be updated when 3.1 is released and that should be soon. You may find <https://wiki.list.org/x/17891998> of interest. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 7 months

[MM3-users] Re: Weird hourly indexing error

by Mark Sapiro

On 6/9/20 9:29 PM, Mark Dadgar wrote: > On Jun 9, 2020, at 1:57 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> THANK YOU for all the help. >> >> >> I'm glad we finally got it resolved. > > > I may have spoken too soon: > > [ERROR/MainProcess] Failed indexing 1 - 1000 (retry 5/5): Term too long (> 245): XSUBJECT95251413 (pid 729081): Term too long (> 245): XSUBJECT95251413 > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", line 97, in do_update > backend.update(index, current_qs, commit=commit) > File "/usr/local/lib/python3.8/dist-packages/xapian_backend.py", line 492, in update > database.replace_document(document_id, document) > xapian.InvalidArgumentError: Term too long (> 245): XSUBJECT95251413 > > "XSUBJECT95251413“ has some serious weirdness embedded in it. > > Not sure how to search for that in the django shell? I suspect the issue here is the 'weirdness' is in the Subject: rather than the message body. The script we were using only looked at the body. The message you sent me had a Subject which visually looked like `[PDC] MEGAMillions- Ticket №7383246 9` but the № and the digits were interspersed with strings of unicode zero width spaces, so the decoded Subject: was actually '[PDC] MEGAMillions- Ticket №7\u200b\u200b\u200b\u200b\u200b\u200b\u200b3\u200b\u200b\u200b\u200b\u200b\u200b\u200b8\u200b\u200b\u200b\u200b\u200b\u200b\u200b3\u200b\u200b\u200b\u200b\u200b\u200b\u200b2\u200b\u200b\u200b\u200b\u200b\u200b\u200b4\u200b\u200b\u200b\u200b\u200b\u200b\u200b6\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b9\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b' where all the \u200b unicodes are the zero width spaces. I suspect your current issue is with the Subject:. Actually, looking back at the thread, the prior one probably was too, but we also found messages that had this in the body. To alter the specific script to look at the Subject: just change the line if email.content.find('\u200b'*5) >= 0: to if email.subject.find('\u200b'*5) >= 0: There's probably a reply there somewhere that has the Subject: but didn't quote the bad stuff in the body. -- 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: Memory footprint

by Mark Sapiro

On 04/10/2017 02:25 PM, David Krantz wrote: > Hi. > > Now running mailman 3 I am a bit surprised that the memory footprint > is so large. I count to 13 processes with each a virtual space of > 160-250MB and a reserved space of about 50MB each. Not much, but quite > much to run on smaller cloud instances which generally have limited > memory. This is (a lot) more than the corresponding postgres > installation uses, > > Is this normal? Those numbers seem "normal" but you really have to look deeper to understand if you just have a bunch of processes sitting in memory because the memory is available and nothing else wants it, or if there's real memory contention going on. The article at <https://wiki.list.org/x/4030711>, while written about Mailman 2.1, has some general information which may be of interest. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

[MM3-users] Re: Template Ignored?

by Mark Sapiro

On 2/17/22 10:10, Stephen Daniel wrote: > 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:… You are using Mailman core's REST API which is wrong. You need to get the template from Postorius. Maybe something like http://localhost/postorius/api/templates/list/list.example.com/list:user:no… Where http://localhost/postorius/ is the URL you use to access Postorius, maybe mailman3 instead of postorius. Once you figure that out, POSTORIUS_TEMPLATE_BASE_URL is just the scheme and domain part of that. -- 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: Subscribing users stuck in pending hell

by Mark Sapiro

On 5/24/23 08:11, Quanah Gibson-Mount wrote: > Hi, > > We frequently end up with users who never receive their email to confirm > their account, leaving them in a netherworld where they cannot become > list members. If I try to subscribe them via the mass subscribe option, > it says I can't because their subscription is pending. If I go to > subscription requests, it says there are 0. If I go to "non-members" in > the UI, I can find them, but I don't see an option to convert them to > members. Subscription requests says 0 because it only counts those pending moderator approval, but if you pull down the menu and select Pending Confirmation, it should show the request and enable you to delete it, and then mass subscribe will work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: General question mailman3: message sender acceptance "always"

by Mark Sapiro

On 10/23/23 05:41, Wikinaut wrote: > > I could not find such an option (in the moderation dialog) in Mailman3 (only "accept" or "reject" and "discard", but "accept and add to white-list = accept always"). In the Postorius held messages view, click on the message's subject to open a dialog showing the messages content and a dropdown to set the moderation for this user and a box to enter a reject reason if you are going to reject the message. If you want to accept further messages from this yser, it is best to set moderation to Default processing rather than Accept immediately as the latter bypasses other checks that could result in the message being held. Note that even though the dropdown says Set member moderation, it works for non-members too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: repeated headers in mails from mailinglists

by Mark Sapiro

On 7/12/24 11:30 PM, Tobias Diekershoff wrote: > Dear all, > > we have recently migrated from Mailman2 to Mailman3 and now discovered > that all mails going through Mailman3 have the headers Archived-At and > List-Archive repeated identically in the mail header ~100 times each. This should definitely not happen unless mailman/handlers/rfc_2369.py is broken. > We are running Mailman3 on Debian Bookworm from the Debian repositories > (mailman3 3.3.8-2~deb12u2) with postfix (3.7.11-0+deb12u1) and > hyperkitty (1.2.1-1). This may be a Debian issue. See https://wiki.list.org/x/12812344 > Can somebody of you help me to get rid of the repeated header? You could in Postorius set Alter Messages -> Include RFC2369 headers to No, but this will not include any of the List-* or Archived-At headers at all which is not what you want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: makemigrations --merge error after Debian upgrade

by Mark Sapiro

On 9/30/24 03:00, Chupin Maxime via Mailman-users wrote: > Hi, > I upgraded my debian version, Issues with the Debian Mailman packages should be reported to Debian. Please see https://wiki.list.org/x/12812344 and https://mail.python.org/archives/list/mailman-users@python.org/message/T6LB… > and since, it seems that I have a problem. I tried `mailman-web migrate` (and `mailman-web collectstatic` etc.) and I get the error message: > ``` > CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0010_auto_20220618_2315, 0014_schedule_cluster in django_q; 0014_auto_20220618_2315, 0018_alter_emailtemplate_language in postorius). > To fix them run 'python manage.py makemigrations --merge' > ``` > So I tried `mailman-web makemigrations --merge` that ended with > ``` > PermissionError: [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/postorius/migrations/0019_merge_20240930_1159.py' > ``` Did you run this as the Mailman user (`list` in the Debian packages)? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Connection lost during _handle_client()

by Mark Sapiro

On 11/27/24 5:58 PM, Alain D D Williams wrote: > Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) connection lost > Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) Connection lost during _handle_client() > > I am concerned about the connection lost message above. It is normal and not a concern. > Mailman sees it, the message ID matches that at the end of the first line > in the exim log (above): > /var/log/mailman3/mailman.log > Nov 28 00:59:45 2024 (1268377) ACCEPT: <Z0fAe9xODd2y33N8(a)phcomp.co.uk> So Mailman got the message and accepted it. > Is there any more logging that I can look-at/switch-on to see what is happening ? Is there anything else in mailman.log? Does the message get archived? Is there anthing in any of Mailman's var/queue/* directories? Is Mailman core running? Does `mailman members --nomail enabled` list any members? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Apple Mail encoding again

by Mark Sapiro

On 4/14/22 08:21, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > That combination at least produces multipart/signed messages with > > multipart/* parts containing a Content-Transfer-Encoding: header. > > > > The Python 3 email library considers this to be a > > InvalidMultipartContentTransferEncodingDefect() message defect. > > Merely containing C-T-E is not an error per RFC 2045, although it > seems to consider it a stupid thing to do. If present, it may be > "binary", "7-bit", or "8-bit" (below summarized as "cleartext"). > > Did Apple Mail apply a non-cleartext C-T-E? Or has an RFC tightening > that restriction been published since? (I don't know why it would, > though.) Yes. The C-T-E on all the multipart parts was quoted-printable, not allowed under RFC 2045. > Even with a non-cleartext C-T-E, it seems reasonable for Mailman to > treat it as application/octet-stream and pass it through, unless the > list is configured to do something like strip application/octet-stream > or that requires decoding like spam-filtering (Postel principle, > although one could argue it shouldn't be sent on on the same principle > -- ah, the joys of being an e-mail Mediator). That would be > especially true it if were quoted-printable, since any relevant MIME > headers would (presumably) be pure ASCII and therefore unencoded. The Python email library says the message is defective. Mailman's lmtp runner in turn rejects the defective message with a 501 status https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… It could accept a defective message or one with specific defects, but this is problematic for further processing. For example, at least one MUA, Thunderbird, renders such a message with an empty body. -- 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: ARC issues

by Mark Sapiro

On 3/2/20 7:45 AM, Stephen J. Turnbull wrote: > David Krantz writes: > > > Is there any known issues with ARC that I should be aware of? > > Doesn't Postfix do ARC yet? :-( rspamd seems to be recommended by a > couple of Linux distros, supports the milter interface that Postfix > uses to call out to 3rd party processes, and the website looks good. > See rspamd.com. That said, if you want to use Mailman's support... I've been trying openarc <https://github.com/trusteddomainproject/OpenARC> with Postfix as well as Mailman's ARC. I still haven't got it all worked out - I have a fairly convoluted mail flow with the possibility of messages being altered before they ever get to Mailman. There is an issue with Mailman's ARC signing in a supporting library. See <https://github.com/ValiMail/authentication-headers/issues/5>. -- 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: Where do I find the check_hk_archive script

by Mark Sapiro

On 11/18/23 11:21, Lars Bjørndal wrote: > In https://docs.mailman3.org/en/latest/migration.html I'm adviced to run > the check_hk_archive script found in hyperkitty/contrib. When trying > `git clone https://gitlab.com/mailman/hyperkity`I get: > > Username for 'https://gitlab.com': > > Is it possible to get the script without an account on gitlab? I've updated some project settings. You should now be able to `git clone https://gitlab.com/mailman/hyperkity` without a gitlab account. However, why are you wanting to do this. If you have HyperKitty installed, there should be a hyperkitty/contrib directory in your installation, e.g. /opt/mailman/venv/lib/python3.x/site-packages/hyperkitty/contrib/ containing the check_hk_import and cleanarch3 scripts. Even if you don't have that, you can download the script from https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/chec… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: "mailman start" hangs

by Mark Sapiro

On 02/13/2018 05:40 AM, Peter Münster wrote: > Hi, > > When starting mailman in a terminal, then it works: > > --8<---------------cut here---------------start------------->8--- > $ mailman start > Starting Mailman's master runner > $ > --8<---------------cut here---------------end--------------->8--- > > But from "cron", it seems to hang. Output of pstree: > > --8<---------------cut here---------------start------------->8--- > |-cron(3022)---cron(21962)-+-mailman(21986) > | `-sendmail(22043)---postdrop(22044) > --8<---------------cut here---------------end--------------->8--- > > So it seems, that mailman does not go into the background, and the email > with the output is never sent... I think Abhilash's answer is probably closer to the mark, but there can be issues with running 'mailman' from cron or init scripts which don't set a UTF-8 compatible LANG in the environment as described at <http://mailman.readthedocs.io/en/latest/src/mailman/docs/install.html#runni…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

[MM3-users] Re: Changing posting address

by Mark Sapiro

On 11/7/18 10:59 PM, Johannes Winter wrote: > Dear list, > > I'd like to change the sending address of a mailinglist, but when I try > to set it via mmclient with > > ./manage.py mmclient > lists=client.lists > l=lists[listnumber] > l.settings['posting_address']='new name' > > > I get `ValueError: value is read-only`. > > Is it possible to change this value, or should I use another setting > for this objective? You can't change the list's posting_address. You have to change the list_name which you can't do via mmclient, but you can do via 'mailman shell'. If you want to change the posting_address without changing the list name, you can alias the desired posting address to the list_name@domain address in the MTA and add the desired posting address to the list's acceptable_aliases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: Shunt Error Mail?

by Mark Sapiro

On 3/2/21 2:52 PM, Pete Ashdown wrote: > I have a number of list managers with subscribers who are confused as to > why their messages are silently disappearing. I've read the archives on > how to decipher why a message was shunted, but this is not workable at > scale. Is sending an error email back to the sender a consideration? Why are messages being shunted? Each shunted message has thrown some kind of uncaught exception which is logged with a traceback in Mailman's mailman.log. These should be due to bugs that should get fixed or possibly malformed messages which are almost always spam. In short, under normal circumstances messages should not be shunted at all and when they are it is something the site admins need to address. It is normally not something the sender of the message can do anything about. -- 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: Help! List traffic shunted to gmail/yahoo spam folders

by Mark Sapiro

On 7/10/21 2:42 PM, Matt Wilbur EFS via Mailman-users wrote: > Hello, > > I've been through DKIM hell and back. Now I'm to the point where when I > "show original" mail with gmail it says SPF, DKIM and DMARC all pass, > but it's still going to the spam folders. Does your list domain publish a DMARC record? If not publishing a DMARC record with policy of none may help, but it seems you are probably doing that. Beyond that, it is probably filtering based on something in the message content and the recipient ISPs will never tell you what because they consider that kind of information proprietary. Setting up feedback loops with gmail and yahoo also may help, but there's really not much else you can 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, 8 months

[MM3-users] Re: Template - "You can use these variables in the templates" - The variable for "leave" is missing

by Mark Sapiro

On 11/4/23 06:28, Stephen J. Turnbull wrote: > Wikinaut writes: > > > fxied in merge request > > https://gitlab.com/mailman/postorius/-/merge_requests/852 > > I wish you wouldn't. It's just bloat in the code and in the > docstring. Better to document that the administrative addresses can > be constructed using ${short_listname}. I believe Mailman still > supports both "list-leave" and "list-unsubscribe", as well. Actually, https://gitlab.com/mailman/postorius/-/merge_requests/852 only added documentation of the existing $description replacement which is appropriate, but it duplicates part of https://gitlab.com/mailman/postorius/-/merge_requests/851 which does that and adds a bit more documentation. Also see https://gitlab.com/mailman/mailman/-/issues/1108 and https://gitlab.com/mailman/mailman/-/merge_requests/1153 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: False attachments in Outlook 2019?

by Mark Sapiro

On 1/24/21 3:29 AM, Brian Olesen wrote: > Dear Mailman 3 users, > > I seriously think of upgrading from Mailman 2.1.33 to this new RC2 or the > final one, when it comes out. > > > > But there is an annoying issue that I'd like to ask you about. > > It's the false attachments that Outlook creates for the footer. Is this > still an issue when using Mailman 3, or have you made some sort of work > around? See the FAQ at <https://wiki.list.org/x/4030707> for a discussion of why we don't try to insert headers and footers into HTML message parts. This applies to Mailman 3 as well as Mailman 2.1. I don't know if anyone has tried it, but the MIMEDefang solution mentioned in the FAQ would probably work with Mailman 3. -- 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: Unable to get Postfix to bounce messages to non-existent lists

by Mark Sapiro

On 2/19/24 09:14, skenny(a)scss.tcd.ie wrote: > > The only problem with this is that if someone sends a message to a non-existent mailing list, Postfix nevertheless accepts the mail, and it loiters in the queue for several days before eventually being bounced back to the sender. I want to get Postfix to reject mail to non-existent mailing lists immediately. I've come up short with each variation of main.cf settings I've tried, and would greatly appreciate any advice. What is Postfix's reason for deferring the mail - `mailq` will show the reason. What if you just omit the relay_domains = regexp:/var/mailman-data/postfix_domains setting. This may cause all list mail to be rejected, but it may work (I'm not sure if transport_maps takes priority). -- 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: Hyperkitty search on Message-ID?

by Mark Sapiro

On 12/5/24 04:25, Bryan Fields wrote: > I've been working with a rather large import and am finding that I can't seem > to get the search on a Message-ID: to return anything. ... > Any ideas how to get it indexing the ID so a layperson can search on it? Message-ID is not one of the fields indexed. These are defined at https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/search_index… A bit obscure for laypersons, but one can compute the message_id_hash from the Message-ID ``` from base64 import b32encode from hashlib import sha1 def get_message_id_hash(msg_id): return b32encode(sha1(msg_id).digest()).decode() ``` I can't help but wonder though how one has the Message-ID without having the message. I'm wondering in general how often if ever the layperson would be searching the archive for a Message-ID. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Mm3 - new adventure

by Mark Sapiro

On 03/15/2017 07:35 AM, SP2L wrote: > > Today started reading belows document: > > http://docs.mailman3.org/en/latest/devsetup.html > > There is evidently misleading command > repeated more than once: > > $ git clone git@gitlab.com:mailman/mailman.git > > (at least, above is not working from Debian command line) > > which should read: > > $ git clone https://gitlab.com/mailman/mailman.git In order to use the former command, you must register for a gitlab account and install your ssh public keys there. This is mentioned in two places in the document at https://wiki.list.org/DEV/SetupDevEnvironment which is the first thing referenced in the document at http://docs.mailman3.org/en/latest/devsetup.html It also needs to be mentioned at http://docs.mailman3.org/en/latest/devsetup.html Thanks for pointing that out. This is now reported at https://gitlab.com/mailman/mailman-suite-doc/issues/3 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] Re: mailman.cfg (use_https: yes) fails

by Mark Sapiro

On 11/16/19 4:54 AM, Wolfgang Bock via Mailman-users wrote: > I will look at the https issue further when I get time. > In this context I faced a strange behavior: > > In the database mailman3web in table django_site are listed several > domains, either in the django-domain-management site > https://[mydomain]/mailman3/admin/sites/site/ > > id domain name > 1 example.com Example.com > 2 [mydomain-1] [mydomain_name_1] > 3 [mydomain-2] [mydomain_name_2] > 4 [mydomain-3] [mydomain_name_3] > > In case I delete line 1 with the id 1, in the database or in the > django-web-site, postorius fails to work. After re-inserting this line, > postorius works again. In your settings.py, you probably have SITE_ID = 1. Thus, when you delete the site with id = 1, Postorius fails. You need to set SITE_ID to an existing site in settings_local.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

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

by Mark Sapiro

On 7/28/20 1:07 PM, joseverde(a)gmail.com wrote: > [Does your systemd script set the user to the Mailman user, and does the > Mailman user have read/write permission on Mailman's var/locks/?] > > How do I check for that? ls -la /path/to/mailman/var/locks > Also, what's the difference between the mailman command and the systemctl mailman3? Are they the same processes? Presumably your mailman3.service actually uses the `mailman start` command to start Mailman. The `mailman` command is a shell with many subcommands for various purposes including starting and stopping Mailman. > Oh and does the /3.1 matter at the end of the Rest url for Django? Do not put the 3.1 at the end of your MAILMAN_REST_API_URL. Postorius adds it. See <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/utils.py#L…>. -- 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: web api

by Mark Sapiro

On 8/4/21 10:44 AM, Ethan Furman wrote: > Greetings again! > > Is there a remote API I can use to manage a list? Mailman core's REST API is documented at <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. By default it listens only on localhost:8001 and requires authentication with user = restadmin and password = restpass but these are all settings in the webservice section of mailman.cfg. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> for the settings and their defaults. You could set [webservice] hostname: 0.0.0.0 admin_pass: My_Secret in mailman.cfg to have it listen for connects from anywhere and require a different password. You'd also need to adjust some or all of the settings for MAILMAN_REST_API_URL MAILMAN_REST_API_USER MAILMAN_REST_API_PASS In your Django settings. There is also <https://gitlab.com/mailman/lemme> however, that's only a skeleton and not useful as is. -- 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: OK, so I backed out completely and re-installed. Here's my *original* error. Should I modify virtual mailbox maps?

by Mark Sapiro

On 10/16/24 10:26, Bill Oliver wrote: > > 1) I set up a mailinglist (tradfp(a)forensicpath.us) for "old school" > forensic pathologists to discuss cases. Does the forensicpath.us domain have an alias_domain configured in mailman causing mailman to create /opt/mailman/mm/var/data/postfix_vmap and /opt/mailman/mm/var/data/postfix_vmap.db? You need this. > In my previous attempt, I added > > hash:/opt/mailman/mm/var/data/postfix_lmtp > > to both virtual_mailbox_maps and virtual_alias_maps, but I haven't > done that yet here. I thought I'd ask and make sure I should. > > Should that be my next step? You should add hash:/opt/mailman/mm/var/data/postfix_vmap to virtual_alias_maps only. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users]Re: Installation issues

by Mark Sapiro

On 04/20/2016 01:11 AM, Andrew Hodgson wrote: > > My next stab at this was going to be using venvs, but creating the venv as the directory /opt/mailman which gives cleaner paths (to my mind anyway), but haven't got round to doing it yet. You should be aware that mailman-bundler uses two venvs, one for Python 2 and one for Python 3. The idea is you create the Python 2 venv and activate it when running mailman-bundler's buildout, but that process will also create a venv-3.x venv in the bundler directory. I think what may make sense is to clone mailman-bundler directly into /opt/mailman rather than /opt/mailman/mailman-bundler. Then follow the docs from there. This should give you paths like /opt/mailman/venv/, /opt/mailman/venv3.x/, /opt/mailman/deployment/, /opt/mailman/mailman-web/, /opt/mailman/bin/, /opt/mailman/var/ and so on without the extra mailman-bundler/ level. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 11 months

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 07/25/2017 12:35 PM, Rafael Mora wrote: > This is from the file /var/log/maillog: > > Jul 24 17:29:21 localhost postfix/postfix-script[2092]: starting the > Postfix mail system > Jul 24 17:29:21 localhost postfix/master[2096]: daemon started -- version > 2.10.1, configuration /etc/postfix > Jul 25 03:30:05 localhost postfix/pickup[2785]: 03F4160D143F: uid=0 > from=<root> > Jul 25 03:30:05 localhost postfix/cleanup[3191]: 03F4160D143F: > message-id=<20170725073005.03F4160D143F(a)localhost.localdomain> > Jul 25 03:30:05 localhost postfix/qmgr[2113]: 03F4160D143F: > from=<root(a)localhost.localdomain>, size=508, nrcpt=1 (queue active) > Jul 25 03:30:05 localhost postfix/local[3195]: 03F4160D143F: > to=<root(a)localhost.localdomain>, orig_to=<root>, relay=local, delay=0.11, > delays=0.07/0.03/0/0.01, dsn=2.0.0, status=sent (delivered to mailbox) > Jul 25 03:30:05 localhost postfix/qmgr[2113]: 03F4160D143F: removed > > > It seems that postfix is working, isn't it? At least for receiving mail queued by the sendmail command and delivered to root. -- 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: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 4/20/19 10:13 AM, brian(a)emwd.com wrote: > Hi Mark, > > I followed your instructions to confirm the user. When I ran ">> util.confirm('hex_token')" nothing happened which I take it to mean it worked. I then ran ">> list(util.find(mlist=m,pend_type='subscription'))" and the pending member did not show up which I thought was a good thing. But . . . > > I tried to mass subscribe the user and got back: > > "HTTP Error 409: b'{"title": "409 Conflict", "description": "Subscription request already pending"}'" Did you do commit() or exit shell (which does an implicit commit) before trying the mass subscribe? I'm not going to be able to look at this further for some time as I am traveling today, but I will. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Subscribing by E-Mail

by Mark Sapiro

On 5/21/20 4:47 PM, Peter Adebahr via Mailman-users wrote: > > on MM2 systems, we used to subscribe people via an external application > by sending an e-mail to the request address with a subject of > "subscribe address=user(a)example.com" > > This returns a "bad argument" in MM3 - any ideas how to solve this? Currently, a subscribe or join command sent to the -request address only supports one argument, `digest=<no|mime|plain>`. To subscribe an arbitrary address, you can send to the -join or -subscribe address with the From: set to the address you want to subscribe, but you say > We cannot set the actual from-address in a foreign application... Modifying mailman/commands/eml_membership.py to accept an address= argument shouldn't be difficult. If you submit an issue at <https://gitlab.com/mailman/mailman/-/issues>, I'll look at it. -- 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: "To:" header field

by Mark Sapiro

On 08/05/2018 06:20 AM, Asaf Ohayon wrote: > > Comparing to Mailman 2.1, which we recently upgrading from, > and didn't got spammed, the "To:" field was set to the actual reciever, > While in Mailman 3.2, the "To:" field is set to the list's address. > > How can this be configured ? This is full personalization. See <http://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/cook-head…>. This setting is not yet exposed in Postorius, so you have to set it via 'mailman shell'. E.g. $ bin/mailman shell -l test(a)msapiro.net Welcome to the GNU Mailman shell The variable 'm' is the test(a)msapiro.net mailing list >>> m.personalize <Personalization.none: 0> >>> from mailman.interfaces.mailinglist import Personalization >>> m.personalize = Personalization.full >>> m.personalize <Personalization.full: 2> >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: API access to Hyperkitty

by Mark Sapiro

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. -- 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: Problems with web interface after upgrade

by Mark Sapiro

On 2/9/21 3:26 PM, Victoriano Giralt wrote: > > It's CentOS7, but sassc was already installed and has -t as short for --style. You wrote > ModuleNotFoundError: No module named 'sassc -t compressed {infile} {outfile}' It should be looking for just sassc, not 'sassc -t compressed {infile} {outfile}'. Whats in your settings for COMPRESS_PRECOMPILERS. That may not be the issue. You also wrote > compressor.exceptions.FilterError: Error: It's not clear which file to > import for '@import "../libs/bootstrap/stylesheets/bootstrap"'. > Candidates: > ../libs/bootstrap/stylesheets/_bootstrap.scss > ../libs/bootstrap/stylesheets/bootstrap.scss > Please delete or rename all but one of these files. > on line 4 of static/hyperkitty/sass/hyperkitty.scss You need to remove the older of hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap.scss and hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_bootstrap.scss That may be the whole issue. -- 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: migrate MM3 list from an old server to a new one

by Mark Sapiro

On 8/6/24 01:43, noc(a)iem.at wrote: > > PS: (again) I'm resending this message, as the one i sent yesterday seems to have vanished (i *did* check the archvies). i have no clue why this happens, as i can post via the webinterface just fine (only when using my trusted MUA they just vanish). Your messages are being discarded for matching a header filter rule. The messages contain content-type: application/pgp-keys; name="OpenPGP_0xB65019C47F7A36F8.asc" and the content-type rule regexp is `^ *application(?!.*signature)` I.e we accept things like application/pgp-signature and application/pkcs7-signature, but not application/pgp-keys I have changed that regexp to `^ *application/(?!(pgp|[^ ;]*signature))` so we will now accept `content-type: application/pgp.*` as well so you now should be able to post/reply from your MUA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Must issue a STARTTLS command first when forwarding from old server to new server

by Mark Sapiro

On 11/14/24 15:53, jkoral(a)luc.edu wrote: > I have a fully functioning Mailman3 server now and have setup and alias on the old server to forward mail to the new server. We have TLS enabled on the new server, but not the old server, so the new server is rejecting the mail coming through. Our IT security will not allow me to disable TLS on the new server. > > Is there a way to make an exception in mailman3 to allow a specific host to send mail through without using TLS? This is all the MTA, not Mailman. As you suggest in a follow up, you should enable TLS on the old server. In Postfix main.cf, I think ``` smtp_tls_security_level = may ``` should do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/5/25 09:59, dap1--- via Mailman-users wrote: > As far as I know I did everything (except the /etc/mailman3 stuff) in the venv environment. Pip is not even available outside of mailman user. When I try to run pip again it says requirement already satisfied. I don't suppose there is a checkparms like in mailman2. I'm not aware of any Mailman 2.1 checkparams. There is check_perms, but I don't know if that's what you want. The fact remains that something is checking for `/usr/bin/django-admin`, finding it and then trying to run `flock -n /var/run/mailman3-web/cron.minutely /usr/share/mailman3-web/manage.py runjobs minutely` If everything is in your venv, why is there a `/usr/bin/django-admin` and perhaps a `/usr/share/mailman3-web/manage.py`. These all look like artifacts from an install of the Ubuntu mailman-web package. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 2 weeks

[MM3-users] Re: Header Filters

by Mark Sapiro

On 5/31/20 7:23 PM, Peter Adebahr via Mailman-users wrote: > > Hi *, > > we are trying to dispose of automatic replies like "out of office" etc. > > For these ends, we have set > > Header to "subject" (w/o quotes) > Pattern to ".*out.of.office.*" > Action to "Hold for moderation" This should hold any message that contains 'out of office' (case insensitively) anywhere in the Subject: - also the leading and trailing '.*' is superfluous as the pattern is matched with re.search - BUT this test is applied after member moderation so if the message is from a member and the member's moderation action is Accept either explicitly or via list default, the message will be accepted without applying further tests. You want the member's moderation action to be Defer so that additional checks such as header matching are applied. -- 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: Source Installation Assistance

by Mark Sapiro

On 11/29/19 7:37 AM, actionmystique(a)gmail.com wrote: > mark.van.holsteijn＠gmail.com > I stumbled across the same issue as Brian Carpenter within a slightly different environment: > Ubuntu focal 20.04 > PostgreSQL 12.1-1 > > I tried to replace the following line in ```/usr/lib/python3/dist-packages/hyperkitty/migrations/0007_allauth_20160808_1604.py``` from ```python3-django-hyperkitty``` (1.3.0-1ubuntu1): > ``` > cursor.execute("SELECT 1 from social_auth_usersocialauth") > ``` > with > ``` > cursor.execute("SELECT 1 from information_schema.tables where table_name ='social_auth_usersocialauth' and to_regclass('social_auth_usersocialauth') is not null") > ``` > then > ``` > python3 manage.py makemigrations > ``` > leads to a different issue: We are working on a proper fix for this issue. See <https://gitlab.com/mailman/hyperkitty/merge_requests/200>. In the mean time, to work around this issue on a new install, the simplest change is to just delete the second to last line ``` migrations.RunPython(migrate_social_users), ``` from hyperkitty/migrations/0007_allauth_20160808_1604.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: How to create user accounts and mail addresses through CURL instead of Site Administration ?

by Mark Sapiro

On 8/10/20 11:18 AM, Shashikanth Komandoor wrote: > I am currently automating a few things using the CURL commands but only > postorius related as of now. Now I have a requirement. > > I need to create a lot many users and their mapping email ids through > Site Administration almost daily. But it is becoming to do the same through > Graphical Interface. > > So, I just want to know the CURL commands that can be used to create the > user accounts and email ids mapped to user accounts. The accounts you are talking about are Django accounts. You cannot create these via CURL to the Mailman core REST API. You might find <https://www.django-rest-framework.org/tutorial/quickstart/> of interest. -- 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: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Mark Sapiro

On 2/26/21 1:19 PM, Andreas Barth wrote: > > Re the "latest greatest", that's always the same question for all > software. If one is happy what comes from the distribution, I always > recommend to use that (or just use the currently developed stable > version, i.e. testing or unstable, perhaps even only for these > packages). If one needs something newer / else / specific local > patches, it's good to have documentation that helps. We're not talking bleeding edge here (although the server that supports this list and the python.org lists is bleeding edge). We are talking about installing the current releases from PyPI. Mailman 3 is still relatively young and there are many important features and fixes in the current releases that aren't in the Debian/Ubuntu packages. -- 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: Moderation request reminders

by Mark Sapiro

On 1/14/23 09:33, Allan Hansen wrote: > > I and my moderators are getting daily moderation request reminders. Is there a way to set them to be weekly instead? I looked around in the UI for it but did not see it. It started with my latest server upgrade. As list owner I get 50+ of these messages every morning and my modertors each get only one, but don't like it. This is `mailman notify` <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…> run by cron. > I still don't see a link for my moderators to see the membership lists even though the lists are set to allow it. Is that among the planned bug fixes? This is <https://gitlab.com/mailman/postorius/-/issues/369>. There is an abandoned MR at <https://gitlab.com/mailman/postorius/-/merge_requests/423> but see the recent notes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: search this list searches more then just this list

by Mark Sapiro

On 1/29/24 03:09, Marco van Tol wrote: > > Right now I’m back at the original issue as I see no other solution than to go back to whoosh. > > Thanks! > > Marco van Tol > > Paste: > ---- > Indexing 194620 emails > [ERROR/MainProcess] Failed indexing 156001 - 157000 (retry 5/5): Term too long (> 245): XSUBJECThttp://www.google.com/url?q=%68%74%74%70%73%3a%2f%2f%68%64%72%65%64… (pid 32): Term too long (> 245): XSUBJECThttp://www.google.com/url?q=%68%74%74%70%73%3a%2f%2f%68%64%72%65%64… I'm not sure why the patch you are using doesn't avoid this, but you could try the other patch at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…> instead. If that fails, you could always find the offending message in the database maybe with a query like ``` SELECT * FROM hyperkitty_email Where subject LIKE 'http://www.google.com/url?q=\%68\%74\%74%'; ``` and modify or delete it - it's probably spam anyway. -- 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: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 9/23/25 09:39, Stephen J. Turnbull wrote: > nirmal--- via Mailman-users writes: > > > Eventhough I have downgraded it. Archiving is not working. Kindly > > help me to solve. > > Does the subject have anything to do with this problem, or did you > reply to some other thread? > > If it's related to the problem, that's one problem. Most likely the > api_key setting in mailman-hyperkitty.cfg' doesn't match the > MAILMAN_ARCHIVER_KEY in 'settings.py', or possibly you have the wrong > quoting in one of the files. This could have happened in the > downgrade if you downgraded only some of the Mailman packages. Actually, this is an incompatibility issue. It results from mailman-hyperkitty < 1.2.0 in combination with HyperKitty >= 1.3.5 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by Mark Sapiro

On 1/7/22 6:07 PM, David Newman wrote: > On 1/7/22 4:32 PM, Mark Sapiro wrote: > >> I suspect an issue trying to connect to the MTA to send the messages. >> This can be caused by permission errors. Check permissions on >> Mailman's var/templates/* > > Bingo. This list had regular and digest footer templates with 0644 > permissions owned by root:root, and there was an exception and traceback > for the most recent message in shunt about the permissions issue. That comes from running `mailman import21` as `root`. Always run `mailman` commands as the Mailman user. > I've changed ownership to mailman:mailman and restarted the mailman3 > service. > > As soon as I fixed this, my inbox filled with test messages... Good! >> Is there a 'Cannot connect to SMTP server ... on port ...' anywhere in >> mailman.log? > > Yes, lots. This might or might not be a different issue. It is exactly this issue which is now corrected. > As I mentioned earlier, the most recent message in shunt was from 0000 > hours today. There are many "Cannot connect" messages since then, but > none since fixing the issue above. The Cannot connect messages are from the issue of ownership of the templates and Mailman's out runner continually retrying the send. This is separate from the shunted messages. > Seems OK now. The superuser sees all posts after the unshunt action. So it appears that you ran `mailman unshunt` and the shunted messages were successfully processed, so whatever caused them to be shunted in the first place is fixed. Individual messages don't get shunted because of this template ownership issue, but it may be that digests do get shunted for this reason. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Any known limit of number of lists that one can be owner/member of?

by Mark Sapiro

On 5/14/19 12:18 AM, Alan So wrote: > One more finding. If the user select "All" in the "Filter by role" box, nothing can be shown. So, that shouldn't be related to the default limit of 50 with find_lists. Otherwise, at least some lists should be displayed. If you are saying no lists are shown when the user selects "all", is it possible that no lists are advertised? I.e., all lists have Settings -> List Identity -> Show list on index page = No. If that is not the case the advertised list should be shown on the "all" view or when not logged in. I don't see an issue at <https://lists.mailman3.org/mailman3/lists/> or <https://mail.python.org/mailman3/lists/>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: Language Support In Templates

by Mark Sapiro

On 1/25/21 12:18 PM, Brian Carpenter wrote: > Hello MM3 Users, > > I have a question regarding the use of templates in different languages. > I created a template for the unsubscribe notification in Postorius in > Greek. The template shows up fine in Greek via Postorius. However the > email that is sent out has a bunch of question marks where the Greek > should be: This is a bug in Postorius. I just reported it at <https://gitlab.com/mailman/postorius/-/issues/465>. There are a couple of workarounds. Assuming the list's preferred language is Greek (el), You can put the template in Mailman's var/templates/lists/<list-id>/el/ directory (creating it if necessary and ensuring it's readable by the Mailman user. You can set ``` [language.master] charset: utf-8 ``` in mailman.cfg to change the default character set from ascii to utf-8 -- 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: Dealing with recipients' servers spam filtering

by Mark Sapiro

On 2/13/21 7:31 AM, Gilles Filippini wrote: > > Writing down what I've learned so far, in case it may help others: > > 1- The lists server DNS record (lists.example.com) should be of 'A' type > (no 'ALIAS' or 'CNAME') Not only that, reverse lookup of the IP in the A record must point back to the same (lists.example.com) domain. See, e.g., <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. > 2- The SPF record should be set for the very same DNS name; e.g. > lists.example.com (not just example.com) > 3- This record seems to work for my server: > lists.example.com. IN TXT "v=spf1 ip4:123.123.123.123 -all" > Where the IP address is the same as the one registered for the 'A' > record. And you should also DKIM sign outgoing mail. -- 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: How to store additional information about lists?

by Mark Sapiro

On 5/25/21 12:28 AM, Stephen J. Turnbull wrote: > Andreas Barth writes: > > > private: hand-selected people, think about e.g. board or steering > > committees internal discussions. Of course, the archive (if there is > > any) should be restricted to the actual members. Posting to these > > lists is currently not restricted, so no derivation needed from the > > current set in postorius. > > This is already possible by requiring admin approval, or by setting > the ban list to something that matches everything like "^.". The ban list can't be used in this way. A banned address can't be subscribed by any means including admin action. And even if an admin temporarily removes the ban, subscribes the address and then restores the ban, the now banned member can't post. -- 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: How to delete user completely?

by Mark Sapiro

On 1/21/22 4:32 PM, William Oliver wrote: > I have installed mailman3 and it's up and running great. However, I > noticed that, during a mass subscribe, I mis-typed an address, e.g. > name(a)domain.ned rather than name(a)domain.net. I found how to unsubscribe > the bad address, but I haven't found a "delete" option under Users or > anywhere else. How to I purge a user from the users list? You need to do it via REST or `mailman shell`. In mailman shell, ``` >>> um = getUtility(IUserManager) >>> usr = um.get_user('user(a)example.com') >>> um.delete_user(usr) >>> commit() ``` > As a related question, in docs.mailman.org, I can find a list member's > manual, but I can't seem to find an admin manual. Is there one? No, not per se. -- 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: Pb with archive display

by Mark Sapiro

On 5/4/22 05:45, Pierre Malard via Mailman-users wrote: > > On the other hand Mailman3 does not seem to take into account the display of the archives. The contributions are indeed in the directory "/var/lib/mailman3/archives/hyperkitty/spool" but HyperKitty does not take them into account when displayed on the Web interface. > > Is this normal? No. The messages are in /var/lib/mailman3/archives/hyperkitty/spool because delivery to HyperKitty failed. There should be messages in Mailman's var/logs/mailman about the failures. The setting for api_key in mailman-hyperkitty.cfg must match the setting for MAILMAN_ARCHIVER_KEY in your Django settings. Also, the setting for base_url in mailman-hyperkitty.cfg must be good. If you append `/api` to that url, the result should return a page of documentation of HyperKitty's REST API. Also 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

3 years, 10 months

[MM3-users] Re: Issues encountered while upgrading to 3.3.7

by Mark Sapiro

On 12/5/22 02:37, Odhiambo Washington wrote: > > Here again, Google-fu came to the rescue. I added the following line to > settings_local.py and the warnings were suppressed. > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > I need to understand how this affects everything and how this is likely to > impact the functionality of MM3. What is the proper solution for this? > And should it be django.db.models.BigAutoField or > django.db.models.AutoField? Which is which? Prior to Django 3.2 Django set default primary keys to 32 bit integers. In 3.2 Django introduced the possibility to set default primary keys to 64 bit integers by setting the type to django.db.models.BigAutoField. Thus, putting ``` DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' ``` in your settings will maintain compatibility with pre 3.2 versions and existing tables and this is the correct thing to do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner

by Mark Sapiro

On 4/3/23 23:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > Just to make it clear: It happened upgrading from 3.3.7 to 3.3.8 > > The upgrade procedure I did all the times is > > pip install --upgrade django-mailman3 mailman mailman-hyperkitty > mailmanclient postorius django hyperkitty uwsgi mod-wsgi > > and if I see some trouble I did it with a --force-reinstall parameter > (not that I remember it happened last times that I upgraded) > > (and then the collectstatic, etc.) > > If I missed something, I don't know. Mailman 3.3.5, 3.3.6 and 3.3.7 all required aiosmtpd>=1.4.1 so your prior upgrades should have installed aiosmtpd>=1.4.1. Possibly aiosmtpd>=1.4.1 was installed somewhere, but your jail configuration was such that it wasn't the one actually used by lmtp runner. -- 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: How to change the language in mailman3

by Mark Sapiro

On 7/22/20 10:17 AM, blackout69 wrote: > Hi everybody, > > with > $sudo updatedb > $sudo locate,I don't find these path Mailman core in mailman/messages/ > Hyperkitty in hyperkitty/local/ > django-mailman3 in django-mailman3/local/ > postorius in postorius/local/from here > https://www.pratico.work/file.tar.xz you can download the following > files: my file /usr/share/mailman3-web/settings_local.py $sudo locate > it/LC_MESSAGES > mypath.txt I can't (re)generate the .mo files because > there are no path above. Thank You for help Max I'm having trouble deciphering what you are saying, however, the actual paths you are looking for are: For Mailman core: mailman/messages/it/LC_MESSAGES/mailman.po For HyperKitty: hyperkitty/locale/it/LC_MESSAGES/django.po For djangomailman3: django_mailman3/locale/it/LC_MESSAGES/django.po For Postorius: postorius/locale/it/LC_MESSAGES/django.po Note 'locale', not 'local' -- 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: Posterious membership listing for non-owner/moderators?

by Mark Sapiro

On 3/11/21 4:58 AM, Duane Raymond wrote: > Hi, > > I'm configuring my new mailman3 lists and one option I wish to use is a membership listing (which list members can opt-in/out of via their preferences). The only problem is, via the web interface (Posterious / Hyperkitty) I can't find that listing when logged in as an ordinary member. Am I missing something or is this not built in yet? > > I have my test list setting under List Identity -> Members List Visibility set to "Only mailinglist members", but all I can find in terms of members is the side-listing of posters to the list/thread. > > (as usual before asking the question I explored a lot and searched the archives/documentation). Maybe you should also check issues. This is <https://gitlab.com/mailman/postorius/-/issues/369> -- 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: Apple Mail encoding again

by Mark Sapiro

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

3 years, 11 months

[MM3-users] Re: Aborted connection message in log in every 5 minutes

by Mark Sapiro

On 1/31/24 04:00, andrea.janna.unipd(a)gmail.com wrote: > > Yes it's mailman gatenews that triggers mariadbd "[Warning] Aborted connection" log entries. > I don't use this feature so as a workaround I set a large gatenews_every interval in mailman.cfg. > > [nntp] > gatenews_every: 1000000m Or you can do as Danil does <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> and put ``` [runner.nntp] start: no ``` in mailman.cfg. However, it is unclear what in gatenews would do this. Assuming you have no lists for which gateway_to_mail is true, all gatenews will do is ``` def process_lists(glock): list_manager = getUtility(IListManager) for mlist in list_manager.mailing_lists: glock.refresh() listname = mlist.fqdn_listname if not mlist.gateway_to_mail: continue ``` The database operations involved in this are things Mailman core is doing all the time, presumably without issues. -- 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: Installing mailman 3

by Mark Sapiro

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

8 years, 7 months

[MM3-users] Re: Subscription notification sent from the site admins work-mail.

by Mark Sapiro

On 09/13/2018 05:01 AM, Henrik Rasmussen wrote: > One of my list administrators told me that all seven list administrators on a list received a "None <foo(a)example.com> has been successfully subscribed to [LIST NAME].", when someone subscribed to their list, however the sender of the mail (From:) was my own work mail address. I am not associated with the list other that I am site admin. This is expected behavior. In Mailman 2.1 notices like this were sent From: the site list (normally 'mailman'). In Mailman 3, there is no site list so the notices are from the site admin. If you'd rather not expose your work mail address in this way, set the site admin to something generic like mailman-admin(a)example.com and alias that to where you want the mail to go. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: Cannot see the cron jobs for Mailman 3 Installed

by Mark Sapiro

On 1/23/20 4:49 AM, Shashikanth Komandoor wrote: > Hi, > > I have setup the Mailman 3 on my RHEL 7.5 box and found it was working > fine. But I found that I am not getting daily summary notifications for > which I learnt after browsing through different websites, there should be > an entry of *checkdb* in the cron job list. checkdbs is a Mailman 2.1 job The equivalent Mailman 3 job is `mailman notify` > But I did not find any such nor I don't find any cron job updated after > the installation of mailman 3. See <https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs> and <https://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required> If you installed Mailman from a package and the cron's weren't installed, report this to the packager. -- 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: Subscription issue with ghost confirmations

by Mark Sapiro

On 10/31/20 7:28 AM, Brian Carpenter wrote: > > This has occurred again. A person sends an email to listname-subscribe@listdomain and the subscription policy of said list is set to moderate only. Instead of honoring this, a confirmation email is sent out. The issue is that when a request is received to subscribe an address to a list and that address is not verified and the pre_verified flag is not set in the request, the user is sent a confirmation request. This is not a request to confirm the subscription request, but rather a request to confirm the address, however they use the same template so they are indistinguishable. We probably should check the subscription policy and not send this request if the policy is moderate. We should also ignore a pending request if the policy is moderate per <https://gitlab.com/mailman/mailman/-/issues/789>. -- 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: Can't deliver mails in queue

by Mark Sapiro

On 5/19/21 2:45 PM, Nathanael Schneider wrote: > > They were in fact not identical, as I changed some stuff in hopes to get > it up and running again quickly. I now changed the completely new List > to be identical with the cleanly created one (as far as postorius shows > me) and it still works just fine. Do I understand correctly that you deleted the MM 2.1 imported list and created a new list in Postorius with just two members and it doesn't work. If that understanding is not correct, please outline all the steps you took to arrive at the current list that doesn't work. Also, please capture one of the .pck or .bak files from the out queue and send it to me off list. I will treat it confidentially, but there might be clues in it. -- 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: list footer web customization procedure

by Mark Sapiro

On 11/30/21 1:11 AM, Stephen J. Turnbull wrote: > > Does Django empty out the "spacetebasket" if it's all white space, or > does spurious whitespace in that box lead to an (apparently) empty > footer being added? Postorius used to remove leading and trailing whitespace from the template, but not since https://gitlab.com/mailman/postorius/-/issues/301 was fixed. > Anway, I recommend to the OP that they make sure there's no whitespace > in the Data box. A good recommendation. While a header or footer template with some whitespace might not be noticeable when added to a text/plain message, it will cause extra mime parts to be added to more complex messages. Also, if the goal in setting an empty footer is to avoid breaking a DKIM signature, even adding a bit of whitespace to a text/plain message is an issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Python 3.9 support

by Mark Sapiro

On 2/24/22 14:01, dancab(a)caltech.edu wrote: > > Only mail delivery was hung overnight. I had to restart the Gunicorn process followed by a Mailman core restart for mail to flow again. Because Mailman's "out" runner (/opt/mailmanve/lib/python3.9/site-packages/mailman/runners/outgoing.py from the above traceback) is what hit the exception and died. The master watcher should restart it, but see https://gitlab.com/mailman/mailman/-/issues/898 > Any insight into how we could monitor this in the future? For example which specific "runner" reported the error above? Something like ``` ps --ppid=`cat /opt/mailman/mm/var/master.pid|tr -d '\n'`|wc -l ``` will report the number of child processes of the master. You could test that against the expected number and do something. Note that `mailman restart` probably won't start a runner that died - you need to do `mailman stop;mailman start` to be sure. -- 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: Strange messages after upgrading Mailman3

by Mark Sapiro

On 12/4/22 20:09, Allan Hansen wrote: > Hi all, > > I have been getting a few of these messages after my Mailman 3 was upgraded: > > "The content of this message was lost. It was probably cross-posted to > multiple lists and previously handled on another list." > > The messages appear to come from list members and are distributed to the relevant lists, but with nothing of the original contents. > They have appeared on different lists with, apparently different senders (unless spoofed). > Other messages are going through the system unchanged. > > Anyone has any ideas? To what version did you upgrade? This is most likely https://gitlab.com/mailman/mailman/-/issues/955 which was fixed in Mailman core 3.3.6, but it could be https://gitlab.com/mailman/mailman/-/issues/1027 if the posts are to umbrella lists (lists with other lists as members). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Messages hold for moderation - compared to mailman2 it appears that there are fewer options: missing option(?)

by Mark Sapiro

On 3/7/24 9:35 AM, Wikinaut wrote: > Hello, I miss sadly the option of > > both: > > i) discarding the current message of a sender (not member of a closed list) ; and in the same action > ii) adding this person to the whitelist, i.e. accept further mails from this sender. When you go to the held messages view in the web UI and click the Subject: of the held message, there is a dropdown to set the sender's moderation action. you can select `default processing` to accept subject to additional checks or `accept` to accept unconditionally, subsequent posts from that sender before clicking the `discard` or other button. This works for non-members as well as for members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: [Bug] Someone not a member of list is treated as member - strange

by Mark Sapiro

On 8/23/25 11:51, Wikinaut wrote: > > Because it may be a breaking change in mailman3 - no one wants this I do not think is is a breaking change and I strongly disagree that no one wants it. If you want prior Mailman behavior, just don't link multiple addresses to one user. You can have a separate user for each address and then each address will be considered as belonging to a different person which is apparently what you want. Going back to your original issue, why do you have a problem? The fact that a post from one of your addresses was accepted even though it wasn't from the address that was subscribed in no way says that a post from an arbitrary nonmember would be accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

[MM3-users] Re: Block members from sending cc's and bcc's

by Mark Sapiro

On 10/26/25 10:38, Cathryn McGuire wrote: > > Since setting to Default Processing, ALL members posts are being held for moderation. That's what happened last time. Obviously there's some setting somewhere that's telling the list to do that with that setting. We'll try to find it by doing testing like you said. Meanwhile, we're quite busy in our other endeavours and having to unblock every post (some days more than others, and not that many relatively speaking) is what we're doing. What is the reason given for the post being held? I don't know about affinity, but Postorius gives the reason in the list of held messages. Also the message itself has a X-Mailman-Rule-Hits: header that says which rule caused the message to be held -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/27/20 4:29 AM, Odhiambo Washington wrote: > On Mon, 27 Jul 2020 at 02:49, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> Is there an empty /opt/mailman/mm/__init__.py file? >> > > No. There has to be one. Create it and then Django will be able to import your settings. See the first line after Create directories: ... and files: at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#line-69> > Yes. However, that also means the /opt/mailman should be owned by mailman3, > right? So I wasn't quite mistaken. It doesn't matter what user actually `owns` this directory and its subordinates as long as the Mailman user, mailman3 in your case, can read and write there. Of course, making everything owned by the Mailman user is the easiest way to ensure this. Note also that any commands in /opt/mailman/mm/bin need to be run as the Mailman user and not root. Running them as root can create things owned by root the can't be read by the Mailman user. > PS: There is the issue with qcluster, which doesn't seem to have been > documented in details from your "experience". > I see the configuration file and the init script, but not how to install > it, or whether the procedure already installed it. qcluster is part of Django. If you have this # # Asynchronous tasks # Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'orm': 'default', } or similar uncommented in your Django settings, and also 'django_q' in your INSTALLED_APPS, it's there and all you need to do is run /opt/mailman/mm/bin/django-admin qcluster to run it, but it should be run as a service via init or ?? -- 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: Installing mailman 3

by Mark Sapiro

On 07/21/2017 06:46 PM, Rafael Mora wrote: > Can I use it for mailing lists? like MailChimp? Yes, if all you want is a simple one way announcement type list, Mailman can do that quite well, with appropriate list configuration[1], but as I tried to say, MailChimp has many more features that are oriented towards that kind of mailing. [1]There are many horror stories of people setting up a mailing list and subscribing a bunch of people to it without ensuring that members can't post back to the list. Then with the first post, people start posting back to be removed and then others reply that they didn't send that mail and it snowballs and within an hower, the poor list server is so backlogged that the clueful replies take hours to be delivered. I personally have been added to more that one list to which this happened. -- 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: Uncaught runner exception with out runner process

by Mark Sapiro

On 5/18/19 7:35 AM, Alan So wrote: > The out runner process shutdown with the following error. Any clue? > > May 16 17:32:12 2019 (31602) Uncaught runner exception: (pymysql.err.InternalError) (1053, 'Server shutdown in progress') ... Mailman is running and the MySQL server is being shutdown. If this occurred during shutdown of the entire server, it is a race condition due to the out runner continuing to process a message while the MySQL server is being shut down. Upon restart, the out runner may recover the message from the .bak file in its queue. To avoid this, you could stop Mailman and wait for all Mailman processes to terminate before shutting down/rebooting the server. Note that if the message in process was shunted, the .bak file was probably removed during the shunting process, so you should unshunt it to finish delivery. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: No styling for web apps?

by Mark Sapiro

On 11/26/20 8:44 PM, Morris Jones wrote: > I have most of a new mailman suite server built and working ... > > collectstatic gathered a good array of static files (uncompressed so far) > > nginx appears to be serving them successfully > > The Firefox developer tools show css and js files all being delivered > > But none of the postorius or hyperkitty pages exhibit any styling at > all, only bare HTML elements. > > The Firefox inspector will show the available styles being requested and > delivered (style.css, bootstrap, jquery, all the things). > > But if I use the inspector to look at the page, nothing has any CSS > properties. > > I know I'm missing something simple. Try running collectstatic and, if you use it, compress again. These have to be run following various kinds of changes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Reduction of spam - FROM_LOCAL_HEX

by Mark Sapiro

On 10/31/23 01:55, Kyriakos Terzopoulos wrote: > > My guess is that the From address is very large, for example: > > mylist-confirm+3eafa5bd24e52738c900e2e3fd05e366b7ea7580(a)myproject.eu > > Is there any way to mitigate this problem? The string 'mylist-confirm+3eafa5bd24e52738c900e2e3fd05e366b7ea7580' is created according to the setting ``` verp_confirm_format: $address+$cookie ``` in the [mta] section of mailman.cfg. You could override that by setting ``` [mta] verp_confirm_format: $address ``` or maybe even something like `` [mta] verp_confirm_format: $address+no_reply ``` in mailman.cfg, but then you would also need to provide edited versions of the templates list:user:action:unsubscribe, list:user:action:invite and list:user:action:subscribe to remove the bits about 'simply replying to this message'. Note that your spamassassin report is only assigning a score of 0.3 to FROM_LOCAL_HEX which isn't very much. Plus, there's no evidence that Gmail's proprietory spam checks even care about this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Debian upgrade Hyperkitty not archiving

by Mark Sapiro

On 2/28/26 14:29, Phil Steel-Wilson via Mailman-users wrote: > > I have a bunch of pck files in the spool directory that i think are the > messages from 2021 to the present but i cant get hyperkitty to look at > them. Those are messages which HyperKitty failed to archive. <https://gitlab.com/mailman/mailman-hyperkitty> is a small module with methods called by Mailman core to get information from HyperKitty and to pass messages to HyperKitty to be archived. If archiving fails the message is stored in Mailman's var/archives/hyperkitty/spool/ directory (maybe /var/lib/mailman/archives/hyperkitty/spool/ in the Debian package). Each new post causes mailman-hyperkitty to retry all the messages. Mailman's mailman.log (I think /var/log/mailman/mailman.log in the Debian package). That log will contain information about the failures which will help you diagnose the issue (probably misconfiguration) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 6 days

[MM3-users] Re: Mailman3 on Debian 10

by Mark Sapiro

> On Wed, Jan 29, 2020, at 9:22 AM, Bala Mutyam wrote: > >> but the mailman service is not able to start it’s giving below error. Could you help me how to resolve it please? And also instructions for to install Mailman3 using Debian packages mailman3-full. I would like to use MySQl as backend and Exim4 as mail server. I couldn’t find new mailing list using the command line utility (/usr/sbin/newlist? Questions about the installation of Debian packages should be directed to Debian. >> Please see the attached Traceback. Which said in part: > urllib.error.HTTPError: HTTP Error 401: b'{\n "title": "401 Unauthorized",\n "description": "REST API authorization failed"\n}' The most likely cause of this is your Django settings in settings(_local).py for MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS do not match the mailman.cfg [webservice] settings for admin_user and admin_pass (defaults restadmin and restpass). -- 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: Null sender?

by Mark Sapiro

On 6/28/20 10:18 AM, tom(a)gather.coop wrote: > Oh I get it! Hmm, I wonder why SendGrid is bouncing my mail then. I have the domain validated... Time to contact support... If SendGrid is your outgoing MTA, you probably don't have log info. You need to see the DSN for the reason. Unfortunately, MM 3 doesn't provide a way for you to see that directly (I just filed https://gitlab.com/mailman/mailman/-/issues/737 for this). This patch --- a/src/mailman/runners/bounce.py +++ b/src/mailman/runners/bounce.py @@ -90,7 +90,7 @@ class BounceRunner(Runner): else: log.info('Bounce message w/no discernable addresses: %s', msg.get('message-id', 'n/a')) - maybe_forward(mlist, msg) + maybe_forward(mlist, msg) # Dequeue this message. return False will forward non-verped received bounces to the list admins, not just unrecognized ones. The notice will say it was unrecognized, which it wasn't, but you'll be able to see it. -- 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: MAILMAN_ARCHIVER_KEY - 401 error

by Mark Sapiro

On 4/14/22 06:32, Torsten R. wrote: > Aah, one last question that came just up. > Due to the removal of the list and the recreation there are now some message files with the extension psv in the bad queue. > Is it safe to just delete them manually or how should they be treated? These are messages that were queued in some queue, but now can't be dequeued after a few retries. In your case, this is probably due to permissions because of incorrect ownership. Examine the files with `mailman qfile`. If you don't want to continue processing the message, just remove the file. If you do, rename it, changing the extension from .psv to .pck and change the ownership as needed - probably from root to mailman, and move the file to the original queue indicated in the metadata - the second object shown by `mailman qfile`. -- 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: Importing mailman 2 shows member's "Moderation Action" = "Default processing". But new members show = "None". Why

by Mark Sapiro

On 5/25/23 10:59 AM, mrl(a)psfc.mit.edu wrote: > I imported my mailing lists from mailman 2. If I view the Members, it say "Moderation Action" = "Default processing". > > But when I now subscribe myself or other people to the list, and view the new Members, it say "Moderation Action" = "None" for them. > > Should that be happening? The mailing list 's "Default action to take when a member posts to the list" setting is set to "Default processing". All of that is expected. import21 sets a members Moderation Action based on the Mailman 2.1 list settings and members moderation. New members get Moderation Action = None which means use the list default. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: mailman-web Cleaning Up a Few Issues

by Mark Sapiro

On 11/5/25 10:22, dap1--- via Mailman-users wrote: > Mark: I hope to do that but I am getting killed with emails in the mean time. I'm guessing all these issues stem from the incorrect location of django. How do I fix that? See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I find it very difficult to help you when you don't report the results of things I suggest > Stephen: I can't find anything. Here is /opt/mailman/venv/lib/python3.12/site-packages/hyperkitty/jobs: > > empty_threads.py __pycache__ thread_starting_email.py > __init__.py recent_threads_cache.py update_and_clean_index.py > new_lists_from_mailman.py sync_mailman.py update_index.py > orphan_emails.py thread_order_depth.py The problem isn't with your virtualenv install. It is with some left over crontab from a prior attempt to install Ubuntu packages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 2 weeks

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

by Mark Sapiro

On 03/19/2018 02:22 PM, Aymeric Mansoux wrote: > > Ah, so if I understand you correctly, as long as I'm on 3.1.1, I could > run into this issue again, but then: Yes, this issue will recur with Mailman 3.1.1 and a MySQL database. > - Would patching 3.1.1 with 5477a201 be enough to prevent further issues > until the next stable is released? I think so. The only potential issue is if mailman/database/alembic/versions/4bd95c99b2e7_fix_template_password.py is not in 3.1.1. I think it is, so I think it's OK, but if not, you'd need to modify mailman/database/alembic/versions/3f31035ed0d7_further_increase_pendedkeyvalue_value_.py to point to the 3.1.1 head of the alembic versions. > - How can I clean the current pendedkeyvalue table? With phpMyAdmin or the mysql command. I think you can just delete those entries from the pendedkeyvalue table. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: HyperKitty Question

by Mark Sapiro

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

5 years, 10 months

[MM3-users] Re: Footer from templates not working - DB issue?

by Mark Sapiro

On 9/25/22 05:26, mailman--- via Mailman-users wrote: > Dear All, > I have a similar issue. Also on Debian 11. Also installed as Debian PKG. It's version GNU Mailman 3.3.3 (Tom Sawyer) > I am using sqlite3. When I do the SQL-query I get an URI which is in multiple reasons wrong > http://localhost/mailman3/postorius/api/templates/list/....../list:member:r… The initial part of that URL is set from the Django setting `POSTORIUS_TEMPLATE_BASE_URL`. If that is set to `http://localhost/mailman3/`, it should probably be just `http://localhost/`. > OK - the hostname could be changed but the path is not existing at all. > There is no file "list:member:regular:footer" on the complete filesystem. It's not a file. It refers to an entry in the postorius_emailtemplate table in the database which is retrieved via the Postorius API. -- 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: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 12:01 AM, Ken Alker wrote: > When I view a list via Postorius the "Held Messages" menu item has an inverse-red-"2" next to it, as if there are two held messages. There are, in fact, no messages in "/opt/mailman/mm/var/queue/*" (assuming the held messages should be in "pipeline" subdirectory). When I click on "Held Messages" I get "Something went wrong" followed by "HTTP Error 500: {"title": "500 Internal Server Error"}". How do I fix this? The held messages are not in any queue. They are stored in Mailman's var/messages/ hierarchy. They can be examined with `mailman qfile` Also, there is a long thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and maybe others that might be relevant. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Topics - Tags

by Mark Sapiro

On 3/21/24 21:10, Mark wrote: > Hi, > > I'm reading the docs on "Message tagging" > (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…) as saying shell access is needed to: (a) enable topics, and (b) write the keywords. > > In Mailman 2 there is an Admin web UI for "Topics". Is there such a web > UI that can be enabled in Mailman 3 so that the list owners can create > topics (tags) in their lists? At this point, topics are not exposed in REST. Managing them via Postorius first requires updating the REST API to read and set the topic attributes and then updating Postorius to display/set them. Further, there is currently no implementation for list member topics of interest either in Mailman core or the REST API. I.e., there is no way for a list member to indicate topics of interest. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Moving existing lists to a new domain

by Mark Sapiro

On 11/21/24 07:43, Jeremy Stanley wrote: > > Preparing to test this, I poked around the schema a bit and noticed > that the domain names are also embedded as strings in the following > fields: > > django_mailman3_maildomain.mail_domain > django_site.domain > django_site.name These are all Django things. You can modify those values in the db. Note that django_site.name is just a name and doesn't need to be the exact domain name. > domain.mail_host This is Mailman core's domain table. Again, you can modify the value in the db. > Can anyone think of any additional tables/columns which would need > updating for this? I'll see if scanning a dump of the full DB > content turns up anything I might be missing too. Thanks again! I don't think there's anything else. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: changing the main template for subscriptions and more

by Mark Sapiro

On 6/22/21 2:41 AM, Andreas Barth wrote: > > I'm using this patch (however, german-only) > > > Andi > > > diff --git a/src/mailman/templates/de/list:admin:action:post.txt b/src/mailman/templates/de/list:admin:action:post.txt ... > diff --git a/src/mailman/templates/de/list:admin:action:subscribe.txt b/src/mailman/templates/de/list:admin:action:subscribe.txt ... > diff --git a/src/mailman/templates/de/list:admin:action:unsubscribe.txt b/src/mailman/templates/de/list:admin:action:unsubscribe.txt ... > diff --git a/src/mailman/templates/de/list:user:notice:welcome.txt b/src/mailman/templates/de/list:user:notice:welcome.txt ... It isn't necessary to patch the source in this way. If you put the modified templates in Mailman's var/templates/site/de/ directory, ensuring that the Mailman user can read them, they will be used and you won't have to patch the source every time you upgrade. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: New messages not being archived

by Mark Sapiro

On 7/15/21 2:11 PM, Sarah H wrote: > I get a 301 when I go to http and the full html page not found text that is above if I go to https. if I curl loopback on html I get the same html response, https I get: > > curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number A 301 from http will be an issue always. I'm not sure where the `wrong version number` comes from. This could be the issue. If I do for example, curl -X POST https://lists.mailman3.org/archives/api/mailman/archive I get the response <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>Please check whether the MAILMAN_ARCHIVER_KEY is provided by you and it is correct. </p></body></html> This is the expected response. You need to figure out what base_url will give you a similar response. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: hyperkitty url not found

by Mark Sapiro

On 3/9/22 07:13, Eggert Ehmke wrote: > I installed mailman3 in a virtualenv following this guide: > > https://docs.mailman3.org/en/latest/install/virtualenv.html[1] > The mailinglists work very good. However, I did not manage to set up hyperkitty archiving. > Archiving is enabled in mailman.cfg. I can call the Archive site from my configuration page, > but it is empty. > > In my /opt/mailman/mm/var/logs/mailman.log > file I find error messages like: > > HyperKitty failure on http://localhost/mailman/hyperkitty/api/mailman/archive: > The requested URL was not found on this server. Your setting in mailman-hyperkitty.cfg for base_url is base_url: http://localhost/mailman/hyperkitty/ It needs to be the base URL for accessing hyperkitty, possibly base_url: http://localhost/mailman3/hyperkitty/ or whatever you use to access hyperkitty from a web browser. Whatever it is, `<base_url>/api` should return a page of API documentation. -- 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: hyperkitty_import performance boosting potential

by Mark Sapiro

On 7/8/24 11:59 AM, dlb-ml--- via Mailman-users wrote: > > I can throw all of the resources I need at it in order to make it faster, but I'm not sure if the import application is single-threaded only. Is there a way to enable a multi-threaded option? Can I safely run multiple commands at the same time using something like /usr/bin/parallel? If you're concerned about down time while doing the switch over, you could just do the hyperkitty_import processes while the MM 2.1 lists are still up, and then just import only the latest messages while the MM 2.1 lists are down. That said, in order to provide parallelism, you could split the mbox into pieces and run multiple hyperkitty_import processes concurrently. If you do this, be sure to specify --since on the commands to be sure you get all the older messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Confirmation emails aren't sent to users.

by Mark Sapiro

You are Hijacking threads again. Please compose a new message with a new subject, not a reply, when you post a new topic. On 2/12/26 14:01, Ibiam Chihurumnaya via Mailman-users wrote: > I'd also like to know how I can disable message approval for an email, I don't want to approve some messages. > > These emails are already members of the list and yet they need approval because "Message has implicit destination". You can set their moderation action to Accept. This will bypass all the following checks for that member. Message contains administrivia Message has implicit destination Message has more than {} recipients The message is larger than the {} KB maximum size Post to a moderated newsgroup gateway Message has no subject Message has a digest subject Message quotes digest boilerplate Header "{}" matched a bounce_matching_header line -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: Funny responds to subscriptions emails

by Mark Sapiro

On 09/02/2017 01:36 PM, Claus-Justus Heine via Mailman-users wrote: > > But I also get a second rather confusing email: > >> The results of your email command are provided below. >> >> - Original message details: >> From: Claus-Justus Heine <Claus-Justus.Heine(a)IANS.Uni-Stuttgart.DE> >> Subject: Test >> Date: Sat, 2 Sep 2017 22:24:08 +0200 >> Message-ID: <44151460-05a8-4c35-e0d4-646efe3cf234(a)IANS.Uni-Stuttgart.DE> >> >> - Results: >> Confirmation email sent to Claus-Justus Heine <Claus-Justus.Heine(a)IANS.Uni-Stuttgart.DE> >> No such command: Test >> No such command: --=20 >> No such command: Claus-Justus >> No such command: f=C3=BCr >> No such command: Numerische >> No such command: Stuttgart >> No such command: +49 >> No such command: +49 >> >> - Done. See <https://gitlab.com/mailman/mailman/issues/212>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

[MM3-users] Re: Postorius endless loading on Sign in / Register then "Internal Server Error"

by Mark Sapiro

On 6/10/20 10:55 AM, Jacob Bargery wrote: > So I couldn't find a schema.cfg file but but when checking mailman-web.py and mailman.cfg they both have the same password. Albeit not the restpass but a much longer random password. I was able to connect using both telnet options. > > For reference the instructions I followed for installing this (up to the SSL cert) were here: https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… See <https://wiki.list.org/x/12812344 The next step is to try this in `django-admin shell` from mailmanclient.restbase.connection import Connection from django.conf import settings url = settings.MAILMAN_REST_API_URL user = settings.MAILMAN_REST_API_USER pwd = settings.MAILMAN_REST_API_PASS conn = Connection(url, user, pwd) conn.call('3.1/lists') That should return `<Response [200]>` and a bunch of json. What happens in your case? -- 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: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 6:30 PM, maszap(a)tin.it wrote: > Hi, > > you say I have to delete these lines? > > virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_emails.cf, mysql:/etc/postfix/mysql_virtual_alias_maps.cf > virtual_gid_maps = static:5000 > virtual_mailbox_base = /var/vmail > virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_mailbox_domains.cf > virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf > virtual_transport = lmtp:unix:private/dovecot-lmtp > virtual_uid_maps = static:5000 I say you have to understand what you want Postfix to do and configure it appropriately. I am not a primary resource for Postfix support in general. I will help you to the extent that I can, but you might be better off posting to a Postfix list. I would need much more information in order to know how your Postfix should be configured, and in any case, I don't have time to do any more today. -- 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: Problem with redirection when entering alias without a / at the end

by Mark Sapiro

On 3/19/21 4:53 PM, Jens Günther wrote: > Sure. It's not much, when I get it right, file was created by > debian-package automatically (I only post the lines without #): > > ->/etc/mailman3/uwsgi.ini > > [uwsgi] > uwsgi-socket = /run/mailman3-web/uwsgi.sock > enable-threads = true > chdir = /usr/share/mailman3-web > wsgi-file = wsgi.py > master = true > process = 2 > threads = 2 > uid = www-data > gid = www-data > plugins = python3 > attach-daemon = python3 manage.py qcluster > logto = /var/log/mailman3/web/mailman-web.log > > > Am 20.03.21 um 00:28 schrieb Abhilash Raj: >> >> Can you also share your uwsgi configuration? How about the actual uwsgi config. Maybe something like /etc/uwsgi.ini See https://uwsgi-docs.readthedocs.io/en/latest/Configuration.html -- 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: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Mark Sapiro

On 1/24/24 02:38, amg hsn wrote: working packages with exact version. > for me each time i build venv i have different warning or erro. I understand your frustration and I'm sorry. The problem is that the current release of django-mailman3, 1.3.11, just requires django-allauth>=0.56, so a new install will get the latest django-allauth==0.60.1, but django-mailman3==1.3.11 is not compatible with django_allauth>=0.59. This will be fixed in the next release, but in the mean time, you can apply https://gitlab.com/mailman/django-mailman3/-/merge_requests/237/diffs and https://gitlab.com/mailman/django-mailman3/-/merge_requests/243/diffs to update django-mailman3 for compatibility with the latest django-allauth. This can be an issue when any of our third party dependencies is upgraded in an incompatible way. Short of pinning all the dependencies to a specific version, there's not much we can do about it. -- 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: Welcome message template errors

by Mark Sapiro

On 4/23/24 18:12, Mark wrote: > > >>>> import requests >>>> r = >>>> requests.get('https://MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.MYDOMAIN.COM/li…', timeout=5) >>>> r.text > 'Another test Welcome message for new members.' >>>> Did you delete and recreate the template after changing POSTORIUS_TEMPLATE_BASE_URL? If not, the template table still has the old URI. > > ... so all well there. And mailman is running mailman core ... > > # cd /opt/mailman/venv/bin/ > # ls -la > ... > -rwxr-xr-x 1 mailman mailman 230 Jan 26 04:00 gunicorn > -rwxr-xr-x 1 mailman mailman 231 Jan 26 04:00 mailman > -rwxr-xr-x 1 mailman mailman 230 Mar 25 22:18 mailman-web > ... That only shows the user and group that owns the files, not whose running them. What does `ps -fwwu mailman|grep runner` show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Problem getting Mailman3 to work with Ubuntu 24.04.1 LTS

by Mark Sapiro

On 9/12/24 20:52, sebensteg(a)cod.edu wrote: > Hello everyone, > > We have been using Mailman3 for over a year and half. We upgraded from Ubuntu 22.04.5, where it was working fine, to Ubuntu 22.04.1. Since then, mailman3 won’t work. When we tried to start it immediately after the upgrade, we got this error: > > 024-09-12T23:08:04.322353+00:00 weather1 systemd[1]: Starting mailman3.service - GNU Mailing List Manager... > 2024-09-12T23:08:04.935569+00:00 weather1 mailman[23628]: SystemError: type psycopg2.extensions.ReplicationConnection has the Py_TPFLAGS_HAVE_GC flag but has no traverse function See https://github.com/psycopg/psycopg2/issues/1598 ... > But yet, we have this installed: > > venv mailman@weather1:~$ pip install psycopg2-binary > Requirement already satisfied: psycopg2-binary in ./venv/lib/python3.12/site-packages (2.8.6) > > Any advice on how to get this working again would be GREATLY appreciated! Try pip install --upgrade psycopg2-binary -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: clean_users.py

by Mark Sapiro

On 12/8/25 07:37, Christian Stalberg via Mailman-users wrote: > I just ran the clean_users.py script and it removed user email addresses > from Django. I can still find these addresses however using Postorius which > show > > Subscriptions > User has no subscriptions. > Ownerships > User has no ownerships. > > Why are they still listed then? How can I purge my system of all instances > of unsubscribed registrants please? Postorius is showing you Mailman users. If you ran the clean_users.py script with default settings, it only removed Django users. To delete Mailman users with no subscriptions or ownerships, you have to set DELETE_MAILMAN_USER = True As it says, # Set True to delete Mailman users that have no memberships with any role. # Set False to not delete Mailman users. You can change the setting for DELETE_MAILMAN_USER to True and run it again and it will delete those Mailman users. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 1 week

[MM3-users] Re: Deliverability and Spam Filtering

by Mark Sapiro

On 1/30/20 1:58 PM, Tom @ Gather wrote: > Interesting! Does the `in` queue also work for emails to subaddresses like > foo-owner, etc? Or is it only for list posts? -bounces goes to bounces -confirm, -join, -leave (and their synonyms -subscribe and -unsubscribe) and -request go to command -owner goes to in. But there's more to it that that. There's also things put in the metadata in the queue entry such as mail to -owner sets to_owner = True > Relatedly, why is `list_id` a required parameter? Isn't that information > contained in the email? Possibly not. The recipient list is the envelope recipient which may or may not be in the message headers - it could be a Bcc to the list. Thus, listid needs to be set in the metadata as well. You need to look at mailman/runners/lmtp.py and emulate what it does. -- 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: Mailman Suite installation on CentOS 7

by Mark Sapiro

On 11/8/21 4:18 AM, Kimmo L wrote: > Hello! > > I want to install fresh Mailman, which is combined with hyperkitty+postorius. After checking documentation i found, that Mailman Suite is perfect for me. > But i have some misunderstandings about installation. I only found this part in documentation, which explains how to clone and start using Mailman Suite (https://docs.mailman3.org/en/latest/devsetup.html#run-the-mailman-suite-com…) > > But am i correct, that before doing so, i need to install mailman core, mailman client, django-mailman3 ? > Or what would be the correct steps to build up my first Mailman Suite on CentOS? The docs you want to look at are https://docs.mailman3.org/en/latest/#the-pre-installation-guide and https://docs.mailman3.org/en/latest/install/install.html. There is also information at https://wiki.list.org/x/17891998 and in docs linked from thefirst paragraph thereof. -- 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: Messages not picking up header or footer template

by Mark Sapiro

On 2/26/23 13:04, benjamin(a)tougshire.com wrote: > > I can see the entry in the database with the uri: http://localhost:8000/mailman3/api/templates/list/testing.comms.sdcvirginia… > > I can do a wget on that uri and download a copy of the footer, and it looks right > > But when I send a message to the list and the message is forwarded, the footer isn't on the messages that members receive > > Looking at mailman.log, I cannot see any attempt to access the footer. I can see connections to the REST API (config, roster/owner, roster/moderator) that correspond to the time I sent the message Can you see an attempt to GET /mailman3/api/templates/list/testing.comms.sdcvirginia.org/list:member:regular:footer in your web server's logs? Is there anything in Django's log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Social signup?

by Mark Sapiro

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

3 years

[MM3-users] Re: unrequested unsubscription

by Mark Sapiro

On 6/14/23 19:40, Mike Wertheim wrote: > I have a Mailman 3 email list, running on Mailman 3.3.3 on Debian 11. > > A few of the list members are reporting that they received Email Address > Unsubscription Confirmation emails, but claim that they never requested to > be unsubscribed. (All are Gmail users. but they might be coincidental, > since most list members are Gmail users.) > > Has anyone seen this behavior before? Any ideas on what might be happening? Yes. This is someone sending an email `leave` or `unsubscribe` command for the user in question. This may be malicious, i.e. someone doesn't like a user's posts and tries to unsubscribe them, or it may be just spam of some sort. the user should just ignore the email. Beyond that, there's not much you can do unless you can identify from mail logs the source of the requests. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Removing the footer from mailing list messages

by Mark Sapiro

On 12/7/25 14:00, MegaBrutal via Mailman-users wrote: > > What I already tried: define a custom template for > list:member:regular:footer. The result was that the mailing list stopped > operating altogether, no messages passed through until I deleted this > template. After I deleted it, all delayed e-mails were forwarded at once. How did you create the footer? If you created a file at Mailman's var/templates/whatever/list:member:regular:footer.txt, it probably was not readable by the Mailman user. If you created it via Postorius there is probably and issue with your setting for POSTORIUS_TEMPLATE_BASE_URL. > What would be the right way to remove the footer? For all lists sudo -u mailman cp /dev/null var/templates/site/en/list:member:regular:footer.txt For a single list sudo -u mailman cp /dev/null var/templates/lists/LIST-ID/en/list:member:regular:footer.txt -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 1 week

[MM3-users] Re: Disable Sign-up per domain

by Mark Sapiro

On 7/31/25 23:00, Mark wrote: > > The traceback does suggest that the SITE does not exist... Yes. Please confirm that the issue only occurs with the modified /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py and does not occur with the original .../user_adapter.py. Also, prior to installing the modified /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py did you have ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' in your settings or did you only add that with the modified .../user_adapter.py I.e., I'm trying to determine if there is some issue with the modified ../user_adapter.py or if the issue does not involve the modification, but rather just the setting of ACCOUNT_ADAPTER Also, when does this error occur? Does it occur an all web access to the site or only on access to the accounts/signup page? and does the host in the https request make a difference? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 2 weeks

[MM3-users] Re: Mailing lists sometimes do not honor moderation_action of non-members

by Mark Sapiro

On 11/3/19 6:58 PM, Alan So wrote: > Are there any pointer of documentation that I can clear all _these_nonmembers settings by updating the databases directly or using mailman shell? I am not so familiar with mailman shell though. We expect list owners use moderation_action only for members and non-members. $ bin/mailman shell -l test.example.com Welcome to the GNU Mailman shell The variable 'm' is the test.example.com mailing list >>> m.accept_these_nonmembers = [] >>> m.hold_these_nonmembers = [] >>> m.reject_these_nonmembers = [] >>> m.discard_these_nonmembers = [] That will just blindly clear them all. If you want to see what you're clearing, you could do things like >>> if m.accept_these_nonmembers: ... m.accept_these_nonmembers ... m.accept_these_nonmembers = [] ... which if the list's accept_these_nonmembers is non-empty will display it and then set it empty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

Search results for query "sapiro"