- Mailman-users - lists.mailman3.org

mm3 installation question
by advorkin＠cs.princeton.edu March 7, 2024

March 7, 2024

Hello, everyone. I just completed the initial installation by following the instructions: https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install I went with the apache/uswgi configuration. The site is up and running, but if I click Postorius, it gets redirected to https://mysite.com/postorius/lists and I get not found error message. The same goes for Lists and Archives. What did I do wrong? I've found some discussions online, but they seem to be related to a different installation, thus my confusion. Thank you!

4 10

mass unsubscribe/subscribe
by ronn.ramirez＠pge.com March 6, 2024

March 6, 2024

Hi Mailman Admins, Whenever we mass subscribe or unsubscribe more than 500+ users, we would get a "500-internal-server-error" or a timeout. Is there something we can tweak or increase to way to increase this threshold?

3 2

export/import list?
by Dave McGuire March 1, 2024

March 1, 2024

I'm migrating to a new Mailman3 instance, finally escaping a fairly old (3.1.1) and problematic distribution repo install on a Linux VM and moving to a venv install in a native SmartOS Zone. I've gotten everything running well and integrated with our (fairly complex) mail server. I'd like to begin migration of the lists on the old mm3 instance. 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? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

6 9

Migration from old server to new server failed
by Helio Loureiro March 1, 2024

March 1, 2024

