- Mailman-users - lists.mailman3.org

Problems with signed messages from Apple Mail
by Rainer Herbst Nov. 18, 2021

Nov. 18, 2021

Dear all, after upgrading his Mac to MacOS 12.0.1 Monterey, one of our users can not send send signed messages to lists using Apple Mail v. 15.0 (3693.20.0.1.32). mailman3 denys the delivery of the mail with error message: host 172.19.0.4[172.19.0.4] said: 501 Message has defects (in reply to end of DATA command) I.e. mailman does not process the message, but rejects it already in the incoming smtp session. Is that a known issue? We use mailman3 docker installation, version info: GNU Mailman 3.3.4 (Tom Sawyer) Python 3.8.10 (default, May 6 2021, 06:30:44) Viele Grüße, Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 ----------------------------------------------------------------------------------------------- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/x-pkcs7-signature Name: smime.p7s

3 3

Bulk update of members' moderation settings
by Alex King Nov. 18, 2021

Nov. 18, 2021

I imported a list from mailman 2.1 using https://docs.mailman3.org/en/latest/migration.html. It happens that emergency moderation was set on the mailman 2.1 list, and this has resulted in all members having Moderation set to Hold. I now want to change that to Default Processing for all members. Is there a way to achieve that in bulk without clicking through the members options for each member in Postorius? Thanks, Alex

2 1

'str' object has no attribute 'token_type'
by Marco Marinello Nov. 16, 2021

Nov. 16, 2021

Hi everybody, I'm sorry for being always the strange guy with strange errors here but for some reason... I am. On a Mailman installation that was doing just fine for more than a year, I started receiving error messages per email. It happens when mailman daemon archives a messages. Although the messages is correctly archived, this exception is thrown by Hyperkitty: Traceback (most recent call last): File "/usr/local/lib/python3.9/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/local/lib/python3.9/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.9/dist-packages/django/views/decorators/http.py", line 40, in inner return func(request, *args, **kwargs) File "/usr/local/lib/python3.9/dist-packages/hyperkitty/views/mailman.py", line 118, in _decorator return func(request, *args, **kwargs) File "/usr/local/lib/python3.9/dist-packages/django/views/decorators/csrf.py", line 54, in wrapped_view return view_func(*args, **kwargs) File "/usr/local/lib/python3.9/dist-packages/hyperkitty/views/mailman.py", line 164, in archive add_to_list(mlist_fqdn, msg) File "/usr/local/lib/python3.9/dist-packages/hyperkitty/lib/incoming.py", line 79, in add_to_list from_str = header_to_unicode(message['From']) 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 343, in parse [Address(mb.display_name or '', File "/usr/lib/python3.9/email/headerregistry.py", line 343, in <listcomp> [Address(mb.display_name or '', File "/usr/lib/python3.9/email/_header_value_parser.py", line 462, in display_name return self[0].display_name File "/usr/lib/python3.9/email/_header_value_parser.py", line 393, in display_name return self[0].display_name File "/usr/lib/python3.9/email/_header_value_parser.py", line 574, in display_name if res[-1][-1].token_type == 'cfws': Exception Type: AttributeError at /hyperkitty/api/mailman/archive Exception Value: 'str' object has no attribute 'token_type' Request information: USER: AnonymousUser I upgraded both to Debian 11 (from 10) and to latest versions of Hyperkitty, mailman-hyperkitty and mailman but still getting the error. Other installations with same specs I'm managing to do not encounter this problem. Any clue of what could have happened, why and how to fix it? Thanks in advance, Marco

2 1

Race condition when mass subscribing same email addresses to two lists?
by Alan So Nov. 14, 2021

Nov. 14, 2021

We are testing the latest Mailman core 3.3.5 and Postorius 1.3.6. My colleagues reported that some email addresses cannot subscribe to the lists when two of them are using mass subscribe feature to add email addresses to the list. Then I try whether I can repeat the same issue. I did this: 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 There are quite a lot of similar errors in mailman.log. Did not study the code yet. Which part is causing the issue? SQLAlchemy 1.3.24 psycopg2-binary 2.8.6 [2021-10-28 08:38:30 +0000] [20141] [ERROR] Error handling request /3.1/members Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 136, in handle self.handle_request(listener, req, client, addr) File "/opt/mailman/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 179, in handle_request respiter = self.wsgi(environ, resp.start_response) File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/database/transaction.py", line 51, in wrapper config.db.commit() File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/database/base.py", line 52, in commit self.store.commit() File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 1046, in commit self.transaction.commit() File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 502, in commit self._assert_active(prepared_ok=True) File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/session.py", line 296, in _assert_active code="7s2a", sqlalchemy.exc.InvalidRequestError: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (psycopg2.errors.UniqueViolation) duplicate key value violates unique constraint "ix_address_email" DETAIL: Key (email)=(testemail999(a)example.com) already exists.

