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

[MM3-users] Re: Why is it VERPing every message?

by Mark Sapiro

On 6/23/26 3:31 PM, Paul Tomblin via Mailman-users wrote: > So i was going down the rabbit hole of why every outgoing message for a certain 500+ member list is being VERPed, which lead to RoadRunner/Spectrum complaining about too many connections, and I tried to look at the verp configuration: > > (venv) *mailman@mail*:*~*$ mailman conf |grep verp > [mta] verp_confirm_format: $address+$cookie > [mta] verp_confirm_regexp: ^(.*<)?(?P<addr>[^+]+?)\+(?P<cookie>[^@]+)@.*$ > [mta] verp_confirmations: yes > [mta] verp_delimiter: + > [mta] verp_delivery_interval: 1 > [mta] verp_format: ${bounces}+${local}=${domain} > [mta] verp_owner_notifications: yes > [mta] verp_personalized_deliveries: yes > [mta] verp_probe_format: $bounces+$token@$domain > [mta] verp_probe_regexp: ^(?P<bounces>[^+]+?)\+(?P<token>[^@]+)@.*$ > [mta] verp_probes: no > [mta] verp_regexp: ^(?P<bounces>[^+]+?)\+(?P<local>[^=]+)=(?P<domain>[^@]+)@.*$ > > I'm quite confused about why verp_delivery_interval is 1 instead of the default 0, and why verp_probes is no. I did make sure that "Personalize" was set to None. > I tried to override them in mm/var/etc/mailman.cfg, but it seems to be having no effect, even after restarting mailman. > Is this not the correct syntax: > [mta] > verp_delivery_interval: 0 > verp_probes: yes > > Is something else overriding my mailman.cfg setting? Are you sure mm/var/etc/mailman.cfg is the actual mailman.cfg in use. `mailman info` will tell you. > I do have a list:member:regular:footer but it doesn't have any user information in it, so that shouldn't cause it to do the messages individually, should it? No, the footer has nothin to do with it. I suspect you may have installed following <https://docs.mailman3.org/en/latest/install/virtualenv.html> in which case yoor mailman.cfg is /etc/mailman3/mailman.cfg and I suspect that file has `verp_delivery_interval: 1` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: The future is here?

by Mark Sapiro

On 1/3/21 3:47 PM, ieso(a)johnwillson.com wrote: > > Any ideas on what might cause that? More context below.. > > [uwsgi-daemons] respawning "python3 manage.py qcluster" (uid: 33 gid: 33) > Traceback (most recent call last): > File "manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 364, in execute_from_command_line > utility.execute() > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 356, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 206, in fetch_command > klass = load_command_class(app_name, subcommand) > File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 40, in load_command_class > module = import_module('%s.management.commands.%s' % (app_name, name)) > File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1006, in _gcd_import > File "<frozen importlib._bootstrap>", line 983, in _find_and_load > File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 677, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 728, in exec_module > File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed > File "/usr/lib/python3/dist-packages/django_q/management/commands/qcluster.py", line 4, in <module> > from django_q.cluster import Cluster > File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 24, in <module> > from django_q import tasks > File "/usr/lib/python3/dist-packages/django_q/tasks.py", line 12, in <module> > from django_q.cluster import worker, monitor > ImportError: cannot import name 'worker' from 'django_q.cluster' (/usr/lib/python3/dist-packages/django_q/cluster.py) This is a django_q issue. Apparently <https://github.com/Koed00/django-q/issues/331>, fixed by <https://github.com/Koed00/django-q/pull/356> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: disabled users

by Mark Sapiro

