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

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/10/25 18:30, MegaBrutal via Mailman-users wrote: > > Thanks, I successfully removed my unwanted address, so it now doesn't > appear anywhere. (Looks like .remove(n) wasn't needed, it only gave an > exception, and the settings were saved even without commit() – which is > concerning because I would have assumed that I can cancel transactions by > omitting it.) As it says when you first invoke `mailman shell` Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. > However, the problem still persists: I can't post to the list from > HyperKitty. In this regard, nothing has changed since my original report. > I'm subscribed to the list with my primary, preferred address, which is the > GMail address right now. So your gmail.com address is a list member and your megabrutal.com address is only an owner. Is that correct? What if you add your megabrutal.com address as a list member - you can set delivery to disabled if you don't want it to get mail. Does that work? How are you logging in to the web UI. I am concerned, because if you are logging in to an account that has both addresses linked, you should see the ``` This message will be sent as: user(a)example.com Link another address ``` line below the text box in the message dialog and if you click on user(a)example.com, you should be able to pick the other address. Also, if you go to https://example.com/user-profile/ you should see a Primary email: and Other emails:. Do you see that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Not able to start mailman server

by Mark Sapiro

On 8/5/21 12:53 AM, Kartheek Reddy Bondugula wrote: > Hi, > > I am trying to setup postorius using this website - > > https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/docs/W... That documentation is out of date. Start at https://docs.mailman3.org/en/latest/ > I am trying to create a mailling list and it web interface for the users in my group > > The command 'pip install -e ./'(python3) runs successfully but still i am not able to start the server Is the result the same as in your post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, i.e., /usr/local/Cellar/python(a)3.9/3.9.5/bin/python3.9: can't open file '/usr/local/opt/python(a)3.9/bin/master': [Errno 2] No such file or directory > my mailman info shows - > > GNU Mailman 3.3.5b1 (Tom Sawyer) > Python 3.9.5 (default, May 4 2021, 03:36:27) > [Clang 12.0.0 (clang-1200.0.32.29)] > config file: /Users/.../Documents/mailman/var/etc/mailman.cfg > db url: sqlite:////Users/.../Documents/mailman/var/data/mailman.db > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass We recommend following this guide https://docs.mailman3.org/en/latest/install/virtualenv.html What is the content of the /Users/.../Documents/mailman/var/etc/mailman.cfg file? The 'pip install -e ./' command should have created a bin/ directory containing both `mailman` and `master` executable files and this `mailman` command is the one you should be running. It appears the `mailman` command you are running is '/usr/local/opt/python(a)3.9/bin/mailman'. If that is in fact a symlink to a different bin/mailman file, there should also be a symlink from '/usr/local/opt/python(a)3.9/bin/master' to the existing bin/master or you should adjust your path. What do `which -a mailman` and `which -a master` show? -- 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: Search function returning results from another list

by Marco van Tol

Hi there, For completeness, I could fix the issue by issuing a './manage.py rebuild_index' from the hyperkitty container. (We're running mm3 in containers) Thanks! Marco van Tol RIPE NCC On Mon, 14 Oct 2024 at 16:53, Marco van Tol <mvantol(a)ripe.net> wrote: > Hi there, > > We actually found that if you look for "*" it will find exclusively > messages from the other list, from the first looks of it. > > But if you "show the archive" in the normal way, without using the search > function, it will work as expected. > Other lists on the same server show the correct messages when you search > for "*", I wonder what went bad with this list. > > It originally came from a mailman2 server and was imported from that. > > Thanks! > > Marco van Tol > RIPE NCC > > > On Mon, 14 Oct 2024 at 16:06, Marco van Tol <mvantol(a)ripe.net> wrote: > >> Hi there, >> >> We have several lists on our list server here, and noticed that if we do >> this: >> - go to the archive of public list x >> - type in "minutes" in the search bar >> >> If will: >> - show a screen: list-x search results for query "minutes" >> - have 3 results in there for another private list >> - show a message that you need to login to view the message if you click >> on one >> >> Our current mailman core version is: 3.3.9 >> Our current hyperkitty version is: 1.3.10 >> Our index engine is: xapian_backend.XapianEngine >> >> Does this make sense? >> >> Thanks! >> >> Marco van Tol >> RIPE NCC >> >

1 year, 8 months

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

by Odhiambo Washington

On Mon, 27 Jul 2020 at 02:49, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 9:12 AM, Odhiambo Washington wrote: > > On Sun, 26 Jul 2020 at 18:48, Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 7/26/20 3:15 AM, Odhiambo Washington wrote: > >> > >>> There is still some confusion on my part about the directives in the > file > >>> so allow me to seek some clarifications. > >>> > >>> The following are the contents of a file I have created and placed in > my > >>> Apache Includes/ directory. > >>> I was hoping that with it, I can now access http://lists.my.server/mm3 > >> and > >>> get the UI. > >>> > >>> <CUT> > >>> > >>> # Global section > >>> WSGIDaemonProcess mailman-web display-name=mailman-web > >>> maximum-requests=1000 umask=0002 user=mailman3 \ > >>> group=mailman3 > >>> > >> > python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 > >>> \ > >>> python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > >>> WSGIRestrictSignal Off > >>> > >>> <VirtualHost *:80> > >>> ServerName lists.my.server > >>> ServerAdmin odhiambo(a)gmail.com > >>> > >>> # (I'm not sure that WSGIRestrictSignal Off is required, but it was in > >> the > >>> # provided example so I kept it. I also made changes to > WSGIDaemonProcess > >>> # based on my own mod_wsgi experience elsewhere.) > >>> > >>> ErrorLog /var/log/myserver-error.log > >>> LogLevel debug > >>> > >>> # This goes in the VirtualHost block for the domain. > >>> > >>> # Mailman 3 stuff > >>> Alias /static "/var/spool/mailman-web/static" *<----- Where is this > >>> directory supposed to be and what/who creates it and with what > >> permissions?* > >> > >> > >> It is created/updated by the mailman-post-update script based on CONFDIR > >> and STATIC_DIR. > >> > > > > The fact that I have run the mailman-post-update script and these > > directories aren't created means there is a problem in my setup, yes? > > > If your mailman-post-update script is essentially the same as > < > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > > > and it ran successfully, it would have created opt/mailman/mm/static and > populated it. What was the output when you ran it? > > > Yes, I have these files: > > (venv) [root@gw /opt/mailman/mm]# ls -al /opt/mailman/mm/settings* > > -rw-r--r-- 1 mailman3 wheel 15518 Jul 25 14:34 > > /opt/mailman/mm/settings.py > > -rw-r--r-- 1 mailman3 wheel 15773 Jul 26 10:33 > > /opt/mailman/mm/settings_local.py > > > Is there an empty /opt/mailman/mm/__init__.py file? > No. root@gw:/usr/local/mailman # ls -al /opt/mailman/mm/ total 88 drwxr-xr-x 8 mailman3 wheel 512 Jul 26 14:55 . drwxr-xr-x 6 mailman3 wheel 512 Jul 26 18:38 .. drwxr-xr-x 8 root wheel 512 Jul 25 22:16 .sass-cache drwxr-xr-x 2 mailman3 wheel 512 Jul 26 16:35 __pycache__ drwxr-xr-x 2 mailman3 wheel 512 Jul 25 14:42 bin -rw-r--r-- 1 mailman3 wheel 248 Jul 25 14:37 gunicorn.conf -rw-r--r-- 1 mailman3 wheel 266 Jul 26 15:34 gunicorn.conf.py lrwxr-xr-x 1 mailman3 wheel 24 Jul 25 14:39 logs -> /opt/mailman/mm/var/logs -rw-r--r-- 1 mailman3 wheel 370 Jul 25 14:32 mailman-hyperkitty.cfg -rw-r--r-- 1 mailman3 wheel 1291 Jul 26 17:12 mailman.cfg -rw-r--r-- 1 mailman3 wheel 15518 Jul 25 14:34 settings.py -rw-r--r-- 1 mailman3 wheel 15805 Jul 26 21:22 settings_local.py drwxr-xr-x 9 mailman3 wheel 512 Jul 25 22:16 static -rw-r--r-- 1 mailman3 wheel 1395 Jul 25 14:35 urls.py drwxr-xr-x 12 mailman3 wheel 512 Jul 26 19:30 var drwxr-xr-x 5 mailman3 wheel 512 Jul 26 17:11 venv -rw-r--r-- 1 mailman3 wheel 1170 Jul 26 11:39 wsgi.py > > > PS: I made my /opt/mailman to be owned by mailman3:wheel because of a > > confusion with the instructions at some point in the reading > > of some documentation previously (in my previous attempt last year!) and > > had noted that in my NOTES. I'll change this once things get clear for > me. > > Also, the fact that one of the init scripts > > < > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > > > > in your "reflection" page was calling sudo :) > > > It does `sudo -u $USER ...` so that it runs Mailman as the Mailman user > as it should. Have you set > > USER=mailman3 > in yours? > Yes. However, that also means the /opt/mailman should be owned by mailman3, right? So I wasn't quite mistaken. 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. Kindly clarify. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 10 months

[MM3-users] Re: MM2 to MM3 on debian 10

by Mark Sapiro

On 4/27/20 8:26 AM, Gelpi Andrea wrote: > Hi, on a debian 10 with MM3 I'm trying to migrate form some old MM2 > mailing lists. I know that not all can work. > > In my old lists I have email and regular expressions in > reject_these_nonmembers and discard_these_nonmembers > > After importing the list all these email are in non member list. > > All these email have Delivery status enabled. Delivery status is not relevant for non-members and only has to do with receiving list posts in any case. What version of Mailman core is this? There have been changes in `mailman import21` that may affect this, but an address in `reject_these_nonmembers` should be imported as a non-member with a moderation action of `reject` and similarly for `discard`. Note that regexps in *_these_nonmembers should be imported into the MM 3 legacy *_these_nonmembers attributes. Some older versions of import21 also imported non-regexp addresses here, but that was wrong. > Does this mean that all of them will receive any message sent to the list? > The moderation rule is correct, but if I understood correct Delivery > status should be disabled. Delivery status is irrelevant for non-members. Only members are candidates for delivery. > For migration I followed this link > https://docs.mailman3.org/en/latest/migration.html > > To migrate archives it states to run > > python manage.py hyperkitty ... > > I cant' find a manage.py on debian 10 manage.py is a Django generic term for the Django admin command. You probably want something called django-admin or similar. > A search shows the only /usr/share/mailman3-web/manage.py exists. > > Is there any documentation specific for debian? That would be up to Debian. -- 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: So near, and yet so far (Configuring Mailman)

by Joel Lord

On 1/29/2021 12:01 PM, Jack Lenox via Mailman-users wrote: > Hello all, > > I've spent more time than I care to admit trying to configure Mailman. And I almost have it all working now, but I just can't seem to get my Mailman/Postfix combo to receive emails. > > When I try to send emails to lists I'm rebuffed with undelivered notices with: > > <testlist(a)lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists type=AAAA: Host not found > and: > <testlist(a)lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists.fiftyshadesof.green type=MX: Host not found, try again > > This to me appears to be an issue with my DNS settings, but I can't work this out either. I have an A record for lists.fiftyshadesof.green pointing at my server, and an MX record pointing at that: > > lists.fiftyshadesof.green. 0 IN MX 0 lists.fiftyshadesof.green. > lists.fiftyshadesof.green. 0 IN A 193.37.35.191 > > I have driven myself mad with this and would very much appreciate any advice anyone can offer. The key here isn't in your mailman config, or even your postfix config (you might be able to fix it there, I'm not sure). The key is in the error: <testlist(a)lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists type=AAAA: Host not found Specifically, type=AAAA. It's looking for an IPv6 host record and you don't have one. I'm going to guess you got that bounce not from your lists host, rather from your mail relay? Somewhere along the way something is trying to use IPv6 and needs to get kicked to either not do that or at least fall back to IPv4. -- Joel Lord

5 years, 4 months

[MM3-users] ValueError: The ADMINS setting must be a list of 2-tuples.

by David Partain

Greetings, We're trying to move from an ancient and bad Ubuntu-package based installation of mailman3 to a venv-based do-it-the-right-way installation. # mailman --version GNU Mailman 3.3.9 (Tom Sawyer) Things seem much better than past migration attempts. We are, though, seeing tons of errors in uwsgi-error.log that look like this: Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/wsgi.py", line 131, in __call__ response = self.get_response(request) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 140, in get_response response = self._middleware_chain(request) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 58, in inner response = response_for_exception(request, exc) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 144, in response_for_exception log_response( File "/local/mailman/venv/lib/python3.10/site-packages/django/utils/log.py", line 241, in log_response getattr(logger, level)( File "/usr/lib/python3.10/logging/__init__.py", line 1506, in error self._log(ERROR, msg, args, **kwargs) File "/usr/lib/python3.10/logging/__init__.py", line 1624, in _log self.handle(record) File "/usr/lib/python3.10/logging/__init__.py", line 1634, in handle self.callHandlers(record) File "/usr/lib/python3.10/logging/__init__.py", line 1696, in callHandlers hdlr.handle(record) File "/usr/lib/python3.10/logging/__init__.py", line 968, in handle self.emit(record) File "/local/mailman/venv/lib/python3.10/site-packages/django/utils/log.py", line 128, in emit self.send_mail(subject, message, fail_silently=True, html_message=html_message) File "/local/mailman/venv/lib/python3.10/site-packages/django/utils/log.py", line 131, in send_mail mail.mail_admins( File "/local/mailman/venv/lib/python3.10/site-packages/django/core/mail/__init__.py", line 124, in mail_admins raise ValueError("The ADMINS setting must be a list of 2-tuples.") ValueError: The ADMINS setting must be a list of 2-tuples. Our ADMINS setting in /etc/mailman3/settings.py has ADMINS = ( ('Mailman Suite Admin', 'someone(a)our.domain', 'someoneelse(a)our.domain'), ) Can someone point me in a direction to correct this? Thanks in advance. David

2 years, 2 months

[MM3-users] Re: Python 3.13 compatibility

by Thomas Ward

Okay, so links get purged apparently [1] was supposed to point at https://docs.mailman3.org/en/latest/install/install.html On 2026-03-30 13:49, Thomas Ward via Mailman-users wrote: > With recent revisions I made to the general Installation page that > leads to other pages [1], we could write a > "Install-From-HEAD-DANGEROUS" document (akin to the existing > virtualenv install documents but then specify alternative install > commands to install from HEAD), detailing how to install from HEAD > with the major disclaimer notice about this NOT being recommended > unless you want or need to track Git HEAD. > > The parent page there at [1] can thus have a huge disclaimer saying > "You should only do this if you really need to or are intending to > work with development of Mailman 3 and its components." > > Happy to write a proposal of such a document for review. > > > Thomas > > > On 2026-03-30 13:45, Stephen J. Turnbull wrote: >> Stephen J. Turnbull writes: >> >> > Putting that recipe as is in the developer docs also doesn't make >> > that much sense to me, as developers are expected to have full >> > clones of the components they're working on. On the other hand >> > something that points at the dev's local repos of the Mailman Suite >> > components does make a lot of sense to me. >> >> That would be somewhere in the neighborhood of >> mailman/src/mailman/docs/install.rst. >> >> Steve >> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to teward(a)thomas-ward.net

2 months, 2 weeks

[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, 6 months

[MM3-users] Re: Problem updating mailman

by Brian Carpenter

Mark Sapiro wrote: > On 1/24/21 1:03 AM, Odhiambo Washington wrote: > > I uninstalled rubygem-sass from the OS. I don't > > remember consciously > > installing that because it was never in the guide I followed (which is your > > own writeup). > > But I still have a problem: > > (venv) [mailman3@gw ~/mm]$ /opt/mailman/mm/bin/mailman-post-update > > > > '[' False == False ']' > > mkdir -p /opt/mailman/mm/static > > /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > > --verbosity 0 > > /opt/mailman/mm/bin/django-admin compress > > CommandError: An error occurred during rendering > > /opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3-1.3.5-py3.7.egg/django_mailman3/templates/socialaccount/signup.html: > > /bin/sh: sass: not found > > > > You can't just uninstall rubygem-sass. You have to replace it. Here's > one recipe for Ubuntu > cd /usr/local/lib > # See https://github.com/sass/dart-sass/releases/tag/1.32.5 for the > # appropriate version. > wget > https://github.com/sass/dart-sass/releases/download/1.32.5/dart-sass-1.32.5-... > sudo tar -xf dart-sass-1.32.5-linux-x64.tar.gz > sudo chmod -R o-w dart-sass > sudo ln -s dart-sass/sass /usr/local/bin/sass > rm dart-sass-1.32.5-linux-x64.tar.gz > Then you should see the command > sass --version > prints > 1.32.5 > Then, because dart-sass doesn't recognize the short form -t option for > --style, you have to edit your settings(_local).py and change > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass -t compressed {infile} {outfile}'), > ('text/x-sass', 'sass -t compressed {infile} {outfile}'), > ) > to > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass --style compressed {infile} {outfile}'), > ('text/x-sass', 'sass --style compressed {infile} {outfile}'), > ) I had to do a new installation of Mailman 3 with Postorius/Hyperkitty today and these directions were very helpful. Thank you, Mark.

5 years, 4 months

[MM3-users] Re: Template for Password Reset Email

by Mark

On 2024-11-18 01:38, Mark Sapiro wrote: > On 11/17/24 16:57, Mark wrote: >> >> I can see the French text for the "Password Reset Email" in the >> django.po file. And running the compilemessages command reports the >> "django.po" for French is okay and up to date. Should I be recompiling >> the ".mo" file? > > No, It's fine. The issue is the language context for this message has > nothing to do with any Mailman list's preferred language. > > Again, see > https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… > > If all the lists on your server are French, you could set > > LANGUAGE_CODE = 'fr' > > in your Django settings. Otherwise, the user's browser has to include > an Accept-Language: header specifying French as the most preferred > language in it's request. > > Also note the ordering of SessionMiddleware, LocaleMiddleware and > CommonMiddleware in the above doc. I have recently updated the various > places where we suggest or supply MIDDLEWARE settings, but you may > find that your settings have LocaleMiddleware after CommonMiddleware > and you should fix that. It's just the one list that is using French. Others are in English I've edited the order of the middleware settings in this file ... /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/settings/base.py I reordered as below, restarted everything but no joy :-( ... at Line 76 ... MIDDLEWARE = ( 'allauth.account.middleware.AccountMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.middleware.common.CommonMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware', ) ... I'm thinking this is not the file I'm looking for. Apologies for my cluelessness here.

1 year, 7 months

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

by Abhilash Raj

On 10/23/23 20:37, Thomas Ward via Mailman-users wrote: > I want to add a custom handler that implements customized thread IDs in > the system. I already have the DB logic worked out, but the > documentation for plugins is NOT clear on how to define a handler in a > plugin, nor does the example plugin in the documentation on Gitlab have > any custom handlers. > > I'm looking to add a custom handler so that the private pipeline for > threaded-subject-list can use thread-subject (the custom handler) > instead of subject-prefix (builtin). https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/plugins/testin… https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do… These are two places you can find docs for an example plugin that ships with Mailman's code. Adding a new "component", like a Handler, works very similar to the "rules" in the example shown above. You will probably need a directory tree like: ``` example/ __init__.py hooks.py handlers/ __init__.py handlers.py ``` Installing the handler is same as per shown in docs using below (do note that the above example is the name of the package that is importable): ``` [plugin.example] class: example.hooks.ExamplePlugin enabled: yes [logging.plugins] propagate: yes ``` Finally, you can verify that your handler was loaded properly using something along the lines of: ``` $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> for each in config.handlers: ... print(each) ... member-recipients to-archive cleanse-dkim file-recipients to-outgoing mime-delete after-delivery decorate to-digest avoid-duplicates arc-sign cook-headers replybot tagger acknowledge dmarc subject-prefix validate-authenticity owner-recipients to-usenet cleanse rfc-2369 ``` -- thanks, Abhilash Raj (maxking)

2 years, 7 months

[MM3-users] Re: Subscribe only to one thread

by Ivan Perez

I don't have the skills but, is there any other way I can help? Ivan On 7 May 2018 at 19:45, Terri Oda <terri(a)toybox.ca> wrote: > We've already got the code for it. It was the "dynamic sublists" project. > Systers built dlists for their needs with mailman 2 and we had a student > implement it on mailman 3. > > The problem has just been in getting the patches integrated, which was > mostly on me not being able to follow through at the critical time (as > opposed to there being technical reasons it wasn't done). I still don't > have the volunteer time necessary to port them forward to the latest > version of mailman now and do the integration, but would be happy to help > answer questions if someone else is interested in working on it. > > Terri > > On May 7, 2018 12:59:32 PM PDT, Ivan Perez <ivanperezdominguez(a)gmail.com> > wrote: > >> Dear Mailman users, >> >> There are many high-traffic mailing lists in which I would only be >> interested in receiving messages in specific threads (not all messages, nor >> some topics, nor a daily digest). >> >> Is there a way of "subscribing" to individual threads only, mainly those I >> initiate, or I actively participate in, but generally not receiving any >> emails from the list? >> >> If not, would others find this useful, and could it be implemented? (I >> understand that everyone wants features; I just don't know if it's a 2-hour >> patch or a 2-month project). >> >> Best wishes >> >> Ivan >> ------------------------------ >> >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> >>

8 years, 1 month

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

by Thomas Ward

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

2 years, 11 months

[MM3-users] Re: psycopg2 error?

by Mark Sapiro

On 10/26/23 01:03, Odhiambo Washington wrote: > > <CUT> > root@debian12:/home/wash# systemctl status mailman3.service > × mailman3.service - GNU Mailing List Manager > Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: > enabled) > Active: failed (Result: exit-code) since Thu 2023-10-26 09:36:41 EAT; > 8s ago > Process: 1893842 ExecStart=/opt/mailman/venv/bin/mailman start > (code=exited, status=1/FAILURE) > CPU: 789ms > > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: dbapi = > dbapi_meth(**dbapi_args) > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: > ^^^^^^^^^^^^^^^^^^^^^^^^ > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: File > "/opt/mailman/venv/lib/python3.11/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", > line 690, in import_dbapi > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: import psycopg2 > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: File > "/opt/mailman/venv/lib/python3.11/site-packages/psycopg2/__init__.py", line > 51, in <module> > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: from > psycopg2._psycopg import ( # noqa > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: SystemError: > initialization of _psycopg raised unreported exception > Oct 26 09:36:41 debian12.wash.lan systemd[1]: mailman3.service: Control > process exited, code=exited, status=1/FAILURE > Oct 26 09:36:41 debian12.wash.lan systemd[1]: mailman3.service: Failed with > result 'exit-code'. > Oct 26 09:36:41 debian12.wash.lan systemd[1]: Failed to start > mailman3.service - GNU Mailing List Manager. > </CUT> Is your database PostgreSQL or some other? If it's not PostgreSQL, see the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… - particularly https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Also see https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… where it now says in part "This will install latest release of Mailman Core, and Python bindings for Postgresql database. If you are using a different database manager, do not install psycopg2-binary." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Why is it so difficult to setup Mailman3?

by Thomas Ward

Most of that can be done with scripting in the container. It would ultimately though end up as a 'ready to go' venv environment if people want it. I'm already working on an approach to automate install and setup of MM3 for other things I'm working on, so I'll keep this as a backup consideration for contributions. Thomas Sent from my Galaxy -------- Original message -------- From: "Stephen J. Turnbull" <steve(a)turnbull.jp> Date: 4/8/26 16:21 (GMT-05:00) To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Why is it so difficult to setup Mailman3? Thomas Ward via Mailman-users writes: > Stephen, would a prebuilt LXD-style container or VM that is respun > quarterly but is still a base virtualenv setup based on Ubuntu > 24.04 and otherwise fully 'setup' except for actual domain configs, > etc. be useful here as an 'alternative' to 'do it yourself' but > still work as a full venv setup? That's a good question, but I don't know the answer. I can see that it has fewer moving parts than docker-mailman, but whether the people who find the current venv install too complex would find it appealing, I can't say. There is also the problem that you will need some way to generate the various authentication tokens and install them in the image ex post -- they can't be hard-coded. I don't think that's too hard, though. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to teward(a)thomas-ward.net

2 months, 1 week

[MM3-users] Re: Attachement processings questions

by Mark Sapiro

On 2/3/20 4:27 AM, Lars Schimmer wrote: > > In a mailinglist it seems some mails are not forwarded to a member, but > is listed in archive in hyperkitty. > That mail did include a PDF attachement, but HyperKitty does not list > any attachement. There are two issues here. Why wasn't the message delivered to list members?, and why is there no attachment in Hyperkitty? For the first issue, you need to examine mailman.log for the time of the post looking for errors and tracebacks. Also, the MTA logs may have useful info if the messages were sent but not delivered. For the second, there are many content filtering settings not (yet) exposed in Postorius. These include filter_extensions, filter_types, pass_extensions and pass_types which control which MIME parts are removed. For a newly created Mailman 3 list, these four settings are empty, but importing a Mailman 2.1 list will set them according to the corresponding MM 2.1 list's settings. > All I found was "convert HTML to plaintext", but does this setting > remove attachements? It would only affect HTML parts, not pdfs. > Is there any generel documentation about attachement processing in MM3? <https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/filterin…>. > I would like this mailinglist to accept mails with attachements, send it > to the members and archvie the attachments in HyperKitty, to. You can set Settings -> Alter Messages -> Filter content to No in Postorius to not do any content filtering at all. This will override the Collapse alternatives and Convert html to plaintext settings and pass the message without removing any MIME parts. But, I think you must have other issues, either with this mail in particular or in general as evidenced by the mail not being received by list members. -- 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] Hyperkitty: Error when rebuilding Index

by M4tze

Dear list members, if there is any Hyperkitty expert here, I have issues in Hyperkitty (just updated Maxkings Docker images) when rebuilding the Index. Unfortunately, there are more than 25,000 mails and I do not know which one is/might be broken. Does the error mean that the rebuilding process is incomplete or does it simply skip the erroneous message? Thank you in advance - M4tze Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/haystack/management/commands/update_index.py", line 297, in handle self.update_backend(label, using) File "/usr/lib/python3.8/site-packages/haystack/management/commands/update_index.py", line 342, in update_backend max_pk = do_update( File "/usr/lib/python3.8/site-packages/haystack/management/commands/update_index.py", line 100, in do_update current_qs = list(current_qs) File "/usr/lib/python3.8/site-packages/django/db/models/query.py", line 269, in __len__ self._fetch_all() File "/usr/lib/python3.8/site-packages/django/db/models/query.py", line 1308, in _fetch_all self._result_cache = list(self._iterable_class(self)) File "/usr/lib/python3.8/site-packages/django/db/models/query.py", line 53, in __iter__ results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size) File "/usr/lib/python3.8/site-packages/django/db/models/sql/compiler.py", line 1156, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 66, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3.8/site-packages/django/db/backends/mysql/base.py", line 73, in execute return self.cursor.execute(query, args) File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 209, in execute res = self._query(query) File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 317, in _query self._post_get_result() File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 352, in _post_get_result self._rows = self._fetch_row(0) File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 325, in _fetch_row return self._result.fetch_row(size, self._fetch_type) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xed in position 3209: invalid continuation byte

4 years, 6 months

[MM3-users] Race condition when mass subscribing same email addresses to two lists?

by Stephen J. Turnbull

Alan So writes: > 1) Create two lists with default setting > 2) Prepare a list of 1000 fresh email addresses not added to the > system before > 3) Mass subscribe both lists of these 1000 email addresses around > the same time with all three Pre (confirm, approved, verified) > checked [...] > (psycopg2.errors.UniqueViolation) duplicate key value violates > unique constraint "ix_address_email" > DETAIL: Key (email)=(testemail999(a)example.com) already exists. I think there's some kind of race condition. I would bet it's in Mailman core, not in the RDMBS code or the ORM. The process is 1. Check if the address is known. 2. If yes: a. Get the address's user. b. Add the subscription pair (address, list) to the user. c. Add the address to the list. 3. If no: a. Create the address object. b. Create a user for the address, and link them together. c. Add the subscription pair (address, list) to the user. d. Add the address to the list. Each line is a separate database query, I suspect, so the race is between 1 and 3a. If two requests for the same new address arrive at the "same" time, both will try to create the address, only one can succeed. I guess we should catch the error and retry. Raising and handling exceptions in Python is relatively slow, so even in your well constructed worst case, this shouldn't happen on every address, so I don't think having a separate queue or putting the whole thing in a transaction would be better. If you still have the log, I'd be curious to know how many unique errors you got. I need to do other work for the next 48 hours, but a patch would be very welcome. I don't know offhand where this code lives, sorry. Steve

4 years, 7 months

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

by Prasanth Nair

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

4 years, 8 months

[MM3-users] Setting up on ubuntu server 22.04

by Stephen J. Turnbull

Kyriakos Terzopoulos writes: > ImportError: cannot import name 'path' from 'importlib_resources' Try putting the error message into Google with "" around it. (This is generic advice for the future, obviously I already know what it is and will tell you. :-) This is a known issue where Python changed some APIs that Mailman uses. Discussion is here: https://gitlab.com/mailman/mailman/-/issues/1093 There's a simple patch to requirements.txt at the end of the comments. Edit it, and delete and reinstall the mailman package, it will take 10 minures. If you're familiar with Python and pip you can also force remove that package, then reinstall with the additional version constraint. > In general would it be better or/and easier to set this up on a new > machine in my Hetzner cloud e.g. on Debian which seems to have > packages of mailman available? That depends. Do you want to get your Mailman help from Debian (the answer is "NO!!"[1] unless you mostly expect to need no help -- that probably works for 70% of Debian + Mailman users) or from us? Unless your use case is exactly what the distro maintainer envisions, you will occasionally run into issues that are impossible for them to figure out, and rather expensive for us to help you with since they depend on old and modified versions. We strongly prefer you use a venv install, and if Mailman is at all important to your site's mission, you probably will too. Footnotes: [1] At least for servers, I prefer Debian myself. Distros are the best thing since sliced bread. But Mailman is still a relatively fast-moving target[2] and none of the distros keeps up. [2] In part because Gmail, Yahoo!, and O365 hate mailing lists, almost as much as the spammers hate us, and we keep tweaking things to deal with both kinds of Internet mischief.

2 years, 8 months

[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, 10 months

[MM3-users] Re: no mails to list members

by Thomas Stein

On 04.01.19 16:05, Abhilash Raj wrote: > > > On Fri, Jan 4, 2019, at 7:02 AM, Thomas Stein wrote: >> On 04.01.19 15:55, Abhijith PA via Mailman-users wrote: >> > >> > >> > On Friday 04 January 2019 08:19 PM, Thomas Stein wrote: >> >> On 04.01.19 09:40, Thomas Stein wrote: >> >>> >> >>> Turns out mailman was not able to read a specific template. That seemed to be enough to throw an exception. Maybe >> >>> i missed something else but after adjusting the permissions of that template everything worked as expected. >> >> >> >> While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? Should >> >> I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? Is there some documentation >> >> what variables i can put in those templates? >> > >> > If you are using 3.2.0, you can do that from webapp itself. [ I haven't >> > tried though] >> >> Running 3.1.1 right now. 3.2.0 isn`t in the ubuntu repo yet afaik. >> >> https://launchpad.net/ubuntu/+source/mailman3 > > This link mentions that 3.2.0-1ubuntu1 is the current stable version. But not for ubuntu 18.04. This one indeed does. https://launchpad.net/~efficios/+archive/ubuntu/mailman3 cheers t. >> >> thanks and cheers >> t. >> >> > >> > --a >> > _______________________________________________ >> > Mailman-users mailing list -- mailman-users(a)mailman3.org >> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> >

7 years, 5 months

[MM3-users] Notes about successfuly upgrade from python 3.7 to 3.9

by Guillermo Hernandez (Oldno7)

I've successfuly upgrade servers with mailman3 lists from FreeBSD 12.3 with python 3.7 to FreeBSD 13.1 with python 3.9 After doing the O.S. and all the python related apps upgraded I did the following steps: (note that my mailman3 installation is system-wide, pip drived and apache24/uwsgi served. The user that owns mailman3 is "mailman3" and all the stuff lies in "/usr/local/mailman3") -> su -> cd /usr/local/mailman3 -> pip install --upgrade django-mailman3 mailman mailman-hyperkitty mailmanclient postorius django hyperkitty uwsgi mod-wsgi -> mod_wsgi-express module-config (it returns the path for the apache24 httpd.conf adjustments. I edited it) -> su -m mailman3 -c "python3 manage.py collectstatic" -> su -m mailman3 -c "python3 manage.py migrate" -> su -m mailman3 -c "python3 manage.py compress" -> cd /usr/local/lib/python3.9/site-packages/ -> cd postorius -> django-admin compilemessages -> cd ../hyperkitty -> django-admin compilemessages -> cd ../django_mailman3 -> django-admin compilemessages I had to edit again /usr/local/lib/python3.9/site-packages/mistune/scanner.py and add this two lines (this is a little bit annoying) from mistune.util import escape_html from mistune.util import escape_url And that was all. Restarted the servers and all is going smoothly All of this steps have been documented in this list by Mark & Stephen whom I'm very grateful. P.S.: As I did some upgrades ago, I didn't have to modify settings.py in the Hyperkitty area to add DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' But if you come from an old mailman/Hyperkitty version, you'll have to include in it. And the it's same if you are using UWSGI, you have to include in your apache config: WSGIPassAuthorization On -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 11 months

[MM3-users] Re: Cannot Install Web UI

by Stephen J. Turnbull

dap1--- via Mailman-users writes: > I made all the suggested changes and now am down to the next layer > of the onion when starting mailmanweb: You should have gunicorn installed in your Mailman virtual environment. Here's what that looks like for me (your "/opt/mailman3" may vary, your "/.v" almost certainly does, the part from /lib on down should be the same except maybe for the minor version of python3): $ ls /opt/mailman3/.v/lib/python3.13/site-packages/gunicorn/ __init__.py app debug.py http reloader.py util.py __main__.py arbiter.py errors.py instrument sock.py workers __pycache__ config.py glogging.py pidfile.py systemd.py $ > gunicorn[53945]: ModuleNotFoundError: No module named > 'gunicorn.app'; 'gunicorn' is not a package This error message appears to be saying that the file __init__.py is missing (that's how Python defines a folder to be a package). It's also possible that the gunicorn package is installed somewhere other than Mailman's virtual environment, and so missing entirely from Mailman's virtual environment. > I hope all this gets added to the docs for the next poor sole that > has to do this on Ubuntu. :-) I'm not really sure what to add, except to recommend gunicorn instead of uwsgi. uwsgi is a FAQ because it's usually installed as a system package, and so has different ideas where things go in the file system from Mailman. uwsgi is not a Python app so can't be installed automatically in the virtual environment. uwsgi issues come up several times a year. gunicorn has traditionally been unproblematic because it's a requirement of Mailman core anyway. When we figure out why your installation doesn't seem to have gunicorn, maybe there will be something to say. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

7 months, 3 weeks

[MM3-users] Mailing lists as the main collaboration centre at SME

by Stephen J. Turnbull

Rodrigo Camacho writes: > If your company uses mailing lists to run, please reach out. We are > currently using Gitlab issues to collaborate which has been quite > successful. I would be very interested to trade tips. While (obviously :-) I support the use of mailing lists for collaboration and have used them successfully in multiple contexts for decades, you should pay careful attention to the user experience. 1. Mail user agents vary widely in their capabilities and user interfaces. Sometimes that means quality. For example, Gmail's customizable filters seem to be ordinary Sieve filters, that's fine, but the user interface is terrible. In other cases, they're just different (think Emacs-based MUAs vs Gmail). You should consider providing support to users of various MUAs, and lean to "more" resources for that rather than "less". Make sure that users have access to good threading in their MUAs. Gmail "conversations" aren't a great model; that's about the minimum capability. For corporate mail, both internal and incoming from suppliers and customers, etc, you should provide an IMAP server. This allows you to deal with document retention policy and privacy requests centrally. But you need to remember that users may be keeping local copies. You may also want to provide a corporate webmail server. I can't recommend a good one; we just decommissioned ours in favor of IMAP access because everybody has a personal MUA with a better UI. (I think we're using Cyrus imapd suite.) 2. Avoid the temptation to create many precisely defined lists. In my experience, it's more important that it be easy to choose the lists to post to and to subscribe to, than they be closely focused on specific interests. Focus is better served by an MUA that allows collapsing and suppressing individual threads and subthreads. 3. More important than wiping out top-posting is that everyone agree on style. I've seen a few lists where people absolutely could not get the concept of "appropriate amount of context" where switching to top-posting improved the flow. In general for technical content interlinear responses are best. However for managerial content ("Do this" -> "Done" -> "What about" -> "That too" conversations) top-posting is often fine because it's so linear. "Bottom posting" of course is right out. 4. The HyperKitty archiver was designed with the "we demand Discord" crowd in mind. As an archive, it provides the obvious features, including integration with various full-text indexers for search. But the authors also added a bunch of forum-like features, including the ability to post from the HyperKitty web ui and likes. There are alternatives, such as the IETF's MailArchive, which uses a maildir message store, which makes it easy to add an IMAP server to the archive, one feature that HyperKitty doesn't provide. This allows seamless access to the archive via the MUA (personally I don't like switching back and forth between the MUA and the browser). I think it's also possible to configure IMAP servers like Cyrus to function as list archives, but I'm not sure about how to configure MUAs for that architecture. (Note that IETF is the kind of place where people are always experimenting and don't hesistate to rewrite applications to test it. But I thought the idea was cool.) 5. Choice of full-text indexing backend is important. We default to Whoosh because it's pure Python and just a pip away. We recommend Xapian for production, but I don't think we thought terribly carefully about it. The Django-Haystack project appears to recommend Solr or ElasticSearch for Haystack 2.0.0 (and these are "included" in Haystack 2.0,0, not sure what that means, while Xapian is a separate download). I don't think we support Haystack 2 yet, but surely we will. 6. Colleagues who are new to mailing lists will need training and encouragement in netiquette. Reply style (top vs interlinear) is mentioned above. Mailing lists are prone to branching threads. Members need to learn to (1) change the subject when mutating the topic so that subthreads can be distinguished and (2) use new posts to start a new topic (ie, "don't hijack threads"). You write that GitLab collaboration has been successful for you, so it may be that your discussions are usually quite linear, and (1) may not be so important for you. 7. Some people (like me :-) may take naturally to "long form", which is enabled by mailing lists. Others may find long, discursive posts annoying. Be sensitive to people who have different preferences. 8. Some posters will tend to combine several somewhat related issues in one post, which naturally leads to many branches into subthreads. This likely will work itself out, but it can be a point of irritation for some users. Just remember that mailing lists afford that style of posting more so than forums or tracker issues do. 9. Remember that email is not adapted to modern affordances such as live editing. Nor is it suitable for realtime interactions such as incident response. Often it will be obvious, but sometimes it will take some time to work out which channels are well-served by mailing lists and which need an alternative medium. In general, just remember that people will respond to the change in different ways, and the goal is to improve communication, not to get people to adapt to a particular notion of "how it *should* work". Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

9 months, 2 weeks

[MM3-users] Re: Dealing with spam from Web users

by Mark Sapiro

On 4/1/23 08:09, Jeremy Stanley wrote: > We recently migrated a bunch of lists from 2.1 to 3.3.7 and have > started to get spammers posting via HyperKitty (because I guess > that's easier for them than SMTP). It looks like I should be able to > set posts from HyperKitty to be automatically moderated by creating > a header filter on "User-Agent" matching "HyperKitty" but is there a > better/easier way? Typically, these would be non-members posting from HyperKitty and then being automatically subscribed. Set `Default action to take when a member posts to the list` to `Hold for moderation` so that all posts from members you haven't seen before are held. Then when handling a held post, if it is spam set the posters moderation action to discard and discard the message; if it is on topic, set the posters moderation action to default processing and accept the message. > Also, for things which already went out to the list, obviously I can > ban the spammer but what's the cleanest solution for removing > their posts from list archives so that we don't further their goals > by continuing to publish their handiwork? List owners should be able to delete messages and threads from HyperKitty, but they can't. See <https://gitlab.com/mailman/hyperkitty/-/issues/261>. You need to be a superuser to do this. If you are logged in as a user with Superuser status there will be a `Delete this thread` link in the thread view and a `Delete this message` link in the message view. You can use the `django-admin createsuperuser` command to create superusers. Also, anyone who is a superuser can set this for any user via the Django admin web UI. -- 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: Speed up importing mailman2 lists

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/19/25 06:08, t.maintz(a)fz-juelich.de wrote: > > We are currently planning to migrate from mailman2 to mailman3 as > > a container, have around 1500 lists and would like to complete > > the migration ideally in a few hours. I've done two massive migrations in the last year. In the first (~20k lists), the lists were down for maybe two hours, but it took 22 hours for HyperKitty to populate, mostly in Xapian indexing we realized in post-mortem analysis. In the second (~1k lists), no perceptible downtime because they have their own bespoke archiver that has a list-manager-agnostic API. The trick to zero delivery downtime is that you can configure your MTA to route to Mailman 3 if the list exists there, if not route to Mailman 2 if the list exists there, and if not continue to any lower priority routes. It worked as designed (mops sweat off brow ;-). We did take Postorius and the Mailman 2 management CGIs and email command addresses offline for the duration (3 hours in the first case, 30 mminutes in the second). This is sraightforward if Mailman 2 and Mailman 3 are running on the same host. Life is more complex if you're spinning up Mailman 3 in a separate node but it should be possible. I think if you're migrating to HyperKitty you can speed up the migration by shutting off indexing, and doing that later at the cost of confusing people who expect the lists to be indexed. I'm not sure if it's possible to migrate the archives concurrently with accepting new posts, or maybe to migrate archives in advance and backfill any posts that arrive during the list migration. And there's no reason why you can't leave the legacy Mailman 2 archives up for browsing as a backup for as long as needed. Steve

1 year, 3 months

[MM3-users] Re: templates

by Christian

Okay I sent a test message this morning and subscribers are reporting they did not receive it. The smtp.log shows 'smtp to degrowcali(a)lists.ccalternatives.org for 25 recips, completed in 3276.275292634964 seconds' (see below) I alone received it however and it is listed in the archive. Below is the excerpt from smtp.log. Two of my 5 lists are exhibiting this behavior, while 2 other lists are working normally. Please advise. Thank you. root@zarathustra:/opt/mailman/mm/var/logs# vi smtp.log May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) recip: degrowcali-bounces+vortexanthony=hotmail.com(a)lists.ccalternatives.org May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) >> b'DATA' May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) >> b'QUIT' May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) connection lost May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) Connection lost during _handle_client() May 05 08:11:35 2023 (768) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) May 05 08:11:35 2023 (768) Peer: ('127.0.0.1', 60312) May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) handling connection May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'LHLO zarathustra.ccalternatives.org' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'MAIL FROM:<> SIZE=9885 BODY=8BITMIME' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) sender: <> May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'RCPT TO:<degrowcali-bounces+alaitz.aritza=gmail.com(a)lists.ccalternatives.org>' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) recip: degrowcali-bounces+alaitz.aritza=gmail.com(a)lists.ccalternatives.org May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'DATA' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'QUIT' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) connection lost May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) Connection lost during _handle_client() May 05 08:13:46 2023 (771) <046f01d97f5c$27c4ada0$774e08e0$(a)degrowthcalifornia.org> smtp to degrowcali(a)lists.ccalternatives.org for 25 recips, completed in 3276.275292634964 seconds May 05 08:13:46 2023 (771) <046f01d97f5c$27c4ada0$774e08e0$(a)degrowthcalifornia.org> post to degrowcali(a)lists.ccalternatives.org from christian(a)degrowthcalifornia.org, 5012 bytes May 05 08:13:46 2023 (771) <168329874052.765.12737190159456781981(a)zarathustra.ccalternatives.org> smtp to degrowcali(a)lists.ccalternatives.org for 1 recips, completed in 0.011698722839355469 seconds May 05 08:13:46 2023 (771) <168329874052.765.12737190159456781981(a)zarathustra.ccalternatives.org> post to degrowcali(a)lists.ccalternatives.org from degrowcali-bounces+6397d6fde210be0b39dbf22a9868e61d6e2d0f23(a)lists.ccalternat ives.org, 11445 bytes May 05 08:13:46 2023 (771) <168329886073.765.17844938860507947692(a)zarathustra.ccalternatives.org> smtp to degrowcali(a)lists.ccalternatives.org for 1 recips, completed in 0.00799560546875 seconds May 05 08:13:46 2023 (771) <168329886073.765.17844938860507947692(a)zarathustra.ccalternatives.org> post to degrowcali(a)lists.ccalternatives.org from degrowcali-bounces+62749dfe16f9d39e2cd0c3e94754723efbe8169d(a)lists.ccalternat ives.org, 11400 bytes May 05 08:13:46 2023 (771) <168329958151.765.3625387421642934590(a)zarathustra.ccalternatives.org> smtp to degrowcali(a)lists.ccalternatives.org for 1 recips, completed in 0.008965730667114258 seconds May 05 08:13:46 2023 (771) <168329958151.765.3625387421642934590(a)zarathustra.ccalternatives.org> post to degrowcali(a)lists.ccalternatives.org from degrowcali-bounces+8890cbead24710cdebeedbbd96d99fcd7f6f1343(a)lists.ccalternat ives.org, 11426 bytes May 05 08:13:46 2023 (768) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) May 05 08:13:46 2023 (768) Peer: ('127.0.0.1', 39046) May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) handling connection May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'LHLO zarathustra.ccalternatives.org' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'MAIL FROM:<> SIZE=15076 BODY=8BITMIME' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) sender: <> May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'RCPT TO:<degrowcali-bounces+6397d6fde210be0b39dbf22a9868e61d6e2d0f23(a)lists.ccalte rnatives.org>' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) recip: degrowcali-bounces+6397d6fde210be0b39dbf22a9868e61d6e2d0f23(a)lists.ccalternat ives.org May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'DATA' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'QUIT' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) connection lost May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) Connection lost during _handle_client() May 05 08:13:46 2023 (768) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) May 05 08:13:46 2023 (768) Peer: ('127.0.0.1', 39050) May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) handling connection May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'LHLO zarathustra.ccalternatives.org' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'MAIL FROM:<> SIZE=15049 BODY=8BITMIME' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) sender: <> May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'RCPT TO:<degrowcali-bounces+8890cbead24710cdebeedbbd96d99fcd7f6f1343(a)lists.ccalte rnatives.org>' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) recip: degrowcali-bounces+8890cbead24710cdebeedbbd96d99fcd7f6f1343(a)lists.ccalternat ives.org May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'DATA' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'QUIT' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) connection lost -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, May 4, 2023 12:19 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: templates On 5/4/23 11:15, Christian via Mailman-users wrote: > In March when I started troubleshooting my lists, you stated: > > "Also, one other thing you might check. Do these non-working lists > have templates defined in postorius, in particular, one for > list:member:regular:footer, and if not, are there any in Mailman's > mailto:var/templates/lists/redlatinleg@lists.ccalternatives.org/ derectory > that Mailman doesn't have permission to find and read?" > > There are no other templates listed in either Postorius nor in > Mailman's var/templates (as I stated, I do not even lave a 'lists' > subdirectory under Mailman's var/templates). My subscribers are not > receiving message distributions from my lists, even while some of them > are listed in the archives. See the original thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U HWOG6S57FM2SIQWHEPWM3CDUSAMLOOP/ (which you hijacked about 4 messages in) and particularly the message at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ NZ7G3JMYXFTQNVJ2DYGJ6PETEQT55SKB/ Without further information, I can't say more than that. -- Mark Sapiro <mailto:mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailto:mailman-users@mailman3.org To unsubscribe send an email to mailto:mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ GJNYZK3DK4UZYAILV7JZ62PPVPDPKNOZ/ This message sent to mailto:csa@web-analysts.net

3 years, 1 month

[MM3-users] Re: Removing an archive from hyperkitty

by Stephen J. Turnbull

Phil Stracchino writes: > On 10/4/20 4:09 PM, Loïc Dachary wrote: > > Hi, > > > > It turns out to be a feature added in 1.3.1 [0]. I wonder if the MySQL instructions listed in this comment[1] are safe to use? I'm reluctant to upgrade because the machine is for production and using packages from Debian GNU/Linux buster is recommended. > > > > Cheers > > > > [0] https://gitlab.com/mailman/hyperkitty/-/issues/146 > > [1] https://gitlab.com/mailman/hyperkitty/-/issues/146#note_423111350 > > > To be honest, they don't look like very well written queries. They're not elegantly written, but they look correct to me (they're *supposed* to be a bulldozer :) and they worked for that user. If one doesn't have 1.3.1 and is unwilling to upgrade, it should be safe enough. 1. For extra safety you can take a snapshot of the database. 2. Make absolutely sure you have the right mailinglist_id. And that procedure should work. @Loïc Oerhaps you should review your policy on upgrading with respect to this particular application (choose Mailman suite or HyperKitty, depending). We're not seeing many regressions, but over time we are fixing inconveniences where documented features work as documented but are insufficient to get your work done, so you have to drop into "hack the Mailman command shell" or even "hack the backend RDBMS" mode. Ie, we're adding features that allow you to do the work with code we've written and tested, rather than some third party script. This is something only you can decide, of course, and I'm not going to advocate one way or the other. If you're pretty comfortable with direct access to your MySQL database, that way lowers risk of regressions by not upgrading the software. If you're not, upgrading lowers the risk you face with lightly tested third party procedures. Steve

5 years, 8 months

[MM3-users] Re: Two Questions: One General, the Other Specific

by Brian Carpenter

On 2/26/21 12:10 PM, David Wilson wrote: > For context, I have been lurking on this site for a number of years > now, in order to track the progress of this wonderful mailman3 project. > > Further context, I am chair of a 66 unit condominium and pay for two > lists provided by EMWD.com and get a hands on feel from an mailman3 > operations perspective. > > *Is there another site that might best communicate the future goals, > plans, objectives, and time frames for mailman3 or is the status of > the project at the state of being primarily reacting to problems, as > evidenced in this problem solving forum, at least as it seems to me, > with no offense meant or intended?* > > Something I find surprising is a problem described in an image grab > below relating to an inability to amend a list entry to include a name > to be associated with an email address, as if the data needs to be > immutable. When a workaround was unsuccessfully explored to delete > the entry and then resubmit an amended entry but with the same already > deleted email address, that was still refused, presumably because of > pointers to archived data don't permit, but this seems like a > particularly onerous restriction, or perhaps even a bug, or at least a > severe design constraint. *Is this item on an existing to do list?* The server that David's lists is on, is running the latest stable versions of Mailman 3, Postorius, and Hyperkitty in case that helps. @David, we have the issue that you ran into mitigated to a great extent with our Affinity user interface. Just contact me via our support ticket system if you want to explore have your lists migrated to our Mailman 3 Affinity platform. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 3 months

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

by hansen＠rc.org

I just had my Mailman suite upgraded. When it got started, I starting receiving messages that hundreds of subscribers to the lists had been disables, including several of the list moderators. This version started supporting bounce processing, but how in the world was this upgrade allowed to act on bounces that were being collected PRIOR to enabling bounce processing?? I got many angry emails, messages and phone calls asking what was going on, as they were bona fide list members. I was very surprised myself. I then looked at several of the disabled accounts, but the subscription info page in Postorius had no information about whether an account was enabled or disabled. Why is this not displayed???. The members can't see if their account is enabled. Is this another example of the disconnect between Mailman and Postorius? Further, even after the upgrade, the moderators still cannot access the list memberships even though all the lists are set to allow that. I would have asked the moderators to do this if this access bug had been fixed, but they can't get there. As a result of these bugs, after consulting with Brian, who helped with the upgrade, I spent many hours re-enabling the several hundred accounts that had been disabled. I had to go through each email notification to find the address of a disabled account, then find the list, then the member, in Postorius, and finally enable the account (at which time Postorius DID show the enabled status). Please, can the next upgrade include these very basic fixes/enhancements, which I requested a long time ago: a. The ability of moderators to see the list membership (a bug). b. The ability of members to change their addresses for all lists they are subscribed to. and further, now: c. That when members go to look at their subscription info, they can actually see the settings. Thank you, Allan

5 years, 4 months

[MM3-users] Re: Unknown templates being used

by Tom Stoddard

On 2/14/2021 1:31 PM, Mark Sapiro wrote: > That message is not built from a template. It comas from the `mailman > notify` command which currently says > ```> def _send_notice(mlist, count, detail): >> """Creates and sends the notice to the list administrators.""" >> subject = _('The {} list has {} moderation requests waiting.').format( >> mlist.fqdn_listname, count) >> # XXX This should be a template. >> text = _("""The {} list has {} moderation requests waiting. > ``` > I.e., we know it should be a template, but it currently isn't. That's fine but it doesn't explain why I have received messages that were built by a template for some subscription requests. In other words, why is there a template being used in some instances and on others a "mailman notify command" is being used? Are there different methods for people to use to request a subscription? Please understand that I'm new to mailman 3 and don't have knowledge of its source code. From reading some of the messages that have been sent by this list, I assume it's written in python, which is a language I have not year learned. I'm asking this because I help to administer several different lists and there are some other moderators who have very limited technical skills. I try to help them the best I can, which is why I'm trying to understand why these messages seem to differ so that I can explain it to others. By the way, Brian at EMWD has been extremely helpful to me already and, as he stated, he informed me that this is an issue with Mailman 3 so I thought I'd try getting the answer directly from this group. Thank you for your time. I do recognize and appreciate the time and effort that goes into creating and maintaining open source software.

5 years, 4 months

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

by Mark Sapiro

On 10/5/19 11:30 AM, Mark Dadgar wrote: > > Running the commands as the correct user solved my issues. Specially, I ran the import21 command as the “list” user (created by the debian/ubuntu package) and the hyperkitty import command as the “www-data” user. I had to add login shells to the passwd entries for those users to make it happen as they get installed with nologin. You could just run, e.g., `sudo -u list bin/mailman import21 ...` which will work even if 'list' can't log in. > I imported a 24G archive inbox and something went wrong along the way - the archives for many months consist of just a single identical thread. Re-running the import results in the following in just a few seconds: ... > Any thoughts on how I can re-run the full import to make sure that all the archives are present? As far as reimporting the entire archive, you need the --since option. As it says in hyperkitty_import --help > --since SINCE only import emails later than this date. Defaults to > the date of the newest message in the existing archive > if any. If you run hyperkitty_import --since=1990-01-01, that should do it. As far as "the archives for many months consist of just a single identical thread", were there error messages when you ran the initial import? Were there issues in the imported mbox that you have corrected? Mailman 2.1's bin/cleanarch can help identify unescaped 'From ' lines that cause problems. If unescaped 'From ' lines is the issue and you have fixed them, rerunning the import should import the messages correctly, but it won't delete the bogus threads. You can delete these threads manually in HyperKitty if you are logged in as a Django superuser. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Mailman3 is wrongly display name a list member

by Allan Hansen

Thank you, Mark. I have Postorius Version 1.3.4 I see no 'Users' in Postorius, but I do see it in Django. I'll assume that my Postorius is out of date and will take steps to update it. Yours, Allan On 1/11/22, 10:38 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 1/11/22 9:24 AM, Allan Hansen wrote: > Thank youi, Stephen. > > Oops. When I wrote below that I set the name 'B' in the account, I did describe it wrongly. Sorry. > The member just wants one name, 'A' for all her subsriptions. Somehow the 'B' got into the system when we upgraded from Mailman 2 to Mailman 3. > > I removed the address from all the lists, set the account display name to 'A' in Django, verified that she was not subscribed to any list at all, and then resubscribed her again as 'A'. In other words, no 'B' anywhere - straight 'A's. > Nevertheless, the new subscriptions still show up as 'B'. A user has a user record and one or more address records. Each of these has a display name. Removing users from lists does not remove these records. If you have recent Postorius, you should have a `users` item at the top of Postorius pages. Go there, find the user and click "Manage". You can change Display Name there. Otherwise, in `mailman shell` for example ``` >>> usr = getUtility(IUserManager).get_user('user(a)example.com') >>> usr.display_name = 'First Last' >>> for adr in usr.addresses: ... adr.display_name = 'First Last' ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 5 months

[MM3-users] Docker or virtualenv?

by Stephen J. Turnbull

Johannes Rohr writes: > Overall, the docker method looks easier. Not sure what you mean by that. If you mean using Mailman-provided Docker images, yeah, it's almost turnkey -- until you need support. Which seems to happen frequently enough on install (network issues, mostly, non-trivial because the three apps are configured as separate containers, and communication among Mailman apps, MTAs, webservers, and WSGI providers takes place over TCP connections). :-/ If you mean that you'll configure your own Docker image and you know how to plumb through the various TCP/IP connections to communicate among the various applications and services, and get to and from your users (presumably by the public Internet), definitely, go ahead with Docker rather than venv. But basically Docker and venv are equivalent in the sense that they are ways to isolate your Mailman installation from the system Python to a great extent. Creating a venv is a one-off, you can put bin/activate in the 'mailman' user's .profile, and after that you don't touch the venv itself until you need to upgrade Python 6 or 7 years later. It's definitely fewer commands to patch your venv in-place and hit "/etc/init.d/$APP restart", than to patch sources and rebuild and reload a docker image. > Is docker the default method by now? Definitely not. While I would say mostly people still install via distro packages, our recommendation for people want good control over their sites and support from us is definitely venv. Abhilash maintains our Docker images on a "best effort" basis, we don't promise support (although they're always more up-to-date than LTS packages for any distro). I don't think Mark has any Docker-specific expertise, and I have no experience yet. venv currently provides the best environment for people who are new to maintaining software (specifically Mailman) beyond what apt or yum will do for you.

3 years, 5 months

[MM3-users] Re: Mailserver Log entries following through mailman?

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [231110 23:54]: > On 11/10/23 12:39, Andreas Barth wrote: > > > >is there some way to find an ID to follow an email through mailman? In > >the exim logfile there is only something like C="250 Ok" (whereas in > >mails sent to another exim there is something like C="250 OK id=…"). > >(What I sometimes need to do is to follow an mail whether it is sent > >through mailman and to where.) > > Every message should have a unique Message-ID: header. According to > my reading of https://www.exim.org/exim-html-current/doc/html/spec_html/ch-log_files.html > Exim should create a => log entry with an id= field containing the > Message-ID when the message is received for delivery to Mailman and > another similar entry when the message is received from Mailman for > delivery to one or more list members. There is the message-id as part of the mail itself, and set by the user. That one is not unique, e.g. if a mail is bounced to the list. Exim has an internal id, and that is also part of the log (also if a mail is delivered to a remote mailserver, the id there is logged). This works fine. However, mailman doesn't have an internal id I can use to follow the message (or at least, it doesn't transfer one to exim upon delivery). I can indeed use the user set message id for following mail. However, I would prefer some internal id, and also to have logged the IDs exim (or probably any other MTA) transmits upon delivering the mails when handing the mails over to the MTA again. (Probably in some format as "mailman-ID recepient MTA-id" so that it's easy for me to grep for message if a user complains.) Regards, Andi

2 years, 7 months

[MM3-users] Re: Active archivers and archiving and thread question.

by Mark Sapiro

On 3/31/22 04:39, bob B via Mailman-users wrote: > Thanks, that make sense, Also is there any way to turn that off via command line for a bunch of lists or just in the GUi, I looked at "'mailman shell --details:" but could not find a command to turn it off. > > I had archives off on my lists in mailman 2, and when I import they stayed off, but the archiver is enabled. The HyperKitty and Prototype archivers are enabled by default for new and imported lists. To change that, add ``` [archiver.hyperkitty] enable: no [archiver.prototype] enable: no ``` to mailman.cfg. > I have a script that pulls all the list configs > "curl --user *******:******* http://127.0.0.1:##/3.1/lists/"$i"/config | python3 -m json.tool >> ${OUTPUT_DATA_DIR}/listconfigs.txt > > Then I look to see if any list has changed this setting "archive_policy": "never", so I know if any list admin has enabled archives... > > But is there a setting in the config that shows if the archiver got turned on? I want to know if anyone turns it on after I turn it off You can do the following in `mailman shell` ``` $ mm/bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>>for mlist in getUtility(IListManager): ... print(mlist.display_name) ... print(f' ArchivePolicy was {mlist.archive_policy}') ... if mlist.archive_policy != ArchivePolicy.never: ... mlist.archive_policy = ArchivePolicy.never ... print(' set to ArchivePolicy.never') ... aset = IListArchiverSet(mlist) ... for ar in aset.archivers: ... if ar.is_enabled: ... ar.is_enabled = False ... print(f' Archiver {ar.name} was enabled; set disabled') ... >>> 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, 2 months

[MM3-users] Re: Cannot Run Web Frontend

by Mark Sapiro

On 12/24/25 08:14, dap1--- via Mailman-users wrote: > How do I tell if mailman-web is running? There is no such service. In this case, the mailman-web service is gunicorn. > /etc/mailman3/gunicorn.py (recall I had to use py rather than conf to get it to work under Ubuntu): It should have worked as gunicorn.conf despite the warning (not error) that it didn't have a .py extension. > # /etc/mailman3/gunicorn.conf > # # > bind = ['127.0.0.1:8000'] > proc_name = "mailman-web" > # # If you are having response issues you can tune the number of workers. > # # The suggested starting point is (2 x $num_cores) + 1 > # # See https://docs.gunicorn.org/en/latest/design.html#how-many-workers > workers = 3 > chdir = "/opt/mailman/mm" > pidfile = "/opt/mailman/mm/var/gunicorn.pid" > accesslog = "/opt/mailman/mm/var/logs/access.log" > errorlog = "/opt/mailman/mm/var/logs/error.log" > loglevel = 'debug' > > I did notice one thing in the access.log that is wrong: > > 127.0.0.1 - - [24/Nov/2025:16:02:55 +0000] "GET /archives/api/mailman/urls?mlist=lllllllllll%40dddddd.net&msgid=705caa > ab-afcc-4249-8d1d-cc48050d02d1%40bellsouth.net HTTP/1.1" 200 113 "-" "python-requests/2.32.5" This request came from HyperKitty. > The mlist name is wrong. It should be lllllllllll%40gmail.com. I don't know where that is coming from but I'm sure it is left over from before I changed the list name. To you have a hyperkitty list named lllllllllll%40dddddd.net. What does SELECT name FROM hyperkitty_mailinglist; show? > When I include the port in the URL I get an unable to connect page. So nothing is listening on 127.0.0.1:8000 (localhost:8000 assuming the `localhost` is 127.0.0.1 in /etc/hosts and not an IPv6 fe00::0 address) What if any does `netstat -lntp` show is listening on 127.0.0.1:8000? -- 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: A new issue with installation

by Abhilash Raj

On Sat, Feb 20, 2021, at 9:53 AM, Brian Carpenter wrote: > On 2/20/21 12:35 PM, Abhilash Raj wrote: >> Also, it is possible depending on your distro that packaged Rust compiler is too old. cryptography requires a more recent version of Compiler, 1.45 is the min supported version I think. FAQ: https://cryptography.io/en/latest/faq.html#installing-cryptography-fails-wi… You can skip the Rust components by setting `CRYPTOGRAPHY_DONT_BUILD_RUST` but that would work just for this release and you won't be able to skip from the next release of cryptography. >> > I am going to need further assistance here. It is easy enought to install the rust compiler using rustup but I am still getting the same error: > =============================DEBUG ASSISTANCE============================= > If you are seeing a compilation error please try the following steps to > successfully install cryptography: > 1) Upgrade to the latest pip and try again. This will fix errors for most > users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip > 2) Read https://cryptography.io/en/latest/installation.html for specific > instructions for your platform. > 3) Check our frequently asked questions for more information: > https://cryptography.io/en/latest/faq.html > 4) Ensure you have a recent Rust toolchain installed: > https://cryptography.io/en/latest/installation.html#rust > 5) If you are experiencing issues with Rust for *this release only* you may > set the environment variable `CRYPTOGRAPHY_DONT_BUILD_RUST=1`. > =============================DEBUG ASSISTANCE============================= > > error: Can not find Rust compiler Could it be an issue with your PATH not set correctly for mailman user? Install Rust - Rust Programming Language (rust-lang.org) <https://www.rust-lang.org/tools/install> See the setting the PATH environment. > Running root@list:/opt/mailman/mm# rustc --version returns: > rustc 1.50.0 (cb75ad5db 2021-02-10) > I am doing this as the mailman user using a virtual environment. > -- > Brian Carpenter > Harmonylists.com > Emwd.com -- thanks, Abhilash Raj (maxking)

5 years, 3 months

[MM3-users] Re: mailman-cli tools

by Dmitry Makovey

On 09/27/2017 10:20 AM, Abhilash Raj wrote: > On Wed, Sep 27, 2017, at 08:44 AM, Mark Sapiro wrote: >> On 09/27/2017 08:26 AM, Dmitry Makovey wrote: >>> On 09/27/2017 08:25 AM, Dmitry Makovey wrote: >>>> I've come across mailman-cli docs: >>>> >>>> http://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usin… >>>> > > This is basically one of our GSoC projects which hasn't yet been merged > with MailmanClient. It uses the REST API to to provide a command line > client for Mailman, while there hasn't been any in-compatible changes in > API since this project was finished, I am not sure about the current > status of it. > >>>> yet I cannot figure out what's the official source for the installation. > > Official source for MailmanClient is at gitlab.com/mailman/mailmanclient > and it doesn't have a CLI, the Github project you linked to says right > on the top that it is not official project (Thanks for that Rajeev!). I did see that, thus I was asking the question here. > Also, I would say not to use this client to remotely access Mailman, the > REST API is not meant to be exposed over internet (unless you have a VPN > or other sort of setup to securely access the box remotely). > in my case - I need to use REST API since we're deploying with docker and pieces that need to integrate with mailman commands now live in a different container (and very likely on a different machine). I do need to be able to execute commands remotely - I can handle securing of that connection, but it is not an option for me to run "fat" docker containers thus the only interconnect is via sockets (either UNIX or TCP). -- Sr System and DevOps Engineer SoM IRT

8 years, 8 months

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

by Yvan ♞

Hello, Thanks for this answer, my problem is I'm on yunohost server and the update 3.3.9 is not available now. Any "handmaid" solution should be great. Sincerely Le 22/10/2023 à 10:45, Stephen J. Turnbull a écrit : > elemac(a)free.fr writes: > > > Hello, on 15th October, 120 users with gmail address where suddenly > > removed from lists in mailman3, something changed in google ? > > Google is evil, who knew? > > Google decided to publish a DMARC policy of "p=none". This announces > to the world that you have to decide for yourself whether to accept > mail from Gmail with a broken DKIM signature from gmail.com. Gmail > has decided that they will not accept such email from themselves, even > though they know more about the sender than anyone else, and even have > access to the original sender copy. > > Mark has a patch that applies your preferred DMARC mitigation to Gmail > authors unconditionally. I think it's in the new version just > released 3.3.9, so you can upgrade. The name of the variable is > dmarc_addresses, and in Postorius it will be in the same settings > group as other DMARC settings, with a similar tag. > > If for some reason you strongly prefer not to upgrade immediately but > want this feature, it's commit #8532f751b6b8bfee3210c1327d755756f99d99ac > (you can shorten that to 8532f). I do not recommend this. It probably > is independent of other changes in 3.3.9 from other releases. But if > not you could have issues. > > I think you also need the patches in Postorius, but I don't think > they've been released yet. "Coming soon" as they say. The relevant > commit is #770add1ebf27fd335c675607f26bb8f7cf313ddd, > > If you search back in the archives, I think Mark posted a link to his > original patches. > > Steve >

2 years, 7 months

[MM3-users] Re: Email verification

by Allan Hansen

Thank you, Abhilash. Yes. People are getting these messages. I just got a message from one who had the issue. I asked her to try to sign in again and then she got the verification message. It’s just that some have issues, and I’d like to be able to help. Yours, Allan Hansen hansen(a)rc.org > On Feb 9, 2020, at 9:12 , Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > > On Sun, Feb 9, 2020, at 8:05 AM, Allan Hansen wrote: >> Some members cannot get past the email verification when they create >> their accounts. >> They insist that they have looked in their spam folders. Their email >> addresses they entered are correct - the are able to log into their >> accounts with the right email address. But they get the message saying >> that a confirmation message was sent and if they don’s see it to >> contact us. > > Is your Django configured to send out emails? > > https://docs.mailman3.org/en/latest/config-web.html#setting-up-email-requir… > > >> >> 1. Who is ‘us’? My members are asking... >> 2. How do I help them? >> >> I tried subscribing them to a bogus list with pre-verified email, but >> that did not work, so both they and I are stuck. >> Tried finding help in archive, but did not see anything. >> >> Yours, >> >> Allan Hansen >> hansen(a)rc.org >> >> >> >> >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > -- > thanks, > Abhilash Raj (maxking) > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 4 months

[MM3-users] Re: Link to account

by Lars Bjørndal

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

3 years, 2 months

[MM3-users] Re: Finding a mailman3 installation description that works

by Abhilash Raj

On Wed, Apr 1, 2020, at 11:21 AM, Andrew Hodgson wrote: > Abhilash Raj wrote: > > >On Tue, Mar 31, 2020, at 11:28 AM, Andrew Hodgson wrote: > >> ralf.wiegand(a)tena-sda.org wrote: > >> > >> >WE are currently using mailman2. I have the task to setup and install a maiman3 server. Postfix is installed and working. Can anybody point me to a link where the actual installation is described using RHEL 7 or RHEL 8. This will be a >hardened DISA compliant server, so I am trying to avoid installing compilers and tools that are not part of the standard RHEL 7 repos. > > > >> Have you looked at creating a development environment using a Python3 > >> venv somewhere else (eg another server or container) then copying the > >> venv out to the production server? > > >Python virtualenvs are really not movable because of the paths that are in there. It is tricky to get that working right, I would caution against doing that. > > Thanks for this, I actually did this work over the weekend to test a > restore on a new server using the same paths because I was worried > about this being an issue. It did work, but the paths were exactly the > same. > > I may have to re-investigate quick restore options (probably writing a > script to create the venv and re-constitute the packages). You could look into Shiv project[1], which will basically bundle Python application into a single binary that you can move around without having to worry about dependencies & virtualenv. Only thing you probably need constant is the version of the Python, which isn't bundled. But, otherwise, you can just use this to create a relocatable binary artifact. [1]: https://shiv.readthedocs.io/en/latest/ > > Andrew. > -- thanks, Abhilash Raj (maxking)

6 years, 2 months

[MM3-users] Re: AH01102: error reading status line from remote server 172.19.199.3:8000

by Henrik Rasmussen

Hi Thanks for pointing that out. It seems that before I get a change of signing in, at the moment I click the >]Sign In link at the top right of the webinterface I get the following ==> mailmanweb.log <== WARNING 2017-07-18 11:43:30,483 22 django.template Exception raised while rendering {% include %} for template 'account/login.html'. Empty string rendered instead. Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/django/template/loader_tags.py", line 210, in render return template.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 210, in render return self._render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 994, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 961, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/site-packages/allauth/socialaccount/templatetags/socialaccount.py", line 65, in render for p in providers.registry.get_list(request)]) File "/usr/local/lib/python2.7/site-packages/allauth/socialaccount/providers/facebook/provider.py", line 143, in media_js raise ImproperlyConfigured("No Facebook app configured: please" ImproperlyConfigured: No Facebook app configured: please add a SocialApp using the Django admin When I do sign in, I get the following from uwsgi-error.log ==> uwsgi-error.log <== Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/django/core/handlers/wsgi.py", line 170, in __call__ response = self.get_response(request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 124, in get_response response = self._middleware_chain(request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py", line 41, in inner response = response_for_exception(request, exc) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py", line 86, in response_for_exception response = handle_uncaught_exception(request, get_resolver(get_urlconf()), sys.exc_info()) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py", line 124, in handle_uncaught_exception extra={'status_code': 500, 'request': request}, File "/usr/local/lib/python2.7/logging/__init__.py", line 1193, in error self._log(ERROR, msg, args, **kwargs) File "/usr/local/lib/python2.7/logging/__init__.py", line 1286, in _log self.handle(record) File "/usr/local/lib/python2.7/logging/__init__.py", line 1296, in handle self.callHandlers(record) File "/usr/local/lib/python2.7/logging/__init__.py", line 1336, in callHandlers hdlr.handle(record) File "/usr/local/lib/python2.7/logging/__init__.py", line 759, in handle self.emit(record) File "/usr/local/lib/python2.7/site-packages/django/utils/log.py", line 121, in emit self.send_mail(subject, message, fail_silently=True, html_message=html_message) File "/usr/local/lib/python2.7/site-packages/django/utils/log.py", line 124, in send_mail mail.mail_admins(subject, message, *args, connection=self.connection(), **kwargs) File "/usr/local/lib/python2.7/site-packages/django/core/mail/__init__.py", line 103, in mail_admins mail.send(fail_silently=fail_silently) File "/usr/local/lib/python2.7/site-packages/django/core/mail/message.py", line 342, in send return self.get_connection(fail_silently).send_messages([self]) File "/usr/local/lib/python2.7/site-packages/django/core/mail/backends/smtp.py", line 100, in send_messages new_conn_created = self.open() File "/usr/local/lib/python2.7/site-packages/django/core/mail/backends/smtp.py", line 58, in open self.connection = connection_class(self.host, self.port, **connection_params) File "/usr/local/lib/python2.7/smtplib.py", line 256, in __init__ (code, msg) = self.connect(host, port) File "/usr/local/lib/python2.7/smtplib.py", line 316, in connect self.sock = self._get_socket(host, port, self.timeout) File "/usr/local/lib/python2.7/smtplib.py", line 291, in _get_socket return socket.create_connection((host, port), timeout) File "/usr/local/lib/python2.7/socket.py", line 575, in create_connection raise err socket.error: [Errno 111] Connection refused Henrik -----Oprindelig meddelelse----- Fra: Abhilash Raj [mailto:raj.abhilash1@gmail.com] Sendt: 17. juli 2017 18:04 Til: mailman-users(a)mailman3.org Emne: [MM3-users] Re: AH01102: error reading status line from remote server 172.19.199.3:8000 Hi Henrik, On Mon, Jul 17, 2017, at 02:31 AM, Henrik Rasmussen wrote: > I've just installed Mailman 3.1 on RHEL7 (Docker-Mailman3) and to get the > right CSS layout I installed Apache on the Mailman server outside Docker, > as advised by Abhilash Raj and Alexander Klotz. > > My Mailman server is on a secured network and the https connection from > Internet will be handled by proxy servers, so I will be using http (port > 80) between proxy-servers and Mailman server. > > But when I sign in (currently via an SSH tunnel to the Mailman server > from my workstation) I get "Internal error: [client ::1:41912] AH01102: > error reading status line from remote server 172.19.199.3:8000, referer: > http://localhost/accounts/login/?next=%2Fpostorius%2Flists%2F" Output from logs might be more helpful to debug what is wrong. They are present at `/opt/mailman/web/logs/mailmanweb.log` for Django. You may also find some other log files there which are related to uwsgi, the WSGI server that is used to interface Django with Web Servers like Apache. > If I type a wrong password, I am just warned about that, so the problem > appears when log in is accepted. > > I expect that it is because I connect to localhost:80 through SSH tunnel. > What do I miss in my Apache configuration on the Mailman server to avoid > this problem? > > <VirtualHost *:80> > ErrorLog /var/log/httpd/error_log > LogLevel warn > CustomLog /var/log/httpd/access_log combined > > ServerAdmin root(a)example.foo > ServerName list.foo.bar > Alias /static /opt/mailman/web/static > Alias /favicon.ico /opt/mailman/web/static/hyperkitty/img/favicon.ico > > ProxyPassMatch ^/static/.* ! > ProxyPass / http://172.19.199.3:8000/ > ProxyPassReverse / http://172.19.199.3:8000/ > > <Directory /> > Allow from all > Require all granted > </Directory> > > <Directory /opt/mailman/web/static/hyperkitty/img/> > Allow from all > Require all granted > </Directory> > > # ssl config here ... > </VirtualHost> > > > Thanks, > Henrik Rasmussen > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj _______________________________________________ Mailman-users mailing list mailman-users(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

8 years, 11 months

[MM3-users] Installing Mailman3 on Debian Bullseye

by Stephen J. Turnbull

Franklin Weng writes: > I had a blog article describing how I did it. > > https://blogs.slat.org/node/1012 Thank you for mentioning this. As far as I know, Debian packages use the system Python and the system Django. Is that correct? I have had trouble myself with [language.en] charset: ascii myself when importing Mailman 2 lists into Mailman 3. This was an *ancient* instance (Mailman 2 installed in 2009, 21.1.15). Save yourself pain and set it to utf-8. I need to make sure before I make such a change in a public release though. As far as I know [language.master] charset isn't relevant anymore as all out message catalogs are UTF-8 now. I need to think about the 'django_mailman3.lib.auth.fedora' issue. I'm not sure why that should be enabled out of the box in Mailman's distribution. HyperKitty was originally a Red Hat/Fedora contribution, I guess that's why it's there and nobody has removed it. But I need to make sure before I make such a change in a public release here, too. The utf8mb4 problem is Somebody Else's problem. We don't know what the implications of setting utf8mb4 are, that's for the MySQL folks or the Debian packager. (The fact that MySQL-family databases can't handle 4-byte UTF-8 out of the box in 2023 doesn't make me feel warm and fuzzy about MySQL, though.) Postgresql and sqlite do not have this problem. In our current releases, the "mailman" command and the "mailman-web" command are separate. mailman-web/manage.py and django-admin are basically aliases for mailman-web. I think "mailman-web", not "mailman" is what you mean in your last note. Note that "manage.py" doesn't know anything about functions of the "mailman" command, since it is derived from Django. So you might want to check that and correct it. Steve

2 years, 9 months

[MM3-users] Upgrading dockerized Mailman3 from 0.4 to 0.5.1

by Stephen J. Turnbull

jesper.holck--- via Mailman-users writes: > I am a happy user running Mailman 3, dockerized, in combination > with Mailcow. After a few initial problems, everything is running > smoothly. Now I'm considering upgrading from 0.4 to 0.5.1, but I'm > not sure about the right procedure. Is it something like this? Evidently "0.4" and "0.5.1" refer to Mailcow, not Mailman. As usual, your first line of support for a third party integration should be the packager. We don't know what they're distributing. They have never consulted or informed us (which is perfectly reasonable for various reasons, but it does mean we can't be much help without a lot of work on our part which they have already done). Most issues in Mailman upgrades are in fact integration issues (eg, a dependency makes a change to its API and the first we know about it is when somebody tries to use the new release of the dependency in a Mailman install, or a stale patch by the integrator). Assuming that they are distributing vanilla (straight from PyPI or git) versions of the Mailman suite and its dependencies (seems very likely), then I would guess your procedure should work. The database schema migrations should be automated in the docker compose phase. Issues are rare in Mailman suite upgrades, so unless you have space mission levels of need for uptime and reliability, I would just do it and deal with the fallout in the rare case. If you are using the containerized Mailman provided by Abhilash, I don't know anything about it, and I'm not sure Mark knows much. So for issues with that particular product, you should probably CC him as he hasn't been active on the lists for months. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

5 months, 3 weeks

[MM3-users] Re: Timeouts

by Abhilash Raj

> On Apr 25, 2021, at 7:06 PM, tlhackque via Mailman-users <mailman-users(a)mailman3.org> wrote: > > On 25-Apr-21 20:34, Mark Sapiro wrote: >> On 4/25/21 4:37 PM, tlhackque via Mailman-users wrote: >> >>> The described timeouts are something that hyperkitty ought to be able to >>> avoid. For apache, the timeout is idle time between blocks of output. >>> Hyperkitty can avoid this by generating the archive in segments (based >>> on size, or elapsed time), flushing its output buffer, generating a >>> multi-file archive, and/or using Transfer-Encoding: chunked (chunked >>> doesn't work for http/2). It ought to be able to break the > work into >>> blocks of "n" messages & do something to generate output. Besides >>> avoiding timeouts, working in segments allows the GUI to display >>> meaningful progress (e.g. if you're loading with XMLHttpRequest, >>> "onprogress") It really oughtn't be up to the user to break up the >>> request. >> It is not the web server that times out. I'm not sure about uwsgi >> because I don't use it, but the timeouts I see are on servers that use >> gunicorn as the WSGI interface to Django and the timeout is in a >> gunicorn worker. This is controlled by the timeout setting in the >> gunicorn config. <https://docs.gunicorn.org/en/stable/settings.html#timeout> >> >> Note that even 300 seconds is not enough to download the entire >> <https://mail.python.org/archives/list/python-dev@python.org/> archive. >> >> It may be possible to get HyperKitty to chunk the output to avoid this, >> but it doesn't currently do that. Care to submit an MR? >> >> > I'm afraid (u)WSGI, Django, and gunicorn are not technologies that I > work with. > > It sounds as if hyperkitty is compiling the entire archive before > sending the first byte. > > The gunicorn doc that you pointed to says > > Workers silent for more than this many seconds are killed and restarted. > Setting it to 0 has the effect of infinite timeouts by disabling > timeouts for all workers entirely. > > "Silent" sounds like the standard webserver "you have to push some bits, > or we assume you're stuck". > > My understanding is that gunicorn is a Python persistence server that is > run behind a webserver proxy. So the (proxy) webserver (apache, nginx, > ...) timeouts also apply and would need to be increased. > > Might be interesting to try 0 (gunicorn) / 1200 (webserver) with your > python-dev archive, time it and see how much (encoded) data is > transferred... (I would expect most mailing list archives to compress > nicely, though those with binary attachments wont.) For uwsgi, I think the parameter is called `harakiri`[1][2] (I don’t know why such a name though). [1]: https://uwsgi-docs.readthedocs.io/en/latest/Options.html#harakiri [2]: https://uwsgi-docs.readthedocs.io/en/latest/Glossary.html > if request takes longer than specified harakiri time (in seconds), the request will be dropped and the corresponding worker recycled. This should be set to a long enough value that allows downloading the archive. If you are using http socket, then you want http-timeout. Also, to set the timeout in webserver (nginx) location / { uwsgi_read_timeout 120s; uwsgi_send_timeout 120s; uwsgi_pass 0.0.0.0:8000; include uwsgi_params; } Or some other value that you want. > But fiddling with timeouts is treating the symptom, not the root cause. > The right solution is to stream, segment (or chunk) the output, because > in the general case, no timeout is long enough. It'll always be > possible to find an archive that's just one byte (or second) longer than > any chosen timeout. (See the halting problem.) You want > the timeout > to catch a lack of progress, not total time that's a function of > transaction size. (Webservers may also have limits on transaction size > - e.g. mod_security, but they're only useful when the upper bound on a > response is knowable.) Thus, the timeout(s) should be roughly > independent of the archive size; on the order of time-to-first-byte > (which ordinarily is longer than time between segments/chunks). > > Also note that streaming requires fewer server resources than compiling > a complete archive before sending, since you don't need to create the > entire archive in memory (or in a tempfile). You only need enough > memory to efficiently buffer the file I/O and to contain the compression > tables/output buffer. Except for trivial cases, this will be > independent of the archive size. The only downside is that if the comm > link is slow, you may hold a reader lock on the source data for longer > than necessary with the current scheme. > > Seems as though this deserves an issue. I guess I could open one - but > you have the experience/test cases. Hyperkitty doesn’t actually create an archive in memory or in a temp file. It uses streaming response with on the fly compression to read from database and relay to the client for download. https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/mlist.… The problem could be that uwsgi seems to kill an ongoing downloading process, not an idle one for some reason. And, it seems that it is a known and intentional behavior. I don’t see a good way to disable it completely, but perhaps it can be set to a long enough value that it never essentially kills a running worker which is moving bits. -- thanks, Abhilash Raj (maxking)

5 years, 1 month

[MM3-users] Importing issue from mailman2 to mailman3

by David Partain

Hi, I'm in the process of moving 1400-ish lists from a very old mailman2 installation to an installation on Ubuntu 18.04 with the version of mailman3 packaged for that distro. (Yes, that was a mistake, but I'm committed at this point.) I'm doing this import as per: sudo -u list mailman import21 somelist@one-of-the-domains<mailto:somelist@one-of-the-domains> /tmp/lists/somelist/config.pck where /tmp/lists includes all of the list configs from the old installation. Most of it's going fine, as best I can see. However, I get exceptions on some lists that look like this: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1182, in _execute_context context) File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 470, in do_execute cursor.execute(statement, parameters) File "/usr/local/lib/python3.6/dist-packages/pymysql/cursors.py", line 163, in execute result = self._query(query) File "/usr/local/lib/python3.6/dist-packages/pymysql/cursors.py", line 321, in _query conn.query(q) File "/usr/local/lib/python3.6/dist-packages/pymysql/connections.py", line 505, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/usr/local/lib/python3.6/dist-packages/pymysql/connections.py", line 724, in _read_query_result result.read() File "/usr/local/lib/python3.6/dist-packages/pymysql/connections.py", line 1069, in read first_packet = self.connection._read_packet() File "/usr/local/lib/python3.6/dist-packages/pymysql/connections.py", line 676, in _read_packet packet.raise_for_error() File "/usr/local/lib/python3.6/dist-packages/pymysql/protocol.py", line 223, in raise_for_error err.raise_mysql_exception(self._data) File "/usr/local/lib/python3.6/dist-packages/pymysql/err.py", line 107, in raise_mysql_exception raise errorclass(errno, errval) pymysql.err.DataError: (1406, "Data too long for column 'info' at row 1") My assumption is that what's in the "Info" field on the old mailman2 config is simply too long. Is that correct? In that case, I suppose the right thing is to (1) edit each one, reducing the size, which'll create a new config.pck, (2) pull it over to the new machine, and (3) run the import again. Seem reasonable? Cheers, David

5 years, 3 months

[MM3-users] Re: Hacking attempts?

by Tim Cutts

> On 15 Jul 2022, at 17:15, Dave McGuire <mcguire(a)neurotica.com> wrote: > > On 7/15/22 12:02, Mark Dadgar wrote: >>>> > For fail2ban, here's my jail.local entry: >>>> Thanks! I'm sure this will be helpful to several users. >>> >>> I hope so. If I can spare anyone else the pain of spending two solid hours with fail2ban's configuration-system-of-questionable-judgment, I'll count that as a win. >> Hah. I grew up on pre-m4 sendmail configs, so fail2ban seems pretty middle-of-the-road by comparison. >> - Mark <— old > > I'm right there with you, olde pfarte. m4 sure did make things nice. I just expect much better configuration systems by now, for such commonly-used software. > > The all-time winner has to be amavisd. A configuration file that's actually a Perl script? Come ON. I am loving this thread, even though it’s somewhat irrelevant to Mailman3! It’s made me laugh out loud a couple of time! What is it about spam filter apps and hideous configuration? I currently use rspamd, which is quite effective but also has horrible configuration syntax. Very complex, and half of it seems to be in Lua. Sendmail was hateful. I moved to exim in its very early days (about 1996) purely because its config file was so easy to understand (and also because Phil Hazel worked about 200 metres away if I had an issue). More recently I’ve switched to Postfix because it seems to have the most mindshare, but its configuration is really horrible compared to exim and I may switch back - if you’ve got complex mail routing to do (and I think running mailing lists counts) it’s much much simpler to debug what’s going on with exim than with postfix. Postfix configs are nice for simple cases, but rapidly become impenetrable once you add milters, mailing lists, DKIM and whatnot. Tim

3 years, 11 months

[MM3-users] Re: confirm-email: error NoReverseMatc

by Simon Hanna

> ERROR 2018-01-31 09:31:57,143 28537 django.request Internal Server Error: /accounts/confirm-email/Ng:1egno5:_T5eipR8TTan-zWjLK8EhYuetjQ/ > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 71, in view > return self.dispatch(request, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 89, in dispatch > return handler(request, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 283, in post > resp = self.login_on_confirm(confirmation) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 332, in login_on_confirm > redirect_url=self.get_redirect_url) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/utils.py", line 157, in perform_login > get_login_redirect_url(request, redirect_url)) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/utils.py", line 50, in get_login_redirect_url > url = url() > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 362, in get_redirect_url > self.request) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 176, in get_email_confirmation_redirect_url > return self.get_login_redirect_url(request) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 156, in get_login_redirect_url > return resolve_url(url) > File "/usr/lib/python2.7/site-packages/django/shortcuts.py", line 205, in resolve_url > return urlresolvers.reverse(to, args=args, kwargs=kwargs) > File "/usr/lib/python2.7/site-packages/django/core/urlresolvers.py", line 579, in reverse > return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, *args, **kwargs))) > File "/usr/lib/python2.7/site-packages/django/core/urlresolvers.py", line 496, in _reverse_with_prefix > (lookup_view_s, args, kwargs, len(patterns), patterns)) > NoReverseMatch: Reverse for '' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: [] It's complaining about an empty url used for reversing. Do you mind sharing your settings.py file? we don't need the secret key and logins for stuff, so you can mask those. the rest should be ok to make public.

8 years, 4 months

[MM3-users] Re: Moderate mails from owner

by Malcolm Austen

On Thu, 21 Mar 2019 16:58:45 -0000, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Thu, Mar 21, 2019, at 8:47 AM, Malcolm Austen wrote: >> On Wed, 20 Mar 2019 18:42:10 -0000, Mark Sapiro <mark(a)msapiro.net> >> wrote: >> >> > However, this is apparently not relevant because both the Member and >> > Non-Member actions are Hold. Thus, the post should be held unless it >> has >> > an Approved: header with the list's moderator_password attribute if >> > there is one, or it matches a Header filter rule with an accept >> action. >> >> At the risk of getting this really wrong - I have only limited MM3 >> knowledge - I will ask what is, I fancy, a closely related question ... >> >> My only experience of MM3 is with Ancestry's 'RootsWeb' installation. >> From >> the emails I can see a header "X-Mailman-Version: 3.1.0" but I can't >> find >> anything to identify Postorius which is the only interface I have to the >> system. >> >> From symptoms seen and described by others, I have deduced that the >> Postorius admin-per-user moderation options of "Default processing" and >> "List default" mean that a user may be set (by default on the rootsweb >> system!) to use the system default moderation settings rather than the >> list default settings. > > "Default Processing" means the default pipeline defined in Thanks, I will do some (more!) reading. > List > Settings > Alter Messages > 'Pipeline' ( in the bottom). This > pipeline is > system wide and is defined in source code, so it can't be customized by > site administrator. Unfortunately, that is not available to list-owners on the system concerned. Ancestry must have removed it. Malcolm. -- Malcolm Austen <malcolm.austen(a)weald.org.uk>

7 years, 2 months

[MM3-users] Re: Localization of auto-responses, question marks in welcome message

by Stephen J. Turnbull

Claus-Justus Heine via Mailman-users writes: > Kind thanks for the response. I have to apologize: my "test user" had > its preferred language set to en_US, so that was the reason for the > question marks. So this was indeed a user-error (i.e. my fault). But we'd like to have that user get the English version of the message. One of two things seems reasonable: 1. You have customized the German template, but not the English template. In that case, I think it makes sense for Mailman to assume the German template has important information that the English does not, and send the German template with its appropriate encoding (UTF-8, nowadays). The fact that en_US can be encoded in ASCII should not affect the encoding of the de template, ever.[1] 2. You have not customized the German template. In that case the user should get the default English template. How do those sound to you, as goals for Mailman behavoir? So ISTM this is a Mailman issue, if Mailman is sending out the German message with question marks substituted for non-ASCII characters, or if Mailman is sending out the German message with US-ASCII as the Content-Type charset parameter. The only way I can see this as a user (admin) issue is if you overwrote the English template with German (and even then, it's nuts for Mailman not to use UTF-8 for English what with directed quotes, emoji, and all the other enhancements to the character repertoire that US English speakers use). Can you tell me a little more about whether you configured any custom templates, and if so, how? That is, did you use the Postorius text field or overwrite files directly? Steve Footnotes: [1] Note to self: perhaps the admin UI can check the list of supported languages and warn if some but not all are customized.

4 years, 1 month

[MM3-users] Re: Migration of the e-mail templates

by Markus Grandpré

Dear Stephen, Thank you for your prompt reply. Based on a customer request, it seems that custom templates need to be copied manually. Could you kindly indicate which files and locations should be considered when transferring them from the source to the target system? Best regards, Markus Am 3/5/25 um 15:01 schrieb Stephen J. Turnbull: > Markus Grandpré writes: > > > When migrating the lists and archives from Mailman 2.1 to Mailman > > 3, the e-mail templates were obviously not migrated. > > Which templates? Headers and footers are in the database, and they > should be migrated. The standard templates for autoreplies, moderator > notifications, and so on will have versions appropriate for Mailman 3, > and as far as I know all of the languages standard in Mailman 2 have > been translated to Mailman 3, or the Mailman 2 version crudely adapted > to Mailman 3. > > Do you mean custom templates (such as moderator noifications) that > overwrote stock templates in the Mailman 2 installation? I would > think you would have to copy those by hand, because the upgrade > process would not know that they're customized, and would just assume > the new installed versions are good for you. I'm pretty sure you can > copy them to a different place that has higher precedence in the > search path so you don't have to worry about them being overwritten by > upgrades. > > Unfortunately Mark is on vacation. > > Steve > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to markus.grandpre(a)uni-konstanz.de -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

1 year, 3 months

[MM3-users] Unable to ban users via mailman-shell

by Mihai Moldovan

Hi I can't seem to be able to add bans via mailman-shell: # mailman-wrapper shell Welcome to the GNU Mailman shell >>> from mailman.testing.documentation import dump_json >>> from mailman.interfaces.mailinglist import IMailingList >>> from zope.component import getUtility >>> list_manager = getUtility(IListManager) >>> mlist = list_manager.get('x2go-commits(a)lists.x2go.org') >>> bans = IBanManager(mlist) >>> new_bans = ["really", "long", "list", "with", "addresses", "I'd", "like", "to", "ban"] >>> for new_ban in new_bans: ... bans.ban(new_ban) ... >>> for ban in bans: ... print('{0}: {1}'.format(ban.list_id,ban.email)) ... [long list of bans] >>> exit() # mailman-wrapper shell Welcome to the GNU Mailman shell >>> from mailman.testing.documentation import dump_json >>> from mailman.interfaces.mailinglist import IMailingList >>> from zope.component import getUtility >>> list_manager = getUtility(IListManager) >>> mlist = list_manager.get('x2go-commits(a)lists.x2go.org') >>> bans = IBanManager(mlist) >>> for ban in bans: ... print('{0}: {1}'.format(ban.list_id,ban.email)) ... >>> exit() GNU Mailman 3.3.8 (Tom Sawyer), installed on Ubuntu 24.04 via distro packages (yes, they are completely broken; yes, I had to backport fixes from your Gitlab instance to even get this properly installed and working; yes, I think I can handle this) What could possibly be the cause of this? I don't even see any calls to the REST API for each bans.ban() call. Should I see those? Or is bans.ban() directly modifying the database? I skimmed the source code and it looks like as if IBanManager and the concrete BanManager model seem to work directly on a DB connection, so I assume that it's not going through REST. If that is the case (I'm using sqlite3, nothing fancy), why doesn't it stick? Do I have to commit changes somehow? Mihai

1 year, 2 months

[MM3-users] Re: How to set up mailman 3

by David Krantz

Okay, I AM very stupid sometimes. The login problem was due to an commeted backend line for auth. Sorry for that. Still annoying to hear that the mailman_bundle is deprecated. Best regards // David On Sat, Mar 25, 2017 at 8:13 PM, David Krantz <david(a)krantz.dk> wrote: > Hi. > > I have tried and failed to set up mailman 3 using the mailman_bundle. I > get the mailman3 server running correctly, but the problem is the extremely > sensitive web user interface... > > Now when I found this mail list I understand that mailman bundle is > depricated and that I must restart from scratch. Is this true? This annoys > me quite a lot, can someone responsible within the project please mark the > deprecated package as such? > > Almost none of the documentation is completely correct. It is useful but > very incomplete. The mailman_bundle generated configuration examples for > e.g. apache simply is wrong or incomplete. That said I got it running using > http only, but when I switched to HTTPS the login simply ceased working. I > use password+username as the other solution is quite complicated to get > running. I could of course switch to e.g. google login, but that would > require at least some documentation on how to do that. > So, is there any documentation on how to use mailman 3? > > The error I get now is "Please enter a correct username and password. Note > that both fields may be case-sensitive." I know that I enter the correct > password as it worked before I added HTTPS. > > Sorry for the rant, but I am very annoyed by this. I just need a mail list > server that works and thought it would be very neat to run mailman3 after > running a hoste mailman2 for many years. > > Best regards > // David >

9 years, 2 months

[MM3-users] Unwanted E-mail to Maillists Submitted via Postorius Interface

by Stephen J. Turnbull

matthew(a)alberti.us writes: > I$B!G(Bve seen a recent uptick in SPAM messages making it into > mailing lists. Looking at the raw, it seems that the e-mails are > being submitted thru the Postorius/Hyperkitty $B!H(BStart a New Thread$B!I(B > interface. Is there a way to turn that off? I think this is HyperKitty only. Postorius doesn't know anything about posting or distributing posts. You can disable web posting by setting HYPERKITTY_ALLOW_WEB_POSTING = False (as above, no quotation marks etc) in settings.py. I don't know much about HyperKitty, so I'm not sure where that file lives in your installation. > Part of the problem is that our anti-spam system RSPAMD trusts the > mailman-web IP$B!D(B so it doesn$B!G(Bt scan things originating from > there.. %G��%@ You know your organizational constraints, but it's a bad idea to trust any web-facing application that can send email to be responsible about it. :-( > Another uestion: Is there a way to implement captcha, or is > there a recommended gate that can be put in the signup process? Here's the most recent technical discussion I can find. Archived-At: <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> However, it turns out that bots are almost as good at solving captchas as humans, and they can retry a lot faster. Captchas are also really horrible from an accessibility perspective. > Apparently bots are finding a way thru the signup process, and then > sending messages to the list via the Postorius web interface. There > seems to be a Django plugin for it; but it appears the Mailman code > would have to be adjusted to implement it. I don't think so, because Mailman (that is, HyperKitty and Postorius) delegate authentication to Django. Why do you think Mailman code needs to be adjusted? Steve

4 years, 9 months

[MM3-users] Re: Problem upgrading from 2.1 to 3, dockerized

by Mark Sapiro

On 8/8/25 11:43, jesper.holck--- via Mailman-users wrote: > I recently followed the instructions here https://github.com/g4rf/dockerized-mailcow-mailman, and was able to create a new Mailman 3, Debian-based installation. I then followed the instructions here https://docs.mailman3.org/en/latest/migration.html in order to migrate from my old, Centos-based installation, to the new, Debian-based installation. It seemed to work well, but unfortunately a problem showed up. > > Whenever someone posted to one of the lists on the new installation, the messages were rejected by Postfix: > > postfix-mailcow-1 | Aug 5 20:55:48 ef2b760c2e61 postfix/cleanup[8681]: B7B856099EC: message-id=<A8946B8E-2A47-4701-9548-4544981FAC5E(a)gmail.com> > postfix-mailcow-1 | Aug 5 20:55:49 ef2b760c2e61 postfix/cleanup[8681]: B7B856099EC: milter-reject: END-OF-MESSAGE from unknown[172.22.1.1]: 5.7.1 This message does not meet our delivery requirements; from=<mylist-bounces(a)myserver.dk> to=<mylistuser1(a)gmail.com> proto=ESMTP helo=<[172.19.199.4]> > postfix-mailcow-1 | Aug 5 20:55:50 ef2b760c2e61 postfix/cleanup[8681]: 216D36099EC: message-id=<A8946B8E-2A47-4701-9548-4544981FAC5E(a)gmail.com> > postfix-mailcow-1 | Aug 5 20:55:50 ef2b760c2e61 postfix/cleanup[8681]: 216D36099EC: milter-reject: END-OF-MESSAGE from unknown[172.22.1.1]: 5.7.1 This message does not meet our delivery requirements; from=<mylist-bounces(a)myserver.dk> to=<mylistuser2(a)mail.dk> proto=ESMTP helo=<[172.19.199.4]> The above messages are not messages normally seen from Postfix. They apparently come from some mailcow milter. > So, for each of the existing lists, I had to delete the old list and create a new one - with the same name and the same users. After this, everything seems to work as expected. I can think of nothing that `mailman import21` would do that would be different from creating a list, configuring it and adding members. Since you are following a third party how-to, please see https://wiki.list.org/x/12812344 - perhaps reporting this at https://github.com/g4rf/dockerized-mailcow-mailman/issues would be appropriate. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 1 week

[MM3-users] Re: Equivalent of listadmin Perl script for Mailman 3?

by Stephen J. Turnbull

Philip Colmer writes: > On Fri, 19 Nov 2021 at 09:13, Stephen J. Turnbull < > stephenjturnbull(a)gmail.com> wrote: > > > It probably wouldn't be hard to write a bare-bones workalike if the > > admin has shell access to the mailman host. > > > > I was hoping that I could write an alternative using the REST API, but I'd > overlooked the fact that there is a single username and password protecting > the API. Correct. That's why I suggested ssh's command= parameter in authorized_keys. > Unfortunately, even trying to solve this via shell access would have a > similar problem because I can't see how one person running the command can > be restricted to just the lists they administer. You could create a system user per list admin, make authorized_keys for each user owned by somebody else (root or list or domain_admin, maybe?), and put command=list_admin.py as an option. Alternatively, it must be possible to determine which public key was authorized (sorry, not that familiar with sshd), and register that with list_admin.py, which would live in a single list_admin account. Either way, list_admin.py would manage authz permissions based on the authn data, including access to lists and which REST (or mailmanclient) APIs are allowed. This stuff is not easy to do really well, but if you are mostly worried about accidental damage or kids-will-be-kids mischief rather than actively malicious admins, could be good enough. > Oh well ... maybe something for the project to consider as an > improvement in the future, particularly for the REST API. There's a project called "lemme" which is a proof-of-concept program to put some authn/authz in front of the REST API. I was never involved, so I don't know if it got any farther than a PoC. It was a few years ago.

4 years, 6 months

[MM3-users] Re: Improve logging?

by Mark Sapiro

On 1/31/23 00:40, Odhiambo Washington wrote: > Some entries in the log files can be very scary, while in actual sense they > are harmless. > Such inconsequential, but scary entiess can mess up the well-being of a > SysAdmin. > I humbly request for the logs related to posts by non-members to a MM3 list > to be improved a little bit :-) > Here is the example in mailman.log: > > <cut> > Jan 31 10:03:54 2023 (92481) DISCARD: < > 2a1c588a6ccd47abbf57ee5fc61c9946(a)phellineconsultancy.co.ke>; ['The message > is not from a list member'] > [31/Jan/2023:10:04:48 +0300] "GET > /3.1/users/1bad08f703fe4bc0a829f4bdce10fc8f HTTP/1.1" 200 253 "-" "GNU > Mailman REST client v3.3.5" > [31/Jan/2023:10:04:48 +0300] "GET > /3.1/users/1bad08f703fe4bc0a829f4bdce10fc8f/addresses HTTP/1.1" 200 473 "-" > "GNU Mailman REST client v3.3.5" > Jan 31 10:18:09 2023 (92343) deque: do_confirm_verify > Traceback (most recent call last): > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/app/workflow.py", > line 69, in __next__ > return step() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/app/subscriptions.py", > line 476, in _step_send_confirmation > raise StopIteration > StopIteration > </cut> > > Is there a possibility to change the logging engine to just *fold* the last > 7 lines into "The message is not from a list member. It was discarded", or > something close? No. This entry Jan 31 10:03:54 2023 (92481) DISCARD: <2a1c588a6ccd47abbf57ee5fc61c9946(a)phellineconsultancy.co.ke>; ['The message is not from a list member'] is a single entry about a discarded message. The next two are logging requests via the REST API that have nothing to do with the discard and are logged by a different module. The last entry with a traceback is yet another separate event. That one could probably be suppressed because raising StopIteration is a normal occurrence in workflow processing. -- 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: Mailman3 Docker question and importing lists from MM2

by Andrew Hodgson

Hi, Thanks for this, I saw the Docker entrypoint script which assumes the domain variable in the Docker environment expects a single domain. If I alter the local settings file, do I need to add in the domains from the default settings file, or will that get merged? Thanks. Andrew. ________________________________________ From: Abhilash Raj [raj.abhilash1(a)gmail.com] Sent: 01 September 2017 17:29 To: C. R. Oldham; mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman3 Docker question and importing lists from MM2 On Fri, Sep 1, 2017, at 08:51 AM, C. R. Oldham wrote: > > > > I had a question regarding the parameter: SERVE_FROM_DOMAIN. > > > > I want to use multiple domains, what is the best way to specify multiple > > domains in this environment variable? > > > > > This works OK for me: > > SERVE_FROM_DOMAIN=lists.domain1.org,lists.domain2.net,lists.domain3.com I never thought this would work, I would correspond to an invalid entry in ALLOWED_HOSTS in Django configuration. The best way would be to put the domain you are going to serve from in the SERVE_FROM_DOMAIN variable as this would replace the `example.com` SITE that Django creates by default. And then, you can list all your domains in /opt/mailman/web/settings_local.py in a Python list: ALLOWED_HOSTS = ["domain1", "domain2", "domain3"] Note that you need to also include the domain you set in SERVE_FROM_DOMAIN here. > > I also had to login to the Django admin interface and create the domains > there under Home->Sites And yes, for Django to allow domains, you need to create a 'Site' in the admin console. The default one is created automatically using SERVE_FROM_DOMAIN variable. > > --cro > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj _______________________________________________ Mailman-users mailing list mailman-users(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

8 years, 9 months

[MM3-users] Re: [Mailman-Developers] Rolling releases for Container Images and Funding Campaign for Mailman

by Barry Warsaw

On Nov 8, 2017, at 04:38, Simon Hanna <simon(a)hannaweb.eu> wrote: > > On 11/08/2017 12:03 AM, Abhilash Raj wrote: >> New images are available on quay.io and, moving forward, the rest of >> the image builds will also be moved to Quay[4][5]. > Since docker deployment is currently the recommended install, with manual installs using the master branches for "experts" I wonder why you are using Quay. > It looks like it's a non-free system. Why use Quay but refuse to use a non-free translation system like transifex? Is there a free (software) equivalent to Quay? Caveat: I don’t know anything about Quay, so I don’t know what services and advantages it provides. > If this campaign succeeds, here is a road map of what I intend to get >> done: > Sounds great, what is the limit where the campaign succeeds? What will happen to the funds if it doesn’t? The funds all go to the GNU Mailman project’s FSF donation fund. A portion of every donation goes to the FSF, and the Mailman Steering Committee ultimately decides what to do with what’s left in our account. In the past we’ve used it sponsor GSoC students coming to Pycon sprints. > To be honest, I don't think we should all in on containers. > Yes they are nice, but I guess most people would prefer distro packages. > Even if people want containers, I for instance would prefer plain systemd-nspawn There are folks working on Debian packages. I’m not aware of similar efforts for other distro ecosystems. But I don’t think it’s all or nothing, and it does make sense for us (the GNU Mailman project) to support containers to help with adoption, experimentation, and deployment, while working with distro volunteers to package the code up for those platforms. Cheers, -Barry

8 years, 7 months

[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, 5 months

[MM3-users] Strange bug I can't reproduce

by Stephen J. Turnbull

MegaBrutal via Mailman-users writes: > What I found out is that the second address must match the pattern > "Some Name" <a.b0(a)example.com>. The e-mail is properly formatted > when it gets into Mailman, but when it is sent out to list members, > it gets malformed to Some(a)serverhostname.example.com. This looks more like the kind of thing that an MTA sometimes does, rather than Mailman. Mailman does not modify addresses ever as far as I know, although in some cases it will substitute a different, fixed address for the original one in the message. (The three cases I know of are rewriting From to contain the list address for anonymous lists and DMARC mitigation, and it can be configured to substitute a fixed address in Reply-To.) Mailman doesn't do the kind of editing you describe, as far as I'm aware. Is example.com your domain? If you can look at the MTA configuration for that domain, check for address rewriting in the configuration. The easiest way to test it is to install the Mailhog application on the same host as Mailman, then configure Mailhog to send to the same SMTP gateway as Mailman, and configure Mailman to send to localhost and the Mailhog port. Mailhog will then capture Mailman's outgoing mail, you can check it in Mailhog's queue directory. Then you can release any non-test emails from Mailhog. If the messages captured by Mailhog show the problem, then it's probably Mailman. You can also get the same effect by just shutting down the MTA, and looking at the message in Mailman's 'out' queue (or perhaps the MTA's 'in' queue for some MTAs). But that would affect all incoming and outgoing mail, not just Mailman. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months

[MM3-users] Re: Implicit destination

by David Krantz

On Mon, Aug 27, 2018 at 2:50 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > That is not the issue. Sending the held message notice to a spammer, if > it reaches the spammer, is probably inconsequential. The issue is that > virtually always in spam the sender address is either undeliverable or > is the address of an innocent 3rd party. Sending these notices to > innocent 3rd parties is called backscatter and is a bad thing. > > To avoid this backscatter, you can set the list's > respond_to_post_requests attribute to False. There are two problems > here. One is this setting is not currently exposed in Postorius, and the > other is this will also stop desired held message notices such as those > from list members. Aha. That was a simple solution although with a bad consequence. Will it stop moderation mails to the moderator as well? I'll try. Otherwise it will not be a problem in my case. The lists where I have this problem are more of function addresses for a number of persons (like a board or workgroup) so they accept posts from non-members. I use mailman as a simple forward gets legit mail caught in the receivers spam filters and might cause more black-list problems. You are of course entirely correct in that backscatter is the real problem, I should have thought of that. The thing in the spam I've received lately is somewhat sophisticated: the senders have correct (albeit strange) domains and correct SPF records so they try to seem legit although the senders are located in unexpected parts of the world. I just checked one example, in that case the MX pointed to the sender IP, the SPF was very sloppy (~all) and everything looked correct except for the fact that we usually do not receive mail from Ukraine and the cryptocurrency scam in the body. It almost got caught in the spam filter, but not quite. cheers // David

7 years, 9 months

[MM3-users] Re: LTMP to Postfix problem

by Mark Sapiro

On 6/18/20 5:38 PM, Brian Carpenter wrote: > > Then there was this little bit of info: > > Jun 18 00:00:12 mm4 kernel: [19548549.442555] Out of memory: Kill > process 29676 (python3) score 37 or sacrifice child > Jun 18 00:00:12 mm4 kernel: [19548549.444508] Killed process 29676 > (python3) total-vm:192224kB, anon-rss:93084kB, file-rss:0kB, shmem-rss:0kB > Jun 18 00:00:12 mm4 kernel: [19548549.464907] oom_reaper: reaped process > 29676 (python3), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB > > I suspect the above process was ltmp. > > So the server has 2 gig of ram with about a dozen MM3 lists on it. Is > this an issue with tuning performance of the Postgresql server or do I > need to add more memory. I am curious how much ram your server is > running and if you had run into any OOM of problems. I haven't seen any OOM issues on the servers I manage. Those include mail.python.org 16 GB RAM 261 MM2.1 lists, 139 MM 3 lists lists.mailman3.org 4 GB RAM and other than tests and demos, only this list www.grizz.org 8 GB RAM This is my bicycling club's server. 7 MM 2.1 lists, only 2 of which are really active, 7 MM 3 lists including 2 test/demo - MySQL for the club database and Postgres for Mailman 3. It also supports some non Mailman club email and the club's web site including a MoinMoin wiki. The grizz.org domain was recently migrated from from a larger server in a colo that supported multiple domains to a DigitalOcean droplet which initially had only 4 GB RAM, but that seemed marginally enough at best, so I upgraded it to 8 GB. So the bottom line is I haven't run Mailman 3 on a server with only 2 GB and that may well not be enough. -- 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] can't get mail into mailman3 in docker

by bob B

I am trying to get mail into mailman in docker, I can send a test messages out from the container. But can't get mail in. Any idea what I am missing? mydomain.mydomain.com is substituted for the actual domain in the below output My /etc/postfix/main.cf has ------------------------------------- mydestination = $myhostname, localhost.$mydomain, localhost, mydomain.mydomain.com transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains # Support the default VERP delimiter. recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no ------------------------------------- my /opt/mailman/core/mailman-extra.cfg has ------------------------------------- # mailman-extra.cfg [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver # mailman-core hostname or IP from the Postfix server lmtp_host: localhost lmtp_port: 8024 # Postfix server's hostname or IP from mailman-core smtp_host: outbound-mail.mydomain.mydomain.com smtp_port: 25 configuration: /etc/postfix-mailman.cfg [mailman] # This address is the "site owner" address. Certain messages which must be # delivered to a human, but which can't be delivered to a list owner (e.g. a # bounce from a list owner), will be sent to this address. It should point to # a human. site_owner: admin(a)mydomain.mydomain.com ------------------------------------- The instructions say "The configuration file /etc/postfix-mailman.cfg is generated automatically." But I do not have that file is this the issue?? cat: /etc/postfix-mailman.cfg: No such file or directory When I send mail to my domain to a list i created called 'test' I get ------- 2021-08-02T13:33:08.666502-04:00 bmimailmandr1 postfix/cleanup[113557]: A068930294D8: message-id=<7C8556BA-156D-4A31-A64E-428C62D31AA1(a)mac.com> 2021-08-02T13:33:08.680953-04:00 bmimailmandr1 postfix/qmgr[113209]: A068930294D8: from=<testuser @bmail.com>, size=8275, nrcpt=1 (queue active) 2021-08-02T13:33:08.713683-04:00 bmimailmandr1 postfix/lmtp[113559]: A068930294D8: lost connection with localhost[127.0.0.1] while receiving the initial server greeting 2021-08-02T13:33:08.725326-04:00 bmimailmandr1 postfix/lmtp[113559]: connect to localhost[::1]:8024: Connection refused 2021-08-02T13:33:08.735727-04:00 bmimailmandr1 postfix/lmtp[113559]: A068930294D8: to=<test-join(a)mydomain.mydomain.com>, relay=none, delay=0.07, delays=0.03/0.01/0.03/0, dsn=4.4.1, status=deferred (connect to localhost[::1]:8024: Connection refused) -----

4 years, 10 months

[MM3-users] User cannot reset password

by Greg Newby

I imported MM2.1 lists to Mailman3 (using import21 - details are in my previous messages to mailman-users), and have had a couple of reports of people for whom the password reset function via "Forgot password" on the list login screen doesn't work as expected. This is a venv installation using PostgreSQL as the database: $ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.12.3 (main, Jul 31 2024, 17:43:48) [GCC 13.2.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:redacated@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:redacted The user selects "Forgot password" and enters their email - which I've confirmed is subscribed and receiving messages. They get this email: You are receiving this email because you, or someone else, tried to access an account with email redactaed(a)gmail.com. However, we do not have any record of such an account in our database. This mail can be safely ignored if you did not initiate this action. If it was you, you can sign up for an account using the link below. I looked in the PostgreSQL address table and confirmed the entry is there, and also of course looked at the Members list in the web-based front end. Everything looks ok. I suspect that lots of people will have the same problem, but have not yet tried to login & reset their password. The earlier reports indicated that people's saved passwords did not work, but I haven't replicated that. Any advice on what's going on and how to address it? I've migrated over 200 lists with thousands of users, so would rather not need to deal with every user via the web-based front end. But at this point I don't even know what to try to fix things. With the previous reports I unsubscribed the user and had them resubscribe - that worked as expected but required back-and-forth discussion and, more importantly, user inconvenience. Thanks, Greg Newby

1 year, 10 months

[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, 10 months

[MM3-users] Re: Disabling Mass operations

by Mark Sapiro

On 1/23/26 17:39, iMark wrote: > Hi All, > > Can anyone give me a pointer on disabling "Mass operations" > (subscribe/removal) in Postorius. > > Just removing the menu link from the list-owners administration pages > would be a good start. This patch will do that ``` --- a/src/postorius/templates/postorius/menu/list_nav.html +++ b/src/postorius/templates/postorius/menu/list_nav.html @@ -84,6 +84,7 @@ {% if user.is_superuser or user.is_list_owner %} <li class="nav-item"><a href="{% url 'list_template_list' list.list_id %}" class="nav-link {% nav_active_class current 'templates' %}">{% trans 'Templates' %}</a></li> <li class="nav-item"><a href="{% url 'list_settings' list.list_id %}" class="nav-link {% nav_active_class current 'list_settings' %} ">{% trans 'Settings' %}</a></li> + {% if user.is_superuser %} <li class="dropdown nav-item"> <a href="#" class="{% nav_active_class current 'list_mass_ops' %} dropdown-toggle nav-link" data-bs-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false"> @@ -98,6 +99,7 @@ <li><a href="{% url 'mass_removal' list.list_id %}" class="dropdown-item">{% trans 'Mass removal' %}</a></li> </noscript> </li> + {% endif %} <li class="nav-item"><a href="{% url 'list_bans' list.list_id %}" class="{% nav_active_class current 'list_bans' %} nav-link">{% trans 'Ban List' %}</a></li> <li class="nav-item"><a href="{% url 'list_header_matches' list.list_id %}" class="nav-link {% nav_active_class current 'list_header_matches' %}">{% trans 'Header filters' %}</a></li> <li class="nav-item"><a href="{% url 'list_delete' list.list_id %}" class="{% nav_active_class current 'list_delete' %} nav-link">{% trans 'Delete' %}</a></li> ``` Some lines in the above may be wrapped but basically it just adds {% if user.is_superuser %} and {% endif %} around the Mass operations code. -- 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: Mailman3 without Hyperkitty in docker

by Abhilash Raj

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

7 years, 3 months

[MM3-users] Re: logrotate

by Mark Sapiro

Please don't hijack threads. Post a new topic as an original post, not as a reply to an old thread. On 5/2/23 15:45, Christian via Mailman-users wrote: > I noticed that my mailman logfiles are not being rotated. I followed the > instructions in > https://mail.python.org/archives/list/mailman-developers@python.org/message/ > FM3TSMQ63JR2KROJGOSPENODOOQVRYCL/ Those instructions are for Mailman 2.1. > Now when I try and run logrotate I get the following error > > root@zarathustra:/opt/mailman/mm/logs# logrotate /etc/logrotate.conf > error: stat of /opt/mailman/mm/logs/bounce.log failed: No such file or > directory > error: stat of /opt/mailman/mm/error.log failed: No such file or directory > error: stat of /opt/mailman/mm/mailman.log failed: No such file or > directory > error: stat of /opt/mailman/mm/mailmansuite.log failed: No such file or > directory > error: stat of /opt/mailman/mm/smtp.log failed: No such file or directory > root@zarathustra: > > What am I doing wrong please? Here's a logrotate script I use: ``` /opt/mailman/mm/var/logs/*.log { missingok sharedscripts su mailman mailman postrotate sudo -u mailman /opt/mailman/mm/bin/mailman reopen &>/dev/null || true if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then PID=`cat /opt/mailman/mm/var/gunicorn.pid` kill -s USR1 $PID fi endscript } ``` A couple of caveats. The first line of the postrotate script may be wrapped. `sudo ... true` is all one line. That line could also be ``` /opt/mailman/mm/bin/mailman --run-as-root reopen &>/dev/null || true ``` I.e., it either has to run as the mailman user or specify the --run-as-root option. Also, if logs aren't in /opt/mailman/mm/var/logs/ or gunicorn.pid isn't in /opt/mailman/mm/var/ those paths need adjusting. Finally, there may be an issue with `mailman reopen` in the postrotate scrupt. See https://gitlab.com/mailman/mailman/-/issues/1078 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Mailman3 in dockers on EC2 - running out of memory and puking ev.ry.where.

by roger.hislop＠is.co.za

Thanks Danil, Abhilash ... moved instance to a *small, reboote and restated container. Boom, all working. The guide is on the surface fine, but has a number of mistake, and the middle section is a direct copy-paste from the Mailman3 docker instructions page. There are a number of small but important mistakes (syntax errors for eg) -- and the page owner provides no contacts, or hints how to google for them. I guess I'm so use to out of memory errors being a symptom of a giant bork that I don't take them as a sign I don't have enough memory. OK -- so everything is almost good... but nginx is still showing the default page. Could it be as stupid as not using the right single quotes around the domain name (hostname in this case)? I tried this config saved in /etc/nginx/conf.d/listman.blahblah.org.za.conf _________________________ server { listen 80; server_name 'listman.blahblah.org.za'; location /static/ { root /var/spool/mailman-web/; } location / { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_pass http://127.0.0.1:8000/; proxy_redirect off; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } # Error pages error_page 500 502 503 504 /500.html; location = /500.html { root /var/spool/mailman-web/; } } _________________________ I also tried the config in the Olay Farm cookbook ____________________________ server { listen 80; server_name `listman.blahblah.org.za`; location /static/ { alias /opt/mailman/web/static/; } location / { include uwsgi_params; uwsgi_pass 172.19.199.3:8080; uwsgi_read_timeout 300; } _____________________ Even tried the config at https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… but get when I test config nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/nginx.conf:41 nginx: configuration file /etc/nginx/nginx.conf test failed And finally the instructions given here https://github.com/Yexiaoxing/mailman-on-aws/blob/master/05-nginx-proxy.md I'm basically flailing in the dark here...

7 years, 2 months

[MM3-users] Re: mailman web spamming uwsgi error log.

by Mark Sapiro

On 6/28/21 2:02 PM, Sarah H wrote: > I'm having an issue with the mailman web logs (/opt/mailman/web/logs/uwsgi-error.log) spamming the below: > > 20:53:44 [Q] ERROR Failed [rebuild_mailinglist_cache_for_month] - MailingList matching query does not exist. : Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.6/site-packages/django_q/cluster.py", line 436, in worker > res = f(*task["args"], **task["kwargs"]) > File "/opt/mailman/venv/lib64/python3.6/site-packages/hyperkitty/tasks.py", line 79, in _rebuild_mailinglist_cache_for_month > mlist = MailingList.objects.get(name=mlist_name) > File "/opt/mailman/venv/lib64/python3.6/site-packages/django/db/models/manager.py", line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/venv/lib64/python3.6/site-packages/django/db/models/query.py", line 417, in get > self.model._meta.object_name > hyperkitty.models.mailinglist.MailingList.DoesNotExist: MailingList matching query does not exist. ... > I do not have a list named "MailingList". hyperkitty.models.mailinglist.MailingList.DoesNotExist is the name of the exception. MailingList refers to the hyperkitty.models.mailinglist.MailingList class. It is not the name of a list. The actual code is ``` def _rebuild_mailinglist_cache_for_month(mlist_name, year, month): try: mlist = MailingList.objects.get(name=mlist_name) except MailingList.DoesNotExist: log.warning('MailingList with name %s does not exist', mlist_name) return mlist.cached_values["participants_count_for_month"].rebuild(year, month) ``` Thus, there should be a warning level log message MailingList with name xxx does not exist Identifying the list name. This will be in Django's log which is probably not /opt/mailman/web/logs/uwsgi-error.log, but may be /opt/mailman/web/logs/mailmansuitelog. It is defined in settings(_local).py as the value of LOGGING['handlers']['file']['filename'] I'm not sure how this issue comes about. I suspect it comes from a task that was created before some list was deleted and the task is being continuously retried because it fails. What does your Django admin `qinfo` command show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: migration

by Dave McGuire

On 7/30/21 3:43 PM, Abhilash Raj wrote: >> Hi folks. Some time ago, I set up mm3 and have been running a bunch >> of lists on it with great success. I was a long-time mm2 user, and >> while the differences are significant, I'm glad I made the switch. >> >> However, in what seems to have been a moment of insanity in >> retrospect, I installed mm3 from my OS' package repository. >> >> Yeah, I know, that was dumb. Now I'd like to migrate to a new >> server, and I'd like to install mm3 in the normal way. >> >> Is there a way that I can "dump" the configuration from an existing >> mailman3 server, and "import" it into a new instance? I'd really like >> to avoid re-doing all of the configuration, etc, as there are quite a >> few lists and everything is set up pretty much the way I want it. > > You can copy the database from your old install to the new install > using the database native tools (or just point the new install to the > same old database if that is a possibility). Mailman Core will upgrade the > database schema when it first starts to the latest version's expected > schema. For web-components, you'd have to manually run the django's > `migrate` command to upgrade the database. The exact migrate > command depends on how you install the new one (mailman-web or > django-admin --settings settings). Ok. I guess first I've got to figure out where the database lives. I've not been hacking on mm3, just using it. > I'd also say you should avoid updating database versions in this > process because that would just add another variable to the process. Sounds reasonable. Thank you, I appreciate the advice. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

4 years, 10 months

[MM3-users] Re: Speaking of RFC 8058

by Paul Tomblin

This is what it looks like in Gmail when a message has the correct one click unsubscribe headers: On Wed, Mar 25, 2026, at 9:43 AM, Danil Smirnov wrote: > Hi Paul, > > Could you tell me what's you MUA? I'm struggling to see any relevant controls in Gmail... > > Sincerely, > Danil Smirnov > > ср, 25 мар. 2026 г., 15:15 Paul Tomblin via Mailman-users <mailman-users(a)mailman3.org>: >> On Wed, Mar 25, 2026, at 12:10 AM, Stephen J. Turnbull wrote: >> > It is undeniable that Mailman is not suitable for a large fraction of >> > announce lists. It's also true that (except for the relatively recent >> > RFC 8058 "Signaling One-Click Unsubscribe" protocol) all of your >> >> Speaking of which, I was wondering why my MUA didn’t put a one-click unsubscribe banner at the top of my mailman lists like it does for lots of other “mailing list” email I get. So I just read RFC 8058, and I realized that while Mailman puts on a List-Unsubscribe: header, it doesn’t have a URI in it, just an email address. It also doesn’t put on a List-Unsubscribe-Post: List-Unsubscribe=One-Click. The requirement for an “opaque identifier” looks hard to do in templates. I realize that it probably hasn’t been implemented due to your separation of Core and Web. But are there plans to provide something? >> >> -- >> Paul Tomblin >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> This message sent to danil(a)smirnov.la -- Paul Tomblin ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/jpeg Name: image.jpeg Replaced multipart/alternative part with first alternative.

2 months, 3 weeks

[MM3-users] Re: Message of migrated list showing "unsubscribe@%(host_name)s" in footer

by Mark Sapiro

On 10/8/23 16:03, alex(a)presland.net wrote: > > We migrated a number of mailman lists last weekend and I spotted this evening that an email from the list contained a footer along the lines of the following (all bits in CAPITALS were successfully representing the list. > > ===== > LISTNAME mailing-list -- LISTNAME@DOMAIN > To unsubscribe, email LISTNAME-unsubscribe@%(host_name)s > ===== > > 1) I don't know why %(host_name)s hasn't been automagically substituted > 2) I can't find anywhere to change this footer in the Mailman3 Postorius interface The `mailman import21` process creates templates for existing 2.1 regular and digest headers and footers in Mailman 3's var/templates/lists/LIST_ID/LC/ directory. LIST_ID is the list's id like listname.example.com and LC is the language code for the list's preferred language. These have names like list:member:regular:header.txt, list:member:digest:header.txt, list:member:regular:footer.txt and list:member:digest.footer.txt. These are based on the mailman 2.1 lists regular and digest headers and footers with replacements translated to the appropriate Mailman 3 equivalents. However, there are various reasons why some replacements can't be translated, and these are left as is. in your case you need to edit those files and change %(host_name)s to $(domain}, or, since the default mailman/templates/en/list\:member\:generic\:footer.txt is ``` _______________________________________________ $display_name mailing list -- $listname To unsubscribe send an email to ${short_listname}-leave@${domain} ``` just deleting the var/templates/lists/LIST_ID/en/list:member:regular:footer.txt file will probably do what you want. Note that templates defined in Postorius are handled differently, and if a template is currently undefined in Postorius, starting to define it in Postorius starts with an empty template instead of the current file system template. See https://gitlab.com/mailman/postorius/-/issues/366 -- 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: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Eggert Ehmke

Hello Mark, I am also using MySql/MariaDb, I followed your suggestion. This would uninstall a lot of other packages, is that safe? I did not continue. $ pip uninstall psycopg2_binary Found existing installation: psycopg2-binary 2.9.6 Uninstalling psycopg2-binary-2.9.6: Would remove: /opt/mailman/venv/lib/python3.11/site-packages/psycopg2/* /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary-2.9.6.dist-info/* /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libcom_err-2abe824b.so.2.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libcrypto-2cd0ac56.so.1.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libgssapi_krb5-497db0c6.so.2.2 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libk5crypto- b1f99d5c.so.3.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libkeyutils- dfe70bd6.so.1.5 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libkrb5- fcafa220.so.3.3 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libkrb5support- d0bcff84.so.0.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ liblber-69811697.so.2.0.200 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/libldap- e7812872.so.2.0.200 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libpcre-9513aab5.so.1.2.0 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libpq-227f62f1.so.5.15 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libsasl2-883649fd.so.3.0.0 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libselinux-0922c95c.so.1 /opt/mailman/venv/lib/python3.11/site-packages/psycopg2_binary.libs/ libssl-0331cfe8.so.1.1 Proceed (Y/n)? n Regards, Eggert Am Donnerstag, 19. Oktober 2023, 20:31:08 CEST schrieb Mark Sapiro: > On 10/19/23 05:02, Wikinaut wrote: > > (venv) mailman-web migrate > > > Traceback (most recent call last): > ... > > > File > > "/opt/mailman/venv/lib/python3.11/site-packages/django/contrib/postgre > > s/search.py", line 1, in <module>> > > import psycopg2 > > > > File > > "/opt/mailman/venv/lib/python3.11/site-packages/psycopg2/__init__.py", > > line 51, in <module>> > > from psycopg2._psycopg import ( # noqa > > > > SystemError: initialization of _psycopg raised unreported exception > > Since you are using MySql and not PostgreSQL, in your venv do > ``` > pip uninstall psycopg2_binary > ```

2 years, 7 months

[MM3-users] MM3 Bounces status

by Ruth Ivimey-Cook

Hi, I have some lists which are used primarily as a distribution method (rather than chat) and the person who uses these lists doesn't have access to the detailed MM logs and is not interested in that. It would be very helpful for message bounces (& any other anomalous events, if any) were to be available to that person for each message that is sent out, in a manner similar to mailgun et al. I know something of the bounce processing MM3 does, but it seems to be totally hidden from e.g. the postorius end of things (unless I'm missing something?). Is there a way for bounce events to be emailed to the list owner, or for something to be available in postorius to show this info? If not in the standard package, do other people have ad-hoc solutions to this issue? My ideal option would be for a configurable per-message email or postorius link that reports the number of emails to send (=number in mlist), the number on 'no-mail', the number sent successfully (=no bounce?), the emails of those who bounced (with bounce score), and emails of blocked sends (eg by multiple bounces). So for example: Bounce report for listname: Email Subject: Announcement Sent: today at time From Email: user(a)example.com received (today at time) To List: listname(a)example.com with 100 subscribers; 89 successful; 4 bounces; 3 blocks; 4 nomail; Bounces: - foo(a)bar.example.com (no mailbox) - bar23(a)foo.example.com (timeout) - alice(a)baz.example.org (mailbox full) - bob(a)example.net (bounce-reason) Blocked: - foo(a)bob.example.com (score 3) - bar23(a)alice.example.com (admin ban) - alice(a)alice.example.org (score 2) I suspect that my ideal option would require changes to the internal processing, because MM would need to keep more information about bounces than I think it currently does. It might also need to retain more information about LMTP delivery statuses? Thanks in hope? Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog:http://www.ivimey.org/blog LinkedIn:http://uk.linkedin.com/in/ruthivimeycook/

1 year, 8 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 Wikinaut

Not a single mail was sent - I am migrating (and newly setting up from textfiles) the mailman3 suite, installed fresh from the scratch in (venv) in /opt/mailman. I noticed that after having used a mix of addmember and also syncmember, one (or yesterday about 100 entries) of 500 had the MIME-coding. Then I used a script to remove users with the "=?UTF...." begin. In postorius users the user was gone and also in the lists where this user was in. def delete_users(): url = f"{API_URL}/users" r = requests.get(f'{url}', auth = AUTH) r.raise_for_status() users = r.json()['entries'] for user in users: dn = user.get('display_name') if type(dn) == type("string") and dn.startswith("="): print (dn) self_link = user.get('self_link') requests.delete(self_link, auth=AUTH) def main(): delete_users() After a new add/syncmember, that spooky entry was up again! Then I used mailman delmembers --fromall --no-goodbye-msg --no-admin-notify -m <this@address>: Then after a new add/syncmember, that entry was gone and the correct entry was shown. That means, that somewhere some remains were stored somewhere. I also have a another issue, where I cannot get rid of a test display_name like "1111 [äöo]" <myemailaddress> for my own user entry (this issue has not yet been filed, as I do not want to flood you here; the "=?utf.." issue seems to be a more apparent problem). At the moment, none of the ~500 users have "utf" searchable, which is some good news. Perhaps to mention: I noticed the utf-problems when I used Ctrl-C during heavy script actions while add/syncing the lists which I needed to stop. while testing. Perhaps this caused an inconsistent database state??? and that present issue was a consequence of my harsh break?

10 months, 1 week

[MM3-users] Exception when rendering certain emails ([Django] ERROR (EXTERNAL IP): Internal Server Error...)

by Stephen J. Turnbull

Matt Blissett via Mailman-users writes: > I get exceptions logged when certain pages in the email archives > (imported from Mailman 2) are opened. For example, this thread: > > https://lists.tdwg.org/archives/list/tdwg-tag@lists.tdwg.org/thread/HZCJQBJ… > > Could this be a bug in parsing the message? It does not appear to be a bug in parsing this message. Rather, it's trying to build the reply tree and raising the exception then. This: > File "/usr/lib/python3.12/site-packages/mistune/markdown.py", line 120, in __call__ > return self.parse(s)[0] suggests it's trying to parse Markdown out of a non-markdown file. This: > File "/usr/lib/python3.12/site-packages/mistune/core.py", line 214, in parse_method > assert lastgroup > ^^^^^^^^^ > > Exception Type: AssertionError at /archives/list/tdwg-tag(a)lists.tdwg.org/thread/HZCJQBJPACPZZN7UDNKJIPIFNTM7CA63/replies doesn't make sense to me, as core.py has only 207 lines in my installation, and there is no assert in the parse_method function. Check what version you have. A very few versions of mistune have caused problems in the past. I wonder if there's a version incompatibility here. My installation has mistune v3.0.2. (Since the exception triggers only on certain files, you should not consider that version "known good".) It's also possible that it's an issue in HyperKitty, as HyperKitty does tweak the mistune parser with its own rules to handle email-specific syntax such as .signature blocks and multipart/signed. If you do not need the Markdown rendering, you can disable it (per list). See https://docs.mailman3.org/projects/hyperkitty/en/latest/rendering.html for how and for more information on HyperKitty's markdown capabilities. If that's not helpful, Mark or Abhilash will likely be along soon with more expert assistance. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 year, 1 month

[MM3-users] Re: Strange behaviour when SSL (https) is activated

by fr-mm3＠tourde.org

Le 18995ième jour après Epoch, Stephen J. Turnbull écrivait: > According to Google Translate, this means "Secure connection failed", > which seems to be a webserver problem, not a Mailman problem. Recent > Firefox is very picky: it wants a proper certificate (although free > certificates such as CertBot will do), and it won't accept SSL or TLS > versions less than 1.2. Make sure that your webserver is properly > configured to use TLS >= v1.2, and has a properly configured > certificate. Yep, and maybe I wasn't clear enough, but all other pages display correctly. It's only when I try to log-in (ie: POST request). > This suggests that you're seeing a variant on the "redirect from HTTP > to HTTPS loses POST data" problem. The description of the problem is > different and I have no idea what your configuration is, but if the > advice (not the problem description) looks familiar the following post > may be of help: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Unfortunately, it seems no related as far as I understand this post. > More information about your webserver and Django configurations would > be useful. You're right :) ... The request path is as follow: > Firefox --> haproxy front --> nginx on mailman server --> mm3-web socket (unix:/run/mailman3-web/uwsgi.sock) The nginx conf is close to the proposed one on the Debian package: > upstream list.my_dom.ain_mm3 { > server unix:/run/mailman3-web/uwsgi.sock fail_timeout=600; > } > > server { > listen 443 ssl; > listen [::]:443 ssl; > > server_name list.my_dom.ain; > server_tokens off; > > ssl_certificate /etc/letsencrypt/live/list.my_dom.ain/fullchain.pem; > ssl_certificate_key /etc/letsencrypt/live/list.my_dom.ain/privkey.pem; > > > location / { > uwsgi_pass list.my_dom.ain_mm3; > include /etc/nginx/uwsgi_params; > } > ... Django config is as installed by Debian mailman3-web package. Thank you whatever for your help !

4 years, 5 months

[MM3-users] Re: Internal Server Error: Reattach this thread

by Mark Sapiro

On 10/26/22 02:29, cold00water(a)gmail.com wrote: > I have only tested the operation on the web screen. What exactly did you do to test this? > I ran c, but it doesn't work because of another error. > > $ python test_thread.py > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/tests/views/test_thread.py", line 29, in <module> > from django.contrib.auth.models import User > File "/opt/mailman/venv/lib/python3.10/site-packages/django/contrib/auth/models.py", line 2, in <module> > from django.contrib.auth.base_user import AbstractBaseUser, BaseUserManager > File "/opt/mailman/venv/lib/python3.10/site-packages/django/contrib/auth/base_user.py", line 47, in <module> > class AbstractBaseUser(models.Model): > File "/opt/mailman/venv/lib/python3.10/site-packages/django/db/models/base.py", line 107, in __new__ > app_config = apps.get_containing_app_config(module) > File "/opt/mailman/venv/lib/python3.10/site-packages/django/apps/registry.py", line 252, in get_containing_app_config > self.check_apps_ready() > File "/opt/mailman/venv/lib/python3.10/site-packages/django/apps/registry.py", line 134, in check_apps_ready > settings.INSTALLED_APPS > File "/opt/mailman/venv/lib/python3.10/site-packages/django/conf/__init__.py", line 76, in __getattr__ > self._setup(name) > File "/opt/mailman/venv/lib/python3.10/site-packages/django/conf/__init__.py", line 57, in _setup > 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. > > > Please tell me how to test. You need to get the source. E.g., git clone https://gitlab.com/mailman/hyperkitty.git This will create a `hyperkitty` directory in the current directory. Then you can test with tox. Ensure you have tox and then something like tox -e py310-django32 -- hyperkitty/tests/views/test_thread.py will run those tests. You can probably also test with `pytest`, but when I tried that I ran into issues with Django not finding settings. -- 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: message duplication and an NNTP related error

by Laurens Kils-Hütten

Am Wed, Feb 25, 2026 at 08:30:47PM +0100 schrieb Thomas Hochstein: > Laurens Kils-Hütten wrote: > > > # this is in /etc/news/newsfeeds > > news2mail!:!*:Ac,Tc,Wn*:/usr/lib/news/bin/news2mail > > test-grenzland-club/grenzland.club:!*,grenzland.test:Ap,Tm:news2mail! > > # this last line should do two things: forward messages from the > > # test(a)grenzland.club list to the grenzland.test newsgroup, > > No, it doesn't. newsfeeds specifies how incoming articles should be > distributed to other programs and files on the server. It can't > "forward" articles from a mailing list. That's what Mailman does (and > has to do). right, thanks for clarifying. I shouldn't have written "forward" and I mixed it up. > It will forward messages that are posted to grenzland.test to the > news2mail feed and to the test(a)grenzland.club mailing list, so the other > way around. And it will ... > > > # AND don't send any messages back which have grenzland.club > > ... or test-grenzland-club ... I think the Ap flag should prevent this. > > # in their Path header. This last bit seems to fail however, > > # and I fail to spot the error. > > Does Mailman submit the message with a Path header containing > "grenzland.club" or "test-grenzland-club"? Looking at the Path headers it's the former. test-grenzland-club is just an arbitrary identifier used in the inn2 configuration. I'm not sure mailman is even generating the Path header itself. > Does Mailman post the message (via NNRP / nnrpd) or feed it? nnrpd > If the former, what Path element does your nnrpd add? see below > Can you show the relevant entries from the news and news.notice logfiles > and the Path header from a message from the mailing list to the > newsgroup? Path headers always look like this, whether I post a message as news or email: Path: grenzland.club!.POSTED.localhost!not-for-mail So the exclusion pattern should match on the first part. This is what shows up in /var/log/news/news.notice: # I've added some comments ... # first mailman's nnrp client connects ... 2026-02-25T22:49:31.966611+01:00 grenzland innd: localhost connected 21 streaming allowed 2026-02-25T22:49:32.006079+01:00 grenzland innd: localhost:21 NCmode "MODE READER" received 2026-02-25T22:49:32.006427+01:00 grenzland innd: localhost:21 checkpoint seconds 1 accepted 0 refused 0 rejected 0 duplicate 0 accepted size 0 duplicate size 0 rejected size 0 2026-02-25T22:49:32.006490+01:00 grenzland innd: localhost:21 closed seconds 1 accepted 0 refused 0 rejected 0 duplicate 0 accepted size 0 duplicate size 0 rejected size 0 2026-02-25T22:49:32.015322+01:00 grenzland nnrpd[2990705]: localhost (127.0.0.1) connect - port 119 2026-02-25T22:49:32.059569+01:00 grenzland nnrpd[2990705]: SERVER perl filtering enabled 2026-02-25T22:49:32.059711+01:00 grenzland innd: localhost connected 21 2026-02-25T22:49:32.061392+01:00 grenzland innd: localhost:21 checkpoint seconds 0 accepted 1 refused 0 rejected 0 duplicate 0 accepted size 1338 duplicate size 0 rejected size 0 2026-02-25T22:49:32.061463+01:00 grenzland innd: localhost:21 closed seconds 0 accepted 1 refused 0 rejected 0 duplicate 0 accepted size 1338 duplicate size 0 rejected size 0 # and posts successfully: 2026-02-25T22:49:32.061498+01:00 grenzland nnrpd[2990705]: localhost post ok <20260225214930.E77531412C1(a)grenzland.club> 2026-02-25T22:49:32.062568+01:00 grenzland nnrpd[2990705]: localhost posts received 1 rejected 0 2026-02-25T22:49:32.062771+01:00 grenzland nnrpd[2990705]: localhost times user 0.006 system 0.004 idle 0.000 elapsed 0.048 2026-02-25T22:49:32.062895+01:00 grenzland nnrpd[2990705]: localhost time 48 idle 43(6) nntpwrite 1(24) # with a notable delay I sea the same connection procedure 2026-02-25T22:49:33.070321+01:00 grenzland innd: localhost connected 21 streaming allowed 2026-02-25T22:49:33.110111+01:00 grenzland innd: localhost:21 NCmode "MODE READER" received 2026-02-25T22:49:33.111092+01:00 grenzland innd: localhost:21 checkpoint seconds 0 accepted 0 refused 0 rejected 0 duplicate 0 accepted size 0 duplicate size 0 rejected size 0 2026-02-25T22:49:33.111186+01:00 grenzland innd: localhost:21 closed seconds 0 accepted 0 refused 0 rejected 0 duplicate 0 accepted size 0 duplicate size 0 rejected size 0 2026-02-25T22:49:33.124001+01:00 grenzland nnrpd[2990714]: localhost (127.0.0.1) connect - port 119 # but now it fails, presumably because an Injection-Info header field # has already been set. At the same time I see the error message given # in my original email in /var/log/mailman3/mailman.log 2026-02-25T22:49:33.165116+01:00 grenzland nnrpd[2990714]: localhost post failed Can't set system Injection-Info header field 2026-02-25T22:49:33.165765+01:00 grenzland nnrpd[2990714]: localhost posts received 0 rejected 1 2026-02-25T22:49:33.165832+01:00 grenzland nnrpd[2990714]: localhost times user 0.005 system 0.004 idle 0.000 elapsed 0.043 2026-02-25T22:49:33.165876+01:00 grenzland nnrpd[2990714]: localhost time 43 idle 42(6) nntpwrite 0(24) 2026-02-25T22:49:33.173419+01:00 grenzland innd: localhost connected 21 streaming allowed 2026-02-25T22:49:33.213944+01:00 grenzland innd: localhost:21 NCmode "MODE READER" received 2026-02-25T22:49:33.214300+01:00 grenzland innd: localhost:21 checkpoint seconds 0 accepted 0 refused 0 rejected 0 duplicate 0 accepted size 0 duplicate size 0 rejected size 0 2026-02-25T22:49:33.214368+01:00 grenzland innd: localhost:21 closed seconds 0 accepted 0 refused 0 rejected 0 duplicate 0 accepted size 0 duplicate size 0 rejected size 0 2026-02-25T22:49:33.221243+01:00 grenzland nnrpd[2990715]: localhost (127.0.0.1) connect - port 119 2026-02-25T22:49:33.261359+01:00 grenzland nnrpd[2990715]: localhost post failed Can't set system Injection-Info header field 2026-02-25T22:49:33.262391+01:00 grenzland nnrpd[2990715]: localhost posts received 0 rejected 1 2026-02-25T22:49:33.263326+01:00 grenzland nnrpd[2990715]: localhost times user 0.005 system 0.002 idle 0.000 elapsed 0.042 2026-02-25T22:49:33.263816+01:00 grenzland nnrpd[2990715]: localhost time 43 idle 41(6) nntpwrite 1(24) > (Or we can take that to news.software.nntp or > de.comm.software.newsserver, whichever (language) you prefer.) I don't have direct access to either group on this here machine. But news.software.nntp might actually be more on topic. Follow-up wherever you think is more apropriate. Thanks in any case! lkh > -thh > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to lkh(a)grenzland.club -- ~lkh (Laurens Kils-Hütten)

3 months, 3 weeks

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

by Abhilash Raj

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

6 years, 2 months

[MM3-users] Postorius Suggestion: Give owner a view of all users of all owned lists

by Stephen J. Turnbull

Andreas Vetter writes: > it would be real great if owners that own several lists, but are > not superusers, can see all users of all *their* lists and manage > them. A down-"selected" version of the superusers view. > Would that be possible? Possible, yes. I don't know how to do it well enough to add to our distribution. Note that owners can't actually manage users -- that really does need to be a superuser. Owners can manage subscriptions to the lists they own. So first we'd want to create a new "Subscriptions" item for the top menu; the "Users" item isn't appropriate. I'm not sure who that item should be visible to. Most likely only owners, because individuals already have ways to see all their subscriptions, and it's not obvious they would want the same presentation as your superowners. Then you'd iterate over the logged-in owner's lists and collect all of the subscriptions. I guess you'd want them to be organized by address rather than by list. By User is out, I think -- owners can't normally see Users, and I'm unhappy abou the privacy implications of being able to correlate nole(a)alset.com with head(a)dodgy.gov in general, although I realize it's not a problem in your setting. Without a more complete specification of what your users need, and the presentation they'd want to see, I personally am unwilling to go farther than those comments. Maybe one of the other devs feels differently. Also, "domain owner" is way under-implemented currently. For the hierarchical situation you outline, all the problems go away for domain owners. Of course then you'd need to split out lists by domain, but to me that's a small cost to preserve sanity in the structure. Steve

1 year, 3 months

[MM3-users] Re: Mailman3 on FreeBSD

by Abhilash Raj

On Sat, 12 Aug 2017 18:10:49 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/12/2017 04:51 PM, Barry Warsaw wrote: > > On Aug 10, 2017, at 16:32, John Poltorak <karotlopj(a)gmail.com> > > wrote: > >> > >> On FreeBSD they ought to be in /usr/local/etc/mailman.cfg however > >> I don't see any indication as to what I should put in this file > >> and if it was in /usr/local/etc/mailman.cfg then how would mailman > >> find it? > > > > It wouldn’t by default. Right now Mailman does not search > > for /usr/local/etc/mailman.cfg, but that wouldn’t be a difficult > > change to add. I’m not sure whether that would makes sense as a > > general default or not. I’m not up on the FreeBSD conventions and > > standards here; can you explain why /usr/local/etc is preferred > > over /etc on that distro? > > > I was hoping Abhilash would chime in here, because I think John is > using the docker image and there's probably a specific path for > mailman.cfg. As per his first message, I think John is using the prod setup from the documentaion[1]. I don't have anything much to add on top of what Barry mentioned, it looks like something is wrong with the Python install and missing Sqlite3 module. The documentation does mention the paths where Core looks for configuration file and anything else can be specified using -C or MAILMAN_CONFIG_FILE environment variable. [1]: http://docs.mailman3.org/en/latest/prodsetup.html > As far as what goes in it, it could even be empty if you want to > accept all the defaults, but you probably want at least > > [mailman] > site_owner: real_person(a)example.com > > I expect if you do > > find -name mailman.cfg > > in your installation, you'll find at least examples. > thanks, Abhilash

8 years, 10 months

[MM3-users] Re: Does anyone have a working DKIM/ARC configuration?

by Philip Colmer

On Fri, 10 Sept 2021 at 14:52, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > > Philip Colmer writes: > > > However, in sending test messages to a mailbox hosted by Microsoft, > > I'm seeing a header like this: > > We need *all* the relevant fields (all the DKIM signatures, all the > ARC-* fields from both your server and Microsoft, and the From field, > and if possible all the trace fields like Received) to figure out > what's going on. I hadn't wanted to send too much information (initially, at least) if there was something obviously wrong and I appreciate your explanation of what I have shared. > dkim=fail (signature did not verify) header.d=sender.org; > > This is sender.org's DKIM signature, and it is expected to fail unless > Mailman is configured in pure pass-through mode where it does not > touch the body or any of the signed header fields. sender.org's DKIM > signature may as well not be there for a conforming MTA (I assume > Microsoft's does in this, I don't see any advantage to them in > breaking DKIM). I hadn't realised that "dkim=fail" applied to the original email that had been sent to Mailman 3, so that is a relief. > DKIM is all over the place, working fine. Mailman ARC was tested, and > passed, during the ARC development process at the IETF. I don't know > offhand if anybody is using that combination now. If you own the MTA, > we recommend doing ARC there if supported by the MTA (I think Postfix > does). I'm glad to see Microsoft supporting it! I will certainly have a go at adding OpenARC to our Postfix MTA. Presumably I then (re)configure the [ARC] section in Mailman 3 to not be enabled? Thanks again for the quick and detailed examination. Regards Philip

4 years, 9 months

[MM3-users] Re: DKIM signatures with message footers or subject prefixes

by Mark Sapiro

On 3/12/22 12:20, Stanisław Findeisen via Mailman-users wrote: > On Fri, Mar 11, 2022 at 10:41:00AM -0800, Mark Sapiro wrote: >> Also, your outgoing MTA should DKIM sign the mail on the way out. With that and the above setting, the outgoing message will have only your >> valid DKIM signature and no prior Authentication-Results:. > > Ok, you mean after replacing the From address with the list address, right? > I can see no way (or sense) to DKIM sign arbitrary From: addresses. Your DKIM signature only says you sent the mail and if the signature validates, the mail hasn't been modified since you signed it. I.e. validation of the signature is a statement to the recipient that the mail received is what you sent. That's all. If the domain of the From: address doesn't align with your domain, the signature won't help with DMARC, but that's a separate issue and why we have DMARC mitigations suck as replacing the From: with the list address. > This actually works quite good: the recipient just gets 2 DKIM signatures. The original one is broken, the MTA-generated one (after writing my list address into From) is OK. This is good enough even for ProtonMail (no red warning). And your rewriting the From: is only necessary for DMARC. If the ProtonMail red flag is only because there was no valid DKIM signature, you shouldn't need to rewrite From:. If it is because of DMARC, you do. > What about this list (mailman-users). It looks this one also has From address replacement + conditional DMARC mitigation. And remove_dkim_headers: no. Correct? This list has DMARC mitigation action = Replace From: and DMARC Mitigate unconditionally = No and remove_dkim_headers: no. We DKIM sign all outgoing mail from lists.mailman3.org. -- 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: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

On Sun, Feb 5, 2023 at 8:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/5/23 01:13, Odhiambo Washington wrote: > > > > So in my case, I should at least increase the value of > > HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800? > > > It probably isn't even set in your case and defaults to 900 if it isn't > set. I have never seen this config option in any of the settings files and so believe that no one has it set - except the DEVs, maybe. > Yes, you can set it to a larger value. If your archive search > engine is woosh and your archive is even moderately large, 1800 probably > isn't nearly enough. Yes, my archive search engine is whoosh. And my archives size is 2.5GB+ For starters I will make it 3600 and observe next time. > There was no indication of timing in your OP, but you should determine > when that cron job started and when the error was > reported. The difference is the absolute minimum you should set > for HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE, but you should add some margin > to that. > Sadly I deleted the email. I will have to determine those aspects next time. I need to make a request for a small improvement on the documentation at: https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m… The problem I am facing (the subject of this thread is that of a race between the "monthly hyperkitty update_and_clean_index" job and the hourly "hyperkitty update_index job" Would it be possible to add such details to the section, so that it is clear what the corn jobs do and perhaps what can lead to such race conditions (if that's not too much to ask)? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 4 months

[MM3-users] Re: HyperKitty Question

by Samir Faci

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

6 years, 1 month

[MM3-users] Re: Moderation of held emails vs. spam

by David Krantz

> > I now run Mailman 3.3.1, installed from pip. Is there now any way to > > prevent Mailman from forwarding the contents of the held message when > > notifying moderators of held messages? > > There is not now any configuration setting for this. I suspected that. > > In my case these messages often > > are spam messages and if the entire contents are forwarded it triggers > > spam handling in the recipient address(es) which over time risks > > classifying all moderation emails as spam or even classifying the list > > domain or server as a spam source. > > > > Even my own outgoing filter classifies it as spam, which I will fix. > > So if you can recognize them as spam, why are you delivering them to to > list in the first place? Sorry, I see now that that sentence was mostly incorrect. The incoming spam filter (rspamd) does not detect it as spam, but the outgoing filter does (sometimes) as the moderation mail changes to the incoming mail increases the spam points slightly. In those cases the mailman rules trigger in place of the spam filter, e.g. only members may post. Probably bad training of the adaptive filter so that part of the problem will iron itself out over time. What is more problematic is that mail hosts like Hotmail/Microsoft have a more heavy handed approach to spam filtering. Currently this problem is very limited in my case as grey-listing, IP-blocks and filtering catches most spam but I'd still prefer to receive just a moderation mail with just the subject line, sender and size of the message instead of a full quote as that normally is enough to moderate our lists. > You can submit an issue at <https://gitlab.com/mailman/mailman/-/issues>. I'll do that later this week or next week. Thank you for your very useful reply! Cheers // David

5 years, 10 months

[MM3-users] Re: HyperKitty failure

by Mark Sapiro

On 1/2/22 4:34 AM, horvath.arpad.szfvar(a)gmail.com wrote: >> Can you go to https://lists.xxx.hu/hyperkitty/api/lists and get a >> response from Django REST framework which is a json representation of >> your mailing lists info? > > In this list I have just one list that I created for testing. And I can't see there the two lists I've imported from mailman2, e.g. korus. I guess because of admin is not a list list member there. I can see the korus at https://lists.xxx.hu/hyperkitty/ , but not at https://lists.xxx.hu/postorius/lists/ . when you view https://lists.xxx.hu/postorius/lists/ is there a Filter by Role dropdown at the top of the listing? If so, if you select `All` do you then see the lists. Postorius by default shows only those lists in which you have a role. If you still don't see the lists, what does the command `mailman lists` show? > I guess the setting below is not good. > > MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') > > Should I set it to > ('https://lists.xxx.hu/hyperkitty', '::1') ? Doesn't seem to work, like that. It needs to be an IP. Set it to `('xxx.xxx.xxx.xxx', '127.0.0.1', '::1')` where xxx.xxx.xxx.xxx is the IP of lists.xxx.hu or just `('xxx.xxx.xxx.xxx',)` would probably work. > And what about MAILMAN_REST_API_URL? > How can I found its proper value? It's currently the default value > but if I try to reach it with > wget http://localhost:8001 > I get a 404. not found. How can I find the right value? If Postorius works, It's good. `wget http://localhost:8001` returns a 404 as it should because this is a REST API and `/` is not a known endpoint. Something like `wget --user restadmin --password restpass http://localhost:8001/3.1/lists` should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: MM3 Postfix FROM header issue

by Mark Sapiro

On 12/17/23 9:10 AM, eboltz(a)lhtservices.com wrote: > Mark, > > Here is my postconf -n > > alias_database = hash:/etc/aliases > alias_maps = hash:/etc/aliases > always_add_missing_headers = yes > append_dot_mydomain = no > biff = no > compatibility_level = 2 > default_destination_concurrency_limit = 15 > default_destination_recipient_limit = 30 > header_checks = regexp:/etc/postfix/header_checks > header_size_limit = 409600 > inet_interfaces = all > inet_protocols = ipv4 > local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp > mailbox_size_limit = 0 > mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain > myhostname = lists.example.com > mynetworks = 127.0.0.0/8 [::fff:127.0.0.0]/104 [::1]/128 > myorigin = /etc/mailname > readme_directory = no > recipient_delimiter = + > relay_domains = hash:/var/lib/mailman3/data/postfix_domains > relayhost = [mail.smtp2go.com]:587 > smtp_always_send_ehlo = yes > smtp_sasl_security_options = noanonymous > smtp_tls_CApath = /etc/postfix/o365_smtp_cert.pem > smtp_tls_security_level = may > smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache > smtp_use_tls = yes > smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination > smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem > smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key > smtpd_tls_security_level = may > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > unknown_local_recipient_reject_code = 550 > virtual_alias_maps = hash:/var/lib/mailman3/data/postfix_vmap It looks like you are now following <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. > What would I have to do to ensure that MM3 and postfix (same new server) use the newly created lists.example.org domain, which only exists within Postfix when setting up the Postorius domain and lists? > I want to have it so that whatever the list name is, for example 'Staff(a)lists.example.org' will route through Postfix correctly. Have you set an alias_domain for the lists.example.org domain? What are the contents of /var/lib/mailman3/data/postfix_vmap and /var/lib/mailman3/data/postfix_lmtp? If you feel it is necessary to anonymize the domains in these, please only change the tld so we can see the actual subdomains. -- 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: RDS CA changes

by Hirayama, Pat

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

1 year, 10 months

[MM3-users] Re: External MTA incoming mail: configuration

by Odhiambo Washington

On Wed, Jul 31, 2024 at 2:35 PM Roland Giesler via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 2024/07/30 22:39, Mark Sapiro wrote: > > It appears you have a situation where the MX for the Mailman domains > > is not the Mailman server. You need to configure the MTA on > > box2.gtahardware.co.za to relay Mailman's mail to the mailman server. > > You can to this by configuring that MTA to use transport_maps, etc as > > if it were the Mailman server. In order to get Mailman's generated > > files on the other server, you need to create a process to do that. > > When Mailman makes changes by adding or deleting lists or when it is > > started, it updates the postfix_lmtp and postfix_domains files and > > calls a command (normally postmap) to update the corresponding .db > > files. The command can be set by setting `postmap_command` in the > > `[postfix]` section in mailman.cfg. > > > I'm not able to find any documentation about `postmap_command`, not even > in the schema.cfg. If I have to provide method to update the > postfix_lmtp and postfix_domains on another server, then it would have > to something like sftp? mailman changes the files on the mailman server > (in a location I set) and then postmap_command copies those files to the > destination on the MTA server. Is that in principle what needs to be done? > > thanks again! > Read this thread and take a keen look at the solution provided by @Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> : https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 10 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 3/2/21 1:55 PM, David Partain via Mailman-users wrote: > On Tue, 2021-03-02 at 13:43 -0800, Mark Sapiro wrote: >> >> Unless you want to remove the Ubuntu package and install everything >> with >> pip, you need to just stick with what you have that at least partly >> works and we'll try to determine how to fix the utf8mb4 issue. > > Hi Mark, > > You're a very patient soul. Thank you. > > Yes, I'm resigned to exactly that. The archives when folks send emojis > will break, but that's just life. Mail will get sent. Heck, I guess I > could edit the file in /var/lib/mailman3/archives/hyperkitty/spool to > get rid of the emoji in the worst case... You would need to do that, because once one of the `emoji` messages gets into /var/lib/mailman3/archives/hyperkitty/spool, I think no further messages are archived because mailman_hyperkitty tries to process the queued messages first and throws the exception. But, it's still not clear to me whether you have removed the settings_local.pyc and restarted uWSGI or whatever interfaces to Django. > Once I've migrated my 1500 mailing lists (this weekend) to the server, > I'll think about how to get a new server set up that I can shift to and > I'll install that with pip, since that'll clearly give me something > more supportable. > > Is Ubuntu 20.04 a reasonable platform for that? Yes it is. FWIW, this list runs bleeding edge Mailman 3 on an Ubuntu 14.04 server (yes we should upgrade), the only issue being that we needed to install Python 3.6 (the latest at the time) from source because the native Python 3 was 3.4 -- 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: migration

by Abhilash Raj

On Fri, Jul 30, 2021, at 12:06 PM, Dave McGuire wrote: > > Hi folks. Some time ago, I set up mm3 and have been running a bunch > of lists on it with great success. I was a long-time mm2 user, and > while the differences are significant, I'm glad I made the switch. > > However, in what seems to have been a moment of insanity in > retrospect, I installed mm3 from my OS' package repository. > > Yeah, I know, that was dumb. Now I'd like to migrate to a new > server, and I'd like to install mm3 in the normal way. > > Is there a way that I can "dump" the configuration from an existing > mailman3 server, and "import" it into a new instance? I'd really like > to avoid re-doing all of the configuration, etc, as there are quite a > few lists and everything is set up pretty much the way I want it. You can copy the database from your old install to the new install using the database native tools (or just point the new install to the same old database if that is a possibility). Mailman Core will upgrade the database schema when it first starts to the latest version's expected schema. For web-components, you'd have to manually run the django's `migrate` command to upgrade the database. The exact migrate command depends on how you install the new one (mailman-web or django-admin --settings settings). I'd also say you should avoid updating database versions in this process because that would just add another variable to the process. > > I would appreciate any advice from this learned group. > > Thanks, > -Dave > > -- > Dave McGuire, AK4HZ > New Kensington, PA > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 10 months

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

by Shashikanth Komandoor

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

5 years, 7 months

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

by David Newman

(sorry, hit send too soon) On 11/23/21 4:40 AM, Stephen J. Turnbull wrote: > David Newman writes: > > > I am looking for a high-level "do these steps next to get a list > > working" document rather than an API command reference. > > There's no such documentation. "Get a list working" depends on what > you mean by "working". Thanks for getting back to me. IMO post-installation docs for list admins would be a big help in Mailman3 adoption. I'm willing to help with this. When I say "working": I'm looking to migrate Mailman2 mailing lists to Mailman3, but am struggling with even basic setup tasks before we attempt list migtration. For example, on admin page I've set up two lists, one public and one private (each with unique list IDs), but neither appear in the site's list index. And I don't know where to add list members. And clicking the site archives link throws this error: django.urls.exceptions.NoReverseMatch: Reverse for 'hk_list_overview' with keyword arguments '{'mlist_fqdn': 'wheee'}' not found. 1 pattern(s) tried: ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/$'] etc. I am 100.00% certain these and other issues are all down to misconfigurations on my part, but don't know where to turn for direction on correct list setup and maintenance with mailman3. > > - For Django (presumably in /etc/mailman3/settings.py, but the docs > > don't say), what values to use with Postfix to set up the email back end? > > The answer is "that depends on your mail environment". As far as I > know, normally it just works with the default settings, but if your > Postfix requires secure, you need to set that up: > https://docs.djangoproject.com/en/3.2/ref/settings/#std:setting-EMAIL_USE_T… > and possibly the following 3 or 4 variables if authentication is needed. > > There was a thread on this a couple of weeks ago. Thanks for the pointers. Both resolved this issue. dn

4 years, 6 months

[MM3-users] Re: External MTA incoming mail: configuration

by Roland Giesler

On 2024/07/31 13:47, Odhiambo Washington via Mailman-users wrote: > On Wed, Jul 31, 2024 at 2:35 PM Roland Giesler via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> On 2024/07/30 22:39, Mark Sapiro wrote: >>> It appears you have a situation where the MX for the Mailman domains >>> is not the Mailman server. You need to configure the MTA on >>> box2.gtahardware.co.za to relay Mailman's mail to the mailman server. >>> You can to this by configuring that MTA to use transport_maps, etc as >>> if it were the Mailman server. In order to get Mailman's generated >>> files on the other server, you need to create a process to do that. >>> When Mailman makes changes by adding or deleting lists or when it is >>> started, it updates the postfix_lmtp and postfix_domains files and >>> calls a command (normally postmap) to update the corresponding .db >>> files. The command can be set by setting `postmap_command` in the >>> `[postfix]` section in mailman.cfg. >> >> I'm not able to find any documentation about `postmap_command`, not even >> in the schema.cfg. If I have to provide method to update the >> postfix_lmtp and postfix_domains on another server, then it would have >> to something like sftp? mailman changes the files on the mailman server >> (in a location I set) and then postmap_command copies those files to the >> destination on the MTA server. Is that in principle what needs to be done? >> > Read this thread and take a keen look at the solution provided by @Stephen > J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> : > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Excellent! I think I can get the sshfs route working, but the pending database solution is elegant! I love it! Thanks for the pointer.

1 year, 10 months

[MM3-users] Re: SPF check fails for lists subdomain

by Jan Eden

On 2023-01-05 08:55, Jan Eden via Mailman-users wrote: > On 2023-01-04 15:07, Mark Sapiro wrote: > > On 1/4/23 14:02, Jan Eden via Mailman-users wrote: > > > Although I could specify the IP address in my SPF records directly (as > > > you suggested), I do hope that my understanding of DNS records laid out > > > above is not entirely misguided. My current setup does work as expected > > > for eden.one, after all. > > > > As I said at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > > I was misreading your DNS and now I am as puzzled as you about the failure. > > It gets even more mysterious. I tried sending messages from both > lists.eden.one and janeden.net (my other domain) to a gmail account and > to another mail provider. Both messages passed the SPF checks on both > services (s. the relevant headers quoted below). Now because I send > those messages via my SMTP user (smtpuser(a)eden.one) and use SRS, the SPF > check operates (and succeeds) on e.g. > srs0=jdm+=5c=lists.eden.one=testlist-bounces+gmailuser=googlemail.com(a)eden.one > (and not on somethingsomething(a)lists.eden.one or > somethingsomething(a)janeden.net) Could this be the reason for the failed > SPF checks in Yahoo's and Google's DMARC reports? There was never a mystery, just my complete ignorance wrt DMARC and alignment[1]. Changing the DMARC DNS entry for lists.eden.one (more specifically, the aspf tag) solved the issue: <policy_published> <domain>lists.eden.one</domain> <adkim>s</adkim> <aspf>r</aspf> <p>quarantine</p> <sp>quarantine</sp> <pct>75</pct> </policy_published> <record> <row> <source_ip>123.123.123.123</source_ip> <count>1</count> <policy_evaluated> <disposition>none</disposition> <dkim>pass</dkim> <spf>pass</spf> </policy_evaluated> </row> For other domains, I would need to turn off SRS, which is not possible for independent reasons. - Jan [1] https://en.wikipedia.org/wiki/DMARC#Alignment

3 years, 5 months

[MM3-users] Re: Setting for archiving multi email domains?

by Duane Raymond

Thanks! So - I've documented what I did below. Now that I am getting bouces, I got an email that said "The response from the remote server was: 550 5.1.1 <test(a)emaildomainA.com>: Recipient address rejected: User unknown in virtual alias table" Specifically to some ot the questions above: > What do you mean by "set"? That the list has archiving enabled? Yes. I meant that archiving had been enabled for the test(a)emaildomainA.com test list. Shunting error: I think the shunting error is a distraction if it is caused by not having a recipient. Early tests to the test list had me as an administrator, but not as a member - so this would have caused that. Once I added myself (before I sent the original message in this thread), the result (not sending the message to the list using a 'virtual' domain and not archiving it) continued. Virtual Domains: So based on the Postfix virtual domain documentation and the Mailman3 specific "Unusual Postfix configuration' section, I added the following to my postfix main.cf file: virtual_alias_domains = emaillistA.com emaillistB.com virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap and removed those domains from the 'mydestination' setting. I then created the postfix_vmap file and added to it: emaillistA.com DOMAIN # emaillistB.com DOMAIN ...then ran postmap with the path and reloaded postfix. On testing I also noticed that a previous counce was to emaildomainC.com - an alias for emaildomainA.com I had originally setup in the Postorius domain setup and then removed. I guessed that it was still in the postfix config, so I double checked in the MM generated postfix_domains file and ran postmap /path-to/postfix_domains and reloaded postfix again...and sent another test message.... This then generated the error email at the top from my email client (gmail). ...but the end result is no email sent and thus the reason there is no archive.... Any further suggestions? I can supply other log messages and configuration options if it helps. Duane

5 years, 3 months

[MM3-users] Re: Programmatic Creation of Users

by Mark Sapiro

On 7/30/22 05:25, jciesla(a)techsupportme.com wrote: > > After a lot of research I now understand that what I am doing in the Core Shell is creating a User entity which has one or more email addresses as well as one or more roles and preferences that exist at the global level. This user entity can Subscribe to zero or more lists. If I am incorrect in the summation please let me know! Almost correct. A User does have preferences but does not have roles. Roles are associated with list memberships, not users. > Assuming that the previous information is correct that brings us to my current dilemma. Specifically, the User entity can Subscribe and interact with lists using the email commands, but they can't Login using the Postorius web interface. If I understand correctly the reason that they can't login is that the underlying Django system does not recognize their account because the account that was created in Core isn't accessible by Django. Instead the user needs to create a Django-specific account at which point the information from Core becomes available in the user's web UI. The simple view is that Django users and Mailman Users are unrelated. Either can exist without the other. They only tie together if they have the same email address. That is the only connection between them. > If that is in fact accurate then I want to take the next logical leap: is it possible to programmatically create an account in Django that is tied to the account that was created in Core? See the script at https://www.msapiro.net/scripts/clean_users.py. This is an example that deals with Django users and Mailman Users and deletes some Django users. See https://docs.djangoproject.com/en/4.0/topics/db/queries/#creating-objects for information about creating objects. Also see the UserManager class in django/contrib/auth/models.py -- 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: Python 3.13 compatibility

by Stephen J. Turnbull

Thomas Ward via Mailman-users writes: > Would it be preferred to have a section for "Install from Git > Master" or a "Install development branch" section under > Installation that addresses this?� If so I can work to edit the > site docs to make such sections. I appreciate the thought, but I don't think it's useful in the general audience documentation. Installing from HEAD is always risky, especially for people using LTS distributions. The Django situation is always fraught. Putting that recipe as is in the developer docs also doesn't make that much sense to me, as developers are expected to have full clones of the components they're working on. On the other hand something that points at the dev's local repos of the Mailman Suite components does make a lot of sense to me. Then you can add a note that "if you're only interested in some of the components, you can automatically get HEAD installations by substituting "https://gitlab.com/mailman/" for your "/path/to/local/repos/" in the `pip` commands for the rest. That makes sense to me because it means you don't have to keep a local mailmanclient clone up-to-date just to work on Postorius. And exercise for the reader: you can get your buddy's django-mailman3 hacks the same way. What do y'all think? Oh, yeah, probably ought to check the requirements.txt DAG to order the pip commands so that you're not overwriting PyPI versions with git master HEAD versions all the time. Steve > On 2026-03-30 07:39, Thomas Krichel wrote: > > pip install git+https://gitlab.com/mailman/mailman@master git+https://gitlab.com/mailman/mailmanclient@master git+https://gitlab.com/mailman/mailman-hyperkitty@master git+https://gitlab.com/mailman/hyperkitty@master git+https://gitlab.com/mailman/django-mailman3@master git+https://gitlab.com/mailman/postorius@master git+https://gitlab.com/mailman/mailman-web@master -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 months, 2 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I logged in with the superuser. It said that it sent a confirmation email which I haven't received yet because I guess I have to configure the mail server right? What do you suggest?? El sáb., 22 jul. 2017 a las 10:23, Rafael Mora (<rafael.mora.guti(a)gmail.com>) escribió: > Thanks for the settings and suggestions. I want just to try it, if it > doesn't work out I will move to mailchimp. > > I really appreciate your willingness to help me. > > Do you know another program for mailing mailchimp/mailman like? > > Thanks > > > > > > > El sáb., 22 jul. 2017 a las 10:00, tlhackque via Mailman-users (< > mailman-users(a)mailman3.org>) escribió: > >> On 22-Jul-17 09:30, Rafael Mora wrote: >> > What would be the config for a simple one way announcement type list >> ???? >> > >> Here is a possible list configuration (this doesn't go in any particular >> file; it's a dump from the REST API, but you should be able to find the >> corresponding settings in the GUI): >> | >> ||# Phantom list 41|| >> ||# ---------------|| >> ||acceptable_aliases = []|| >> ||admin_immed_notify = true|| >> ||admin_notify_mchanges = true|| >> ||administrivia = true|| >> ||advertised = true|| >> ||allow_list_posts = false|| >> ||anonymous_list = false|| >> ||archive_policy = "public"|| >> ||autorespond_owner = "none"|| >> ||autorespond_postings = "respond_and_discard"|| >> ||autorespond_requests = "none"|| >> ||autoresponse_grace_period = "45d"|| >> ||autoresponse_owner_text = ""|| >> ||autoresponse_postings_text = "This is an announce-only list"|| >> ||autoresponse_request_text = ""|| >> ||bounces_address = "phantomtbonesq-list-bounces(a)example.net"|| >> ||collapse_alternatives = false|| >> ||convert_html_to_plaintext = false|| >> ||created_at = "2017-06-28T00:33:14.031754"|| >> ||default_member_action = "discard"|| >> ||default_nonmember_action = "discard"|| >> ||description = "well, you see it's like this"|| >> ||digest_last_sent_at = null|| >> ||digest_send_periodic = true|| >> ||digest_size_threshold = 5000|| >> ||digest_volume_frequency = "weekly"|| >> ||digests_enabled = true|| >> ||display_name = "Phantom list 41"|| >> ||dmarc_mitigate_action = "no_mitigation"|| >> ||dmarc_mitigate_unconditionally = false|| >> ||dmarc_moderation_notice = ""|| >> ||dmarc_wrapped_message_text = ""|| >> ||filter_content = false|| >> ||first_strip_reply_to = false|| >> ||fqdn_listname = "phantomtbonesq-list(a)example.net"|| >> ||http_etag = '"ad12b8647391aa81563c67a164c57156e10efca0"'|| >> ||include_rfc2369_headers = true|| >> ||info = " The wind in the willows|| >> ||talked in the pillows||||" >> ||join_address = "phantomtbonesq-list-join(a)example.net"|| >> ||last_post_at = null|| >> ||leave_address = "phantomtbonesq-list-leave(a)example.net"|| >> ||list_name = "phantomtbonesq-list"|| >> ||mail_host = "example.net"|| >> ||moderator_password = null|| >> ||next_digest_number = 1|| >> ||no_reply_address = "noreply(a)example.net"|| >> ||owner_address = "phantomtbonesq-list-owner(a)example.net"|| >> ||post_id = 1|| >> ||posting_address = "phantomtbonesq-list(a)example.net"|| >> ||posting_pipeline = "default-posting-pipeline"|| >> ||reply_goes_to_list = "no_munging"|| >> ||reply_to_address = ""|| >> ||request_address = "phantomtbonesq-list-request(a)example.net"|| >> ||send_welcome_message = false|| >> ||subject_prefix = ""|| >> ||subscription_policy = "confirm"|| >> ||volume = 1| >> >> The key items are: >> >> allow_list_posts = false >> autorespond_postings = "respond_and_discard" >> autorespond_requests = "none" >> autoresponse_postings_text = "This is an announce-only list" >> default_member_action = "discard" >> default_nonmember_action = "discard" >> >> You don't need to worry about DMARC, since you're the only poster. >> >> Deciding about VERP (bounce verification) will require some thought - >> it's a tradeoff of cost vs. accuracy. It's discussed in the >> documentation. >> >> In addition, you need to define a subscriber with "moderation_action = >> accept", from which you post to the list. >> >> This is from a Mailman 3 application that's still being developed, so it >> may not be fully debugged. >> >> FWIW, your difficulties getting MM3 working are not unique. I have had >> similar problems - and I'm not done yet. I've run Mailman 2.1 lists for >> many years, but 3.1 is a lot more complex to set up. In fact, pretty >> much everyone who has tried to use MM3 has had similar problems. >> >> MM3 is in early stages of adoption & development. You should expect the >> challenges of any early adopter of complex software. There will >> undoubtedly be bugs - some serious, some not so. But if you continue to >> provide feedback, there's hope that the developers will improve it. >> >> On the other hand, if you want a more stable platform and are willing to >> settle for fewer features, you might consider using MM2.1. It's widely >> deployed and quite stable. Your distribution will have it packaged & >> easy to set up. You can always migrate when 3.1 is more mature. >> >> Finally, as others have noted, Mailman is fine for distributing moderate >> volumes of e-mail. For high volume, you need to tune your mailserver >> and platform - this may not be cost effective in terms of your time and >> investment in bandwidth and hardware. Also, Mailman doesn't provide the >> "services" that many people expect from mass mailing services such as >> MailChimp - e.g. beacons indicating how many people open your mail, >> correlation with purchases, tests to see how it fares with spam filters, >> compatibility tests with common e-mail clients, and so on. >> >> If an open loop system meets your needs, Mailman can work well. If you >> need feedback, it may not meet your needs. >> >> >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 10 months

[MM3-users] Re: duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Mark Sapiro

On 3/24/22 01:11, Stanisław Findeisen via Mailman-users wrote: > Hi > > I am having 4 different virtual domains (FILTER_VHOST = True). However on the domain list page in Postorius: https://.../postorius/domains/ I can see only 3 different SITE_IDs: 1,1,4,3. If I recall correctly, the "3" and "4" were created manually using the Postorius Web UI, whereas the two "1"s were created using the Mailman Client: > > client.create_domain(name) > > Is this a bug? Or did I mess something up? > What significance do those SITE_IDs have? The issue is client.create_domain doesn't support setting a Web Host. Web Hosts are the sites in the django_site table and SITE_ID is the id of the table entry. See `sites` in the Django admin UI. So when you create a domain with client.create_domain it gets arbitrarily assigned to a `site` > What I also noticed is that in the Postorius Web UI: https://.../postorius/lists/ both "1" domains display the lists contained in "3", whereas both "3" and "4" display correctly their lists. Except the "3", all domains are empty at the moment (no lists) (so "4" correctly displays no lists). Not sure if this is related?... FILTER_VHOST = True is imperfect. Lists have no Web Host attribute, only a Mail Host. Thus, with FILTER_VHOST = True, we get the Mail Host from the domains that have a Web Host matching the host in the http request. If that results in only one Mail Host, we limit the display to only those lists with that Mail Host, but otherwise we don't limit by domain. In other words, FILTER_VHOST = True only works if each Mail Host domain has a unique Web Host. If you have multiple Mail Host domains with the same Web Host (SITE_ID), FILTER_VHOST won't work for that Web Host. -- 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: There are currently no mailing lists!?

by Odhiambo Washington

On Tue, Jul 23, 2024 at 2:28 PM Christian <csa(a)web-analysts.net> wrote: > I meant to say I updated Buster. > > When I ran 'sudo systemctl start mailman' I get > How can you be helped when you don't give the details you requested? [snip] > > Job for mailman.service failed because the control process exited with > error code. > See "systemctl status mailman.service" and "journalctl -xe" for details. > root@lists:~# systemctl status mailman.service > ● mailman.service - GNU Mailing List Manager > Loaded: loaded (/lib/systemd/system/mailman.service; enabled; vendor > preset: enabled) > Active: failed (Result: exit-code) since Tue 2024-07-23 04:15:47 PDT; > 10s ago > Process: 1357 ExecStart=/opt/mailman/mm/bin/mailman start (code=exited, > status=2) > > Jul 23 04:15:46 lists.gaiapacha.ie systemd[1]: Starting GNU Mailing List > Manager... > Jul 23 04:15:47 lists.gaiapacha.ie mailman[1357]: Usage: mailman start > [OPTIONS] > Jul 23 04:15:47 lists.gaiapacha.ie mailman[1357]: Try 'mailman start -h' > for help. > * Jul 23 04:15:47 lists.gaiapacha.ie <http://lists.gaiapacha.ie> > mailman[1357]: Error: A previous run of GNU Mailman did not exit cleanly > (stale_lock). Try using --force* > Jul 23 04:15:47 lists.gaiapacha.ie systemd[1]: mailman.service: Control > process exited, code=exited, status=2/INVALIDARGUMENT > Jul 23 04:15:47 lists.gaiapacha.ie systemd[1]: mailman.service: Failed > with result 'exit-code'. > Jul 23 04:15:47 lists.gaiapacha.ie systemd[1]: Failed to start GNU > Mailing List Manager. > From the above, you see the bolded line? So do something like: systemctl restart mailman Alternatively: rm /opt/mailman/mm/var/locks/* Then: systemctl start mailman PS: Kindly put your further responses below the responses you receive. Not at the top. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 10 months

[MM3-users] Re: Mailman not starting after restoring from snapshot

by Odhiambo Washington

On Mon, Apr 28, 2025 at 4:45 PM <zachr(a)mta.ca> wrote: > I made a snapshot of my mailman3 VM before running a script to modify a > bunch of lists. I stupidly did not turn the VM off before I made the > snapshot, so Im almost certain this is a corrupted DB problem from doing a > snapshot restore. The issue is now that the mailman service will not start > automatically. Im able to get to the web interface but I see the error > "Mailman REST API not available. Please start Mailman core." I can su to > the mailman user and run 'mailman start -f' which seems to get things going > again and shows the lists as they were before the snapshot, which is good, > but I would like to get the issue fixed so that services start normally. > Any help is appreciated. Here is some terminal output: > ===================== > ''' > root@mlist3:~# systemctl status mailman3 > × mailman3.service - GNU Mailing List Manager > Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; > preset: enabled) > Active: failed (Result: exit-code) since Mon 2025-04-28 13:24:43 UTC; > 1min 39s ago > Process: 1873 ExecStart=/opt/mailman/venv/bin/mailman start > (code=exited, status=2) > CPU: 776ms > > Apr 28 13:24:42 mlist3 systemd[1]: Starting mailman3.service - GNU Mailing > List Manager... > Apr 28 13:24:43 mlist3 mailman[1873]: Usage: mailman start [OPTIONS] > Apr 28 13:24:43 mlist3 mailman[1873]: Try 'mailman start -h' for help. > Apr 28 13:24:43 mlist3 mailman[1873]: Error: A previous run of GNU Mailman > did not exit cleanly (stale_lock). Try using --force > cd /opt/mailman/var/locks/ rm *master* Then start mailman, -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 1 month

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

by bob B

is this the info you need for the container version [root@..... docker-mailman]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 30af82ac9315 maxking/mailman-web:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8000->8000/tcp, 127.0.0.1:8080->8080/tcp mailman-web cd01a99cf908 maxking/mailman-core:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core 77fe89ced9e8 postgres:9.6-alpine "docker-entrypoint.s…" 2 hours ago Up 2 hours 5432/tcp dockermailman_database_1 for smtp host ------------ cat /opt/mailman/web/settings_local.py #allowed_hosts = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] #ALLOWED_HOSTS = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] ALLOWED_HOSTS = ['*'] DEBUG = True EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'smtp.example.com' EMAIL_PORT = 25 --------------------------- cat /opt/mailman/core/mailman-extra.cfg # mailman-extra.cfg [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver # mailman-core hostname or IP from the Postfix server lmtp_host: localhost lmtp_port: 8024 # Postfix server's hostname or IP from mailman-core smtp_host: smtp.example.com smtp_port: 25 configuration: /etc/postfix-mailman.cfg [mailman] # This address is the "site owner" address. Certain messages which must be # delivered to a human, but which can't be delivered to a list owner (e.g. a # bounce from a list owner), will be sent to this address. It should point to # a human. site_owner: my_real_email_is_in_the_file.com __________________________________ My docker most machine /etc/postfix/main.cf has transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains # Support the default VERP delimiter. recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no ------------------------------ is that correct? I leave them set to smtp.example.com because the will send out via the docker host machine, and so i ONLY have my actual outbound server listed in /etc/postfix/main.cf on the docker host machine, or do i need to replace smtp.example.com with our outbound server? Also, If I want to blow away everything away (databse etcc) and rebuild it... what are those steps?

4 years, 10 months

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

by Bill Oliver

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

1 year, 8 months

[MM3-users] Re: moving list from mm3 -> mm3

by Stephen J. Turnbull

Jens Günther writes: > Am 09.12.23 um 00:27 schrieb Mark Sapiro: > > You need a PUT command, not POST. Try the above with `-X PUT`. > > With the `-X PUT`-command, there is the following error: > {"title": "400 Bad Request", "description": "Unexpected parameters: > bounces_address, created_at, digest_last_sent_at, fqdn_listname, > http_etag, join_address, last_post_at, leave_address, list_name, > mail_host, next_digest_number, no_reply_address, owner_address, post_id, > posting_address, request_address, usenet_watermark, volume"} You should post the exact command or interactive conversation you're using. My guess is that the REST API is expecting a single JSON object, and you sent it multiple parameters. Have you played with the REST API interactively? The documentation at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… is really quite good as a tutorial. It's not a full API reference, and not organized that way, although the table of contents is very useful for what it does mention. But I think what you need (if you want to explore it that deeply) is a tutorial to get a "feel" for how the REST API "likes to talk". > Is there another way to preserve these information about the > members? You can query the REST API (you might need to fetch the subscriber roster, then iterate over that to get the details), or you can dump the database table (or the whole database) using SQL-based utilities like psql (Postgres, I forget the MySQL equivalent). > (in general I don't think a lot of people put in effort to > customize there memeberships ... and furthermore they would need to > register, right?) Not sure what you mean by "register", but every address that writes to Mailman gets a temporary user until a "real" user claims it via the mailbox ownership dance. If they receive mail in a mailbox, they've done the ownership dance for that mailbox. If you don't preserve that record, they'll have to do it again. Steve

2 years, 5 months

[MM3-users] Re: MM3 templates

by Mark Sapiro

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

3 years, 4 months

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

by Mark Sapiro

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

2 years, 8 months

[MM3-users] Re: Welcome message issue

by Mohsen Masoudfar

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

1 year, 7 months

[MM3-users] Re: Time Stand Still

by Fabian A. Santiago

On November 23, 2017 11:38:00 AM EST, Barry Warsaw <barry(a)list.org> wrote: >Somewhen in the dark recesses of intarweb history, I found myself as >the project leader for both Jython (née JPython) and GNU Mailman. I'd >been involved with Jython since it was invented by Jim Hugunin around >the time he came to work with us at Pythonlabs. I'd been contributing >to Mailman since we inherited John Viega's Python-based Dave Matthews >Band list server, and put it to use replacing python.org's Majordomo >installation. > >I'd enjoyed both projects, but knew I could not lead both, so I had to >make a choice. I chose to turn over Jython to a team that's done a >much better job over the years than I ever could have. Something about >email, and especially the communication and collaboration patterns that >it facilitates, really fascinated me. I know, I know, but we all have >our lapses of sanity. Mine has lasted almost 20 years, a bit more than >"momentary" perhaps. > >I've rarely gotten paid to work on Mailman, but it did provide me some >great opportunities. Most notably it led to my 10 year stint at >Canonical. I was originally hired on there to integrate mailing lists >with Launchpad, and Mailman was the obvious choice. I learned a ton >doing that project, and working within the constraints of integrating >the two Python-based systems, especially since Launchpad was originally >not free software and Mailman was GPL'd. Later, the Zope-based >Launchpad source code was released under the AGPL, making much of the >monkeypatching unnecessary, but by then the system was solid and >reliable, and you don't fix what's not broken. > >Except, I guess I did. I took a lot of the lessons from that work, >along with a good hard look at all the problems with Mailman 2, and >began to break another cardinal rule of software development: second >system syndrome. The result is Mailman 3. It took forever, and we're >still not at complete feature parity with Mailman 2, but at least it's >Real Enough to be used at many Real Sites, including python.org and >lists.fedoraprojects.org. > >It would be ridiculous for me to take significant credit for this. I >have to acknowledge the amazing user community -- you! -- for all the >support, patches, suggestions, feedback, patience, criticism, >donations, and contributions that you've given to the project, and to >me personally over the years. And my deepest gratitude goes to all the >core developers that have stayed or come and gone, but most especially >the current Cabal: Abhilash Raj, Aurelien Bompard, Florian Fuchs, Mark >Sapiro, Stephen J. Turnbull, Terri Oda. You should know that each and >every one of them is truly awesome, both in what they contribute >technically, and in their amazing friendships. Mailman is infinitely >better because of their involvement, and I've loved spending time with >them over the years at the Pycon sprints, making releases and sharing >teas and meals. > >My blog is called We Fear Change, and that's humorously taken from a >90's bit in Mike Myer's excellent Wayne's World movie (a phrase >actually uttered by the brilliant Dana Carvey as Garth). The irony of >course is that while we all may fear change, it's the one constant >thing we can count on. And in fact, we *require* change to thrive, >because if you aren't changing, you aren't alive. Time, and being >engaged with life's vagaries, means there's no alternative to change; >it must be embraced. > >And so, with a vague reference to the many (good!) changes in my >personal and professional life, I'm announcing that I'm stepping down >from the project leadership role of GNU Mailman, effective... nowish! >And it's with unanimous agreement among the GNU Mailman Steering >Committee (a.k.a. the Mailman Cabal), that we are announcing Abhilash >Raj as the new project leader. > >If you don't recognize Abhilash's name, you probably aren't paying >attention, at least to Mailman 3. Abhilash came to us in 2013 as a >Google Summer of Code student, and he's become one of the project's >most valuable contributors. His list of accomplishments is long, and >it includes everything from redesigning the website, to integrating CI >with our GitLab build system, porting our code to the SQLAlchemy ORM, >adding MySQL support, revving up adoption through his Docker images, >along with his great coding work on Core, Postorius, HyperKitty, and >mailmanclient. > >This transition is good for the project too. Email, its defining >protocols and standards, and its role in our daily lives, has changed >profoundly since the early days of Mailman. A fresh perspective and >enthusiasm will help keep Mailman relevant to the changing ways we -- >especially the FLOSS and tech communities -- communicate. > >Please join me in supporting Abhilash in every way possible as he takes >over in this new role as project leader. I'll be here when and if >needed, even as I create space in my "spare" time for... Something >Else. I look forward to the vision that Abhilash will bring to the >project, and I know that he will do a great job. To me, Mailman has >always been about collaboration, and the best >way for it to succeed is for you to continue to contribute your >insights, experiences, opinions, and skills with positive intention. > >-Barry > >https://www.wefearchange.org/ Congrats Abhilash! Love the docker images! Thank you Barry! Mailman rocks! -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

8 years, 6 months

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

by Michael Heseltine

Hi all, after many more attempts, I've still failed to find any set of instructions that can install mailman3 on an Ubuntu 20.04 LTS server of mine. I've recently switched to a new server without any previous installation (apart from an apache web server) so that I can follow the instructions provided in https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 to the letter, if possible. But still, I run into an error I do not understand. I have followed the instructions until this point: > # pip install importlib_resources==1.1.0 > Once the above packages are installed run “mailman info” in your virtual environment. That will install Mailman core into your /opt/mailman/mm/var directory. (I had to add "apt install libmemcached-dev" to the instruction for "pip install psycopg2-binary" to succeed.) Then, I run "mailman info", but get an error message: > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 508, in connect > return self.dbapi.connect(*cargs, **cparams) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/psycopg2/__init__.py", line 122, in connect > conn = _connect(dsn, connection_factory=connection_factory, **kwasync) > sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "localhost" (::1), port 5432 failed: FATAL: password authentication failed > for user "mailman" > connection to server at "localhost" (::1), port 5432 failed: FATAL: password authentication failed for user "mailman" This suggests that the connection to postgresql fails, but if I test this using # psql --user mailman and type in the password listed in settings_local.py, I can login fine. I've also changed the port number in that configuration from '' to '2222', but the connection is still made to port 5432, which suggests to me that my call to mailman info uses another set of connection parameters provided elsewhere. Where can this be found? How will I be able to run "mailman info" w/o error and continue the installation as detailed in https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 ? Any help is appreciated. Happy new year, Michael.

4 years, 5 months

[MM3-users] share directories between postfix and mailman 3

by Thomas Schachtner

Hi there, I think I have (finally) set up a working instance of mailman 3 on a host separate from the companion postfix mail server actually sending out the mails. One server (postfix) is directly in the internet and the other one is in an internal network not directly reachable from the internet (but connected using a reverse proxy). The services on the hosts are available to one another (i. e. the postfix server is reachable using 127.0.0.1:25 from mailman and mailman is reachable using 127.0.0.1:8024 from postfix using a permanent ssh tunnel betwenn the two hosts). I think that this solution could work quite reliably... (at least I hope so.) But that's not the full deal. Postfix needs access to some hashed configuration files containing the transport maps and the domains of the mailman installation, and mailman needs the contents of the postfix configuration file. As a quick and dirty solution, I've established a process which periodically copies the /var/lib/mailman3 directory from the mailman box to the postfix box using rsync. But I would like to have a more professional solution, like a directly shared directory between both. I did not yet find any suggestions on how to achieve this. Are there any best practices recommendations? I already tried sharing the directories using sshfs, but that did not work. I connected the remote directory postfix.example.com:/var/lib/mailman3 to my local directory /var/lib/mailman3 using sshfs root@postfix.example.com:/var/lib/mailman3 /var/lib/mailman3 This seemed to work pretty fine, as all files and directories seemed to be available, but when starting mailman 3, the following error message was shown: FileExistsError: A race condition might have happened. /var/lib/mailman3 actually exists and is not a directory. Any idea why this message is shown? So, is it a bad idea to use sshfs? Do I have to install an NFS server? But I am not sure if sharing directories using NFS across the Internet is a good idea... Any suggestions? Best regards Tom

2 years, 4 months

[MM3-users] Re: Mailman shutting down Hyperkitty: Request too large

by Arte Chambers

Thanks, this was helpful. It was a message I sent to the list that was just an image attachment with no body text. I noticed this other thread about messages with attachments, without text discarded silently <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. I am attaching the pickle file hoping that it helps anyone researching this issue. Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Fri, Jan 31, 2025 at 2:55 AM Stephen J. Turnbull < turnbull(a)sk.tsukuba.ac.jp> wrote: > Arte Chambers via Mailman-users writes: > > > There is only 1 .pck file in $var_dir/archiver/hyperkitty/spool and > > it is only 3.5M - Is there a way I can see what this pck file is? > > That file would be related to the response. The *request* in the > HyperKitty protocol is going to be much smaller. I believe the normal > upper limit is 4kB. The previous report raised the limit on the > request to 16kb or maybe 64kB, but then ran into a different problem. > None of these numbers should be big enough to cause consistent OOM > conditions unless your memory is truly tiny. > > To view the file content, su to mailman, activate the virtual > environment if you are using one, and type > > mailman qfile $var_dir/archiver/hyperkitty/spool/xxxx-xxxx.pck > > (with the correct name for the qfile, of course). mailman qfile -h > will give you help, but IIRC qfile is one of the simplest subcommands: > '-h' may be the only option it takes. > > There are two parts to the output. The first is the Message object > flattened to an RFC 822 message file. The second is a mapping of > metadata that gives hints about what Mailman was doing with the file. > > Steve > ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

1 year, 4 months

[MM3-users] Re: Help request, almost got it going, but ....

by Claus-Justus Heine

Am 02.09.2017 um 01:57 schrieb Mark Sapiro: > On 09/01/2017 04:20 PM, Claus-Justus Heine via Mailman-users wrote: >> >> The issue seems not to be overly active. I thought -- coming from >> Mailman v2 -- that the configuration of acceptable submitters to an >> email list (e.g. keep everyone moderated?) would be a central and >> prominent and important configuration issue. Seems not to be a central >> point. Mmmh. > > > > Acceptable aliases corresponds directly to MM 2.1 Privacy options... -> > Recipient filters -> acceptable_aliases. It has nothing to do with > submitters. It is a list of other addresses that can be in the To: or > Cc: of a post to avoid and "implicit destination" hold if the list > posting address is not there. However, the point here is that this bug makes the entire configuration tab unusable. I could live WITHOUT acceptable_aliases. This bug spoils the possibility to set ANY message acceptance settings _easily_. Of course, I can work around: * delete the text field for acceptable aliases before hitting submit * insert a fance @ character there, and give a damn about the fancy stuff mailman3 does with this However, the possibility to make an entire mailing list moderated -- ALL POSTS -- is a central point. Or not? If this is so complicated then one option might be to remove the entire "acceptable aliases" field. It does not work anyway, and spoils other useful things (read: all other settings in the "Message Acceptance" tab) The point is not so much what this particular setting is for, but: it is broken for more than a year now and spoils other useful settings in the configuration dialog that it is located at. The "Message Acceptance" dialog is a central point IMHO. You make have another opinion about that. Cheers Claus -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

8 years, 9 months

[MM3-users] Re: Mailman3 reinstall fail, need some help

by Yvan ♞

Yes it's debian and I have root access but it's a more "user friendly" server release. I tryed this but it block https://github.com/YunoHost-Apps/mailman3_ynh/blob/master/README.md https://yunohost.org/en/administrate/whatisyunohost Sincerely Yvan Le 12/03/2022 à 15:28, Eggert Ehmke a écrit : > Hello Yvan, > > I would suggest to install mailman3 following this guide: > https://docs.mailman3.org/en/latest/install/virtualenv.html > > but at first check, which operating system is on your yunohost? Is it Debian/ > Ubuntu? In this case the guide is fine, else there will be some adaptions. > > Tell me some details of your system, and if you have root access and can > install software packages. > > Regards > Eggert > > Am Samstag, 12. März 2022, 15:16:11 CET schrieb Yvan ♞: >> Hello, just made a try to install mailman 3 on yunohost unsuccessfully >> Sad... >> If some body can help me... >> Thanks >> https://paste.yunohost.org/raw/hujesebita >> >> Le 07/02/2022 à 15:57, Stephen J. Turnbull a écrit : >> >>> Yvan ♞ writes: >>> >>> >>> >>> > Just to know if I have a chance, do I have to unistall mailman before >>> > installing mailman 3 ? >>> >>> >>> >>> No. In fact, you can run both at the same time. Not for the same >>> list, obviously. And it requires a fair amount of planning and careful >>> attention to your web and MTA configurations. As far as I know there >>> are no naming conflicts in the default installations, Mailman 2 >>> installs into directory trees under directories named "mailman", while >>> Mailman 3 installs under "mailman3". >> _______________________________________________ >> Mailman-users mailing list --mailman-users(a)mailman3.org >> To unsubscribe send an email tomailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > >

4 years, 3 months

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

by Stefan Bauer

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

4 years, 4 months

[MM3-users] Re: Fwd: Re: Removing a mail addresses and users

by Allan Hansen

All, Thank you for your thoughtful responses to my call for a removal of the core vs. Django disconnect. From your responses it appears that my suggestion my issues were caused by the Mailman Core was not based in reality. Instead, the issue is how Postorius interacts with the Core. My apologies for overreaching, as the cause of my issues is not an issue to me. Keeping Core a simple list manager is fine, if Postorius is easy to use and does the expected. As a Subscriber, you are able to do switch emails in subscriptions from your options page. The URL to which is displayed in the List's Summary page when you are logged in. Yes, it requires an approval if the list's settings are set to moderate but that is going to be fixed, see this issue[1]. It is quite simple IMO to fix this one, if someone wants to take this up. Well, it’s more than that. Based on the current setup, I have asked my subscribers who want to change their subscription addresses to: a. Create an account if you do not already have one. b. Go to the user profile page. c. Select ‘E-mail Addresses’. d. Add the new e-mail to the user profile. e. Wait for the verification notice and verify the new address. e1. If it does not show send email to hansen(a)rc.org <mailto:hansen@rc.org> to get the email verified manually. f. Sign in to the account again and to the user profile (or refresh the page if not signed out). g. Select the new address as the primary address. h. Click on ‘Manage Lists’ i. For each list you are subscribed to: i1. Select the list i2. Click ‘List Options Page.’ i3. Pull down the ’Select Email’ menu. i4 Select your new email. i5. Press ‘Change email used for subscription. i6. When the moderator contacts you, explain that you are just changing your email. i6.1. If the moderator is late, send a reminder or send email to hansen(a)rc.org <mailto:hansen@rc.org> to bypass the moderator. Most people choke on these instructions, so I have unfortunately resorted to just asking them to subscribe the new address and forget about the old. This is not good for our reputation when the old addresses start bouncing. So, in more detail: I would like to ask my subscribers who want to change their address to: a. Create an account if you did not already have one. b. Go to the user profile page. c. Select ‘E-mail Addresses’. d. Select an existing address e-mail listed the user profile. e. Press new button ‘Change address’. f. When page refreshes, enter the new e-mail address. g. Press ‘Apply.' d. Wait for the verification notice. d1. If it does not show send email to hansen(a)rc.org <mailto:hansen@rc.org> to get the email verified manually. In other words, in addition to ‘Make Primary’ and ‘Re-send Verification’ and ‘Remove’, another button says: ‘Change Address’ or’ ‘Replace Address’ or some such. This button brings up another page that looks the same, but instead of ‘Add E-mail Adress’ is says : Enter New E-mail Address’ and instead of ‘Add E-mail’ is says: ‘Apply’. Then the page refreshes back to the original page, but the new address is now replacing the old address. Optionally, it can show the old address still with a ‘pending change’ until verification. Further, when the new address is verified, all lists get updated with the new address replacing the old address and all settings associated with the old address are now associated with the new address. No moderator or admin involvement needed (other than d1). You are able to sign in via web and manage your email and subscriptions. The preferences also work exactly how you described above where the lower level override the default and/or upper level settings. To some extent that is true, Abhilash, and I appreciate that. The above (address change) is a missing piece in that picture and I look forward to seeing it added, if you have time. Yours, Allan Hansen hansen(a)rc.org > On Jun 14, 2020, at 0:19 , Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Mark Sapiro writes: > >> Then the people who developed the web based management UI (Postorius) >> and archive UI (HyperKitty) chose to develop those within a Django >> framework and Django has its own concept of User separate from Mailman >> Core and that is where the disconnect occurs. >> >> It's not that Mailman Core lacks what you want. It's that Django doesn't >> use it. > > I think that's mostly right, in terms of the features that users miss. > However, as far as I know, Mailman core does lack facilities for > identification, authentication, and authorization of connections to > the REST API. And that means that the front ends have to handle > this. I would guess that's why the web interfaces are built around > Django user authentication. > > I think it would be possible to have somewhat tighter integration > between the Django "web users" and the Mailman core User objects, but > it's not necessarily going to be trivial. > > I see that Abhilash is pretty optimistic, but I fear this this is > going to be a long-tail situation where we're going to be seeing core > user vs. web-gui user integration issues in 2030 (maybe by then only 1 > every 450 days ;-). I have some ideas, maybe in a couple weeks I can > sketch them out. > > Steve > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years

[MM3-users] MM3 not starting

by max.diener＠hpi.de

Hi, i am trying to install MM3 and had a few issues with it. First i was trying the Mailman3-full package for Debian which didnt work good for me. There was missing paths and files, after some research i found out it may not be well maintained right now. I was working to fix the issue i come up with but had no luck with it. After that i was trying this Howto: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 the Installation worked in some aspect. i had a running mailman3 service but the webinterfaces was not working. After some searching i found a issue that was stating that the current release had a bug in it wich made it not working. For instance was the config file different for "systemctl start mailman3" then when i was checking it "mailman info" and some paths was not like in the instructions again, this time i added the folders and put the files needed for it in to it but could not make it work. i kept digging and find out for prod it is best practice to install in a virtual environment so i waited for the bug to fix and took this Installation Instructions: https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install i was a little bit confused that there seems to be two spots from the official site where you can find Installation Instructions: https://wiki.list.org/DOC/ and https://docs.list.org/ since the last one made it seem like it was newer i choose the venv installation instructions. From the install instructions at https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install i was seeing that there is also some folders not showing up like mentioned in the howto: /op/mailman/mm was not there. In the part where you configure mailman core it says you need to add the /etc/mailman/mailman.cfg file it shows that the path is used for the hyperkitty config as well as it is the path vor the "var_dir: /opt/mailman/mm/var". i added the paths and at the point in the install instructions here https://docs.list.org/en/latest/install/virtualenv.html#starting-mailman-au… i checked if i can start mailman3 now but still fail to do so. when i check "journalctl -xe" i find the following information but cant get more information on how to fix it in the net with it: Aug 22 09:54:05 mailman3test mailman[55134]: Starting Mailman's master runner Aug 22 09:54:05 mailman3test mailman[55134]: Generating MTA alias maps Aug 22 09:54:05 mailman3test systemd[1]: mailman3.service: Can't open PID file /opt/mailman/mm/var/master.pid (yet?) after start: Operation not permitted Aug 22 09:54:12 mailman3test mailman[55146]: Traceback (most recent call last): Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/bin/runner", line 8, in <module> Aug 22 09:54:12 mailman3test mailman[55146]: sys.exit(main()) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 1130, in __call__ Aug 22 09:54:12 mailman3test mailman[55146]: return self.main(*args, **kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 1055, in main Aug 22 09:54:12 mailman3test mailman[55146]: rv = self.invoke(ctx) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 1404, in invoke Aug 22 09:54:12 mailman3test mailman[55146]: return ctx.invoke(self.callback, **ctx.params) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 760, in invoke Aug 22 09:54:12 mailman3test mailman[55146]: return __callback(*args, **kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func Aug 22 09:54:12 mailman3test mailman[55146]: return f(get_current_context(), *args, **kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/mailman/bin/runner.py", line 188, in main Aug 22 09:54:12 mailman3test mailman[55146]: runner.run() Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/mailman/runners/lmtp.py", line 255, in run Aug 22 09:54:12 mailman3test mailman[55146]: self.lmtp.start() Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/aiosmtpd/controller.py", line 210, in start Aug 22 09:54:12 mailman3test mailman[55146]: raise self._thread_exception Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/aiosmtpd/controller.py", line 176, in _run Aug 22 09:54:12 mailman3test mailman[55146]: srv: AsyncServer = self.loop.run_until_complete(self.server_coro) Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete Aug 22 09:54:12 mailman3test mailman[55146]: return future.result() Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 1460, in create_server Aug 22 09:54:12 mailman3test mailman[55146]: infos = await tasks.gather(*fs, loop=self) Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 1400, in _create_server_getaddrinfo Aug 22 09:54:12 mailman3test mailman[55146]: infos = await self._ensure_resolved((host, port), family=family, Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 1396, in _ensure_resolved Aug 22 09:54:12 mailman3test mailman[55146]: return await loop.getaddrinfo(host, port, family=family, type=type, Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 856, in getaddrinfo Aug 22 09:54:12 mailman3test mailman[55146]: return await self.run_in_executor( Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run Aug 22 09:54:12 mailman3test mailman[55146]: result = self.fn(*self.args, **self.kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/socket.py", line 953, in getaddrinfo Aug 22 09:54:12 mailman3test mailman[55146]: for res in _socket.getaddrinfo(host, port, family, type, proto, flags): Aug 22 09:54:12 mailman3test mailman[55146]: socket.gaierror: [Errno -2] Name or service not known Aug 22 09:55:01 mailman3test CRON[55176]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Aug 22 09:55:01 mailman3test CRON[55177]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Aug 22 09:55:01 mailman3test CRON[55176]: pam_unix(cron:session): session closed for user root Aug 22 09:55:34 mailman3test systemd[1]: mailman3.service: start operation timed out. Terminating. Aug 22 09:55:35 mailman3test systemd[1]: mailman3.service: Failed with result 'timeout'. Anybody knows whats going on and what i am doing wrong?

3 years, 9 months

[MM3-users] Re: Issues with migrating from Mailman2 to Mailman 3

by Mark Sapiro

On 9/22/19 10:29 AM, Uwe Grasshoff wrote: > Hello all, > > I'm currently trying to convert a Debian based mailman2 installation to > a docker based mailman3 installation. > I successfully running the mailman-web and mailman-core containers > together with the database container but I'm struggling with the import > of the old mailing lists. In the core container I'm running this two > commands for every mailing list: > > mailman create mailman(a)example.com > mailman import21 mailman(a)example.com > /oldmailman/lists/mailman/config.pck > > Then I'm switching over to the mailman-web container and running this > two commands: > > python3.6 manage.py hyperkitty_import -l mailman(a)example.com > /oldmailman/archives/private/mailman.mbox/mailman.mbox > python3.6 manage.py update_index_one_list mailman(a)example.com > > I'm getting no errors or something else which could indicate a problem. > After that I'm looking into the web interface > http://example.com/postorius/lists/ > There I can only see the public mailing list and the private ones are > not shown there (as expected). Everything up to this point is expected behavior. > When I then try to login with the List > Manager credentials of the lists (from mailman2) I can't login in. So I > thought maybe I have to "register" myself again to than get access to > the list management. > So I tried that but when I filled out the form and click "Register" I'm > presented with an error page which titles "Serverfehler" (Server error > in german) and the message "An error occurred while processing your > request." I'm not sure about the error, but the import21 process registered you so what you need to do is go to the Login page, click "Forgot Password?" and then request a password reset. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: One bounce, 5 bounce counts

by Mark Sapiro

On 1/13/22 6:17 AM, Henrik Rasmussen wrote: > > My problem, though, is that some subscribers may be disabled even they are able to receive mails (confirmed with sendmail -bv), and I have been looking at one subscriber in particular. > > > 1. Can there be (i'm not saying there are, maybe it's my lack of knowledge) somthing regarding Mailman? > 2. And what would the appropeiate per list bounce settings, if not default? Referring to the example below, it seems that your Postfix delivers successfully to the first hop MX of the recipient, but the mail bounces further downstream resulting in an emailed bounce. One thing you can do to help mitigate scoring of bounces of emails due to spam filtering is to set ``` [mta] verp_probes: yes ``` This will cause Mailman to not disable delivery when bounce score reaches threshold, but rather send a probe which hopefully won't be detected as spam and only disable delivery if the probe bounces. > Actual example: > > > * Mailman sent seemly 6 mails to a member on January 6th. > * I see one bouce message D1426CE22A in Postfix log that was delivered back to Mailman > * I see that Mailman is counting the bounce score from 1 to 5, one at the time, but that was day after receiving the bounce, and no other mails have been sent to the user on the 7th nor received as bounce on the 7th. I suspect that it must have been in the Postfix queue until then, but I wonder why that could be - but could be. > * The bounce would be in the Postfix queue until sent to Mailman and thus removed from the Postfix queue. I suspect the issue is something like a connection problem from the recipient MX to a relay MX that is not being reported as a bounce until the retry interval has expired. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Configuration Question

by Abhilash Raj

On Fri, Aug 24, 2018, at 5:53 AM, Ryan McClung wrote: > Greetings, > > Sorry, I wasn't entirely clear. That message was written pretty > quickly and without much thought to explaining my situation.> > A while back I opened a ticket talking about how mailing lists keep > disappearing when running:> > mailman lists > > In a directory that wasn't the same as the config/db original > location. What I was wondering is if there was a way to make it so > that the location remains static regardless of how you invoke the > mailman command. This[1] should help you understand how Mailman manages its configuration and how can you make a single config file that is picked up my Mailman everytime. [1]: https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.htm… > > Ryan > > On Thu, Aug 23, 2018 at 8:46 PM Abhilash Raj > <maxking(a)asynchronous.in> wrote:>> >> >> On Thu, Aug 23, 2018, at 12:08 PM, Ryan McClung wrote: >> > Greetings, >> > >> > Is there a simple way to force the mailman3 install to run off >> > of a>> > specified config/specified db without having to enter it manually >> > each>> > time? >> > >> > I just want any administrator to be able to enter mailman without >> > wrecking>> > the config/db. >> >> What do you mean by "enter Mailman"? >> >> -- >> thanks, >> Abhilash Raj (maxking) >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> > > -- > > > Ryan McClung > Systems Administrator @ Afilias Canada > A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8[1] > W. www.afilias.info > T. +1.416.646.3304 x4186 > -- thanks, Abhilash Raj (maxking) Links: 1. https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…

7 years, 9 months

[MM3-users] Re: Mixing Mailman 3 with AWS SES

by Abhilash Raj

Hi Ralph, > On Mar 17, 2021, at 5:14 PM, Ralph Weber <roweber(a)ieee.org> wrote: > > I am moving the website www.t10.org from a private/corporate VM to AWS EC2s. > > For many years, t10.org has had very happy results with using Mailman 2 for its email reflector, and I have no real concerns about moving to Mailman 3. My bugbear is the fact that I need the following mixed bag of incoming email addresses to work in concert with each other to receive and handle emails. > >> t10(a)t10.org (Primary Mailman Reflector) >> chair(a)t10.org (Mailman Reflector to direct messages to the T10 chair and his designates) > * docs(a)t10.org (document posting mechanics - serviced by a small mountain of home-grown code code) > * bbs(a)t10.org (other publicly accessible services - serviced by code that recalls the days when everything as done on a Bulletin Board System, BBS) I am not entirely sure what a “Reflector” really is. > > My best guess is that the AWS Simple Email Service (SES) needs to sit in front of both Mailman and the home-grown code, to properly direct the incoming emails to the right places. The big worry is as follows... > > All available evidence read to date suggests that the default AWS installation of Mailman 3 assumes that Mailman 3 is the *only* receiver of emails in the configuration. If true, then putting SES in front of Mailman could be a Herculean challenge. Which specific AWS installation guide are you referring to? Mailman doesn’t really care about being the only receiver of emails. Mailman can receive emails via LMTP or HTTP protocols. If you can do either of those two, you should be good. I don’t remember offhand someone sharing SES configs/setups for receiving emails, but maybe if someone did get that working, hopefully they’ll chime in. Sending out emails with SES is easy, you just need to setup the right SMTP server in Mailman’s config. -- thanks, Abhilash Raj (maxking)

5 years, 3 months

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Mark Sapiro

On 7/9/22 6:35 AM, Andy Smith wrote: > > I'm concerned that Mailman seems to have scored my address as > bouncing even though it isn't, merely because it appears inside a > message that was rejected. > > Is that expected? Is there any way to avoid it? No, it's not and it should not ever happen. > I see that Mailman has a bunch of heuristics to parse bounce > messages. In this case though, there shouldn't have been a bounce > message received to users-bounces@, as this was an SMTP-time > rejection. Mailman seems to have parsed addresses out of the actual > mail it was sending, rather than only scoring the subscriber address > it was trying to send a list posting to. Yes, flufl.bounce is used to parse messages delivered to the -bounces. There are a lot of hueristic recognizers, but RFC 3464 compliant DSNs should be recognized by the DSN detector which is tried first and which gets the failed address from the report. See https://gitlab.com/warsaw/flufl.bounce/-/blob/master/flufl/bounce/_scan.py#… However, SMTP failures do not result in DSNs to the -bounces address. If recipients are refused at SMTP time, this should result in a message in Mailman's smtp.log of the form ``` <message_id> recipients refused: <mta's message> ``` and we create a fake DSN (see https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoi…) to be processed as a bounce for the failed recipient. In this case, no parsing of the failed message should occur. I can't explain what happened in your case. It seems that somehow the original post was delivered to the -bounces address and parsed by one of the heuristic recognizers (probably simplematch), but how could that happen? -- 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: Disabled by bounce

by tlhackque

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

3 years, 4 months

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

by Odhiambo Washington

On Sat, Nov 25, 2023 at 5:35 PM Jered Floyd <jered(a)convivian.com> wrote: > > OK -- my turn to ask a question... > > I created a new domain and lists in my (functioning) Mailman 3 install. > > Messages to these new lists are successfully delivered via LMTP to Mailman > and then disappear. They are in the shunt queue, with a source queue of > "in". There are no exceptions logged in my mailman.log. > > An example from a qfile: > { '_parsemsg': False, > 'envsender': 'noreply(a)[domain].com', > 'lang': 'en', > 'listid': '[listname].[domain].com', > 'original_size': 2654, > 'received_time': datetime.datetime(2023, 11, 25, 14, 0, 6, 968185), > 'rule_hits': [], > 'rule_misses': [], > 'to_list': True, > 'version': 3, > 'whichq': 'in'} > Unshunting the message has no effect, and no logs are generated. > > Any suggestions? I recently migrated an MM3 ML to my functional server. Don't ask about the details now :-) From the Django Admin interface, I created the site and a mail domain. From Postorious I created the domain and selected the webhost. I then created the ML by giving the name and selecting the mailhost. The only special thing I had to do was to configure my MTA to know that the new domain name is to be treated as local. I use Exim as the MTA. And yes, I had to restart the MTA after making the change. I don't think Postfix requires a restart like Exim does. TBH, I think your problem would be something with the MTA whose logs you haven't mentioned you checked. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 6 months

[MM3-users] Re: How can we solve ZoneInfoNotFoundError

by Washington Odhiambo

On Tue, Apr 14, 2026 at 11:39 AM Markus Grandpré < markus.grandpre(a)uni-konstanz.de> wrote: > Dear list members > > A user of our Mailman system reports having trouble logging in to access > a mailing list archive. In the error messages that the Mailman system > sends via email, we find: > > > ... > Internal Server Error: /mailman3/accounts/login/ > > ZoneInfoNotFoundError at /accounts/login/ > 'No time zone found with key US/Eastern' > > Request Method: POST > Request URL: https://mailman.uni-konstanz.de/mailman3/accounts/login/ > Django Version: 4.2.28 > Python Executable: /usr/bin/uwsgi-core > Python Version: 3.13.5 > ... > Exception Type: ZoneInfoNotFoundError at /accounts/login/ > Exception Value: 'No time zone found with key US/Eastern' > Raised during: allauth.account.views.LoginView > Request information: > USER: **** > > GET: No GET data > > POST: > csrfmiddlewaretoken = > 'E6IT1iObdZYMyGKUgAHSxJ6LCzSZPDOKZmgVCaN9Kaae3s5gJy75Dwh8ptWjzcdI' > login = '****' > password = '****' > next = '/mailman3/hyperkitty/list/basex-talk(a)mailman.uni-konstanz.de/' > > FILES: No FILES data > > COOKIES: > csrftoken = '********************' > ... > > (full error stack is attached to this email) > > > Is there a server-side solution available for our GNU Mailman system > 3.3.10 (Tom Sawyer), which runs on Debian GNU/Linux 13 (trixie)? > Out of curiosity, is that time zone setting inside your config files? And what does the logs say if you check them? Again, seeing as you are using Python 3.13 and this - 'Python Executable: /usr/bin/uwsgi-core' (because I do not expect to see /usr/bin in $PATH when using the virtualenv install) - are you running in a virtualenv? Check your MM3 logs for a clue. Others will have a way to nail the culprit. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 months

[MM3-users] Re: disabling social login

by Dmitry Makovey

On 11/06/2017 10:59 AM, Abhilash Raj wrote: > On Mon, Nov 6, 2017, at 10:26 AM, Simon Hanna wrote: >> On 11/06/2017 07:22 PM, Dmitry Makovey wrote: >>> Hi, I'm trying to disable social login and running into troubles >>> stepping on it's remnants all over the place. What's the proper sequence >>> for disabling social login in MM3 install? >> comment out 'allauth.socialaccount' and all social providers in the >> INSTALLED_APPS in your settings.py > > This apparently doesn't work, Hyperkitty apparently depends on this to > do some stuff. I haven't dug up in there, but the migrations would break > if we remove this from INSTALLED_APPS. > > Instead, please let the 'allauth.socialaccount' be there, along with > 'allauth.account' and 'allauth' and everything else related to allauth > should be removed. > > It looks something like this: > > ```` > INSTALLED_APPS = ( > 'hyperkitty', > 'postorius', > 'django_mailman3', > # Uncomment the next line to enable the admin: > 'django.contrib.admin', > # Uncomment the next line to enable admin documentation: > # 'django.contrib.admindocs', > 'django.contrib.auth', > 'django.contrib.contenttypes', > 'django.contrib.sessions', > 'django.contrib.sites', > 'django.contrib.messages', > 'django.contrib.staticfiles', > 'rest_framework', > 'django_gravatar', > 'paintstore', > 'compressor', > 'haystack', > 'django_extensions', > 'django_q', > 'allauth', > 'allauth.account', > 'allauth.socialaccount', > ) > > ``` > > I tested this works, see [1]. thanks! that worked indeed. > > > [1]: https://lists.araj.me/postorius/lists/ >> They shouldn't be enabled by default in the first place I guess, since >> pretty much all of them require further setup in order to work >> properly... >> >> How are you running MM3? >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- Sr System and DevOps Engineer SoM IRT

8 years, 7 months

[MM3-users] Re: migrate MM3 list from an old server to a new one

by IEM Network Operation Center (IOhannes m zmölnig)

On 8/7/24 10:52, IEM Network Operation Center (IOhannes m zmölnig) wrote: >> >> With the dump and other utilities from your database manager. Almost >> everything is in the database. There are some things in Mailman's var/ >> directory, but those can simply be moved. >> sorry for keeping you all busy, but: which "things in Mailman's var/" need to be copied over to the new host? in my old instance (from Debian packages) i find in /var/lib/mailman3/: - ./archives: dirtree without files - ./cache: (afaict) currently active templates for mailinglist mails (hashed filenames) - i assume that these can safely be ignored and will be restored from the db? - ./data: empty - ./lists: empty directories named after each list (i think these are used by the MTA to determine whether it should hand over a mail to the mm3-ltmp) - ./locks: plenty of lock-files, most of them rather stale (as in: 3 years old) - ./messages: a couple of old messages (i think all of them have been held for approval) - ./queue: dirtree without files - ./templates: more templates for the existing mailinglists, though they don't seem to be used (are these the fallbacks when I remove a template via the webinterface?) - ./web/static/*: seem to be copied over from various Debian packages (dependencies of mm3), with minor differences in icons and jquery (I assume these files get copied over when the mm3 instance is created, and do not get updated when the corresponding Debian packages get updated) - ./web/static/CACHE - can these be ignored? - ./web/fulltext_index: are these files regenerated when running "update_index"? so i think the only stuff that needs to get recreated from mailman's var is the ./lists directory. is this correct? mgfdasr IOhannes ___________________________________________ Die Inhaltsfilterung von Mailman hat die folgenden MIME-Teile aus dieser Nachricht entfernt. Content-Type: application/pgp-keys Name: OpenPGP_0xB65019C47F7A36F8.asc

1 year, 10 months

[MM3-users] Re: missing graphics in Postorius

by Mark Sapiro

On 12/7/21 4:01 PM, David Newman wrote: > On 12/7/21 11:17 AM, Mark Sapiro wrote: >> Add '127.0.0.1' to ALLOWED_HOSTS anyway. > > Done, thanks. > > Given that DNS works fine on this host, with localhost and 127.0.0.1 > resolving backward and forward, this seems like a bug. Shouldn't the > resolver be able to recognize localhost without hard-coding an address? It's probably a bug, but if so, it's a Django bug and not anything Mailman can do anything about. ... >> Assuming you have >> ``` >> STATIC_ROOT = '/opt/mailman/web/static' >> ``` >> in your /etc/mailman3/settings.py file, you may need to create that >> directory if it doesn't exist. You shouldn't need to manually create >> the /opt/mailman/web/static/postorius directory if the >> /opt/mailman/web/static directory exists and is writable/searchable by >> the Mailman user. > > Yes, that was it. Thanks. > > Previously you'd pointed out what you considered an error in the venv > docs, with the workaround to manually create the /opt/mailman/web > directory [1]. I think the same issue applies here, and also that > /opt/mailman/web and subdirectories need to be owned by the mailman user. I don't recall what I said about that but near the end of the Initial Configuration section at https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… it says ``` Make sure that the logging path is created. You can run mkdir -p /opt/mailman/web/logs to create the path. ``` I added ``` Also make sure the ``STATIC_ROOT`` directory is created. ``` after that. As far as things being owned by the mailman user, early in the doc at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup there is a note that says ``` Make sure that you are running commands as mailman user from here forth. Setup Mailman user. ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: mailman 2.1 or 3.0 (or another MLM)

by Mark Sapiro

On 1/26/22 11:05, nate wrote: > > Can I suggest the messaging to new users be improved to communicate > this situation as it is not clear. > > The automated message I got said this was the reason my message was > held: The message comes from a moderated member. > > Which makes sense if I REALLY think about it(I was a moderated member > at first), but then the next question is why was I moderated. Your > explanation makes sense. > > It would be nice if it had more info along the lines of what you > said, or even better adjust the messaging for the "Welcome" email > to indicate your first message(s) will be held for moderation(I checked > both emails I got back from the list just now to verify this info is > not there). I was confused for a while(again 21 year veteran of mailman) > thinking I sent my message using the wrong email address, after confirming > I sent with the right one I just decided to wait to see what would > happen. The situation is no different in Mailman 2.1. The issue is that what may be appropriate in the held message to the user or the list welcome message depends on list configuration and the policies of the particular list. Thus, we can't really modify the default message templates in this way. It requires making list specific templates or possibly domain or site specific templates where all the lists in a domain or site have the same policies. This can be done by list, domain or site admins, but doing or suggesting this on a site like, e.g., mail.python.org which has 232 Mailman 2.1 lists with a total of 243 unique owners and 182 Mailman 3 lists with a total of 212 unique owners is a daunting prospect. -- 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: hyperkitty_import Unicode Errors - Drop all Archives and Start Over?

by Dave Hall

Hello. This is a follow-on to my earlier post about hyperkitty_import Unicode Errors. I am progressing through a migration from Mailman 3.2.1 to Mailman 3.3.3 based on Debian packages. Since I have 3.2.1 instances running in production, I've created new databases for the 3.3.3 instances. I copied the Mailman3 DB to the new database and allowed the install process to upgrade the DB Schema. For the Mailman3-Web DB, due to the codepage issues, I did not initially copy the content. My thought was that I would try to re-import my v2.1 archives into a new database that has the correct Unicode settings. However, this places me at square one with respect to users, permissions, etc. What I would really like to do is to drop all of the previous archives and start fresh. Looking at the table list for the database, It would appear that all of the archive content is stored in the tables with names that start with 'hyperkitty_' I'm wondering if I could just wipe the content of these tables, or exclude them from a backup, and then start fresh. Alternatively, if I restore the exiting archives to the new database with the correct unicode settings, could I re-run the hyperkitty-import tool and get it to pick up all of the messages it skipped due to the unicode problem? Please advise. Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu On Sat, May 6, 2023 at 2:27 PM Dave Hall <kdhall(a)binghamton.edu> wrote: > Hello. > > When running hyperkitty_import to import Mailman 2.1 archives, I > frequently get errors like > > django.db.utils.OperationalError: (1366, "Incorrect string value: > '\\xE1\\x90\\xA7\\x0A\\x0AO...' for column > `mailman3web`.`hyperkitty_email`.`content` at row 1") > > Is there a known cause for this? Is it fixed in some release more recent > than 0+20180916? > > Thanks. > > -Dave > > -- > Dave Hall > Binghamton University > kdhall(a)binghamton.edu > >

3 years, 1 month

[MM3-users] Re: Digests not working correctly

by Mark Sapiro

On 6/4/23 18:35, Joel Lord wrote: > > The periodic digests do seem to be coming out. I also now have > confirmation that the one message in this morning's digest that was from > May 4th was also included in the last digest back on May 4th, so it > seems that the one message was left behind in the digest queue when the > periodic digest was sent. I don't see how that can happen. The process that sends a digest renames the var/lists/<list-id>/digest.mmdf mailbox file in which the messages are accumulated to var/lists/<list-id>/digest.<volume>.<issue>.mmdf, where <volume> and <issue> are the volume and issue numbers of that digest, and then queues a message in the `digest` queue to tell the digest runner to create the digest from the messages in that mbox and send it. Thus, it leaves no var/lists/<list-id>/digest.mmdf mailbox file behind and that is created anew when the next post arrives. Further, if there is a non-empty digest.mmdf file, its messages should be sent no later than the next 11 PM `cron digests`. > There was one earlier message to the list > back on May 4th, before the one that got duplicated, but I can't tell if > that triggered a size-based digest to be sent: the logs aren't clear > enough on that detail for me to tell. OK > Just to inform things: > > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman > django-mailman3==1.3.9 > mailman==3.3.8 > mailman-hyperkitty==1.2.1 > mailman-web==0.0.6 > mailmanclient==3.3.5 > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper > mailman-hyperkitty==1.2.1 Actually, it's HyperKitty, not hyperkitty, but I assume HyperKitty is up to date as are the others. > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post > postorius==1.3.8 > > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: How to build docs and how to contribute documentation

by mailman26＠xse.com

On 5/1/26 09:18, Stephen J. Turnbull wrote: > Craig Leres via Mailman-users writes: > > > I got a version of this to work but was not satisfied because it > > required hacking either mailman or sendmail config to cleanup the > > domain in the recipient address. > > You're talking about the ".private" extension on the domain? I think > you can just put that in the "alternate domain" attribute. Postfix > sometimes requires a similar dummy domain, so it's documented in the > Postfix section of mta.rst. That works great, thanks! > > Next, how are code and documentation contributions submitted for > > consideration? I'm a lot more familiar with github than gitlab and > > know how to fork but it didn't look like I would be able to submit > > a pull request. > > We ask that you write a NEWS item (docs/NEWS.rst), and include that in > the MR. Add "(:mr:42)" at the end, for value of "42" = the merge > request number assigned by GitLab. Just a one-liner saying docs for > Sendmail configuration were added is fine. I don't quite understand this step. My mr is 1496 and the "docs" pipeline seems happy. Do I add a commit to the mr I just created and add something to src/mailman/docs/NEWS.rst? I would guess under "3.3.11" in the "Other" section? > Once you've forked from gitlab.com/mailman/mailman, in your own fork > you find the "merge requests" item in the sidebar. That should take > you to your merge requests. I gather from your question you have none > yet, so you should see a empty page with a "create merge request" > button in the middle. (As with github) gitlab noticed when I pushed a commit to my fork and gave me a button to create the merge request. Craig

1 month, 1 week

[MM3-users] Additional info/tags on Members

by mkoerber＠akamai.com

I am managing a few mailing lists which are hosted on a mailman3 instance. None of these are allowing self-subscription, but I have a need to be able to search the membership by association, ie whether they belong to any of a number of named groups Currently there does not seem to be any means for attaching a comment field, tag or such to group members, which would allow keeping such metadata and using it for searching members. (and no, the email addresses of members of one or more groups may not be similar, hence searching by @domain or such will not work) Also, the group-association info should *not* be exposed externally (ie to the member in question or any others), which makes adding the tag/group info as part of the full name impossible. Is there any way to do this in mailman3? If not can this be counted as a feature request: - in mailman3 itself: + add a facility that allows storing additional info to each member , either as a (largish) comment field or an array of tags ++ if tags, it should support managing thousands of them (but each member is likely to only need a few associated) + if tags are used, each list should have its own set of tags (though a means to designate a list to participate in a global tag collection might be useful). - in postorious: + allow modifying the comment field, or adding/removing/modifying one or more tags to each list-member + allow searching a group's membership by tags (or substring in the comment field), ++ following which mass-operations (deletion, setting moderation flags etc) should be possible based on individual selection of the found fields mailman3 really only would need to support storing the additional data for each member, as (at least in my use case) that data is not actually required for mail forwarding. However, it seems to be desirable to store the info in the mailman3 database rather than an external system (to reduce chances that these might get out of sync).

3 months, 1 week

[MM3-users] Starting from scratch

by Benjamin Ragheb

Hello! Over the weekend, I attempted to install the Mailman Suite on Debian Stretch. My goal is to set up some low volume mailing lists for family and friends. I ran into some problems, and I'm hoping to get some feedback on my overall approach before I make my second attempt. :-) I figured the safest thing to do would be to use pip to install the latest released version of all the components (core, postorius, hyperkitty, etc.). I copied the files from the [mailman-suite repository][1] to set up a Django project and got it mostly working with Apache and mod_wsgi. [1]: https://gitlab.com/mailman/mailman-suite Unfortunately, I was unable to log into the web interface; when I tried, I got a server error like this: > Exception Type: TypeError at /accounts/login/ > Exception Value: authenticate() takes exactly 0 arguments (3 given) Some research leads me to believe this is happening because authenticate() was changed in Django 1.10, and so I must be using a newer version of Django than the app expects. Given that I installed via Pip, I assumed the right version of Django would automatically be installed... I'm open to the possibility that I am misunderstanding how Pip works, or that postorius's and/or hyperkitty's dependency information is incorrect. The two alternatives I am weighing right now are: 1. Stay the course, and see if I can fix this by learning more about Python, Pip, Django and tinkering with the configuration. 2. Ride the bleeding edge, and install postorius and hyperkitty from git. (I'll probably stick with Mailman Core from Pip, since that seemed to work just fine.) Right now I'm leaning toward #2, because it means I'll be in a better position to patch things if I need to, and it seems like Mailman 3 is still rough enough that I will need to. Also, it looks like the master branches of both postorius and hyperkitty are now Python 3 compatible, which could save me from managing two different versions of Python. Which is the least crazy option? -- Ben

8 years, 2 months

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

by Willie Castillo

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

10 months, 3 weeks

[MM3-users] Re: Installing Mailman3 on Debian Bullseye

by Franklin Weng

Hi Steve, Thanks for your comments! Stephen J. Turnbull 於 2023/8/26 21:53 寫道: > Franklin Weng writes: > > > I had a blog article describing how I did it. > > > >https://blogs.slat.org/node/1012 > > Thank you for mentioning this. > > As far as I know, Debian packages use the system Python and the system > Django. Is that correct? Correct. > I have had trouble myself with [language.en] charset: ascii myself > when importing Mailman 2 lists into Mailman 3. This was an *ancient* > instance (Mailman 2 installed in 2009, 21.1.15). Save yourself pain > and set it to utf-8. I need to make sure before I make such a change > in a public release though. > > As far as I know [language.master] charset isn't relevant anymore as > all out message catalogs are UTF-8 now. IIRC I got some errors about handling characters encoding if I don't set up charset in language.master and language.en section. But the memory is vague and I don't want to go back retesting that... > In our current releases, the "mailman" command and the "mailman-web" > command are separate. mailman-web/manage.py and django-admin are > basically aliases for mailman-web. I think "mailman-web", not > "mailman" is what you mean in your last note. Note that "manage.py" > doesn't know anything about functions of the "mailman" command, since > it is derived from Django. So you might want to check that and > correct it. > > Steve Thanks! I've updated my blog post adding your comments there. Honestly I was totally confused by all these, and as I have said, the MM3/Django/Hyperkitty/... documents didn't help much. I struggled a lot to find out "manage.py" could do all the operations (like importing) I wanted. Franklin ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 9 months

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

by Mark Sapiro

On 1/26/24 02:44, Marco van Tol wrote: > Op 25 jan 2024, om 14:16 heeft Marco van Tol <mvantol(a)ripe.net> het volgende geschreven: >> >> Okay, so, I got a bit further, but something still gets stuck. >> >> Here’s what I did. >> Keep in mind I’m using containers that are built from some CI/CD pipeline, so I updated the pipeline to apply the patch attached to this email to `/usr/lib/python3.11/site-packages/xapian_backend.py`. >> >> Before I had 2 list servers with the “Term too long” issue, 1 got resolved by this, and the other did not. >> I opened a shell in the newly deployed container to confirm the patch was applied in it. >> >> The other attachment to this email is a copy/paste from the full error from `./manage.py rebuild_index`. >> >> Is there something else special in the email that makes it choke that evades the xapian patch? >> >> Thank you very much in advance! The message above with the attached "full error" never got to the list. What is the error report? > > I tried to change to ‘hash’, but the code in that bit of the function has not been tested enough. > > For example `hole = sha224(hole.encode('utf8')).hexdigest()` comes back with that the bytes object hole does not have an encode() method. > When I change it to `hole = sha224(hole).hexdigest()`, the following error is: That's only part of it. You need hole = sha224(hole).hexdigest().encode('utf8') > text = text[:match.start()] + hole + text[match.end():] > TypeError: can't concat str to bytes > > The ‘hash’ part of that function needs some debugging. Yes, presumably because no one sets `XAPIAN_LONG_TERM_METHOD=hash` in the environment. Do you have a reason for 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: Installing Mailman3 on Debian Bullseye

by Odhiambo Washington

On Wed, Aug 30, 2023 at 4:06 PM Andy Smith <andy(a)strugglers.net> wrote: > Hi Franklin, > > On Sat, Aug 26, 2023 at 04:59:04PM +0800, Franklin Weng wrote: > > I had a blog article describing how I did it. Maybe there were something > > you find it ridiculous, but they are all what I found important and may > not > > be shown in the current documents. > > > > https://blogs.slat.org/node/1012 > > Having been through this process with Debian 11 last year, in > addition to several of your discoveries, I found that the default > Whoosh full text indexer was just not usable. It is ridiculously > slow and memory-hungry, and used 6+ gigabytes of RAM and days of CPU > time to try to index some of my Mailman 2 mboxes. > > I should think almost everyone will want to switch to Xapian > instead. That is accomplished on Debian with: > > # apt install libxapian30 python3-xapian python3-xapian-haystack > > and then in mailman-web.py: > > HAYSTACK_CONNECTIONS = { > 'default': { > 'ENGINE': 'xapian_backend.XapianEngine', > 'PATH': '/var/lib/mailman3/web/fulltext_xapian_index', > }, > } > > As far as I understand Xapian is not the default because although > Xapian has an open source license, it is one that's not compatible > with Mailman's GPL3 license. > > At the time I installed, Debian 12 had not yet been released, and I > won't upgrade that host until necessary, but I personally would not > do a new install on Debian 11 so I would want to resolve the > problems you had with Mailman 3 on Debian 12. > > Cheers, > Andy > And some unlucky admins might want to look at https://gitlab.com/mailman/hyperkitty/-/issues/408 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 9 months

[MM3-users] Re: DMARC Munging

by Allan Hansen

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

6 years, 4 months

[MM3-users] Re: Hyperkitty import from mailman2

by Sten Aus

Oh my god. :) That's it! There are no latest messages and front page shows only last month "activity". Thank you! I did not thought that I should check some older posts. :D So, import is working just fine, I guess! ;) But how did you manage to import all the lists and members from Mailman2 to Mailman3? As I understand Mailman3 does not "support" (by manual) import right now? On 24/12/2017 00:11, Marvin Gülker wrote: > Just a suggestion -- if your list didn't have any e-mails in the last > month, the front page will show it as inactive. Dig into the archive > links on the left side to actually see your e-mails. I've been bitten by > that behavior as well. The front page simply doesn't show e-mails older > than a month. > > Look here: https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… > > No emails on the front page. Now go here: > https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… > > Well there. > > Greetings > Marvin > > Am 23. December 2017 um 01:05 Uhr +0200 schrieb Sten Aus <sten.aus(a)eenet.ee>: >> Hi >> >> Thank you Mark and Simon for your input! >> >> I can see imported list from Hyperkitty GUI, but it's inactive. >> I can confirm that I can see those emails from command line (python shell >> shows Email Objects). >> >> Import shows everything is OK: >> >> # python2 manage.py hyperkitty_import --settings settings --ignore-mtime -v >> 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox >> Only emails after 2010-01-01 00:00:00+02:00 will be imported >> Importing from mbox file /tmp/test.mbox to test(a)list.domain.com >> /--some 22 emails being imported here --/ >> 22 emails read >> 22 email added to the database >> 22 emails are stored into the database >> Computing thread structure >> Synchronizing properties with Mailman >> Warming up cache >> The full-text search index will be updated every minute. Run the 'manage.py >> runjob update_index' command to update it now. >> >> # python2 manage.py update_index --settings settings >> Indexing 50 emails >> NB! Only 6 of them are archived from new list (which has been created from >> Apache). I have imported 2 times 22 emails from /tmp/test.mbox file (to >> different lists). >> >> >> I am using Apache2.4 with mod wsgi and Postorius and Hyperkitty are in the >> same django application. >> Also tested with running server directly and then connecting to a port 8000, >> but I guess it does not matter, because both of them are using Python >> script. >> >> I have not yet managed to set up cron tasks, as this is relatively new >> installation, but I have ran them manually. Also, I have done update_index >> (runjob update_index and manage.py update_index, both ways). >> >> >> SQLite database shows emails, for example there's a thread >> FMXQVFDRQVRMINVXI4DJB4SHYTJ3EPWP, but If I insert it to web URL I get Django >> error: No Thread matches the given query. >> >> >> As Postorius and Hyperkitty are in the same Django, they share sqlite >> database (mailman/web/database.db). Mailman has it's own database in >> mailman/var/data/mailman.db. >> >> >> Happy holidays >> Sten >> >> >> On 22/12/2017 21:09, Simon Hanna wrote: >>> On 12/22/2017 03:39 PM, Sten Aus wrote: >>>> Hi >>>> >>>> I have installed mailman3 - it looks very great! >>>> >>>> Now I wanted to try import from mailman2 mbox, so i did: >>>> >>>> python2 manage.py hyperkitty_import --settings settings >>>> --ignore-mtime -v 3 --since 2010-01-01 -l test(a)list.domain.com >>>> /tmp/test.mbox >>>> >>>> It shows that it have sucessfully imported all emails and I can see >>>> them from database (sqlite3), but I cannot see them from GUI >>>> (hyperkitty). Only thing I can see is this inactive "test" list. >>>> >>> How did you try to access them using Hyperkitty? Can you try doing that >>> while logged in as a django superuser? Could you try using a permalink >>> for a message? If you can access the files from the database you should >>> be able to construct the urls using the list name and the >>> message_id_hash of a message. You should try this using DEBUG=True in >>> the settings.py. The URL would be similar to http://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/… >>> >>> >>> Another option would be to check if you can access the data using a >>> python shell. >>> >>> `python manage.py shell` to open a python shell preconfigured for >>> Hyperkitty and then input the following two lines: >>> >>> from hyperkitty.models.email import Email >>> Email.objects.all() >>> >>> >>> This should print out all the messages that are stored in the database. >>> (You can limit them by appending "[10:]", or any other python slice) >>> >>> What do you see in the UI? Is it somewhat similar to >>> http://lists.mailman3.org/archives/list/mailman-users@mailman3.org ? >>> _______________________________________________ >>> Mailman-users mailing list >>> mailman-users(a)mailman3.org >>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

8 years, 5 months

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

by Morris Jones

On 11/26/20 10:09 PM, Mark Sapiro wrote: > 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. > Appreciated, but to no avail: (venv) mailman@mail:~/mailman-suite/mailman-suite_project$ python manage.py collectstatic You have requested to collect static files at the destination location as specified in your settings: /opt/mailman/mailman-suite/mailman-suite_project/static This will overwrite existing files! Are you sure you want to do this? Type 'yes' to continue, or 'no' to cancel: yes 0 static files copied to '/opt/mailman/mailman-suite/mailman-suite_project/static', 399 unmodified. (venv) mailman@mail:~/mailman-suite/mailman-suite_project$ python manage.py compress CommandError: Compressor is disabled. Set the COMPRESS_ENABLED setting or use --force to override. And then https://mailman.whiteoaks.com I'll spend time in the Firefox developer tools to see if I can figure out what's missing. A DuckDuckGo search suggested it could be a character encoding issue. The style sheets all come up reporting "0 rules" in the developer tools. I haven't tried any other browsers either. Best regards, Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

5 years, 6 months

[MM3-users] Re: help for new installation.

by Fabian A. Santiago

December 12, 2017 4:49 PM, claudio.jofre(a)yandex.com wrote: > Hi: thanks for your help. > > I find the docker proposal interesting. > I'm trying to follow it, according to the documentation they sent. > I only have two doubts left until now. > First: > where I find the file docker-compose.yaml, I could not find it anywhere. (Install the docker and > docker-compose using yum and using the epel repositories. > second: > How do I access the mailman configuration files inside the docker? > Is there any way to mount it? as a unit, to make the modifications? > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org You shouldn't have to modify the container files at all. the docker-compose.yaml file is where you specify the environment variables or config options needing to be passed. you can also pass addt'l configs to mailman: /opt/mailman/core/mailman-extra.cfg : This is the configuration for Mailman Core and anything that you add here will be added to Core's configuration. You need to restart your mailman-core container for the changes in this file to take effect. /opt/mailman/web/settings_local.py : This is the Django configuration that is imported by the existing configuration provided by the mailman-web container. To change or override any settings in Django, you need to edit this file. read the docs for the docker. they're pretty straight forward. there's only a very small set of required parameters to get it up and running on a basic level. **Tip: you need to make sure mailman_core is at version 3.1+ in order for the postfix aliases to be written correctly, if that's your mail server of choice. I believe maxking has addressed this by creating docker containers of the latest git committed versions in addition to the stable versions. before that i had to manually update my core container to get the fixes from git. good luck. read the docs. -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

8 years, 6 months

[MM3-users] Re: Custom Archiver

by Mark Sapiro

On 4/1/23 16:33, Peter Knowles wrote: > Mark, > > The whole reason I'm developing my own "frontend" for both "list management" and "archive" access is because Python isn't really the language I speak... I'm a PHP guy, and so I'm working to build with the language I know and love, while utilizing Mailman for what it does best... In addition to implementing the frontend the way I want it (expose/hide feature that are useful/unuseful to our users), I want to fully customize the visual appearance to represent the SaaS offering properly. This is exactly the reason why Mailman core was decoupled from archiving and the web UI. HyperKitty and Postorius were developed because we knew that almost no one would use Mailman core without archiving and a web management UI, but we always hoped that others might develop and contribute other web based archiving and management interfaces. Brian Carpenter of EMWD who tragically died of COVID did exactly that with his Affinity and Empathy PHP applications that interface with Mailman core via the REST API. EMWD hosts lists that use those interfaces, and had Brian not died, some version of those might be open sourced, but his initial thrust was to keep them proprietary for his business reasons. There is an early description of Brian's concept for Affinity at https://gitlab.com/mailman/affinity. > *** we're not try to hide that Mailman is in the equation, just how the overall interface is visually represented *** > > That all being said, on a slight segway... Aside from using the REST API, is it practical or possible to manipulate the database directly? That is, in doing so would it just work or are there extra moving parts when an API request is issued? It probably is possible, but I would definitely discourage it. The REST API should provide everything you need without your having to reimplement everything it does. -- 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: export/import list?

by Dave McGuire

On 8/21/23 00:31, Stephen J. Turnbull wrote: > > Is there a way to export a list from one Mailman 3 instance and > > import it into another, on a different machine? Ideally some way > > to capture its settings, members, members' settings, etc? > > All that is in an SQL database. Mailman still manages queues and > digests "on disk", so I would > 1. shut down Mailman completely (but not the RDBMS) > 2. copy the queues (in $var_dir/queue) and digests (in $var_dir/lists/ > *) over to the new installation > 3. dump the SQL database on the old host in SQL script format > 4. restore the SQL database on the new host > 5. restart Mailman > > This shouldn't take more than 15-20 minutes, faster if you're handy > with all the relevant utilities. The main forseeable issue is Mailman > traffic queuing up on the old installation. Depending on your mail > routing this may not be a problem: > - same MTA, just point it at the new host and everything will go > through when Mailman starts) > - different MTA, before shutting down Mailman reroute Mailman traffic > to new MTA where it will queue until Mailan starts > > Of course if something is wonky somewhere, you could get an error in > dumping or restoring the database. Also if you're changing databases > eg from MySQL to Postgres you may need to edit the dump by hand. > Don't forget to set your MySQL family databases to handle Unicode > correctly (at least older versions would throw exceptions on 4-byte > UTF-8 such as emoji). 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. Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

2 years, 9 months

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

by Mark Sapiro

On 7/15/21 12:55 PM, Sarah H wrote: > > The log is mostly these three errors repeatedly with the same above wall of html between them, some of them end with (404) after the last html tag indicating url not found and browsing to them gives the same custom 404 page for postorius. The code is if result.status_code != 200: logger.error("HyperKitty failure on %s: %s (%s)", url, result.text, result.status_code) raise ValueError(result.text) > Jul 15 12:37:08 2021 (471314) HyperKitty failure on http://lists.client.org/hyperkitty/api/mailman/archive: So the above log entry should be followed by result.text and result.status_code. The next entry below is from the `raise ValueError(result.text)` What do you get from curl http://lists.client.org/hyperkitty/api/mailman/archive and what if you change the scheme in the base_url setting to https? > Jul 15 12:37:08 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: And this one below is is because of the above exception. > Jul 15 12:37:08 2021 (471314) Exception in the HyperKitty archiver: > > I was able to find (about 5000 lines up in the log for a single post attempt... it's a bit excessive to print the html response every error) this when I dug through instead of tailing the last 500 lines. > > [15/Jul/2021:12:37:06 -0700] "GET /3.1/addresses/sarah.h@email HTTP/1.1" 200 380 "-" "GNU Mailman REST client v3.3.2" > > and at the start of the block: > > [15/Jul/2021:12:37:03 -0700] "GET /3.1/lists/admin.lists.client.org/member/sarah.%40email HTTP/1.1" 200 516 "-" "GNU Mailman REST client v3.3.2" > Jul 15 12:37:05 2021 (471317) ACCEPT: <162637782380.3116.619498070458942231@sysname> These are from the Mailman REST API and are not relevant to your 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, 11 months

[MM3-users] Re: Mailman 3 Status Update Please?

by ddw David Wilson

Thanks to the three quality responses to my request for a status update. All respondents clearly know about which they speak, which is certainly more than I can say for myself. From the excellent quality and quantity of the recent messages going through this mailman-users group, it's easy to be excited about the wonderful, thriving development & implementation community. Wow! [Technical term] As a casual, very interested observer, it's nice to see this up-tick (IMO) in activity, suggesting great advances are imminent:-) in this software, originally started over a decade ago. In this environment of ever increasing rate of change with a corresponding increase in complexities, number of dependencies, etc, I continue be impressed how Barry et al can stay the course, moving slowly and steadily (hopefully) towards the objective of 'having everything in the box' that 'just works'. That may be a somewhat unrealistic goal for such a multi-faced program, configurable for the myriad of user requirements. My own goal is to implement and train others (once I learn how to do it myself) to use Mailman3 for various cottage and/or condo/HOA associations, each with their own lists of members, an executive board, (sub)committees, special interest groups, and so on with many common communication/data processing requirements. Your point regarding security of messaging is appreciated but until the average email incorporates something like PGP, then messages themselves will be insecure. Since I am not contemplating a banking system, I am not unduly concerned direct about fiscal consequences such as revealing credit card numbers and/or social insurance numbers.. Regarding financial contributions, until I have a regular revenue stream, anticipated to be priced out at approximately $25 per month per organization, given that we will be operating as a not-for-profit entity, I only spend/invest my own money only to specifically move towards that goal. I was referring to money in exchange for specific, targeted, measurable goals designed to get us going but can see how that would not be feasible with the vast scope of this immense project. Once up and running with a critical mass of users, we anticipate spending/returning about one third of revenue to various OSS software projects, of which Mailman3 is expected to figure prominently. Personally, when it comes to contributing, I like to have my funds tied or directed to specific, measurable, delivered goals such as frequently seen with crowdfunding applications, rather than simply contributing to an open pool of cash, not earmarked for something specific. Just me, perhaps, but tying the dollars to results makes me feel good, even if it's awkward for those who simply want to delve into the code to fix an irritating bug or work on the next inter-application interface, etc. As an example of identifying specific, identifiable goals to motivate donations, I helped start a charity poker run fund raiser for our local hospital, with all funds allocated to purchase specific items, including a digital mammography unit and now stretcher beds for the emergency room, with our four year total contribution approaching CDN$50,000. And all this money from a rural community numbering under 4,000 people. I gather that with the high quality of the talent pool contributing to this user group that volunteer programmer time is more important than money, recognizing that having more money is never a bad thing. I started this message, and plan to end it as well, with many thanks to the various respondents and expressed how impressed I am with the quality and knowledge apparent from both those asking and answering questions. The progress leads me to believe that in the foreseeable future, that this suite of programs will workable for me, with a little/lot of help from my friends:-). Keep up the great work. Your cheerleader, Dave Wilson On 17-07-23 09:53 PM, Stephen J. Turnbull wrote: > Adding a slightly different perspective to Abhilash's and Barry's. > > ddw David Wilson writes: > > > From my perspective of being an senior (ie overaged) person > > desirous of implementing fully-featured, capable, scalable, > > reliable, secure > > I'm not sure if "secure" is a real requirement, a nice-to-have, or > intended as a compliment to Mailman, but "secure" is not something we > can claim. Mail is inherently a security problem, because there is no > universal way to authenticate senders. It's possible under certain > conditions to configure a system to be secure in the sense of allowing > only authentic senders, but even when possible it is not easy. Ask > John Podesta (for a well-known example) or Matt Tait (aka Twitter's > @pwnallthethings, a security expert who has publically admitted that > he's come "this close" to clicking on spear-phishing attachments). > > Mailman itself is a complex application with a very large attack > surface. If containerized, it will be rather difficult to exploit the > rest of the system, but Mailman itself contains a lot of private data > (email addresses and associated display names, which are frequently > real names), and in enterprise situations may have access to > enterprise databases "containing the whole store". > > > applications such as Mailman, I am convinced that I am thoroughly > > over my head. > > That's what we're here for! Of course we're volunteers, so our > availability is less than 99% reliable and time is limited. I don't > know of any consulting services providing Mailman 3 consulting yet, > but given the activity of this list I believe we'll see them soon. If > you have funding to offer and want to kickstart the process, you could > go to the vendors page on our website and talk to some of them. > > > From my limited perspective, it would seem to me that a 'nice to > > have' system would incorporate the following. > > > > 1. An open container standard configurable system install, compatible > > with different web & mail servers, DB utilities, etc; > > We have a container system which is configurable. However, IMHO > "standard" and "configurable/compatible" are incompatible goals. What > we can reasonably provide is a full system-in-a-box for people who > only want to configure Mailman itself (ie, add lists and users, and > configure their settings in the web interfaces). For people with > specific desiderata such as a particular mail transport agent or web > server different from those provided by our "Mailman-3-in-a-box", > they're going to need somewhat advanced sysadmin skills for the > forseeable future because the configuration requirements of web > services and mail services must be coordinated, and have subtle, > implementation-dependent interactions. > > We hope that the vendors referred to above (including mail hosts, mail > consultants, and system management framework vendors like cPanel) will > soon start providing more "Mailman 3 in a box" services (both software > distributions and as VMs in cloud services), as well as consulting > services for those with specific needs not served by existing > containerized versions. > > > 2. Python 3 version Django utilities for archiving and mail list name > > management; > > In progress. > > > 3. A design/plan from an inside expert perspective stating costs, time > > and resources to implement the plan, incorporating crowdfunding to > > pay for project. > > We don't have spare cycles at the moment. None of us actively consult > for money on Mailman, which means neither direct engineering > capability nor management capability are available. I'm considering > this, but since I'm currently a life-long academic with a full-time > job for the next few years, I'm not in a big hurry, and would need to > acquire skills/partners for the aspects I've no experience in. :-) (I > guess that's :-( from your perspective.) With a two-year timeline, if > I decide to do it, likely I'd actually open for business in about > 1.5-2 years (based on seasonal cycles in free time). I don't know > offhand of anyone else even thinking about it. > > This could change at any time with entry of new developers, of course, > but it's only fair to warn you that this is the current status. > > > 4. As a backup incentive to the crowdfunding plan might be the offer of > > an expert to set up a system for each significant amount donated, > > say US$1,000, such as might be accomplished by an SSL session on the > > target computer/server after the user has specified all necessary > > detail as required in a template. > > We do have ways to donate via our relationship with the FSF, but the > same issues described above (no reliable gobs of available time for > project oversight or actual development) apply. > > > I am sure that the program author and other major contributors could > > greatly enhance this list. > > > > In summary, I guess what I am requesting is an overview forecast by half > > year period and out for the next two years? > > For 6 and 12 months out, Abhilash's summary list, and Barry's, all are > goals I support. We should also have a plug-in implementating the ARC > protocol which improves authentication capabilities by allowing a > list's subscribers (more precisely, their mail hosts) to extend > transitive trust to senders that the list has authenticated. Although > providing such authentication services *in Mailman* is suboptimal and > sometimes impossible, we can provide containerized Mailman with that > service. > > Steve > >

8 years, 10 months

[MM3-users] Re: Sendgrid experiences (now Office 365)

by Andrew Hodgson

Hi. Just letting you know that over the weekend I moved from Sendgrid to our Office365 instance similar to what Stephen Daniel did with his Google instance. Some notes: * Instead of using authenticated relay I had to create a connecter which allowed relaying from the static IP of the instance. Option 3 in this article is what I did: How to set up a multifunction device or application to send email using Microsoft 365 or Office 365 | Microsoft Learn<https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-…> * Our list domain is a subdomain of the main domain in Office365. To get this working I had to add lists.domain.com to Office365 and verify the domain DNS records as well as set up DKIM/SPF. I then had to set the domain up as a relay domain and create an outbound connecter for email going to that domain to relay through the Mailman server in order for internal users on our Office365 instance to be able to email the lists. * This means I can now route list traffic through Office365 as an antispam measure but won’t be doing this as it doesn’t give me recipient validation. * All mailman specific headers are preserved and bounce processing now works fine. * Not sure how many emails I can relay through this way but delivery is working fine so far. Thanks. Andrew. From: Stephen Daniel <swd(a)pobox.com> Sent: Thursday, May 11, 2023 3:20 PM To: Andrew Hodgson <andrew(a)hodgson.io> Cc: Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp>; mailman-users(a)mailman3.org Subject: Re: [MM3-users] Re: Sendgrid experiences Also, once I got things running I added some stuff to my DNS records that appears to help with delivery: MYDOMAIN.org TXT 10 minutes "v=spf1 include:_spf.google.com<http://spf.google.com> ~all" On Thu, May 11, 2023 at 10:16 AM Andrew Hodgson <andrew(a)hodgson.io<mailto:andrew@hodgson.io>> wrote: Thanks for this. Another option I am thinking of is buying a cheap Linode or other host which isn’t on as many blocklists as Hetzner for outbound mail relay purposes. Hetzner provide a good cheap VPS but their Ips are on a lot of blacklists. Andrew. From: Stephen Daniel <swd(a)pobox.com<mailto:swd@pobox.com>> Sent: Thursday, May 11, 2023 3:14 PM To: Andrew Hodgson <andrew(a)hodgson.io<mailto:andrew@hodgson.io>> Cc: Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp<mailto:turnbull@sk.tsukuba.ac.jp>>; mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> Subject: Re: [MM3-users] Re: Sendgrid experiences I'll check my notes. I don't think I did anything with mailman. I am running postfix as my local MTA, and mailman talks to it as normal. In /etc/postfix/main.cf<http://main.cf> I have relayhost = smtp-relay.gmail.com:submission set. It took a bit of playing around to get it running, but its been rock solid since then. Domains have not been a problem. My google workspace account is MYDOMAIN.dev and all my email lists are MYDOMAIN.org, and everything appears to work just fine. I took a bunch of cryptic notes on how I got this working. As you would expect, the hard part is getting the authentication and permissions set up. I will send you a private message with a link to my notes. On Thu, May 11, 2023 at 10:00 AM Andrew Hodgson <andrew(a)hodgson.io<mailto:andrew@hodgson.io>> wrote: Hi. Thanks for the recommendation on the Google Workspace. How did you set this up in terms of the domain, since I don’t want to use Google Workspace as the main email provider for this domain. Also did you have to set anything special in Mailman? Thanks. Andrew. From: Stephen Daniel <swd(a)pobox.com<mailto:swd@pobox.com>> Sent: Thursday, May 11, 2023 2:57 PM To: Andrew Hodgson <andrew(a)hodgson.io<mailto:andrew@hodgson.io>> Cc: Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp<mailto:turnbull@sk.tsukuba.ac.jp>>; mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> Subject: Re: [MM3-users] Re: Sendgrid experiences I would definitely look for alternatives to SendGrid. I tried using them and had a very poor rate of people actually getting my emails, even when I temporarily upgraded to an expensive plan with a dedicated IP address. I'm currently hosting mailman in Google Cloud and relaying outbound mail through a Google Workspace account. It's working OK. The workspace account costs me $6/month for basically unlimited mail relay. On Thu, May 11, 2023 at 9:50 AM Andrew Hodgson <andrew(a)hodgson.io<mailto:andrew@hodgson.io>> wrote: Stephen J Turnbull wrote: >2023-05-10 03:49 に Andrew Hodgson wrote: >> Sendgrid is maintaining the Message-Id header which is good for >> archiving. It is re-writing the Return-Path header though which means >> that bounce handling in Mailman won't work, but I think all the >> services do this in some way so I am happy to live with that for the >> moment. >How does it rewrite the Return-Path? Returned mail is not something that such a service would be able to handle properly (although they can help with apparently returned spam). If mail is legitmately sent and returned as undeliverable, only the author or their agent will know how to handle it. So such >services should provide some way to find out about returned mail. An example: Return-Path: bounces+[Sendgrid GUID]-andrew=hodgson.io(a)em6096.lists.hodgsonfamily.org<mailto:hodgson.io@em6096.lists.hodgsonfamily.org> Sendgrid provide information about bounces but crucially that bounce isn't forwarded back to the original return-path sender (i.e, Mailman). A few people have pointed out they can provide list hosting at a cheaper cost than Sendgrid so I'm looking for alternatives again. Andrew. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to swd(a)pobox.com<mailto:swd@pobox.com>

3 years, 1 month

[MM3-users] Re: SECRET_KEY is not defined. Aborting.

by Abhilash Raj

On Tue, Jun 25, 2019, at 5:56 PM, Steven Jones wrote: > 8><--- > root@debian-mailman-001:/opt/mailman/docker-mailman# docker run > maxking/mailman-web:0.2 > SECRET_KEY is not defined. Aborting. > root@debian-mailman-001:/opt/mailman/docker-mailman# > 8><--- > > > I keep getting this, I have attempted to set a SECRET_KEY in > > > /opt/mailman/web/settings_local.py > > > and, > > > docker-compose.yaml Did you set it under mailman-web -> environment? That is where you need to set that value. > > > No joy, can you tell me how I set this variable? or where I get it > from? is it pre-generated somewhere? your documentation just does not > explain this that I can find, despite even a lot of time googling. It is not autogenerate, you neeed to generate a random value and put it there manually. > > > PS I have assumed the hyprekitty key is something I set myself, just > like a manual password sort of thing, again there is no explanation I > can find that explains how to do this properly either. > > > Can this documentation be improved please. > > > To get anywhere at all I finally found this, > > > https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/ > > > So I have core running OK I think, > > > ====== > > root@debian-mailman-001:/opt/mailman/docker-mailman# docker ps > CONTAINER ID IMAGE COMMAND > CREATED STATUS PORTS NAMES > 99f434ef3664 maxking/mailman-core:0.2 "docker-entrypoint.s…" > 2 hours ago Up About an hour 8001/tcp, 8024/tcp > mailman-core > 4c0e165d3a90 postgres:9.6-alpine "docker-entrypoint.s…" > 2 hours ago Up About an hour 5432/tcp > dockermailman_database_1 > root@debian-mailman-001:/opt/mailman/docker-mailman# > ====== > > > > > regards > > Steven > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 11 months

[MM3-users] IndexError in archiving queue

by Jacob Sievert

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. Error for reference: ``` During handling of the above exception (expected atom at a start of dot-atom-text but found '[a9920f8aa52d4a9093e21255f8fb2673-JFBVALKQOJXWILKCJQZFA7CJIFGVGU2QKJ6FGU2QKJCW2YLJNR6EK6DPKNWXI4A=(a)microsoft.com]>'), another exception occurred: File "/usr/local/mailman3/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) File "/usr/local/mailman3/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/mailman3/venv/lib/python3.9/site-packages/django/views/decorators/http.py", line 43, in inner return func(request, *args, **kwargs) File "/usr/local/mailman3/venv/lib/python3.9/site-packages/hyperkitty/views/mailman.py", line 117, in _decorator return func(request, *args, **kwargs) File "/usr/local/mailman3/venv/lib/python3.9/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view return view_func(*args, **kwargs) File "/usr/local/mailman3/venv/lib/python3.9/site-packages/hyperkitty/views/mailman.py", line 163, in archive add_to_list(mlist_fqdn, msg) File "/usr/local/mailman3/venv/lib/python3.9/site-packages/hyperkitty/lib/incoming.py", line 65, in add_to_list msg_id = get_message_id(message) File "/usr/local/mailman3/venv/lib/python3.9/site-packages/hyperkitty/lib/utils.py", line 60, in get_message_id msg_id = email.utils.unquote(re.sub(r'\s', '', message['Message-Id'])) File "/usr/lib/python3.9/email/message.py", line 391, in __getitem__ the values matching a header field name. File "/usr/lib/python3.9/email/message.py", line 471, in get for k, v in self._headers: File "/usr/lib/python3.9/email/policy.py", line 163, in header_fetch_parse return self.header_factory(name, value) File "/usr/lib/python3.9/email/headerregistry.py", line 601, in __call__ return self[name](name, value) File "/usr/lib/python3.9/email/headerregistry.py", line 196, in __new__ cls.parse(value, kwds) File "/usr/lib/python3.9/email/headerregistry.py", line 529, in parse kwds['parse_tree'] = parse_tree = cls.value_parser(value) File "/usr/lib/python3.9/email/_header_value_parser.py", line 2126, in parse_message_id token, value = get_msg_id(value) File "/usr/lib/python3.9/email/_header_value_parser.py", line 2073, in get_msg_id token, value = get_obs_local_part(value) File "/usr/lib/python3.9/email/_header_value_parser.py", line 1516, in get_obs_local_part if (obs_local_part[0].token_type == 'dot' or ``` regards Jacob

3 years, 3 months

[MM3-users] Re: Verification Failed Error

by brian＠emwd.com

Abhilash Raj wrote: > On Thu, Dec 20, 2018, at 10:25 AM, brian(a)emwd.com wrote: > > I am using Exim as the MTA. I followed the instructions located at: > > > > https://github.com/maxking/docker-mailman > > > > In particular the "Setting up your MTA" > > > > Are you saying I need to do something with Django because your > > documentation at github makes no reference to that? Where would I find > > the settings.py file? I used your image to install Mailman3. FYI I am > > referencing the "# To be added to Django's settings.py" instructions at > > > The documentation at Github does makes reference to it. It might not be > in the most visible manner, which I have opened an issue to fix[1] > > > To configure the mailman-web container to send emails, see these > > configuration settings. > The documentation also mentions about the Django configuration file, > settings_local.py (which is imported by settings.py at runtime). [3]. > > I have opened another issue to make that clear as well. [2] > > You can add all your Django related settings in `/opt/mailman/web/settings_local.py` > if you using the images and docker-compose.yaml file from the above mentioned > repo. > > > [1]: https://github.com/maxking/docker-mailman/issues/277 > [2]: https://github.com/maxking/docker-mailman/issues/278 > [3]: https://github.com/maxking/docker-mailman#configuration > > > > http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > I am glad this is going to result in getting more clearer documentation. I have added the following to /opt/mailman/web/settings_local.py EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = <username> EMAIL_HOST_PASSWORD = <password> The question I have is where does the username and password come from? Brian

7 years, 5 months

[MM3-users] Deactivate list without deleting it?

by Colin Watson

Hi, I'm experimenting with a port of Launchpad's mailing list infrastructure to Mailman 3. If Barry's reading, he may remember that this is no trivial task, so I'm very definitely not promising that it will be done any time soon. :-) However, for the most part it looks relatively tractable with the aid of the plugin improvements in Mailman 3.2.0; I have the rough outline of a plugin that implements much the same feature set as our current pile of monkey-patches against Mailman 2.1 in a much nicer way. One of the major things I haven't figured out yet is list deactivation and reactivation. In our current 2.1-based code, you can deactivate a list in a reversible way, which basically tars up the list directory so that the list archives can be restored later. This isn't a native operation in 2.1, but it could be done because everything lived on the filesystem. In 3, it's less trivial. We could go to some effort to dump things out of the HyperKitty database and restore it on reactivation, but that seems rather complex and a bit silly. Ideally, I'd like mailing lists to have a "deactivated" state in addition to full deletion. In this state, the list would appear nonexistent for most purposes: incoming email would be rejected, Postorius would deny its existence, etc. There'd need to be corresponding extensions to the IArchiver interface which caused the archiver to put its archives of that list into a corresponding deactivated state, in which it would retain the messages but queries for them would return 404 or similar; these extensions would need to be optional, since while it should be relatively easy to do this in HyperKitty it could be hard or impossible for other archivers, and perhaps this should be a separate operation from deactivating the list itself since people may want to close a list while leaving its archives accessible. Has there been any discussion of this in the past, or any advice as to implementation strategy? Thanks, -- Colin Watson [cjwatson(a)ubuntu.com]

8 years, 5 months

[MM3-users] Re: How to change or create list styles

by Adam Minski

Steven, many thanks for your answer. Probably my question was not carefully worded enough. What I like to do is creating new or modifying existing styles to have reasonable defaults for creating new lists. If I create a new style using the mailman shell as stated by the documentation, the new style is gone as default after restarting mailman server. Maybe i must store the new style into the database, but for me it looks like defaults are coded into src/mailman/styles files. If I understood you correctly the only way at the moment is hacking the source code, which I always try to avoid without getting changes upstream. Is this correct? What did you mean with "or write SQL"? Are the style defaults stored at database level? This would bypass the upstream problem. Thx. Adam On 10/19/21 4:36 PM, Stephen J. Turnbull wrote: > Adam Minski writes: > > > I think the mailman shell way isn't persistent, > > I don't understand what you mean by "persistent" here. I take that to > mean that once you change the list attributes, they stay changed until > you change them again. But that doesn't seem to make sense. > > > and I would prefer some kind of config file. I have not found any > > helpful yet. > > There isn't a config file yet, except the Python modules in > src/mailman/styles. You have to hack the Python or write SQL. > > We're currently working on this but we don't have working code yet, > let alone anything we can release. The code we're starting from is > designed to allow you to start from a base style, tweak the > configuration, and either save the new configuration as a complete > style, or save the difference as a mix-in style. There will also be > some kind of export/import facility, which you could treat as a config > file, I guess. > > Steve > >

4 years, 8 months

[MM3-users] Any known cases of "non-members" who aren't explicitly allowed to send to the list with a default rule of "discard" on a list getting through?

by Stephen J. Turnbull

Thomas Ward via Mailman-users writes: > Has *anyone* seen any cases like this before? Something like it is common. A member forwards a non-member's message to the list, so that the envelope from (and often Sender) are set to that member's address. You will see only the header From, so it appears that the post was by a non-member. �> If this is repeatable or a known issue, it deserves a CVE security �> bug because this is a **severe** problem. Members-only for posting is a best-effort, use at your own risk, feature, because all of the addresses used for identifying members are easily spoofable. Of them only the header From is normally visible to end users. It's standard in stock Mailman because in practice it's an excellent defense against spam. It is not otherwise a reliable security measure, and the default configuration is quite loose. It allows users to forward messages for others and to use various addresses for the author headers. It allows the apparent author to be different from the user who injects the message to the Internet mail system. In practice, header From is fairly reliable if all of your members have addresses with DMARC policy "p=reject" and your MTA does reject when From alignment fails. But to depend on DMARC processing, you need to remove Sender, Reply-To, and envelope From (From_, I think is the configuration notation) from the member identification configuration. Also note that the purpose of DMARC is primarily to protect the sending organization, not the receiver, so this use case depends on trusting the sending organization to do the authentication. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

5 months, 1 week

[MM3-users] Re: ARC signing outgoing mails

by Wolfgang Bock

Hello, thanks for these hints. Now it works and outgoing mails from my lists are no longer greylisted. .... ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=xx.de ... .... ARC-Seal: i=1; s=dkim; d=xx.de .... Here my mailman.cfg (debian buster/dovecot/postfix/rspamd/mysql/mailman3) quote [ARC] enabled= yes selector= dkim privkey: /path/to/rspamd/dkim/{conf.ARC.domain}.{conf.ARC.selector}.key unquote The below mentioned hash should be deleted. In the above mentioned directory the dkim key-files are saved in following style [domain].[selector].key Regards Wolfgang Am 02.11.2019 um 01:19 schrieb Mark Sapiro: > On 11/1/19 4:04 PM, Wolfgang Bock via Mailman-users wrote: >> Hello, >> >> in >> https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/arc_sign… >> I found this hint >> >> "It is highly recommended that Mailman maintainers configure ARC siging >> of their outgoing email. ..." >> >> So I added in my mailman.cfg: >> " >> [ARC] >> privkey: /path/to/private.key >> " >> >> >> But I don't understand the meaning of >> >> >> "... and located at: >> " >> #{config.ARC.selector}._domainkeys.#{config.ARC.domain} –ex.– >> test._domainkeys.example.com >> " > This doesn't seem correct. The DNS TXT record should be added to > #{config.ARC.selector}._domainkey.#{config.ARC.domain} (note _domainkey, > not _domainkeys) > > I.e., this is a normal DNS TXT record containing the public key for DKIM > signing. > >> Where can I find this string or where do I have to place it. I am using >> bind9 as dns-handler. > > Read the entire ARC section beginning at > <https://gitlab.com/mailman/mailman/blob/master/src/mailman/config/schema.cf…>. > You have to configure more than just privkey. > > Once you have configured > > enabled: yes > privkey: /some/location/yourprivatekey.pem > selector: test (or whatever you want) > domain: your_domain.com > > The substitutions for #{config.ARC.selector} and #{config.ARC.domain} > should be more clear. >

6 years, 7 months

[MM3-users] Re: postorius / adjusted settings menu

by Abhilash Raj

On Wed, Mar 3, 2021, at 9:59 AM, Andreas Barth wrote: > Hi together, > > I want to adjust the settings menu to reduce to the options really > needed. > > The easiest way would be to edit src/postorius/views/list* but I don't > think that's a good idea. There is an easier way actually, you can update the forms[1] that generate those views to remove the fields you don't want to be presented. [1]: https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/forms/list… For example, see this form for creating a new list [2]. The layout defines the fields that show up and also the order that they show up in. [2]: https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/forms/list… So, you can add those layout to all the list settings form, each one controlled with a setting and choose the fields and their order. You won't be able to move the fields around in different groups though. > So what comes to my mind is to have some variable in the configuration > that contains the menu items and - if set - the submenus. > > E.g. the following: > { > 'list_identity': ['!gateway_to_mail', '!gateway_to_news', > '!linked_newsgroup', '!newsgroup_moderation', > '!nntp_prefix_subject_too' ], > 'automatic_responses', > 'alter_messages', > 'dmarc_mitigations', > 'digest', > 'message_acceptance', > 'archiving', > 'subscription_policy', > 'bounce_processing' > } > > would express: default menu and just remove the mentioned items. > > Of course, something like ['advertised', 'description', 'info', > 'display_name', 'subject_prefix'] would work as well. > > > Resorting should also be possible, so something like > { 'list_identity': ['advertised', 'description', 'info', 'personalize'] } > would give a very small list of items to select from. > > > > What do you think about the idea? > > > Andi > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 3 months

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

by Stephen Daniel

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

1 year, 7 months

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

by Alain D D Williams

On Wed, Nov 27, 2024 at 08:47:38PM -0800, Mark Sapiro wrote: > 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? /var/lib/mailman3/queue/out/ contains 4 .pck files and one .bak file. There are being continually read & replaced by other files of similar names - like 1732809409.1069376+eb3354a0fc1f0a9bfa95ff7e15e2430ab7c2b885.pck The process doing this is a 'qrunner' I am getting ~50 lines/second appended to /var/log/mailman3/web/mailman-web.log [pid: 1348330|app: 0|req: 4366/4366] ::1 () {54 vars in 1065 bytes} [Thu Nov 28 17:02:18 2024] GET /mailman3/hyperkitty/api/mailman/urls?mlist=chat%40bray.phcomp.co.uk&msgid=Z0iJAoTHHrzK2ypO%40phcomp.co.uk => generated 126 bytes in 3 msecs (HTTP/1.1 200) 7 headers in 220 bytes (1 switches on core 1) Yes: the mail list is chat(a)bray.phcomp.co.uk /var/lib/mailman3/queue/shunt/ contains 4 .pck files. > Is Mailman core running? Systemctl says so & ps shows me one 'master', several 'runner' & 2 uwsgi > Does `mailman members --nomail enabled` list any members? Yes: it gives the list that I expect. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 year, 6 months

[MM3-users] Re: Generic Cannot connect to SMTP server error, no outgoing smtp connections

by Stefan Bauer

I found the problem. Thanks for your help: As mailman3 via docker, consists of 2 independent containers (mailman-core & web) the templates, the runner used a wrong url when looking for templates. after adjusting my templates via SQL, all is fine now: # sqlite3 /opt/mailman/core/var/data/mailman.db "SELECT * FROM template;" 1|list:user:notice:probe|cubewerk.de| http://localhost:8000/postorius/api/templates/domain/cubewerk.de/list:user:… 3|list:member:regular:footer|cubewerk.de| http://localhost:8000/postorius/api/templates/domain/cubewerk.de/list:membe… 4|list:member:regular:footer|lists.cubewerk.de| http://localhost:8000/postorius/api/templates/domain/lists.cubewerk.de/list… sqlite3 /opt/mailman/core/var/data/mailman.db "UPDATE template SET uri = REPLACE(uri, 'localhost:8000', '172.18.0.3:8000');" # sqlite3 /opt/mailman/core/var/data/mailman.db "SELECT * FROM template;" 1|list:user:notice:probe|cubewerk.de| http://172.18.0.3:8000/postorius/api/templates/domain/cubewerk.de/list:user… 3|list:member:regular:footer|cubewerk.de| http://172.18.0.3:8000/postorius/api/templates/domain/cubewerk.de/list:memb… 4|list:member:regular:footer|lists.cubewerk.de| http://172.18.0.3:8000/postorius/api/templates/domain/lists.cubewerk.de/lis… Am Do., 4. Juni 2026 um 16:48 Uhr schrieb Thomas Hochstein <thh(a)thh.name>: > Stefan Bauer via Mailman-users wrote: > > > Mailman logs Cannot connect to SMTP server, however the server is > > listening, but i see no connection attempts. > [...] > > If i restart the docker-core container, i see a single time the error > > "Cannot connect to SMTP server 172.17.0.1 on port 587". > > Is it possibly to connect e.g. via telnet (from the host/IP mailman is > running on, as the user mailman is running as) to the SMTP server? > That looks more like a connection problem from A to B than a mailman > problem. > > -thh > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to cubewerk(a)gmail.com >

2 weeks, 1 day

[MM3-users] Re: Docker mailman3 delete social logins, did something change?

by Abhilash Raj

On Thu, Sep 16, 2021, at 5:45 AM, bob B wrote: > for version tag you mean the docker images? > 509940b4c44f maxking/mailman-web:0.3 > mailman-web maxking/mailman-core:0.3 Yeah, the version is basically the version tag. Thanks. > > Also this works for /opt/mailman/web/settings_local.py > ************** > #allowed_hosts = ['127.0.0.1', 'localhost','Redacted]'] > ALLOWED_HOSTS = > ['127.0.0.1','localhost','[Redacted]','172.19.199.3','172.19.199.1','172.19.199.4','172.19.199.1'] > #ALLOWED_HOSTS = ['*'] > DEBUG = True > #DEBUG = False > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'Redacted' > EMAIL_PORT = 25 > ******************* > > > But, > > > if I even add in one line like MAILMAN_WEB_SOCIAL_AUTH = []. so i > would have > ************** > #allowed_hosts = ['127.0.0.1', 'localhost','Redacted]'] > ALLOWED_HOSTS = > ['127.0.0.1','localhost','[Redacted]','172.19.199.3','172.19.199.1','172.19.199.4','172.19.199.1'] > #ALLOWED_HOSTS = ['*'] > DEBUG = True > #DEBUG = False > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'Redacted' > EMAIL_PORT = 25 > MAILMAN_WEB_SOCIAL_AUTH = [] > *********** > > When I try to add the items in tot remove social media, It basically > acts like my /opt/mailman/web/settings_local.py. file is ignored and > does not load. Did you re-start your container after editing the settings_local.py file? It will not automatically read new configs. > I do not get debugging. The most authoritative way to see what the loaded settings are by running: $ docker exec -it mailman-web python manage.py print_settings And then look for the keys. > the log says my domian name is > not an allowed which is a sympton that this file did not load. > > > So it appears that adding a section to remove the social media apps, > stops this file from being loaded??? MAILMAN_WEB_SOCIAL_AUTH config was added in main branch but isn't released yet. The last release of 0.3.12 can be seen here[1] [1]: https://github.com/maxking/docker-mailman/blob/v0.3.12/web/mailman-web/sett… So, it basically should have no effect. If your configs are breaking due to something, it is probably not that. -- thanks, Abhilash Raj (maxking)

4 years, 9 months

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

by Jered Floyd

Odhiambo, It appears that django-allauth 0.58.1 has been released to fix this issue. --Jered ----- On Oct 29, 2023, at 10:41 AM, Jered Floyd jered(a)convivian.com wrote: >> Consequent upon this django-allauth issue and the previous issue >> with psycopg2, how likely is it that new MM3 installations will suffer the >> effects? >> I am asking because I am doing my tests on a relatively vanilla system and >> just following the official documentation sin any deviations. > > The allauth issue will happen until the allauth package is patched. Mark's > patch was merged yesterday, so I suspect a new release will be imminent. > > I've noticed the django-allauth ecosystem seems to be somewhat prone to breaking > changes. I'm sure this discussion has happened before, but it may be worth > pinning "known good" dependency versions for django-mailman -- either in the > project, or in your documentation. It's definitely a headache for me since I > rebuild my mailman container roughly weekly, and always need to allow time for > functional testing or rollback to my last image. > > There's not really a right answer here; either dependency versions are left open > and the end user gets security updates for dependencies on their own schedule, > or the Mailman maintainers have to monitor for security updates in the > dependency tree and push a new mailman release. (This can also help ameliorate > supply-chain attacks where an unverified update ends up in PyPI, but I'm not > sure that's a realistic threat model for us.) I'm sure this is something the > maintainers have considered in the past. > > --Jered > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

2 years, 7 months

[MM3-users] Re: Bottom line of message footer

by Brian Carpenter

On 2/14/21 9:05 PM, Mark Sapiro wrote: > On 2/14/21 5:40 PM, Tom Stoddard wrote: >> Here's another question that I have. A regular message just came into my >> email from one of the lists I'm a member of and it had a 3 line footer. >> The first two lines are fine, they just include the list's email address >> and an address to send unsubscribe requests to. The third line is this: >> >> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >> >> It looks to me like it should be a link to the group's list info page. >> Is this a bug or is there something I can do to fix it? It looks like it >> might be missing a forward slash after the first "s". > This is a list whose msg_footer was imported by The Mailman 3 process > that imports Mailman 2.1 lists. This import process will recognize the > default msg_footer and not create a list specific template for it, but > other things in the footer result in a list specific template which > needs to be reviewed for issues like this. > > The way for you to fix it is to create a list:member:regular:footer (and > maybe a list:member:digest:footer) template in your web UI which will > then override the existing list specific template. The available > replacements are listed at > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. > In templates they are all $ strings, e.g. $name. The %(name)s > replacements are Mailman 2.1 and won't work. Also, there is no > replacement for web_page_url because Mailman Core doesn't know what that > is, so you have to include the actual 'https://.../' value if you want > to include a web link. Thank you Mark. @Tom the templates you want to modify to add a Mailman 3 footer to replace the above are: Regular Message Footer Digest Footer -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 4 months

[MM3-users] Re: can't get mail into mailman3 in docker

by bob B

Thanks for the help, I do appreciate it. I am using the docker images provided by the mailman project. The containers are up and running ************* CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9dbad91fe50b maxking/mailman-web:0.3 "docker-entrypoint.s…" 6 seconds ago Up 5 seconds 127.0.0.1:8000->8000/tcp, 127.0.0.1:8080->8080/tcp mailman-web 7005bf66498e maxking/mailman-core:0.3 "docker-entrypoint.s…" 7 seconds ago Up 6 seconds 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core b5336023fa94 postgres:9.6-alpine "docker-entrypoint.s…" 7 seconds ago Up 7 seconds 5432/tcp dockermailman_database_1 ************************ I was looking on the docker host for "/etc/postfix-mailman.cfg." so that explains why it is not there. I have been digging in more and it looks like the mailman-core is not processing or accepting mail or/and the connection gets lost. But I can send mail from mailman in docker. On the docker host my /etc/postfix/main.cf has ************************************ transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains ************************************ My docker yaml has ************************************ mailman-core: image: maxking/mailman-core:0.3 container_name: mailman-core hostname: mailman-core . . ports: - "127.0.0.1:8001:8001" # API - "127.0.0.1:8024:8024" # LMTP - incoming emails ************************************ But when I send a message, the docker host machine in /var/log/email/ shows "connection refused" & "lost connection" to mailman-core port 8024 ************************************ 2021-08-06T09:08:41.885213-04:00 dockerhost postfix/cleanup[109782]: D630B3083ED0: message-id=<4805A7DC-E100-4851-B1BB-E6C1806568A1(a)sender.com> 2021-08-06T09:08:41.896943-04:00 dockerhost postfix/qmgr[105559]: D630B3083ED0: from=<USER(a)sender.com>, size=8308, nrcpt=1 (queue active) 2021-08-06T09:08:41.949022-04:00 dockerhost postfix/lmtp[109783]: connect to localhost[::1]:8024: Connection refused 2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test(a)mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting) ************************************ The /opt/mailman/core/mailman-extra.cfg files has ************************************ # mailman-extra.cfg [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver # mailman-core hostname or IP from the Postfix server lmtp_host: localhost lmtp_port: 8024 # Postfix server's hostname or IP from mailman-core smtp_host: outbound-mail-server.######.### smtp_port: 25 configuration: /etc/postfix-mailman.cfg [mailman] . ************************************

4 years, 10 months

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

by Stephen Daniel

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

4 years, 5 months

[MM3-users] Re: Database problem after system upgrade

by Odhiambo Washington

On Wed, Nov 15, 2023 at 9:39 AM Lars Bjørndal <lars(a)lamasti.net> wrote: > I managed to upgrade the database. However, Mailman3 won't start: > > × mailman3.service - GNU Mailing List Manager > Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; > preset: disabled) > Drop-In: /usr/lib/systemd/system/service.d > └─10-timeout-abort.conf > Active: failed (Result: exit-code) since Wed 2023-11-15 06:49:38 CET; > 44min ago > Process: 28224 ExecStart=/opt/mailman3/venv/bin/mailman start > (code=exited, status=1/FAILURE) > CPU: 948ms > > nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: return > self.loaded_dbapi.connect(*cargs, **cparams) > nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: File > "/opt/mailman3/venv/lib64/python3.11/site-packages/psycopg2/__init__.py", > line 122, in connect > nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: conn = > _connect(dsn, connection_factory=connection_factory, **kwasync) > nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: > sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to > server at "localhost" (::1), port 5432 failed: FATAL: Ident authentication > failed for user "mailman" > nov. 15 06:49:38 dalen.lamasti.net mailman[28224]: (Background on this > error at: https://sqlalche.me/e/20/e3q8) > nov. 15 06:49:38 dalen.lamasti.net systemd[1]: mailman3.service: Control > process exited, code=exited, status=1/FAILURE > nov. 15 06:49:38 dalen.lamasti.net systemd[1]: mailman3.service: Failed > with result 'exit-code'. > nov. 15 06:49:38 dalen.lamasti.net systemd[1]: Failed to start > mailman3.service - GNU Mailing List Manager. > > Mailman.log doesn't contain any info. > > How do I find the cause of this problem? > From the above output, I'd try two things: 1. Is the database really running? ``` $ sudo -u postgres psql ``` 2. Can mailman connect to the database: ``` psql -h localhost -U mailman -d mailman -W ``` What does those two commands give you? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 7 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Phil Thompson

On 06/08/2019 03:38, Abhilash Raj wrote: > On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: >> I'm in the process of setting up mailman3. The only problem I seem to >> be >> having is getting Hyperkitty to archive messages. Rather than the >> authorisation problems people have previously asked about on the list, >> I >> am getting a 403 error... >> >> Aug 05 15:38:40 2019 (10229) HyperKitty failure on >> http://localhost/mailman3/hyperkitty/api/mailman/urls: >> <html><title>Forbidden</title><body> >> <h1>Access is forbidden</h1></body></html> (403) >> Aug 05 15:38:58 2019 (10222) HyperKitty failure on >> http://localhost/mailman3/hyperkitty/api/mailman/archive: >> <html><title>Forbidden</title><body> >> <h1>Access is forbidden</h1></body></html> (403) >> >> Any suggestions would be appreciated. > > How did you install Hyperkitty? On Ubuntu... apt-get install mailman3-full > You probably need to the set the API key correctly in both Core and > Hyperkitty. > > Have you looked at documentation here[1]? > > [1]: > https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-mail… > > Note that the MAILMAN_ARCHIVER_KEY = "value" (this value should be in > quotes, single or double, doesn't matter) in your settings.py for Web > (Django) should be same as the `api_key : value` (without quotes here > in hyperkitty.cfg config file). That's all correct. I'm familiar with the authorisation issues that other people have had. The only thing I'm doing differently (as far as I am aware) is that I'm using a URL prefixed with /mailman3 which is stripped off in my nginx configuration... # mailman3. location /mailman3/ { uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; include uwsgi_params; uwsgi_param SERVER_ADDR $server_addr; uwsgi_modifier1 30; uwsgi_param SCRIPT_NAME /mailman3; } location /mailman3/static { alias /var/lib/mailman3/web/static; } location /mailman3/static/favicon.ico { alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; } ...but I don't see this affecting the mailman to Hyperkitty communication. Posting to lists and the Postorius and Hyperkitty frontends seem to work fine. Phil

6 years, 10 months

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

by Mark Sapiro

On 1/16/21 7:49 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > I can't find any log entry which indicate a problem with this subscription request. > The _request table does not contain a request for the specific mailinglist, but I am not sure if subscription requests are included in this table. It is unclear and confusing, but the requests are not in the _request table. See <https://gitlab.com/mailman/mailman/-/issues/768#note_415536043>. So this is normal. > The token is found in the pended table: > > +-----+------------------------------------------+---------------------+ > | id | token | expiration_date | > +-----+------------------------------------------+---------------------+ > | 115 | 4d6b4b11266c7332684c5a492eb3f92c531f761b | 2031-01-04 16:17:38 | > +-----+------------------------------------------+---------------------+ > > These are the relevant entries in the pendedkeyvalue table: > +------+--------------+-------------------------------------+-----------+ > | id | key | value | pended_id | > +------+--------------+-------------------------------------+-----------+ > | 1130 | type | subscription | 115 | > | 1131 | list_id | "********************" | 115 | > | 1132 | email | "***********************@*********" | 115 | > | 1133 | display_name | "" | 115 | > | 1134 | when | "2021-01-06T16:17:38" | 115 | > | 1135 | token_owner | "moderator" | 115 | > +------+--------------+-------------------------------------+-----------+ > > Can I workaround this problem for this specific subscriber by adding entries in the _request table, and if so what do I need to add? Adding to the _request table won't help. Try confirming by emailing listname-confirm+4d6b4b11266c7332684c5a492eb3f92c531f761b(a)list.domain You could also try confirming via mailman shell mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/app/subscriptions.py", line 570, in confirm raise LookupError LookupError In my case, I get the LookupError because the token doesn't exist, but I think it should work for you. -- 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: FILTER_VHOST not working

by Mark Sapiro

On 3/22/21 1:03 PM, Johannes Rohr wrote: > In /etc/mailman3/mailman-web.py I have added > FILTER_VHOST = True > so that only the list for the current domain are shown. > > But this has no effect. The current situation with Postorius >=1.3.3 and Hyperkitty >=1.3.3 is for HyperKitty, FILTER_VHOST = True works. For Postorius, it works only if in the domains view, each mail host has a unique web host. It doesn't work. See this post <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> and others in that thread for more info. Prior to Postorius 1.3.3 and Hyperkitty 1.3.3 it would only work if the mail host and web host values were identical for the domain. > > What's more, in hyperkitty I see at the top left the lable for the > default domain, even though I am visiting from another domain. That has nothing to do with FILTER_VHOST. The displayed there is the site referenced in the SITE_ID setting. > The web domains are exactly the same as the mail domans > (lists.[domain].[tld]) In that case, I'm not sure what's going on. > In the Nginx config I have added > > location / { > proxy_set_header X-Forwarded-Proto $scheme; > proxy_set_header X-Forwarded-Host $host; > proxy_pass http://localhost:8000/; > [....] > > } > > to make sure that mailman3 knows from which URL it is visited. > > Am I overlooking something? > > I am using the distribution packages on Ubuntu 20.04: > mailman3 3.2.2-1 > mailman3-web 0+20180916-10 > > I see, the mailman3-web package is quite dated. Is it recommended to > install via virtualenv instead? Yes, the issue is at least partially that that mailman3-web package doesn't have any of the FILTER_VHOST fixes. And yes, if you don't want to be stuck with dated packages tha don't include recent fixes, we recommend installation as documented 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

5 years, 2 months

[MM3-users] Migration failure (2.1.29 to 3.3.8 on Debian testing)

by {16/7}

Hello, I have both the mailman and mailman3-full packages installed on my machine and I'm following the migration guide located here: https://docs.mailman3.org/en/latest/migration.html Running the command { mailman import21 mylist(a)mysite.com /var/lib/mailman/lists/mylist/config.pck } completes once I create the list but states that it cannot convert the msg_footer and digest_footer mailing list attributes. (I might also point out that the { mailman create mylist(a)mysite.com } command isn't actually documented on that webpage.) I can't seem to find the manage.py script in my $PATH and after searching, I find it as part of the mailman3-web package. When I run { sudo -H -u list python manage.py hyperkitty_import mylist(a)mysite.com /var/lib/mailman/archives/private/mylist.mbox/mylist.mbox }, it fails with "ImportError: No module named django.core.management". If I run the script directly as { sudo -H -u list /usr/share/mailman3-web/manage.py ... }, I get "PermissionError: [Errno 13] Permission denied: '/usr/share/mailman3-web/settings_local.py'". By default, settings_local.py's group is www-data, and not knowing where to go next, I decided to try changing that file's group to list. When I re-ran the command (as user list), I got a Python traceback that gives "PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/web/mailman-web.log'". Next, I changed the file's group back to list and decided to try running the manage.py script as the www-data user. This results in "/usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured." and "System check identified some issues:" followed by a list of "Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'" warnings for a number of Django tables. At the end of this list is "CommandError: The list address must be given on the command-line". But it *was* given. My questions are: 1. How do I undo any damage (if any) my efforts may have caused? 2. What's the correct way to run manage.py?

3 years

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

by Andrew Hodgson

Mark Sapiro <mark(a)msapiro.net> wrote: >On 9/21/23 17:30, Thomas Ward wrote: >> >> MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). >> >> If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. >It appears however that Mailman does recognize the DSN returned by MS365 as the user's delivery is being disabled by bounce. The issue is whatever DSN is returned to the list-bounces address is not attached to the notice sent to the list owner about the disable and it should be. Ok guys the plot thickens. Yesterday using the Mailman Shell I unbounced all the users on that list. We had a couple of messages yesterday and I also enabled the From munging for all messages sent to the list partway through those messages coming to the list. This morning we got all Gmail users bounced again, with no NDR attached to the message. However on one of the messages the NDR was attached, and so I'm going to send that to Mark separately. It looks like the NDR included the information for all the bouncing messages though, and that is probably because Mailman sends the messages to all users in one SMTP transaction. The message returned from Google was: user(a)gmail.com 9/22/2023 9:44:55 AM - Server at PAVPR08MB9257.eurprd08.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError' 9/22/2023 9:24:03 AM - Server at gmail-smtp-in.l.google.com (142.250.27.27) returned '421 4.4.2 Connection dropped due to SocketError' Thanks. Andrew.

2 years, 8 months

[MM3-users] Re: Reg Archive Inactive Status

by Stephen J. Turnbull

Nirmal J via Mailman-users writes: > The status is enable only. But still It is not coming mail to > archives. Hereby I am attaching the screen shots of the > status. Kindly help me in this regard. This list <mailman-users(a)mailman3.org> does not accept images. I doubt they would be helpful, so I don't think you should try to use a pastebin site. Just copy text from the files that you find, and put it in the mail directly. You need to find your configuration files and logs. Usually 'mailman.cfg', 'mailman-hyperkitty.cfg', and 'settings.py' are located in /etc/mailman3. You are looking for lines like these in 'mailman.cfg'. Some of them may be missing; that is probably normal. They probably won't be all together. Anything after a hash mark (#) is a comment and does not affect Mailman operation at all. ---------------------------------------------------------------- var_dir: /opt/mailman3 # where Mailman keeps data log_dir: /var/log/mailman3 # where Mailman keeps logs archive_dir: $var_dir/archives # where Mailman queues messages # to the archiver [logging.archiver] # you probably don't have these level: debug [archiver.prototype] # you probably don't have these enable: yes # but if you do you have a backup [archiver.hyperkitty] # you should have these class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/mailman3/mailman-hyperkitty.cfg ---------------------------------------------------------------- You are looking for this line in 'mailman-hyperkitty.cfg': ---------------------------------------------------------------- api_key: dXwiLGJ1W2MoODB8X3ZZXA== ---------------------------------------------------------------- and this in 'settings.py': ---------------------------------------------------------------- MAILMAN_ARCHIVER_KEY = "dXwiLGJ1W2MoODB8X3ZZXA==" ---------------------------------------------------------------- Note that 'api_key' is followed by a colon (:) and the value IS NOT quoted, but 'MAILMAN_ARCHIVER_KEY' is followed by an equal sign (=) and the value IS quoted. Of course those two values must match. If you have the line 'log_dir', that's where you will find Mailman's logs. Most likely the file you want is 'mailman.log'. There should be messages explaining why messages are not being sent to the archiver, as Mark explained. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

8 months, 3 weeks

[MM3-users] Re: Template's encoding setup

by Mark Sapiro

On 9/14/19 4:06 AM, Ugnius S wrote: > Yes, I have made several tests. I have set charset: iso-8859-13 > and default_language: lt in mailman.cfg. If you created the list before you set default_language: lt in mailman.cfg, the list's preferred_language is possibly 'en;' with character set us-ascii. > (Also I have set LANGUAGE_CODE = 'lt' in the settings_local.py, but I think > it is not related to this case.) Yes, LANGUAGE_CODE in settings_local.py is not relevant to this. > I have tried to set utf-8 as well in mailman.cfg as well. And I can > confirm - in all tested cases > text characters are correct (in footer as well) if sender sends text only. OK > If sender sends message in HTML (mostly all users send) then no > matter what the encoding is set in my mailman's > configuration or iso-8859-13, or utf-8 message body looks correct, but in > footer all national characters are replaced with > question marks " ? ". The addition of the footer is done by mailman/handlers/decorate.py. In the plain text case the message body is converted to unicode, the unicode footer is appended to the body and the new body is encoded for transmission. The encoding is the first of the list's character set, the incoming message's character set or utf-8 which produces no error. In the case where the incoming message is not a single plain text message part, the footer is added as a separate MIME part with the unicode footer encoded in the list's character set with errors='replace'. This is what produces the '?' characters. I suspect this happens because the list's preferred_language is 'en' with character set us-ascii. try running Mailman's bin/mailman shell -l your_list@domain at the prompt enter m.preferred_language if the response is not <Language [lt] Lithuanian> do m.preferred_language = 'lt' and then control-D to exit. -- 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: Sendgrid experiences

by Stephen Daniel

I would definitely look for alternatives to SendGrid. I tried using them and had a very poor rate of people actually getting my emails, even when I temporarily upgraded to an expensive plan with a dedicated IP address. I'm currently hosting mailman in Google Cloud and relaying outbound mail through a Google Workspace account. It's working OK. The workspace account costs me $6/month for basically unlimited mail relay. On Thu, May 11, 2023 at 9:50 AM Andrew Hodgson <andrew(a)hodgson.io> wrote: > Stephen J Turnbull wrote: > > >2023-05-10 03:49 に Andrew Hodgson wrote: > > >> Sendgrid is maintaining the Message-Id header which is good for > >> archiving. It is re-writing the Return-Path header though which means > >> that bounce handling in Mailman won't work, but I think all the > >> services do this in some way so I am happy to live with that for the > >> moment. > > >How does it rewrite the Return-Path? Returned mail is not something that > such a service would be able to handle properly (although they can help > with apparently returned spam). If mail is legitmately sent and returned > as undeliverable, only the author or their agent will know how to handle > it. So such >services should provide some way to find out about returned > mail. > > An example: > Return-Path: > bounces+[Sendgrid GUID]-andrew=hodgson.io(a)em6096.lists.hodgsonfamily.org > > Sendgrid provide information about bounces but crucially that bounce isn't > forwarded back to the original return-path sender (i.e, Mailman). > > A few people have pointed out they can provide list hosting at a cheaper > cost than Sendgrid so I'm looking for alternatives again. > > Andrew. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to swd(a)pobox.com >

3 years, 1 month

[MM3-users] Reject email based on message size.

by Stephen J. Turnbull

Hitashi mancho via Mailman-users writes: > As configured, posts with a message size greater than 512K are held > for moderation. However, even after multiple reminders, some > moderators accept these postings. > > Is there a way to automatically reject all such messages with an > appropriate rejection reason? Not at present. The size limitation option does not allow specification of an action. I don't recall whether the action is hardcoded in the size limitation or whether it follows a configuration for members or nonmembers. > Can we implement a custom rule or a plugin that will help in this > case? The documentation for plugins is here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do… Unfortunately I don't know of an example of a plugin that's in production somewhere (I tried to implement a list style as a plugin once but it didn't work first try and I'd already had to vendor the source for that client, so I just hacked that in too). However, implementing what you want as a plugin probably requires a large amount of work. If making a local branch of the sources is OK for you, simply changing the ('max-size', LinkAction.defer, None) element in mailman/chains/builtin.py:BuiltInChain._link_discriptions to ('max-size', LinkAction.jump, 'reject') should be enough for you. You may also want to modify the "list:user:notice:rejected" template to explain the 'max-size' policy, You also might need to move that element above the "# Do all of the following before deciding whether to hold the message." comment, or possibly to the very beginning of the list. Moving to the very beginning has the advantage of saving a lot of work in that case, but it has the disadvantage that if there are other rule hits that would cause the message to be held, they won't be recorded and reported to sender. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months

[MM3-users] Re: Emergency Moderation

by Abhilash Raj

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

6 years

[MM3-users] Re: Member Issue Discovered

by Allan Hansen

I agree that deleting, without an explicit request to do so, user-entered information is a violation of the user’s data This applies when the user has set up an account on the system. If he/she has never created an account, then I see no problem cleaning up the system when the user deletes the last subscription, as any remaining data presumably has been created by the server. Keeping that information on the server without the knowledge of the user is not right. Yours, Allan Hansen hansen(a)rc.org > On Nov 2, 2020, at 19:51 , Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Brian Carpenter writes: > >> This is in regard to our Affinity/Empathy UIs. I believe the issue >> [about data retention] that was raised originally in this >> thread/post still exists with Postorius/Hyperkitty. > > I don't speak *for* the Mailman team on this, but my *impression* from > these conversations is that we have a consensus on the team: deleting > the User data (authentication and profile) is a very big deal that > should be done only on explicit request, not as an automatic side > effect of other changes. We understand that others have a different > opinion, but we think that this is a difference of opinion, not a > mistake on either side. > > My own suggestion is that we *should* provide the *option* to delete > the User data, and prompt for it, when that User's last subscription > on the server is deleted. Note that there is a race condition where > the user deletes the second-to-last subscription and an admin then > deletes the last one. The user won't see the option, but the admin > will. I can see this as a bad outcome, depending on user's intent, > whether the admin deletes the User object or leaves it in place. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 7 months

[MM3-users] Re: Postfix-Fehler mit mailman-web

by Jens Günther

So rounding it up, we figured it out (thanks to Abhilash). - After an update from docker-compose v1 to v2, the core-components of my setup suddenly started with a different IP-subnet (192.168.x.y instead of 172.16.0.0/12 ... probably because there were not enough left or so) - The mailman-web-container always got an extra IP within core to talk to the outside world, so always had 2 IPs (1 fixed within mailman subnet, 1 drawn from the external network) - This second IP was before within the 12 subnet and being approved in Postfix. - Probably it was luck, that the correct one was chosen before :-D The solution now was to set the variable SMTP_HOST to the gateway of the mailman subnet within mailman-web, and NOT to the domain of the host: SMTP_HOST=172.22.0.1 (DB, core and web are then 2,3 and 4) I also set this within core-container so that IPs are fixed now. Regards, Jens. Am 28.08.23 um 14:42 schrieb Jens Günther: > > > Am 28.08.23 um 10:21 schrieb Stephen J. Turnbull: >> Jens Günther writes: >> >> > 2023-08-26T08:21:59.522238+02:00 postfix/smtpd[2843414]: NOQUEUE: >> > reject: RCPT from unknown[192.168.176.6]: 450 4.7.25 Client host >> > rejected: cannot find your hostname, [192.168.176.6]; >> > from=<$admin(a)mydomain.de> to=<$recipient> proto=ESMTP >> helo=<mailman-web> >> >> There are a bunch of $myxxxx variables in Postfix, I think $myhosts >> might be the right one. If you add the IP 192.168.176.6 to that >> variable, it will be whitelisted and this problem should go away. >> There may be better ways to handle this, but don't mess with >> hostnames. Find the "right" way to permit that IP should do the job. > > Thank you, adding the IP/network under mynetworks, as Abhilash writes, > the error is gone. > > (this is so dumb, somehow docker started with a different IP and I have > to figure out why ... and there is another Django-error -> shall I open > a new thread? "OSError: [Errno 99] Address not available")

2 years, 9 months

[MM3-users] Re: restrict sending to owner/moderator

by Mark Sapiro

On 09/18/2017 02:28 AM, m.dohmen(a)xconnect.de wrote: > > I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable. And on 09/19/2017 10:52 AM, David Krantz wrote: > > I have just tested a variant of this as I got curious: You find the > member you want to be able to send emails without moderation, then set > Administrative Options to "Accept Immediately (bypass other rules)". > That works. I have found no other ways, though. Or you may wish to set the owners/moderators subscriptions to "Default processing" which will still apply subsequent rule checks. I.e., set Default action to take when a member posts to the list to Reject (with notification) and set an appropriate notice (currently can't be set in Postorius - set it via 'mailman shell') and set Default action to take when a non-member posts to thelist to Discard or perhaps Reject but this creates backscatter. Then ordinary members have Moderation set to List default and owners/moderators have it set to Accept or Default. The problems with this are sall the owners/moderators need to be subscribers and there are maintenance issues with adding/removing owners/moderators. A better way to do this by sharing a "moderator password" for the list among the authorized posters. See <http://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/approved.html> for how this is done to pre-approve posts. Then set the list to Discard/Reject all posts, and people who know the "moderator password" can still post. There is still an issue in that the password needs to be changed and redistributed when people become unauthorized, but this is more secure as regular moderation can be fooled by spoofing the sender. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 8 months

[MM3-users] nextcloud as auth provider for postorius

by Stephen J. Turnbull

mailman3--- via Mailman-users writes: > If i try to login via nexcloud, postorius redirect me to the > nextcloud, where i successful login, and redirected to postorius > But i'm not logged in postorius. I don't know of a howto for Mailman and socialauth. The socialauth I've configured has been for corporate environments, so there was a ground source of truth for IDs that happened to also provide the ground source of truth for email addresses. So everything just worked and there was no debugging to do. :-( First, you need to understand that there's no automatic connection between your socialauth identity and your Mailman identity, and that your email address is not your Mailman identity, although it is linked to your Mailman identity.[1] Now, the traditional identity in email is an email address, and the authentication procedure is to make the user prove they can read the mailbox. That is still necessary, so email addresses are still very closely bound to the identity (Mailman User object). Then there are these questions: 1. Does Nextcloud provide an email address as identifying information? 2. Is it the right address (ie, one of the ones linked to your Postorius login)? 3. Is that address verified in Postorius? If none of those questions help you figure out the problem, you'll need to explain exactly what data Nextcloud is providing to Django socialauth, and how Django socialauth is supposed to connect that to a Postorius/Mailman User object. Steve Footnotes: [1] The identities in Mailman are quite complex. From Mailman's point of view, the identity is in a User object in Mailman core's database. That User is *not* exposed to world, instead, a separate application (Postorius in your case, and for most sites) provides a proxy object that automatically synchronizes with the core User object. Besides the proxy object, Postorius also provides authentication services. Those services are delegated to Django, which handles both traditional password authentication as well as "socialauth". Then the socialauth plugin receives some kind of identifier (not an identity!) from the identity provider.

2 years, 6 months

[MM3-users] Re: Removing a mail addresses and users

by Mark Sapiro

On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: > Hello. > > I tried to remove random email address signing ups (which I signed up > while testing) via admin panel. After removing I tried to sign up again, > but I am getting, > > 'A user is already registered with this e-mail address' You removed the user's subscription from the list, but you didn't remove the user from the system. Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. User's have addresses and a user or one of the user's addresses can belong to a list with one or more roles (non-member, member, moderator or owner) > Combing through the database, I found auth_user table in mailman3web db > still contain those mail address. How to wipe email address entirely > from the db so I can signup again without the 'forget password' method There are a couple of things. If you log in to the web UI as a django superuser, you can go to the django admin UI -> Users section and delete the User, but I think that will only delete the web user and not delete the user from Mailman core. You can also log in to the web UI as the user and go to <https://lists.mailman3.org/user-profile/delete>, but that again only deletes the web user, and if you could do that, you could just subscribe once you're logged in, so I assume that's what you want to avoid. I don't think there is a way for a user as opposed to a site admin to delete her user record from Mailman core and even for a site admin, there's no way in Postorius to delete a user from core. It has to be done via REST <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> or `mailman shell`. -- 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: Docker or virtualenv?

by J.Schulz

For Docker: just use the README on https://github.com/maxking/docker-mailman ; this should be enough for a basic setup. Eventually, you'll need to add some things to core/mailman-extra.cfg : ___ [mailman] site_owner: help(a)elternserver.de SMTP_MAX_RCPTS = 1 VERP_CONFIRMATIONS = Yes VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = 1 # [devmode] # enabled: yes # recipient: you(a)somewhere.com # # extra local settings for mailmen [mta] # NullMTA is just implementing the interface and thus satisfying Mailman # without doing anything fancy # outgoing: mailman.mta.null.NullMTA smtp_user: your_auth@your_MTA smtp_pass: supersecretpassword smtp_verify_hostname: yesorno smtp_secure_mode: starttls # or whatever # [logging.debug] [logging.smtp] level: warn ___ also, web/settings_local.py needs tweaking in some cases; the DJANGO_ALLOWED_HOSTS come from my docker-compose.yml ---- import os # see https://github.com/maxking/docker-mailman/issues/548 django_allowed_hosts = os.environ.get('DJANGO_ALLOWED_HOSTS') if django_allowed_hosts: ALLOWED_HOSTS = django_allowed_hosts.split(':') MAILMAN_WEB_SOCIAL_AUTH = [] SOCIALACCOUNT_PROVIDERS = { } DEBUG = False # see https://gitlab.com/mailman/mailman/-/issues/957 DEFAULT_AUTO_FIELD='django.db.models.AutoField' HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'xapian_backend.XapianEngine', 'PATH': "/opt/mailman-web-data/fulltext_index", }, } ----- Am 10.01.23 um 09:11 schrieb Odhiambo Washington: > Hi Jörg, > > Kindly share the link to the HOWTO, which you use to setup everything. > I just need to test. Perhaps I can use docker on Windows, no? > > On Mon, Jan 9, 2023 at 8:58 PM Jörg Schulz <info(a)joergschulz.de> wrote: > > I have a successful installation using docker, just updated to the > most > recent version - it runs along quite some other docker containers, so > there is a benefit when I want to switch machines. > > Am 07.01.23 um 12:02 schrieb Odhiambo Washington: > > On Sat, Jan 7, 2023 at 1:54 PM Johannes Rohr <johannes(a)rohr.org> > wrote: > > > >> I wanted to say "I have now chosen virtualenv". Sorry for the > confusion. > >> > > I have never tried docker, but soon I will. Just for the kicks. > > > > > > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 5 months

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

by Simon Coggins

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

4 years, 7 months

[MM3-users] Re: import21: ModuleNotFoundError: No module named 'Mailman'

by Mark Sapiro

On 7/28/19 4:18 PM, Christian Schwarz wrote: > > Most mailing lists can be imported successfully using the `import21` subcommand, as described in the docs. Good. > Some mailing lists fail with the following error: > > sudo -u list mailman import21 REDACTEDLIST(a)example.org /var/lib/mailman/lists/REDACTEDLIST/config.pck > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/mailman/commands/cli_import.py", line 64, in import21 > pickle_file, encoding='utf-8', errors='ignore') > ModuleNotFoundError: No module named 'Mailman' I know what's happening, but I need more detail to do more than guess at how to fix it. The issue is there is a Mailman 2.1 Mailman.xxx.yyy object in the config.pck file. My best guess is that the list's bounce_info is the culprit. The list's bounce_info is a dictionary with keys equal to member addresses and values equal to the Mailman.Bouncer._BounceInfo object representing that member's bounce info. So when import21 calls pickle.load to load the config.pck, there is a reference to one or more Mailman.Bouncer._BounceInfo objects, but pickle.load can't find the definition of that object and that raises the exception. As to how to proceed, there are a couple of ways. One is to fix import21 so it ignores this issue. I just reported <https://gitlab.com/mailman/mailman/issues/618> on this, but I'm not sure how to fix it. I don't think it will work to try the pickle.load and pass the ModuleNotFoundError exception because I think the rest of the pickled data won't be returned. It looks like you still have the MM 2.1 installation, so you could use either MM 2.1's bin/withlist or bin/config_list to set the list's bounce_info to an empty dictionary. and then use the updated config.pck for the import. This assumes that bounce_info is the issue. You can verify that there is a non-empty bounce_info dictionary with either bin/withlist or bin/dumpdb. -- 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] UnicodeEncodeError: 'ascii' codec can't encode character

by Stephen J. Turnbull

Marvin Gülker writes: > I've accidentally sent from an unregisted address to one of my lists. > Mailman correctly held the message back for moderation, but when I go to > the page for held messages in postorios, I receive a 500 error. I've > included an except from the log below. To me, it looks as if it errors > on processing my last name (which has a non-ascii character in > it). You're the "it's 2019, let's use SMTP UTF8 everywhere" guy, right? If you're right about the umlaut being the trigger, the first thing I'd look at is a feature-negotiation problem in the MTA delivering to Mailman. I'm pretty sure our LMTP does not offer the SMTP UTF8 feature. > Ideas? And how do I discard the message without access to the held > messages page? I would guess this is in the shunt queue. If there's only one file there, you can just delete it. To get more information about the content of posts, use "mailman qfiles". > UnicodeEncodeError: 'ascii' codec can't encode character '\ufffd' > in position 269: ordinal not in range(128) Assuming you're right about your name being the trigger, U+FFFD REPLACEMENT CHARACTER is not in your name. So the non-ASCII character was replaced *on the way in*, and on the way out Mailman assumes ASCII in the header because Mailman doesn't know how to negotiate SMTP UTF8, and SMTP UTF8 specifies UTF8 in a context where there is no MIME way to indicate it to Mailman. So Mailman has no way of knowing it needs to encode to anything but ASCII (as specified by the Ancient Wisdom of RFC 5322). I'll put SMTP UTF8 support as a feature request in the tracker. I'm not sure how difficult this will be; it presumably involves RFC something (6532 or so?) internationalization support etc. and may not be trivial. So no short term promises, just medium term aspirations (next year's GSoC task list, for example). Steve

6 years, 6 months

[MM3-users] Re: only show mail domains from web host on web-host-url

by Jens Günther

Thank you for your answer. I should have seen that in the Docs, but somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html I set it in the corresponding file, but unfortunately it doesn't work :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS works, changed here from '*' to 'localhost' and my example-domains, this works). It seems to be the same as this user describes (a while ago): https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… How could I check, that the setting is used!? But maybe some additional information: - I use the Debian installation on a stable buster, so mailman is version 3.2.1 - I use apache2 as my web-server and use the given alias-conf-file - Python is version 3.7.3 - Postorius is Version 1.2.4 - HyperKitty is version 1.2.2 -> In Django admin-Panel (/mailman3/admin/) I added 2 Websites test1.xyz.de and test2.xyz.de -> In Postorius (/mailman3/postorius/domains/) I added 2 Domains as Mail Hosts test1.xyz.de and test2.xyz.de with the corresponding Web hosts as stated above -> I added 1 list (/mailman3/postorius/lists/) for each Mail Domain as follows: test1(a)test1.xyz.de and test2(a)test2.xyz.de -> then created a vhost in apache2 with SSL-cert and added the Domains in ALLOWED_HOSTS: test1.xyz.de and test2.xyz.de -> When I go to the 2 Testdomains (corresponding web hosts), I see on each both lists for the different Mail domains What do I miss? Or where to investigate? Thank you in advance, best regards. By the way: what'S the difference in the 2 docs? https://docs.mailman3.org/en/latest/index.html and https://mailman.readthedocs.io/en/latest/README.html Am 18.03.21 um 21:52 schrieb Mark Sapiro: > On 3/18/21 9:20 AM, jens.guenther(a)posteo.de wrote: >> Is it possible, to only show publicly (if advertised) these lists on a certain url, that are corresponding to the web host the url I accessed mailman through? > > Set FILTER_VHOST = True in your settings_local.py or where ever you put > your site Django settings. > >

5 years, 3 months

[MM3-users] Re: Pb with archive display

by Mark Sapiro

On 5/5/22 08:02, Pierre Malard via Mailman-users wrote: > > Unfortunately we still don't have any archives... > > Here are the logs retrieved from the mailman.log logs: > May 05 15:59:42 2022 (579075) Exception in the HyperKitty archiver: {"error": "character with byte sequence 0xe2 0x80 0x99 in encoding \"UTF8\" has no equivalent in encoding \"LATIN1\"\n"} > raise ValueError(result.text) > ValueError: {"error": "character with byte sequence 0xe2 0x80 0x99 in encoding \"UTF8\" has no equivalent in encoding \"LATIN1\"\n"} > > And in mailman-web.log: > WARNING 2022-05-05 13:58:52,996 579167 hyperkitty.views.mailman Could not archive the email with message-id '<C7E61653-D399-466A-BEC3-CE61D567E870(a)teledetection.fr>': character with byte sequence 0xe2 0x80 0x99 in encoding "UTF8" has no equivalent in encoding "LATIN1" > > Is it a way? > > I don't understand the message about LATIN1. > It seems to me that UTF-8 was the encoding retained in Mailman. I too don't understand what's trying to encode as LATIN1. The particular byte sequence is a utf-8 encoding of right single quote (’) which has no LATIN1 equivalent, but there's not enough info in the logs for me to determine exactly what's going on. There is an issue with MySQL and derivatives if that's the database you are using. You need the MySQL encoding to be UTF8MB4. in the DATABASES definition in your django settings you want ``` 'OPTIONS': {'charset': 'utf8mb4'} # Enable utf8 4-byte encodings. ``` but that doesn't seem to be the issue here. I suspect this issue has to do with the particular message. When mailman-hyperkitty processes the queue and a queued message throws an exception, it just dies. You might try moving aside the first (in alphanumeric sequence) message in /var/lib/mailman3/archives/hyperkitty/spool and see if the remaining messages can be processed. If that works I would like to see that message's .pck file. -- 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: Block members from sending cc's and bcc's

by Cathryn McGuire

Hi Mark, 1. Since this post in July, I've been trying to work with EMWD to get the cc's blocked. I've tried every rule configuration in the Header Filter to no avail. EMWD can't seem to help. The setting options are as follows: Acceptable aliases This is a list, one per line, of addresses and regexps matching addresses that are acceptable in To: or Cc: in lieu of the list posting address when 'require_explicit_destination' is enabled. Entries are either email addresses or regexps matching email addresses.Regexps are entries beginning with '^ and are matched against every recipient address in the message. The matching is performed with Python's re.match () function, meaning they are anchored to the start of the string. 2. Require Explicit Destination (this is a checked box. Could it be interfering with the Header filters?) This checks to ensure that the list posting address or an acceptable alias explicitly appears in a To: or Cc: header in the post. 3. Default action to take when a member posts to the list Accept immediately (bypass other rules) Default action to take when a member posts to the list. Hold: This holds the message for approval by the list moderators. Reject: this automatically rejects the message by sending a bounce notice to the post's author. The text of the bounce notice can be configured by you. Discard: this simply discards the message, with no notice sent to the post's author. Accept: accepts any postings without any further checks. Default Processing: run additional checks and accept the message. NOTE - when set here, all members are blocked. 4. We also have the problem of large image file sizes being let through no matter what setting we have. We have it set to 500KB, but everything is accepted. Maximum message size 500 The maximum allowed message size in KB. This can be used to prevent emails with large attachments. A size of 0 disables the check. Perhaps some settings are over-riding others? What do you think? Best, Cathryn

7 months, 4 weeks

[MM3-users]Re: [Mailman-Users] Mailman3 administration

by Mark Sapiro

On 6/24/16 8:18 AM, John Griessen wrote: > On 06/18/2016 02:10 PM, Mark Sapiro wrote: >> I think in the >> long run, you'd be better off with Mailman 3. > > > Is it time to install version 3? > > Is that going to work with different rewrite rules behind nginx? > > Will it cure my problem with moderation and nginx and https? If you are going to post to mailman-users(a)mailman3.org, please join the list. That way you will see replies to your posts such as the one at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. You can join at <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/>. The reply addresses your first question. With respect to your other questions, I think you have resolved your http/https issues in MM 2.1. MM 3 works similarly, but perhaps more obviously. When you create a domain in MM3 you specify a web URL for the domain's web UI. If this is an https URL, you won't have the issues you saw. There is another way to address this, and that's in the web server (nginx in your case) when you configure the web server to redirect http to https with a 301 Moved Permanently status (or maybe a 302), this tells the browser to issue a GET for the new URI, even if the original request was a POST. Thus the POST data is lost. That is the underlying issue. If instead, you configure the web server to issue a 308 Permanent Redirect instead, this tells the browser to issue a request for the new URI using the original GET/POST/whatever method, so the browser SHOULD reissue the original POST to the new URI. This will work provided the browser recognizes 308 and acts appropriately. Thus, fixing the scheme in Mailman is the more reliable solution as it doesn't depend on the browser knowing what to do. See, e.g., <https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#3xx_Redirection>. -- 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] parallel processing of out queue messages

by Stephen J. Turnbull

Dan Caballero writes: > I have tried increasing the number of runners to alleviate a > backlog of messages in the "out" queue. I increased the out runners > to from 32 to 64. How many messages per day are you processing?! How many CPUs do you have? How much memory? I know a site with 2 in runners and 8 out runners on something basically the same as a 8CPU 16GB premium Linode. It processes over 100,000 messages/day. The out queue occasionally gets in double digits but 99% of the time it's back at 0/1 in 3 seconds. Load average is usually around 5, CPU utilization 50-80%. I'm not sure it needs 2 in runners or 8 out runners, but it definitely needs at least 4 out runners. (We haven't tested a 4-runner configuration since resolving the "runner stall" issue described below. Virtual CPUs are not at a premium at that client.) > Is there another configuration needed beyond the number of runner > instances to get more messages processed at once? No, the slicing algorithm is trivial, the only upper bound (if you have enough memory ;-) is 2^160. One thing we ran into on the system above was some (still unidentified) issue between Mailman and its SMTP out gateway that caused an out runner to stall for extended periods (sometimes it would restart, often not, nothing interesting in the log). Unfortunately I don't have the monitoring tool we used, but it's easy to create one. The slicing algorithm is based on the file name, and divides the space of SHA1 hash values into N contiguous regions of each length.[1] Get a directory listing of the out queue, count each slice's length. If you see one (rarely more) that just keeps increasing, that's it. You can also use utilities like lsof to keep tabs on the connections to the outgoing SMTP gateway (connections are identified by the source port). If one lasts more than 5 seconds, that's it. Footnotes: [1] The slicing algorithm is in the __init__ function in mailman/src/mailman/core/switchboard.py.

2 years, 8 months

[MM3-users] Trouble importing a Mailman 3 Postgres database into a new Mailman 3 instance (Docker)

by skenny＠scss.tcd.ie

Our in-production Mailman 3 service is running under Docker (maxking's mailman-web, mailman-core and Postgres database containers). I want to move Mailman to a different server, where I have a clean install of Mailman 3 up and running. When I take a database dump of the in-production database, and import it on the new server, a ton of errors are produced, and the core and web containers die after 15 seconds or so. I have noticed that if I first delete the mailmandb database on the new server, then create it anew, and _then_ do the import, everything is fine. I see all my lists in the web interface on the new server, it's all good. But deleting and then creating a new blank mailmandb database just prior to importing ... it can't be the right thing to do. Below is a sample of the errors that are reported on the stdout from my docker-compose command. I'd be very grateful for any pointers as to where to go next with this. Many thanks in advance, Stephen Kenny database_1 | ERROR: relation "auth_permission_id_seq" already exists database_1 | STATEMENT: CREATE SEQUENCE public.auth_permission_id_seq database_1 | START WITH 1 database_1 | INCREMENT BY 1 database_1 | NO MINVALUE database_1 | NO MAXVALUE database_1 | CACHE 1; database_1 | ERROR: insert or update on table "_request"well violates foreign key constraint "_request_mailing_list_id_fkey" database_1 | DETAIL: Key (mailing_list_id)=(774) is not present in table "mailinglist". database_1 | STATEMENT: COPY public._request (id, key, request_type, data_hash, mailing_list_id) FROM stdin; database_1 | STATEMENT: ALTER TABLE ONLY public.auth_group_permissions database_1 | ADD CONSTRAINT auth_group_permissions_group_id_permission_id_0cd325b0_uniq UNIQUE (group_id, permission_id); database_1 | ERROR: multiple primary keys for table "auth_group_permissions" are not allowed database_1 | STATEMENT: ALTER TABLE ONLY public.auth_group_permissions database_1 | ADD CONSTRAINT auth_group_permissions_pkey PRIMARY KEY (id); database_1 | ERROR: multiple primary keys for table "auth_group" are not allowed database_1 | STATEMENT: ALTER TABLE ONLY public.auth_group database_1 | ADD CONSTRAINT auth_group_pkey PRIMARY KEY (id); database_1 | ERROR: relation "auth_permission_content_type_id_codename_01ab375a_uniq" already exists database_1 | ERROR: relation "account_emailaddress_user_id_2c513194" already exists database_1 | STATEMENT: CREATE INDEX account_emailaddress_user_id_2c513194 ON public.account_emailaddress USING btree (user_id); database_1 | ERROR: relation "account_emailconfirmation_email_address_id_5b7f8c58" already exists database_1 | STATEMENT: CREATE INDEX account_emailconfirmation_email_address_id_5b7f8c58 ON public.account_emailconfirmation USING btree (email_address_id); database_1 | ERROR: relation "account_emailconfirmation_key_f43612bd_like" already exists database_1 | STATEMENT: CREATE INDEX account_emailconfirmation_key_f43612bd_like ON public.account_emailconfirmation USING btree (key varchar_pattern_ops); database_1 | ERROR: constraint "hyperkitty_tagging_thread_id_ab30508b_fk_hyperkitty_thread_id" for relation "hyperkitty_tagging" already exists database_1 | STATEMENT: ALTER TABLE ONLY public.hyperkitty_tagging database_1 | ADD CONSTRAINT hyperkitty_tagging_thread_id_ab30508b_fk_hyperkitty_thread_id FOREIGN KEY (thread_id) REFERENCES public.hyperkitty_thread(id) DEFERRABLE INITIALLY DEFERRED; database_1 | ERROR: constraint "hyperkitty_tagging_user_id_9af832e2_fk_auth_user_id" for relation "hyperkitty_tagging" already exists database_1 | STATEMENT: ALTER TABLE ONLY public.hyperkitty_tagging database_1 | ADD CONSTRAINT hyperkitty_tagging_user_id_9af832e2_fk_auth_user_id FOREIGN KEY (user_id) REFERENCES public.auth_user(id) DEFERRABLE INITIALLY DEFERRED; and finally .... mailman-core | Traceback (most recent call last): mailman-core | File "/usr/bin/mailman", line 8, in <module> mailman-core | sys.exit(main()) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1130, in __call__ mailman-core | return self.main(*args, **kwargs) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1054, in main mailman-core | with self.make_context(prog_name, args, **extra) as ctx: mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 920, in make_context mailman-core | self.parse_args(ctx, args) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1613, in parse_args mailman-core | rest = super().parse_args(ctx, args) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1378, in parse_args mailman-core | value, args = param.handle_parse_result(ctx, opts, args) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 2360, in handle_parse_result mailman-core | value = self.process_value(ctx, value) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 2322, in process_value mailman-core | value = self.callback(ctx, self, value) mailman-core | File "/usr/lib/python3.8/site-packages/mailman/bin/mailman.py", line 95, in initialize_config mailman-core | initialize(value) mailman-core | File "/usr/lib/python3.8/site-packages/mailman/core/initialize.py", line 218, in initialize mailman-core | initialize_2(propagate_logs=propagate_logs) mailman-core | File "/usr/lib/python3.8/site-packages/mailman/core/initialize.py", line 177, in initialize_2 mailman-core | config.db = getUtility(IDatabaseFactory, utility_name).create() mailman-core | File "/usr/lib/python3.8/site-packages/mailman/database/factory.py", line 55, in create mailman-core | SchemaManager(database).setup_database() mailman-core | File "/usr/lib/python3.8/site-packages/mailman/database/factory.py", line 84, in setup_database mailman-core | current_rev = context.get_current_revision() mailman-core | File "/usr/lib/python3.8/site-packages/alembic/runtime/migration.py", line 435, in get_current_revision mailman-core | raise util.CommandError( mailman-core | alembic.util.exc.CommandError: Version table 'alembic_version' has more than one head present; please use get_current_heads() mailman-core exited with code 1 mailman-web | Compiling locale files in /usr/lib/python3.8/site-packages mailman-web | Traceback (most recent call last): mailman-web | File "/opt/mailman-web/manage.py", line 10, in <module> mailman-web | execute_from_command_line(sys.argv) mailman-web | File "/usr/lib/python3.8/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line mailman-web | utility.execute() mailman-web | File "/usr/lib/python3.8/site-packages/django/core/management/__init__.py", line 363, in execute mailman-web | settings.INSTALLED_APPS mailman-web | File "/usr/lib/python3.8/site-packages/django/conf/__init__.py", line 82, in __getattr__ mailman-web | self._setup(name) mailman-web | File "/usr/lib/python3.8/site-packages/django/conf/__init__.py", line 69, in _setup mailman-web | self._wrapped = Settings(settings_module) mailman-web | File "/usr/lib/python3.8/site-packages/django/conf/__init__.py", line 170, in __init__ mailman-web | mod = importlib.import_module(self.SETTINGS_MODULE) mailman-web | File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module mailman-web | return _bootstrap._gcd_import(name[level:], package, level) mailman-web | File "<frozen importlib._bootstrap>", line 1014, in _gcd_import mailman-web | File "<frozen importlib._bootstrap>", line 991, in _find_and_load mailman-web | File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked mailman-web | File "<frozen importlib._bootstrap>", line 671, in _load_unlocked mailman-web | File "<frozen importlib._bootstrap_external>", line 848, in exec_module mailman-web | File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed mailman-web | File "/opt/mailman-web/settings.py", line 65, in <module> mailman-web | MAILMAN_ARCHIVER_FROM = (os.environ.get('MAILMAN_HOST_IP', gethostbyname(os.environ.get('MAILMAN_HOSTNAME', 'mailman-core'))),) mailman-web | socket.gaierror: [Errno -2] Name does not resolve mailman-web | python3: can't open file 'manage.py': [Errno 2] No such file or directory mailman-web exited with code 2

3 years, 10 months

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 12/14/22 13:40, Jeremy Stanley wrote: > > Once these entries are automatically added by visiting that page, > they're all associated with the one "web host" ("site" in Django) we > have for the server, and now the list filtering functionality in > Postorius breaks and any of the vhosts all display the full set of > mailing lists on the server rather than only those associated with a > particular vhost (note that this seems to only be confusing > Postorius, Hyperkitty has them correctly filtered still). See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and also below. > Okay, so it looks like this is because the mail hosts are all tied > to the one web host. Yes. > We can create additional "sites" in the Django > admin UI and then switch the association of the mail hosts to those > distinct web hosts. But after doing so, the first vhost still seems > to show an unfiltered list of all lists in Postorius (Hyperkitty > continues to be fine), while Postorius on the other vhosts correctly > shows their filtered sets of lists instead. > > I also noticed when mailman-web is starting up, its log claims the > first site is being set as the "default domain," so have to wonder > if that's related to this behavior. Should we create an extra web > host to serve as the "default" so that all our typical vhosts get > the expected list filtering behavior, or am I completely off-base > and there's a much better approach I've missed? I'm not really sure what's going on here. You could try creating a dummy default host to see if that fixes the issue for you. There are subtle differences in the implementation between HyperKitty and Postorius that allow HyperKitty to work better, but it too will exhibit some anomalous behaviors. -- 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: Apache+mod_wsgi issue

by Odhiambo Washington

On Fri, Dec 23, 2022 at 4:29 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/22/22 16:03, Odhiambo Washington wrote: > > > > There is just one more thing - I have this in settings.py: > > LOGGING['handlers']['file']['filename'] = > > '/opt/mailman/mm/var/logs/mailmanweb.log' > > > And what are LOGGING['handlers']['file']['level'], > LOGGING['handlers']['file']['class'] and > LOGGING['handlers']['file']['formatter'] > Those are left as defaults in my setup.py. > > However, the referenced file is ever empty. At what point is it supposed > to > > record anything? > > What is logged depends on `level` but even with `DEBUG` not much routine > stuff is logged. See https://docs.djangoproject.com/en/3.2/topics/logging/ I will read that and see if I get to pick up something. And now I am having a problem with mod_wsgi. First, the URL displayed when I load the page looks bogus to me. While I expect the URL to be https://mm3-lists.kictanet.or.ke/mailman3/domains/, mod_wsgi give me https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - there is an extra /mailman3! So I have; 1. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/ - working, or appears to. 2. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - working, or appears to. 3. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/bans/ - working, or appears to 4. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/users - working, or appears to 5. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/kictanet.lists.kic… - This throws an exception error when I click "Manage Subscription". -> https://pastebin.ubuntu.com/p/RkKH793Jgw/ And while I do not quite understand the error itself, there is also one particular line that I also saw that has left me baffled: [Fri Dec 23 08:53:18.290411 2022] [core:info] [pid 91236] [client 197.232.81.246:13865] AH00128: File does not exist: /usr/local/www/apache24/data/archives/list/ kictanet(a)lists.kictanet.or.ke/thread/VIHCC6MSXZSNHY7YPEJ3D2US4N7MHJEC/, refe rer: https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 5 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 Jered Floyd

This is due to a change in the dependencies. You can either demand an older version of django-allauth when doing your install, or I fixed it with this line added to the very end of my settings.py: # Fix for updated django-allauth MIDDLEWARE += ('allauth.account.middleware.AccountMiddleware',) --Jered ----- On Oct 19, 2023, at 7:27 AM, Wikinaut mail(a)tgries.de wrote: > I followed all single steps until this: > https://docs.list.org/en/latest/install/virtualenv.html#run-database-migrat… > (I will improve the documentation with the missing parts later today), > > Now I got this and got stucked and need your help: > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE > > full stack: > (venv) mailman@mail:/run$ mailman-web migrate > Traceback (most recent call last): > File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> > sys.exit(main()) > ^^^^^^ > File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_web/manage.py", > line 37, in main > execute_from_command_line(sys.argv) > File > "/opt/mailman/venv/lib/python3.11/site-packages/django/core/management/__init__.py", > line 446, in execute_from_command_line > utility.execute() > File > "/opt/mailman/venv/lib/python3.11/site-packages/django/core/management/__init__.py", > line 420, in execute > django.setup() > File "/opt/mailman/venv/lib/python3.11/site-packages/django/__init__.py", line > 24, in setup > apps.populate(settings.INSTALLED_APPS) > File "/opt/mailman/venv/lib/python3.11/site-packages/django/apps/registry.py", > line 124, in populate > app_config.ready() > File "/opt/mailman/venv/lib/python3.11/site-packages/allauth/account/apps.py", > line 15, in ready > raise ImproperlyConfigured( > > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

2 years, 8 months

Search results for query "dO"