4 9

Bug in 2.1.36?
by Joel Lord Nov. 12, 2021

Nov. 12, 2021

I'm not sure if this is a bug or something about the new CSRF fix doesn't get along with something I have (mis)configured, but this definitely seems to be related. Sadly the script I use to backup mailman before upgrading I recently stopped backing up the lists themselves, so going back to 2.1.35 doesn't seem to be an option due to the .pck file version bump. Here's the trace I get: Traceback (most recent call last): File "/mailman/mailman-${domainslug}/scripts/driver", line 117, in run_main main() File "/mailman/mailman-${domainslug}/Mailman/Cgi/admindb.py", line 342, in main print doc.Format() File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line 352, in Format output.append(Container.Format(self, indent)) File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line 267, in Format output.append(HTMLFormatObject(item, indent)) File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line 53, in HTMLFormatObject return item.Format(indent) File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line 445, in Format % csrf_token(self.mlist, self.contexts, self.user) File "/mailman/mailman-${domainslug}/Mailman/CSRFcheck.py", line 53, in csrf_token mac = sha_new(secret + `issued`).hexdigest() TypeError: unsupported operand type(s) for +: 'NoneType' and 'str' Running Python 2.7.5 . -- Joel Lord

2 5

Filtering signed mails
by Rainer Herbst Nov. 12, 2021

Nov. 12, 2021

Dear all, today I recived a user complain that his messages were rejected with error "The message's content type was not explicitly allowed" I checked the list and indeed, it was configured to filter content and to allow only a very limited number of content types, namely application/pdf and image/jpeg. After some experiments, the problems seems to be the s/mime signature. The messages contain a signature: <snip> Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" <snap> I added this type to the allowed MIME content type, but signed messages are still rejected. What do I miss? Viele Grüße, Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 ----------------------------------------------------------------------------------------------- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/x-pkcs7-signature Name: smime.p7s

2 1

Moderation Action Changed After Import
by Brian Carpenter Nov. 12, 2021

Nov. 12, 2021

I migrated a Mailman 2 list using import21 and the list's config.pck into a Mailman 3 list. The list owner reported back that about 98% of the list members had their moderation setting changed to Reject (with notification). He said the previous moderation was the list's default which was hold for moderation. Is such a thing possible with an import job? Is this perhaps a bug that has been reported previously? -- Brian Carpenter Harmonylists.com Emwd.com

3 10

Issues with cross posted emails after upgrading to mailman 3.3.6
by Simon Coggins Nov. 10, 2021

Nov. 10, 2021

Since upgrading from 3.3.4 to 3.3.6 we are seeing a high instance of emails that are sent to 2 lists (EG 2 campuses). One campus will get the email and the other campus will get an email that just contains "The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list.” Is this something new in 3.3.6? I’m trying to work out what’s going on and why it would be lost. Both lists need the email as the membership list is different so the people on the second list get a useless email. -Simon --- [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

5 17

outgoing.py mailman@example.com issue
by dancab＠caltech.edu Nov. 9, 2021

Nov. 9, 2021

I deployed Mailman3 last night and today we've had some "bounced" messages with headers referencing mailman(a)example.com. This has only happened with a few lists. Any ideas what causes this? We are using an SMTP relay server for incoming and outgoing messages in front of the Mailman3 service. Thanks! Received: from [172.17.0.2] (ec2-52-25-39-43.us-west-2.compute.amazonaws.com [52 .25.39.43]) by smtp2.caltech.edu (Postfix) with ESMTP id B97472076421 for <xxxxxxx(a)caltech.edu>; Fri, 5 Nov 2021 12:34:34 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.caltech.edu B97472076421 From: Mailman <mailman(a)example.com> To: Mailman Bounces <mailman-bounces(a)example.com> Subject: SMTP Delivery Failure Message-ID: <163614051784.271.12319265021103466218@badc5045e1e5> Date: Fri, 05 Nov 2021 12:28:37 -0700 -- Dan

3 7

Mailman Suite installation on CentOS 7
by Kimmo L Nov. 8, 2021

Nov. 8, 2021

Hello! I want to install fresh Mailman, which is combined with hyperkitty+postorius. After checking documentation i found, that Mailman Suite is perfect for me. But i have some misunderstandings about installation. I only found this part in documentation, which explains how to clone and start using Mailman Suite (https://docs.mailman3.org/en/latest/devsetup.html#run-the-mailman-suite-com…) But am i correct, that before doing so, i need to install mailman core, mailman client, django-mailman3 ? Or what would be the correct steps to build up my first Mailman Suite on CentOS? Br, Kimmo

2 1