On 10/25/23 10:44 AM, Stephen J. Turnbull wrote: > Servizio Informatico U.I.C.I. Sezione territoriale di Brescia writes: > > > Wher I find the disabled user of a mailing list and wher I can > > reactivate them? > > If you are the list owner or superuser, when you visit the list's > information page there will be a horizontal menu across the top. One > of the entries is Users. Click to open the dropdown menu and choose > Members. There doesn't seem to be an explicit notation for disabled > users, but if the entry in the far right column "bounce score" is > None, the member may be disabled. I don't think this is correct. Members with delivery disabled by bounce will normally show 0 rather than None for bounce score. If you have shell access to the server as the Mailman user, you can run this shell interaction to find members with delivery disabled by bounce. ``` $ mm/bin/mailman shell -l test(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the test(a)example.com mailing list >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print(member.address.email) ... >>> ``` But the question is, why do you want to re-enable their delivery. Granted, there are situations such as a misconfigured MTA or not applying needed DMARC mitigations that could result in 'spurious' bounced deliveries, but normally bounce processing disables delivery, sends warnings to the bouncing address and ultimately unsubscribes them because the address it truly not deliverable. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Running Mailman3 v3.2.1 on Devuan 10.0, getting a pid permissions error on Mailman3-web

by Mark Sapiro

On 2/9/21 10:17 AM, rainbear(a)gmail.com wrote: > # service mailman3-web stop > [....] Stopping Mailman3-web uWSGI service: mailman3-webstart-stop-daemon: matching on world-writable pidfile /run/mailman3-web/mailman3-web.pid is insecure > > # ls -l /run/mailman3-web/mailman3-web.pid > -rw-rw-rw- 1 root root 6 Feb 9 13:00 /run/mailman3-web/mailman3-web.pid This would appear to be either a Debian or uWSGI issue. In my case, I use gunicorn as the WSGI interface to Django, and on the server that supports this list, I have > $ cat /etc/init/gunicorn.conf > description "gunicorn for Mailman" > > start on runlevel [2345] > stop on runlevel [016] > > respawn > respawn limit 10 5 > > setuid mailman > setgid mailman > > chdir /opt/mailman/mm/ > > exec /opt/mailman/mm/bin/gunicorn -c /opt/mailman/mm/deployment/gunicorn.conf mailman_web.wsgi:application > $ cat /opt/mailman/mm/deployment/gunicorn.conf > bind = ['127.0.0.1:8000'] > proc_name = "mailman-web" > 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" > #daemon = True > workers = 4 > # Increase timout to allow downloading large archive mboxes. > # Note even 300 is not enough for the entire python-dev(a)python.org archive. > # I added 'disallow: /*/export/' to robots.txt to try to stop crawlers. > timeout = 120 > $ ll /opt/mailman/mm/var/gunicorn.pid > -rw-r--r-- 1 mailman mailman 6 Feb 7 00:13 /opt/mailman/mm/var/gunicorn.pid Some other servers I manage use systemd rather than upstart, but the permissions on the PIP file are the same. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: mailman3 exim4 and debian 1 problem fconnection lost

by Mark Sapiro

On 5/6/21 12:03 AM, roberto Burceni wrote: > [Mailman-Users] mailman3 and exim4 problem in debian bullseye > Good evening, > I'm configuring mailman3 with exim4 on a debian 11. > I followed the official documentation on mailman for exim. It seems to > be all rights, but I have a problem: > when I send a message to a new lists in exim logs I see that exim uses > correctly mailman router and transport. > Unfortunately in smtp.log in mailman3 log folder I have the following > error: > May 04 16:51:01 2021 (2337) ('127.0.0.1', 34746) sender: > servizioinformatico(a)uicbs.it > May 04 16:51:01 2021 (2337) ('127.0.0.1', 34746) Data: b'RCPT TO: > <listtest-unsubscribe(a)uicbs.it>' > > May 04 16:51:01 2021 (2337) ('127.0.0.1', 34746) recip: > listtest-unsubscribe(a)uicbs.it > May 04 16:51:01 2021 (2337) ('127.0.0.1', 34746) Data: b'DATA' > May 04 16:51:02 2021 (2337) ('127.0.0.1', 34746) Data: b'QUIT' > May 04 16:51:02 2021 (2337) ('127.0.0.1', 34746) connection lost > May 04 16:51:02 2021 (2337) Connection lost during _handle_client() > > This causes that messages are not sent from mailman to users. Have you > an idea of the problem? The connection lost messages are normal and not an error and not the cause of the message not being delivered to the list members. > I have no other errors in other log files What other log messages are there that might relate to this? Is mailman core running? Are there any entries in mailman's queues? Is the message Archived? Without more information, I can't say why the message isn't delivered. I can only say for certain the the smtp.log messages you show above are not related to the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Mailman3 / Exim4: Router fails

