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

[MM3-users] Re: configuring postfix local recipient table

by Odhiambo Washington

On Wed, Apr 30, 2025 at 2:55 PM Alexander Inzinger-Zrock via Mailman-users < mailman-users(a)mailman3.org> wrote: > Splitting up answer: > > Am 29.04.25 um 18:27 schrieb Mark Sapiro: > > Also, is there anything in Mailman's logs from the time you ran `mailman > > aliases`? > > Nothing in logs (before or) after command ''mailman aliases'' > and debug level everywhere is: info. > > What logs? > Everything under /opt/mailman/mm/var/logs: > > + bounce.log > + debug.log > + mailman.log > + plugins.log > + smtp.log > > All empty. > ^^^^^^^^^^^ mailman.log should never be empty. At the least, it will contain some entries about task runners, like: ``` [30/Apr/2025:14:00:01 +0300] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 477 "-" "GNU Mailman REST client v3.3.5" Apr 30 14:18:22 2025 (54456) Task runner evicted 0 expired pendings Apr 30 14:18:22 2025 (54456) Task runner deleted 0 orphaned workflows Apr 30 14:18:22 2025 (54456) Task runner deleted 0 orphaned requests Apr 30 14:18:22 2025 (54456) Task runner deleted 0 orphaned messages Apr 30 14:18:22 2025 (54456) Task runner deleted 0 orphaned message files Apr 30 14:18:22 2025 (54456) Task runner evicted 0 expired bounce events Apr 30 14:18:22 2025 (54456) Task runner evicted expired cache entries [30/Apr/2025:15:00:02 +0300] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 477 "-" "GNU Mailman REST client v3.3.5" ``` If those aren't there, then your installation has more problems than you think, IMHO. -- 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]

9 months

[MM3-users] Mailman issues after re-boot

by Paul Rubin

