- Mailman-users - lists.mailman3.org

Too Many From Headers
by dap1＠bellsouth.net Nov. 18, 2025

Nov. 18, 2025

I am getting mail bounced from yahoo and gmail smtp servers with this message: 554: Message not accepted due to failed RFC compliance. Too many From headers. See https://senders.yahooinc.com/smtp-error-codes#rfc-compliance-failures What would cause mailman to build too many from headers when distributing email? It appears the from address is repeated 5 times in the from field. I'm guessing it is something in my configuration but what and where?

4 10

Block members from sending cc's and bcc's
by Cathryn McGuire Nov. 15, 2025

Nov. 15, 2025

Hi everyone, Using Mailman 3 with Affinity web interface and we want to stop our members from sending to cc: or bcc: We've found the Header Filter and cc and bcc appear in it. Tried to configure it to "hold for moderation," but it hasn't worked. Partly because we don't understand what to put in the Pattern input box. I put in cc: because it requires something. Can anyone advise? Cheers, Cathryn

3 26

Postfix Hooks and Fetchmail
by dap1＠bellsouth.net Nov. 14, 2025

Nov. 14, 2025

I'm using fetchmail to feed mailman3 and am having a problem with the postfix hooks. My list name is llllllllll(a)ddddddddd.net. However, fetchmail passes the email to lllllllllll@localhost. So I am getting this error in the mail log: Out: 550 5.1.1 <llllllllll@localhost>: Recipient address rejected: User unknown in local recipient table Is there something I need to add to mailman's recipient table, fetchmail or an alias in postfix?

2 7

mailman-web migrate error
by pashdown＠xmission.com Nov. 13, 2025