by Mark Sapiro

On 5/22/23 07:44, Stephen J Turnbull wrote: > From: "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> > To: ceo(a)sartrack.nz > ... > > > But it fails with this: > > MM3_LISTCHK=/var/lib/mailman3/lists/${local_part}@${domain} > > For reasons I do not understand, although Mailman 3 keeps list > configurations in the RDBMS, when it creates a list it *also* > "touches" a directory for that list in the directory $var_dir/lists. > (If I remember correctly, these are empty. It's a real directory, not > "virtual".) Since I already knew how to search for the > lists/$LIST/config,pck file used by Mailman 2, I used the same method > for Mailman 3. That directory is used to store messages being accumulated for the next digest in a digest.mmdf mailbox file. > $var_dir is set somewhere near the top of mailman.cfg. I don't know > where to find that file in your installation, it's often in > /etc/mailman3. `mailman conf -k var_dir` will show the setting for $var_dir for various layouts and `mailman conf -k layout` will show the layout in use. > Later you wrote: > > > mailman3 create templist(a)sartrack.nz templist.lists.sartrack.nz (?) > > I tried to create it as: > > create templist(a)sartrack.nz templist(a)sartrack.nz > > but it would not accept that. > > I believe that's because "mailman create" wants the posting address > and the list ID. It just wants the posting address, not the list ID. I.e. mailman create templist(a)sartrack.nz `create` is a subcommand of the `mailman command. `create` by itself as opposed to `mailman create` looks like an artifact from cPanel's Mailman 2.1. -- 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: Importing config and archives only partially succeeded?

by Mark Sapiro

On 12/12/20 7:40 PM, Eric Broens via Mailman-users wrote: > There are no messages in var/archives/hyperkitty/spool/. At this time of the night (4:40 AM local time), there is no incoming mail. I'm not sure what is causing the repeated access of /archives/api/mailman/urls... This call comes from Mailman core in order to request the URL at which a message will be archived. It is called from mailman/src/mailman/handlers/rfc_2369.py when adding the Archived-At: header and from mailman/src/mailman/handlers/decorate.py in order to get the hyperkitty_url replacement value. I don't understand why it would be called repeatedly for the same message. Are there any clues in mailman.log. > I just noticed when clicking on "All Threads" or "Threads by month", the emails are displayed. The statistic however shows that there were no mails in the past month, while there actually are.When clicking "Recent", "Most Active", etc. the page shows "No discussions this month (yet)." What if you look at "threads by month" and select the current month? > Another observation. For one list, which is one of the more active ones, the bar diagram is not empty, while showing 0 participants and 0 discussions (see attached screenshot).This one however shows the mailthreads when opening the list. I think the basic issue is when you see no messages, HyperKitty, for whatever reason thinks there are no current messages. I'm not sure, but if there are recent posts, are they all in threads started more than 30 days ago? As far as all the participants/discussions counts being zero, I think one of the periodic jobs will fix that (possibly the daily recent_threads_cache job) -- 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: mailman-web migrate error

by Mark Sapiro

On 11/12/25 11:48, pashdown(a)xmission.com wrote: > I'm migrating from Ubuntu 20.04, mailman 3.2.2, postgresql 12 to Debian 13, mailman 3.3.10, postgresql 17. > > After migrating the postgresql databases and assuring the perms and passwords work, this is what I get with a "mailman-web migrate": > > (user(a)domain.com) redacted from the original > > # mailman-web migrate > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, \ > sessions, sites, socialaccount > Running migrations: > Applying account.0003_alter_emailaddress_create_unique_verified_email... OK > Applying account.0004_alter_emailaddress_drop_unique_email... OK > Applying account.0005_emailaddress_idx_upper_email... OK > Applying account.0006_emailaddress_lower...Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 89, in _execute > return self.cursor.execute(sql, params) > ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^ > psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "account_emailaddress_user_id_\ > email_987c8728_uniq" > DETAIL: Key (user_id, email)=(24, user(a)domain.com) already exists. This is actually a django-allauth issue. This issue is due to changes in Django allauth to prevent creating multiple addresses differing only in case. The problem is if you have such multiple addresses in your account_emailaddress table, this migration fails. There is a script at https://www.msapiro.net/scripts/UC_fix that will fix this. You may need to adjust the shebang and replace psycopg2 with sqlite3. See https://github.com/pennersr/django-allauth/issues/3019 perhaps starting at This issue is due to changes in Django allauth to prevent creating multiple addresses differing only in case. The problem is if you have such multiple addresses in your account_emailaddress table, this migration fails. There is a script at https://www.msapiro.net/scripts/UC_fix that will fix this. You may need to adjust the shebang. See https://github.com/pennersr/django-allauth/issues/3019 perhaps starting at https://github.com/pennersr/django-allauth/issues/3019#issuecomment-1748028… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