*<< I sent this to the mailman3 issues on gitlab and Mark replied but asked me to move to this list, so I copied everything and inserted responses. I hope this makes sense and someone can help me.>>* After a lengthy power failure I had to reboot a machine that has been running for several years. the WEB-UI does not seem to be able to see mailman-core. I have looked for log entries that might explain what the issue is and I am stumped to even find logs that will update when I get an error on the browser. Mailman is definitely running, postgres is running and mailman web is running. if I go to the lists page I see lists, if I try to access a specific list I get Server error: An error occurred while processing your request. I looked in /var/logs/mailman /opt/mailman/web/mailmanweb All I can find is: django.urls.exceptions.NoReverseMatch: Reverse for 'list_unsubscription_requests' not found. 'list_unsubscription_requests' is not a valid view function or pattern name.16688 ERROR 2023-09-12 13:56:58,430 1760 django.request Internal Server Error: /mailman3/lists/goodstein.goodstein.org/ File "/opt/mailman/venv/lib64/python3.8/site-packages/haystack/admin.py", line 8, in <module> from django.utils.translation import ungettextImportError: cannot import name 'ungettext' from 'django.utils.translation' (/opt/mailman/venv/lib64/python3.8/site-packages/django/utils/translation/__init__.py) Also I have to run mailman from "mailman start" because the systemctl returns this: ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2023-09-12 10:06:31 EDT; 13s ago Process: 31159 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=1/FAILURE) CPU: 806msSep 12 10:06:31 mail mailman[31159]: Error in atexit._run_exitfuncs:Sep 12 10:06:31 mail mailman[31159]: Traceback (most recent call last):Sep 12 10:06:31 mail mailman[31159]: File "/usr/lib64/python3.8/logging/__init__.py", line 2126, in shutdownSep 12 10:06:31 mail mailman[31159]: h.flush()Sep 12 10:06:31 mail mailman[31159]: File "/opt/mailman/venv/lib64/python3.8/site-packages/mailman/core/logging.py", line 67, in flushSep 12 10:06:31 mail mailman[31159]: if self._stream:Sep 12 10:06:31 mail mailman[31159]: AttributeError: 'ReopenableFileHandler' object has no attribute '_stream'Sep 12 10:06:31 mail systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURESep 12 10:06:31 mail systemd[1]: mailman3.service: Failed with result 'exit-code'.Sep 12 10:06:31 mail systemd[1]: Failed to start GNU Mailing List Manager. Please tell me where to start looking or adjusting. Reply from Mark Sapiro,* Edited to include responses:* Mark Sapiro <https://gitlab.com/msapiro>@msapiro <https://gitlab.com/msapiro>· 1 day ago <https://gitlab.com/mailman/mailman-web/-/issues/23#note_1557601916> Owner Add reaction More actions The mailman-users(a)mailman3.org list is probably a more appropriate place for issues like this. django.urls.exceptions.NoReverseMatch: Reverse for 'list_unsubscription_requests' not found. 'list_unsubscription_requests' is not a valid view function or pattern name. 16688 ERROR 2023-09-12 13:56:58,430 1760 django.request Internal Server Error: /mailman3/lists/ goodstein.goodstein.org/ /opt/mailman/venv/lib64/python3.8/site-packages/postorius/urls.py should contain re_path( r'^unsubscription_requests$', list_views.list_unsubscription_requests, name='list_unsubscription_requests', ), Y *Yes this exists* and /opt/mailman/venv/lib64/python3.8/site-packages/postorius/views/list.py should define list_unsubscription_requests. *Yes there is a method by this name defined* File "/opt/mailman/venv/lib64/python3.8/site-packages/haystack/admin.py", line 8, in from django.utils.translation import ungettext ImportError: cannot import name 'ungettext' from 'django.utils.translation' (/opt/mailman/venv/lib64/python3.8/site-packages/django/utils/translation/ *init*.py) See https://docs.djangoproject.com/en/4.2/internals/deprecation/#deprecation-re… - ungettext() is removed from django>=4.0 Sep 12 10:06:31 mail mailman[31159]: AttributeError: 'ReopenableFileHandler' object has no attribute '_stream' I don't understand this one offhand, but what is the content of /etc/systemd/system/mailman3.service, in particular the settings for User, Group and ExecStart? *The service looks right:* 1 [Unit] 2 Description=GNU Mailing List Manager 3 After=syslog.target network.target postgresql.service 4 5 [Service] 6 Type=forking 7 PIDFile=/opt/mailman/mm/var/master.pid 8 User=mailman 9 Group=mailman 10 ExecStart=/opt/mailman/venv/bin/mailman start 11 ExecReload=/opt/mailman/venv/bin/mailman restart 12 ExecStop=/opt/mailman/venv/bin/mailman stop 13 14 [Install] 15 WantedBy=multi-user.target *It seems I may have two versions of the mailman script:* mail:/opt/mailman # which mailman /usr/bin/mailman mail:/opt/mailman # ls -al /usr/bin/mailman -rwxr-xr-x 1 root root 382 May 10 2021 /usr/bin/mailman mail:/opt/mailman # ls -al /opt/mailman/venv/bin/mailman -rwxr-xr-x 1 mailman mailman 231 Sep 12 10:02 /opt/mailman/venv/bin/mailman Somehow, your installation is corrupted. I don't know how *I need to know what to remove, how to correctly update, etc., That said the two scripts appear to be very similar:* mail:/opt/mailman # head /usr/bin/mailman #!/usr/bin/python3 # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.4','console_scripts','mailman' __requires__ = 'mailman==3.3.4' import re import sys from pkg_resources import load_entry_point if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) sys.exit( mail:/opt/mailman # head /opt/mailman/venv/bin/mailman #!/opt/mailman/venv/bin/python3 # -*- coding: utf-8 -*- import re import sys from mailman.bin.mailman import main if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0]) sys.exit(main()) mail:/opt/mailman # *Given the two years since the last reboot I also tried following * https://docs.mailman3.org/en/latest/upgrade-guide.html *to make sure I was running the latest* pip install -U mailman postorius django-mailman3 hyperkitty mailman-web