Hi, So we tried to the migration following the steps: - stop mailman in the old machine (v3.1.1 from ubuntu packages) - dump DB mailman3 and mailman3web - backup /var/lib/mailman3 content On the new machine: - checkout from git the version 3.1.1 to match production and install the services - stop mailman3 and mailman3-web on the new machine - load DBs into new machine - copy content from /var/lib/mailman3 into /local/mailman/var (which means: archives/ cache/ data/ ext/ lists/ locks/ messages/ public_suffix_list.dat queue/ templates/ web/) - start mailman3 and mailman-3web - run mailman3-web migrate And I stopped here. Because it crashed. (venv) mailman@new-mailman3-server ~ (v3.1.1) [0|SIGINT]> mailman-web migrate System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. 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 admin.0003_logentry_add_action_flag_choices... OK Applying auth.0009_alter_user_last_name_max_length... OK Applying auth.0010_alter_group_name_max_length... OK Applying auth.0011_update_proxy_permissions... OK Applying auth.0012_alter_user_first_name_max_length... OK Applying django_mailman3.0003_sessions... OK Applying django_q.0010_auto_20200610_0856... OK Applying django_q.0011_auto_20200628_1055... OK Applying django_q.0012_auto_20200702_1608... OK Applying django_q.0013_task_attempt_count... OK Applying django_q.0014_schedule_cluster... OK Applying hyperkitty.0016_auto_20180309_0056... OK Applying hyperkitty.0017_file_attachments... OK Applying hyperkitty.0018_threadcategory_color... OK Applying hyperkitty.0019_auto_20190127_null_description... OK Applying hyperkitty.0020_auto_20190907_1927... OK Applying hyperkitty.0021_add_owners_mods...Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 87, in _execute return self.cursor.execute(sql) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 179, in execute res = self._query(mogrified_query) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 330, in _query db.query(q) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/connections.py", line 261, in query _mysql.connection.query(self, query) MySQLdb.OperationalError: (1050, "Table 'hyperkitty_mailinglist_moderators' already exists") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/local/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main execute_from_command_line(sys.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 96, in wrapped res = handle_func(*args, **kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/migrate.py", line 349, in handle post_migrate_state = executor.migrate( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 135, in migrate state = self._migrate_all_forwards( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards state = self.apply_migration( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 252, in apply_migration state = migration.apply(state, schema_editor) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/migration.py", line 130, in apply operation.database_forwards( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/operations/fields.py", line 108, in database_forwards schema_editor.add_field( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/schema.py", line 104, in add_field super().add_field(model, field) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 636, in add_field return self.create_model(field.remote_field.through) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 447, in create_model self.execute(sql, params or None) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 199, in execute cursor.execute(sql, params) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers return executor(sql, params, many, context) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 84, in _execute with self.db.wrap_database_errors: File "/local/mailman/venv/lib/python3.10/site-packages/django/db/utils.py", line 91, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 87, in _execute return self.cursor.execute(sql) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 179, in execute res = self._query(mogrified_query) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 330, in _query db.query(q) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/connections.py", line 261, in query _mysql.connection.query(self, query) django.db.utils.OperationalError: (1050, "Table 'hyperkitty_mailinglist_moderators' already exists") I tried to drop the table, but then it complained about another one. I dropped all the complained tables and as result hypperkitty never started. So I went back to see why the first error happened. Any clue what to do next? Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro

3 8

Google Summer of Code 2024
by Stephen J. Turnbull Feb. 26, 2024

Feb. 26, 2024

Hi, everybody It's that time of year again! PSF is in GSoC 2024, I'm 99% certain PSF will accept Mailman as a suborg (don't ask about the 1%, it's embarrassing ;-). Student applications open on March 18. So ... If you have ideas for improving Mailman 3, whether misfeatures that need fixing or cool new features, please consult our ideas page https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202024 to get an idea of level of detail and style of description needed (and to see if maybe it's already there. You can send them to me if they're already formed in your mind, or send them here for input from users on requirements, or to mailman-developers(a)python.org for input on implementation feasibility and appropriateness for GSoC. If you know anybody who would be interested in participating as a contributor, please encourage them to look at us. Rules are somewhat relaxed from years ago. They still don't accept below college age, but they no longer restrict to students. They're also offering multiple period lengths from 8 to 22 weeks (stipends vary according to period and by price level in country of residence, see https://developers.google.com/open-source/gsoc/help/student-stipends) They're not as generous as a few years ago, at least for the "rich" countries (US, UK, Japan). You don't need to be an experienced coder or project manager to be a secondary mentor, just willing to communicate with the code contributor. If you're interested in being a primary or secondary mentor, the burden is likely to be "as much as you want". We rarely get more than one good application, and we have enough "default" primary mentors to cover the likely maximum number of slots we could be allocated. It would be very helpful to us and to the PSF organization administrators if you express interest and get signed up by the end of next week, but as far as I know we can add or substitute mentors at any time. Potential mentors should 1. Have a Google account (needed for step 2, and required by GSoC) 2. Sign up with Python-GSoC at https://forms.gle/coJYxhor6FAZcZfU8 3. If you have been a GSoC mentor or org admin in the past, go to https://summerofcode.withgoogle.com and accept the contributor agreement and program rules for 2024. (Definitely if you did last year, probably for 2022 the system still remembers you, and unlikely it has more memory than that.) Steve

1 0

Settings for prevention of spam obfuscation
by Richard Rosner Feb. 26, 2024

Feb. 26, 2024

Are there any settings that may help with making it easier seeing spam as spam? E.g. some mail programs, including Outlook, allow the user to set a from mail address that most mail clients will show instead of the true sender address, but the senders mail address is still present in the sender header field. While some people and companies carelessly abuse that functionality, hiding their true mail address, those bad practices also are abused my spammers and others. Does mailman have any settings that would remove any such obfuscations, e.g. in this case detect the manipulated from address and replace it with the sender address? While I do run my own spam filter, it's virtually getting harder every day to make sure you detect all spam while not having too many false positives. If it was possible to reverse at least the most obvious manipulations, that would probably already help. Also, it would make it much easier for the users to see at first glance who actually wrote an email. It's always less trustworthy if the senders address is shown as user3168(a)suspiciousdomain.gg instead of it being manipulated to say support(a)yourprovider.com.

3 8

Unable to get Postfix to bounce messages to non-existent lists
by skenny＠scss.tcd.ie Feb. 21, 2024

Feb. 21, 2024

We have Mailman working well in our environment, but there's one thing I can't seem to make happen no matter what I try. The situation is as follows: Postfix runs on on a different server than Mailman. Its main.cf says local_recipient_maps = $alias_maps transport_maps = regexp:/var/mailman-data/postfix_lmtp relay_domains = regexp:/var/mailman-data/postfix_domains The file postfix_lmtp is initially generated by Mailman (running on a different machine). A background process creates a version of the file wherein the lmtp IP address is changed to the network IP of the Mailman server, and that version is sync'd over to the Postfix server. On the latter, a typical block for a list then reads as follows (where A.B.C.D is the IP address of the Mailman server): /^some-list(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-bounces(\+.*)?(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-confirm(\+.*)?(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-join(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-leave(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-owner(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-request(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-subscribe(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-unsubscribe(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 The only problem with this is that if someone sends a message to a non-existent mailing list, Postfix nevertheless accepts the mail, and it loiters in the queue for several days before eventually being bounced back to the sender. I want to get Postfix to reject mail to non-existent mailing lists immediately. I've come up short with each variation of main.cf settings I've tried, and would greatly appreciate any advice. Many thanks Stephen Kenny

3 4

Hyperkitty is not archiving due to 405 error - GET instead of POST
by Matthias Feb. 15, 2024

Feb. 15, 2024

Hi there, I am running mailman3 on Debian 12 - latest package (GNU Mailman 3.3.8 (Tom Sawyer)). Message handling in general is working fine, but as soon as a message is released, archiving with Hyperkitty is not working, due to a 405 error: --- Feb 11 16:18:48 2024 (3479662) HyperKitty failure on http://lists.domain.tld/mailman3/hyperkitty/api/mailman/archive: (405) Feb 11 16:18:48 2024 (3479662) Could not archive the message with id <170766472771.3479669.4791049109141956450(a)otherdomain.tld> Feb 11 16:18:48 2024 (3479662) archiving failed, re-queuing (mailing-list jahrgang.domain.tld, message <170766472771.3479669.4791049109141956450(a)otherdomain.tld>) Feb 11 16:18:48 2024 (3479662) Exception in the HyperKitty archiver: Feb 11 16:18:48 2024 (3479662) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError --- When tracing this back, even the frontend Nginx server receives a get in his logs, hence I assume that hyperkitty is really creating a GET instead of a POST request? --- 217.72.204.162 - - [11/Feb/2024:16:18:48 +0100] "GET /mailman3/hyperkitty/api/mailman/archive HTTP/1.1" 405 0 "-" "python-requests/2.28.1" --- Any idea how to trace this down any further? Any help is really appreciated! Thanks, Matthias

2 2

Retrieve users from a list
by pau.baiges＠csuc.cat Feb. 11, 2024

Feb. 11, 2024

A moderator has deleted all the users from a list, is there a way to recover them?

5 6

add / remove / set moderation bit of non-members via mailman shell
by Zaheer Abbas Feb. 9, 2024

Feb. 9, 2024

I have a situation where I need to add / remove 10-20 non-members to a particular list every week and set the moderation bit to 'accept immediately (bypass other rules). I do the above via postorius because I couldn't find a way to do this via mailman shell. Can anyone help me please to achieve the above? I know how to remove all non-members via /opt/mailman/mm/bin/mailman shell -l list.example.com for nonmember in m.nonmembers.members: ... nonmember.unsubscribe() ... commit() I am just having difficulties adding the non-members and setting the moderation bit to 'Accept' Currently I am using Mailman 3.2.2 (La Villa Strangiato) and Postorius Version 1.2.4 so cant use 'postorius => settings -> message acceptance -> id_accept_these_nonmembers' -- Regards, Zaheer

2 1