[MM3-users] Re: Creating superuser - problem with documentation or it's just me?

by Mark Sapiro

On 7/26/20 9:39 AM, Odhiambo Washington wrote: > Hi, > > In my quest to create a superuser, I followed another HOWTO - > https://docs.mailman3.org/en/latest/devsetup.html > > (venv) [root@gw /opt/mailman/git/mailman-suite/mailman-suite_project]# > python manage.py migrate > Traceback (most recent call last): manage.py migrate (or django-admin migrate) is part if the mailman-post-update script. It doesn't work here because when you run it this way, it doesn't get your settings.py. > ModuleNotFoundError: No module named '_sqlite3' And it's looking for sqlite3 because that's the default database. > *<==============================================================* > (venv) [root@gw /opt/mailman/git/mailman-suite/mailman-suite_project]# pip > install pysqlite3 You don't need this. You need to run django-admin with the correct settings. > So I figured out that I need to put my own settings_local.py into the > directory and let the command rely on MySQL as the database backend since > by default, it uses sqlite3 backend. > > But the question then is WHY is this not documented on the above page??? Because that's not relevant to what you are doing. You are trying to install Mailman for production, not development. > How can I delete the superuser after creating it?? The only django-admin or manage.py you should run is /opt/mailman/mm/bin/djhango-admin. You can run `django-admin createsuperuser` to create a superuser. If you want to delete one, you need to go to the Django admin web UI - should be http://your.server/admin - login as a superuser and go to the Users page and delete it. You should probably do this as a different 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, 2 months

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

by Mark Sapiro

On 3/22/24 09:48, David Partain via Mailman-users wrote: > > Right now, archiving is not working on the new installation, both building the archive on the new installation after the move and for new messages. > > uwsgi-error.log is getting blasted with constant errors along the lines of what follows. I suspect that these errors are why archiving isn't working, but I obviously don't know that: > > Message: BadSignature('Signature "ZWBXqQmWZwHTfa390lLIacpp8NQ" does not match') I'm not sure if this is the issue with archiving or not. > What we have in our config files on the old installation and new installation are (the quotes are exactly as they are in the files): ... > settings.py > > SECRET_KEY = 'somerandomstringiaintputtinginmail' > MAILMAN_ARCHIVER_KEY = 'somerandomstringiaintputtinginmail' > > mailman-hyperkitty.cfg > > api_key: somerandomstringiaintputtinginmail > > All of that says that the value is the same for all three (whether I should have done so or not...) and those settings were carried along to the new installation as well. See my reply at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… As I say there, SECRET_KEY is not related in any way to MAILMAN_ARCHIVER_KEY and api_key. The latter two have to do with archiving and must match. The former is a Django thing and is completely separate. At this point, put ``` SECRET_KEY_FALLBACKS = [ 'F6V0Dr_SvBsx5-cY8vcvLXrX8tA', 'ZWBXqQmWZwHTfa390lLIacpp8NQ', ] ``` in your local Django settings file. If you continue to get BadSignature: Signature "..." does not match' errors, add those unmatched signatures to SECRET_KEY_FALLBACKS. Once you are no longer seeing BadSignature errors, if archiving is still not working, report any errors you are seeing from Mailman's mailman.log and Django's log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

Search results for query "sapiro"