2 years, 4 months

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

On Sat, 13 Mar 2021 22:51:46 -0500, Mark Sapiro wrote: > > On 3/13/21 7:08 PM, John Covici wrote: > > On Sat, 13 Mar 2021 16:22:59 -0500, > > Abhilash Raj wrote: > >> > >> My guess is that you updated the database (perhaps, by invoking the mailman > >> command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes > >> up and sees a new revision for the database migration added from 3.3.3 but > >> can’t find the same migration in its source (because it is 3.3.2). > > > > That is sort of what happened, except in the opposite direction, it > > was from 3.3.3 to 3.3.2. My question is therefore, do I have to > > update this alembic_version when I upgrade mailman to a newer version? > > That is what I was getting at. > > > Abhilash's conjecture is that the error was due to a Mailman version > accessing a database that had been previously accessed by a newer > version so that the version_num in the alembic_version table didn't > exist in mailman/database/alembic/versions/. This normally would not > occur on an upgrade of Mailman, but if you went from a gentoo Mailman > core to a version obtained by pip, it's possible that the gentoo Mailman > had an alembic version that wasn't known to the pip Mailman even though > the pip Mailman was newer. > OK, thanks. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 10 months

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

by Roland Giesler

On 2024/07/28 15:42, Roland Giesler via Mailman-users wrote: > > On 2024/07/28 15:26, Roland Giesler via Mailman-users wrote: >> On 2024/07/28 00:39, Mark Sapiro wrote: >>> On 7/27/24 15:16, Roland Giesler via Mailman-users wrote: >>>> >>>> The server runs power-mailinabox, which uses Postfix indeed. All my >>>> mail, and quite a few others' mail is sent from the using SMTP-Auth >>>> on port 465. Actually, this message is sent via that server too. >>>> So it's clear to me that MM3 is not authenticating for some reason. >>> >>> What do you see in Mailman's smtp.log and in the mail.log on the >>> mail server? >> >> The smtp log is in syslog... > > I also see this in /var/log/mailman3/web/mailman-web.log The /etc/mailman3/mailman3-web.py file contains inter alia these lines: # Set default domain for email addresses. EMAILNAME = 'fast.za.net' # If you enable internal authentication, this is the address that the emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#default-from-email # DEFAULT_FROM_EMAIL = "mailing-lists(a)you-domain.org" DEFAULT_FROM_EMAIL = 'postorius@{}'.format(EMAILNAME) # If you enable email reporting for error messages, this is where those emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL # SERVER_EMAIL = 'root(a)your-domain.org' SERVER_EMAIL = 'root@{}'.format(EMAILNAME) fast.za.net was giesler.za.net before, so I changed it.

1 year, 6 months

[MM3-users] Re: MM3 shunting mails

by Barry Warsaw

On Mar 17, 2017, at 11:22 AM, Mark Sapiro wrote: >The above is the last line of > > exists = store.query(ListArchiver).filter( > ListArchiver.mailing_list == mailing_list, > ListArchiver.name == archiver_name).one_or_none() > >which is querying the archivers enabled for this list for the name of a >system enabled archiver and expects to find at most one entry > >> File "/usr/lib64/python3.4/site-packages/sqlalchemy/orm/query.py", >> line 2733, in one_or_none >> "Multiple rows were found for one_or_none()") > >but finds more than one. > >> sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for >> one_or_none() >> Mar 17 11:54:11 2017 (6217) SHUNTING: >> 1489748051.1949184+7a59df19c81493cb419306d620376efc0e381819 > >So the cause is there appear to be multiple database entries for this >list and some archiver name, but I don't know how that can happen. I don't know either, especially since ListArchiverSet.__init__() has this: # Add any system enabled archivers which aren't already associated # with the mailing list. for archiver_name in system_archivers: exists = store.query(ListArchiver).filter( ListArchiver.mailing_list == mailing_list, ListArchiver.name == archiver_name).one_or_none() if exists is None: store.add(ListArchiver(mailing_list, archiver_name, system_archivers[archiver_name])) It runs the exact same query, and only adds the archiver to the store if it doesn't already exist. What does the following give you? % mailman shell Welcome to the GNU Mailman shell >>> # You may have to use getUtility(...).get() to find the offending list >>> m = list(getUtility(IListManager).mailing_lists)[0] >>> m <mailing list "ant(a)example.com" at 0x7face8b2da20> >>> from mailman.model.mailinglist import ListArchiver >>> q = config.db.store.query(ListArchiver).filter( ... ListArchiver.mailing_list == m) >>> list(a.name for a in q) ['mhonarc', 'prototype', 'mail-archive'] Cheers, -Barry