Nov. 13, 2025

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. The above exception was the direct cause of the following exception: The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/share/mailman3-web/manage.py", line 10, in <module> execute_from_command_line(sys.argv) ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 442, in execute_from_command_line utility.execute() ~~~~~~~~~~~~~~~^^ File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 436, in execute self.fetch_command(subcommand).run_from_argv(self.argv) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 412, in run_from_argv self.execute(*args, **cmd_options) ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 458, in execute output = self.handle(*args, **options) File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 106, in wrapper res = handle_func(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/core/management/commands/migrate.py", line 356, in handle post_migrate_state = executor.migrate( targets, ...<3 lines>... fake_initial=fake_initial, ) File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 135, in migrate state = self._migrate_all_forwards( state, plan, full_plan, fake=fake, fake_initial=fake_initial ) File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards state = self.apply_migration( state, migration, fake=fake, fake_initial=fake_initial ) File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 252, in apply_migration state = migration.apply(state, schema_editor) File "/usr/lib/python3/dist-packages/django/db/migrations/migration.py", line 132, in apply operation.database_forwards( ~~~~~~~~~~~~~~~~~~~~~~~~~~~^ self.app_label, schema_editor, old_state, project_state ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/lib/python3/dist-packages/django/db/migrations/operations/special.py", line 193, in database_forwards self.code(from_state.apps, schema_editor) ~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/migrations/0006_emailaddress_lower.py", line 11, in forwards EmailAddress.objects.all().exclude(email=Lower("email")).update( ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^ email=Lower("email") ^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 1206, in update rows = query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1984, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1562, in execute_sql cursor.execute(sql, params) ~~~~~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers( ~~~~~~~~~~~~~~~~~~~~~~~~~~~^ sql, params, many=False, executor=self._execute ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute with self.db.wrap_database_errors: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/utils.py", line 91, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) django.db.utils.IntegrityError: 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.

2 3

My django container keeps getting shutdown by oom-killer
by Hirayama, Pat Nov. 13, 2025

Nov. 13, 2025

Greetings, Ok, I just updated the docker containers that are running my Mailman 3 installation over the weekend. mailman-core is now 3.3.10, with mailman-ngnix at 1.28.0, mailman-postfix at 3.10.5-r0 and mailman-django-uwsgi at "latest". I think I have got everything working normally — messages seem to be processed correctly, and I can access the web pages on the web interface. And I have updated various scripts to use --run-as-root until I can get around to reconfiguring mailman-core to use a non-root user. Anyway, since that time, the EC2 instance that the containers are running on becomes "unreachable", to use AWS's parlance. I can restore functionality by rebooting the instance. According to AWS, this is an application or operating system issue, not their instance. Which means auto-recovery doesn't get activated. This always happens overnight, usually after midnight, though one time it was around 10:40. I don't see any crontab entries that correlate. And the after midnight issues don't always happen at the same time, so it seemed unlikely that it was a crontab job that was causing it I finally looked at the host (rather than the logs of each container) and realized that the oom-killer was killing django-admin. As a temporary workaround, I've limited memory on the mailman-django-uwsgi container to 4 GiB (though, since I just did that this morning, I won't know until after midnight (presumably) if it worked or not), and set the RestartPolicy to always. I'm thinking that this points to a memory leak or some kind? I did have to add a bunch of packages to my Dockerfile when I rebuilt the container, since the last build was like 5 years ago, so I suppose it could be that django is just using more memory than it used to, though at the moment, I see that it is around 1 GiB: FROM python:3.12-alpine3.22 RUN apk update && apk add --no-cache --virtual build-deps \ cargo gcc libffi-dev musl-dev && \ apk add --no-cache gettext postgresql-dev sassc build-base pcre-dev python3-dev libc-dev linux-headers && \ pip install --upgrade pip setuptools wheel && \ pip --no-cache-dir install django-haystack==3.3.0 hyperkitty==1.3.12 \ postorius==1.3.13 psycopg2 uwsgi==2.0.25 whoosh && \ apk update && apk del --no-cache build-deps WORKDIR /opt/mailman/mailman-suite/mailman-suite_project USER mail EXPOSE 8000 CMD ["uwsgi", "--ini", "uwsgi.ini"] Any insights, ideas or assistance would be appreciated. Thanks! Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering - Infrastructure Fred Hutch Cancer Center O 206.667.4856 phirayam(a)fredhutch.org<mailto:phirayam@fredhutch.org>

4 4

Cannot Create New List
by dap1＠bellsouth.net Nov. 13, 2025

Nov. 13, 2025

I'm trying to create a list (on Ubuntu) and I'm getting this: <venv> $ python3 Python 3.12.3 (main, Aug 14 2025, 17:47:21) [GCC 13.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> owners = ['xxxx(a)ddddddddd.net'] >>> from mailman.app.lifecycle import create_list >>> ant = create_list('llllllllllllll(a)dddddddd.net', owners) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/app/lifecycle.py", line 74, in create _list getUtility(IEmailValidator).validate(fqdn_listname) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/zope/component/_api.py", line 180, in getUtil ity raise ComponentLookupError(interface, name) zope.interface.interfaces.ComponentLookupError: (<InterfaceClass mailman.interfaces.address.IEmailVa lidator>, '')

5 67

Xapian alternatives
by Andrew Bernard Nov. 11, 2025

Nov. 11, 2025

Are there alternative search engines to Xapian that can be used for Mailman 3? I have come to understand that Xapian development stalled in the v2.0 attempt.

5 8

custom css?
by jamie＠mayfirst.org Nov. 9, 2025

Nov. 9, 2025

I've installed the mailman3, mailman3-full, mailman3-web, and python3-django-mailman3 packages on Debian trixie. Everything is working - thank you developers! However, I would like to modify how the web pages look (both postorius and hyperkitty). I noticed that the web interface on this server (lists.mailman3.org) looks much nicer than the one showing on my server. For one, on my installed instance, the left and right margins are not set, so content is flush with the edge of the screen. What is the easiest/most maintainable way to add my own css code and/or files to adjust how the web interface is displayed? Is that possible? Thank you! jamie

5 5

Cannot issue commands through email
by stonehold＠thedagora.social Nov. 9, 2025

Nov. 9, 2025

Greetings! I've recently deployed mailman3 for my community but have run into a snag -- none of the emails that issue commands (eg., list1-<join>@domain.com, list2-<unsubscribe>@domain.com, etc. etc.) are going through. They keep bouncing back with an undeliverable message. I can create lists and interact with them otherwise just fine. When I join from the web UI I can post and receive to that list. I've been able to troubleshoot the rest so far on my own, but this has me stymied, so any guidance would be greatly appreciated. Thanks in advance! ~Ken

2 4

mailman-web Cleaning Up a Few Issues
by dap1＠bellsouth.net Nov. 6, 2025

Nov. 6, 2025

I seems to be having a problem with some cronjobs not running; I'm getting the following email errors/warnings: Subject: Cron <www-data@dap002> [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.minutely /usr/share/mailman3-web/manage.py runjobs minutely Body: flock: cannot open lock file /var/run/mailman3-web/cron.minutely: No such file or directory Obviously there is a path specified wrong but I can't find where that is. Subject: Cron <mailman@dap002> /opt/mailman/venv/bin/mailman-web runjobs minutely Body: System check identified some issues: WARNINGS: ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'username', 'email'} ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] Again I could probably fix these if I knew where to look.

3 22