8 years, 10 months

[MM3-users] Re: # comment allowed in a template file?

by skenny＠scss.tcd.ie

Mark Sapiro wrote: > If you mean can you add a '#' line that won't be part of the actual > rendered template, the answer is No. OK, thanks for the clarification. > > Initially, I created the template files with owner set to "root". This resulted in > > postings to lists getting stuck in mailman-core. It's vital that these files are owned > > by user "mailman". Once I changed the owner of the file to the latter, everything > > worked. > I don't think they need to be owned by 'mailman' as long as they are > readable by 'mailman' Yes, your formulation is a more accurate statement than mine (I could have instead simply relaxed the permissions on the files to make them world-readable). The effect of the template files not being readable by user "mailman" was interesting. Hundreds of lines like the following got written to mailman-core's var/log/smtp.log file at the rate of 4 per second: Jul 23 17:09:54 2020 (25) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fdf9e7b5f28> (the hex number was different each time). Having excessively restrictive permissions on the template files is a silly - but easy enough - mistake to make. If it were possible to add it to Mailman 3, a more descriptive logging message could point others who make it in the right direction, perhaps. I spent a long time trying to figure out why messages weren't getting sent out from Mailman core, and in the end it was luck in form of a colleague's suggestion about file permissions that got me out of the rut. Thanks for the great support, Stephen Kenny

5 years, 6 months

[MM3-users] Re: Change the default value for the General Archive Policy

by Markus Grandpré

Dear Mr Hochstein, Thank you very much for providing the link. I'm afraid the same misunderstanding as with Marc Sapiro has occurred here. I'm aware that there are three different styles to choose from when creating a mailing list. However, the setting "Settings > Archiving > Archive policy" can be configured independently of the list creation process. Still, it would be beneficial if the default value after creating a list without an archive were not "Public archive", but rather "Do not archive this list". This would help prevent list administrators from being tempted to immediately enable a public archive when setting up an archive later—especially in cases where the list is intended to be private. Kind regards, Markus Grandpré Am 6/23/25 um 22:48 schrieb Thomas Hochstein: > Markus Grandpré wrote: > >> currently, when I create a new mailing list with MM3 the value for "Archive policy" is always set to "Public archives". >> I'd like to change the default value for "Archive policy" to "Do not archive this list". How can I do this? > > Perhaps > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > has some pointers how to accomplish that? > > -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 markus.grandpre(a)uni-konstanz.de -- Markus Grandpré Universität Konstanz Kommunikations-, Informations- und Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur Sachgebiet Diensteadministration Tel: ++49 7531 88 4342

7 months, 1 week

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

by Abhilash Raj

> On Nov 2, 2021, at 12:51 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 11/2/21 11:50 AM, bob B wrote: >> So I am teaching myself to fish, and see that it is actually django-admin, so that is in >> mailman-web? (in docker) >> But i get this: >> $ docker exec -it mailman-web /bin/bash >> bash-5.0# django-admin shell >> Python 3.8.10 (default, May 6 2021, 06:30:44) >> [GCC 9.3.0] on linux >> Type "help", "copyright", "credits" or "license" for more information. >> (InteractiveConsole) >>>>> from hyperkitty.models import MailingList >> Traceback (most recent call last): > ... >> raise ImproperlyConfigured( >> django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. > > > Do what it says. I.e. run > > DJANGO_SETTINGS_MODULE=path/to/settings; django-admin shell DJANGO_SETTINGS_MODULE expects a Python import path, instead of a filesystem path. The docker has documentation on running management commands, which in this case is “shell” [1] $ docker exec -it mailman-web python3 manage.py shell [1]: https://asynchronous.in/docker-mailman/web/#django-management-commands I know there are plethora of ways to run Django management commands, but this is the easiest one for docker. django-admin will work too, but you have to be in the right working directory for the import path to work and it get weird. I’ve always disliked how Django management commands work unfortunately and in trying to “fix” that with “mailman-web” (which isn’t adopted by container images), i feel I might have re-invented a third option. -- thanks, Abhilash Raj (maxking)

4 years, 2 months

[MM3-users] Re: How to strip DKIM headers on a domain level or a list level

by Mark Dadgar

On Nov 23, 2020, at 8:00 PM, Joel Lord <jpl(a)ilk.org> wrote: > On 11/23/2020 10:48 PM, Mark Sapiro wrote: >> On 11/23/20 7:22 PM, Mark Dadgar wrote: >>> >>> I also believe that it’s common for unsophisticated users to just start marking list emails as spam stop seeing them instead of figuring out how to unsubscribe. Which really sucks for everyone else. >> Several servers I'm involved with managing are subscribed to Yahoo's >> feedback loop (go to https://help.yahoo.com/kb/postmaster and select >> "Complaint Feedback Loop"). Reporting list mail as spam is one way to >> get quickly removed from a list. However, this is a bit complicated >> because the "report spam" button in Yahoo's web mail UI is right next to >> the "delete" button, so some reports are accidents. > > I've done the same thing, but Yahoo is pretty good at sanitizing their report to make it difficult to impossible to tell who actually needs to get ejected. I added "Sent to %(user_name)s at %(user_address)s" to the footer and while they'd generally get the user_address wiped out, the user_name would generally survive. > > And because Yahoo's UI is flawed as Mark pointed out, with the delete and spam buttons adjacent, I'd usually give people a couple chances before I'd airlock them. Yeah, I’ve been subscribed to the Yahoo feedback loops for ever and ever. If you’ve got verp turned on, you can decode the original address from that in the headers. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 2 months

[MM3-users] Re: mailman3 not working for mailman21 lists

by Diana von Bidder

Hi Stephen On Mon, 2022-08-22 at 23:51 +0900, Stephen J. Turnbull wrote: > blup(a)fortytwo.ch writes: > > Try queue/, especially look for the out[going], pipeline, and shunt > subdirectories. I have several entries in /var/lib/mailman3/queue/shunt/ with Aug 21 timestamps, and several entries in /var/lib/mailman3/queue/shunt/ with current timestamp (i.e. everytime I ls -l there is a new timestamp with the current time). > > > Is the 'outgoing' qrunner still running? (ps ax | grep outgoing) > > > > no > > Sorry, I got that wrong. Mark recommends this: > > ps -fwwA|grep runner=|sed s/.*runner=// > > and gave this as sample output: [..] My output looks exactly the same. > > I have more or less no Python knowledge (i.e. I can read and > > understand Python but can't write it). Could you please give me > > detailed command by command instructions. Thanks. > > I'll take a look at it tomorrow, but I can't promise results until > the weekend if I can't write a script in 30 minutes. Normally Mark > Sapiro would handle this kind of thing, but he's offline for a couple > weeks so you've got me. My knowledge is mostly on the email > protocols side of things (Internet message format, authentication > protocols), not the internal processing. I'll do what I can, but if > I can't do it real quick it's probably going to take me several > hours, which I'm not going to have until the weekend. Having something by the weekend would be perfectly fine. Thanks for your time! Regards Diana

3 years, 5 months

Search results for query "sapiro"