Search results for "2021" - Mailman-users

Re: How to identify the exact reason behind the shunting of the mails ?

by Mark Sapiro

On 6/18/21 3:34 AM, Shashikanth Komandoor wrote: > Thank you Mark for your immediate response. > > The below are the tracebacks I could find in the mailman log. > > *Jun 17 19:04:08 2021 (8642) Uncaught runner exception: sequence item 0: > expected str instance, Header foundJun 17 19:04:08 2021 (8642) Traceback > (most recent call last): File > "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in > _one_iteration self._process_one_file(msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in > _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in > _dispose process(mlist, msg, msgdata, pipeline) File > "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in > process handler.process(mlist, msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/handlers/avoid_duplicates.py", line > 59, in process addrs = getaddresses(msg.get_all(header, [])) File > "/usr/lib64/python3.6/email/utils.py", line 112, in getaddresses all = > COMMASPACE.join(fieldvalues)TypeError: sequence item 0: expected str > instance, Header foundJun 17 19:04:08 2021 (8642) SHUNTING: > 1623936848.367641+4753f8127953071ddcabfe828ebe72fcf04d0ae2* This is https://gitlab.com/mailman/mailman/-/issues/881 which is fixed by https://gitlab.com/mailman/mailman/-/merge_requests/841 which will be in Mailman 3.3.5 when it's released. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

Re: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Marco Marinello

Dear Mark, I upgraded the pypi packages as you suggested but the problem remains the same. Tried also installing from git heads but always get ==> /opt/hyperkitty_django/hyperkitty.log <== ERROR 2021-10-23 09:42:42,523 30765 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. WARNING 2021-10-23 09:42:42,523 30765 django.request Unauthorized: /hyperkitty/api/mailman/urls WARNING 2021-10-23 09:42:42,523 30765 django.request Unauthorized: /hyperkitty/api/mailman/urls ==> /var/log/mailman/mailman.log <== Oct 23 07:42:42 2021 (30888) HyperKitty failure on http://127.0.0.1:8080/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>The archiver key must be sent over the Authorization HTTP header. </p></body></html> (401) For information, how does your release cycle work? I prefer installing from a source rather than pypi. Is the master normally stable? When a packages lands on pypi? I'll stick on 1.3.4 / 1.1.0 for the moment. All the best, Marco

3 years, 8 months

Held for notification - runner exception: 'ascii' codec can't encode character

by Seth Seeger

Hello all, Happy new year! I have a case where a user (set to be moderated), posts a message. She got the appropriate email back saying she was being held for moderation. However, the moderator did not get the email. I found the following block in mailman.log: Dec 28 19:37:44 2021 (33) Uncaught runner exception: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) Dec 28 19:37:44 2021 (33) Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/runners/incoming.py", line 79, in _dispose process(mlist, msg, msgdata, start_chain) File "/usr/lib/python3.8/site-packages/mailman/core/chains.py", line 79, in process link.function(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 234, in _process text = MIMEText(expand(template, mlist, substitutions), File "/usr/lib/python3.8/email/mime/text.py", line 42, in __init__ self.set_payload(_text, _charset) File "/usr/lib/python3.8/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) Dec 28 19:37:44 2021 (33) SHUNTING: 1640720264.0541506+b139f885caa9444586b43093a09991b7c19581e6 There are two owners listed, one of them is also listed as the moderator. "mailman version" says: GNU Mailman 3.3.4 (Tom Sawyer) We are running from Docker. I can send you the pck file offline if that would help. Thank you, Seth

3 years, 6 months

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Fri, May 14, 2021 at 7:04 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 5:02 AM, Odhiambo Washington wrote: > > On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: > > > >> > >> > >> On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> > >> wrote: > >> > >> /bin/sh: sass: Permission denied* > >> > >> > >> > >> Did you check the permissions on your sass binary? > >> > > > > My mailman installed in /opt/mailman/mm > > > > find /opt/mailman/ -type f -name sass > > > > yielded nothing! > > > > Try `which sass` > root@gw:/usr/home/wash # su mailman3 (venv) [mailman3@gw /usr/home/wash]$ which sass (venv) [mailman3@gw /usr/home/wash]$ There is no sass. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 1 month

Re: Mailing list welcome message won't update

by frances.du＠uq.edu.au

Thanks Stephen and Mark. I checked whether group and world have 'x' permission on every directory in the path to the files and found below: root@lists:/var/lib/mailman3/templates# ll total 12 drwxr-xr-x 3 list list 4096 Oct 10 2018 ./ drwxr-xr-x 12 list list 4096 Jan 9 05:08 ../ drwxr--r-- 5 list list 4096 Mar 30 2021 lists/ root@lists:/var/lib/mailman3/templates# cd lists/ root@lists:/var/lib/mailman3/templates/lists# ll total 20 drwxr--r-- 5 list list 4096 Mar 30 2021 ./ drwxr-xr-x 3 list list 4096 Oct 10 2018 ../ drwxr--r-- 3 list list 4096 Jan 8 01:14 [redacted].lists.[redacted].org.au/ root@lists:/var/lib/mailman3/templates/lists# cd p[redacted].lists.[redacted].org.au/ root@lists:/var/lib/mailman3/templates/lists/[redacted].lists.[redacted].org.au# ll total 12 drwxr--r-- 3 list list 4096 Jan 8 01:14 ./ drwxr--r-- 5 list list 4096 Mar 30 2021 ../ drwxr--r-- 2 list list 4096 Jan 15 04:45 en/ So, group and world did not have 'x' permission to all the superordinate directories. I didn't see anything relevant in mailman.log. --------------------- I am not sure why the "list:user:notice:welcome" and "list:user:notice:welcome.txt" has different sizes even though they contain the identical welcome message. I decided to delete these two files: list:member:regular:footer list:user:notice:welcome Restarted services and tested again. -> issue still persisted. Should I try giving group and world the 'x' permission for all superordinate directories? Although my other mailing list has the same setup (no 'x' permission for group and world and it seems to be working fine.) Thanks for your help. Frances

5 months, 2 weeks

Re: Request Entity Too Large

by Christian Stalberg

I went into nginx.conf and raised the client_max_body_size from the default 1M to 0, then restarted nginx. The '413 Request Entity Too Large' error has gone away, but postings to the list are not distributed. The mail queue is empty. Now what? -----Original Message----- From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com> Sent: Tuesday, October 19, 2021 7:20 AM To: Christian Stalberg <csa(a)web-analysts.net> Cc: mailman-users(a)mailman3.org Subject: [MM3-users] Request Entity Too Large Christian Stalberg via Mailman-users writes: > Now mail sent to mm3 for distribution is not going out, for two > different lists. Check whether stuff is stuck in your MTA queue, and your MTA logs. Also check Mailman's queues (usually in /var/lib/mailman/qfiles, I think). As for why it's two different lists, is it possible that somebody cross-posted to those lists, or one is subscribed to the other? The mailman.log shows this error: > Oct 17 21:50:00 2021 (491) ACCEPT: > <030601d7c3a0$ee342f20$ca9c8d60$(a)somedomain.com> > Oct 17 21:50:04 2021 (488) HyperKitty failure on > https://somedomain.net/archives/api/mailman/archive: <html> I don't think this should affect mail going out in itself, because this appears to be delivery to HyperKitty, not to any remote host. Why nginx is involved is a mystery to me, though. > <head><title>413 Request Entity Too Large</title></head> > <body bgcolor="white"> > <center><h1>413 Request Entity Too Large</h1></center> > <hr><center>nginx/1.14.2</center> > </body> > </html> > (413) > Oct 17 21:50:04 2021 (488) Exception in the HyperKitty archiver: <html> > <head><title>413 Request Entity Too Large</title></head> > <body bgcolor="white"> > <center><h1>413 Request Entity Too Large</h1></center> > <hr><center>nginx/1.14.2</center> > </body> > </html> It appears that nginx is complaining that a request from HyperKitty is too large. I don't know much about nginx, but usually a request is sent FROM a client TO an HTTPd, and it's saying it's too big. I guess if nginx is the front end for HyperKitty, it could be that some client is requesting a huge email from HyperKitty. I guess you could have nginx between Mailman core and HyperKitty, in which case this is apparently an nginx configuration issue: it has an upper limit on the size of messages it's willing to accept from core and pass on to HyperKitty. If your Mailman is getting messages large enough that an HTTPd balks, I wouldn't be surprised if your MTA is on strike, or is getting "you gotta be kidding, I'm too busy, try tomorrow" from remote recipients. It could be a Mailman problem, but there's nothing in your report to suggest that it is.

3 years, 8 months

Re: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/14/21 12:50 PM, Odhiambo Washington wrote: > On Fri, May 14, 2021 at 7:04 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 5/14/21 5:02 AM, Odhiambo Washington wrote: >>> On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: >>> >>>> >>>> >>>> On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> >>>> wrote: >>>> >>>> /bin/sh: sass: Permission denied* ... >> Try `which sass` >> > > root@gw:/usr/home/wash # su mailman3 > (venv) [mailman3@gw /usr/home/wash]$ which sass > (venv) [mailman3@gw /usr/home/wash]$ > > There is no sass. There has to be. You can't get a permissions error on sass if it doesn't exist (well, maybe if you don't have permission to search a superordinate directory, but that's unlikely). Try `find /usr -name sass` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

Re: user mail not accepted

by Christian Stalberg

My apologies. I did not confirm that what I did already sent you was the message received by the user. The mailing list address is ssan(a)lists.naturalintelligence.us and it seems as though this became an alias for this single user christian(a)sewagesludgeactionnetwork.com . > What I wanted to see was not the message sent to the list, but the message received by the one user from the list. If you are saying this message is that, it didn't come from any Mailman list. > > > Return-Path: <christian(a)sewagesludgeactionnetwork.com> > Delivered-To: ces(a)ecovillage.cc > Received: from box.ecovillage.cc ([127.0.0.1]) > by box.ecovillage.cc with LMTP id MDucNBythmCTSwAAMoO61A > for <ces(a)ecovillage.cc>; Mon, 26 Apr 2021 05:07:56 -0700 > X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on > box.ecovillage.cc > X-Spam-Level: > X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, > DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE autolearn=ham > autolearn_force=no > version=3.4.2 > X-Spam-Report: > * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP > * 0.0 HTML_MESSAGE BODY: HTML included in message > * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature > * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not > necessarily > * valid > * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from > * author's domain > X-Spam-Score: -1.1 > Received: from authenticated-user (box.ecovillage.cc [45.79.28.18]) > (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 > bits)) > (No client certificate requested) > by box.ecovillage.cc (Postfix) with ESMTPSA id 6EADF3E8CC > for <ssan(a)lists.naturalintelligence.us>; Mon, 26 Apr 2021 05:07:54 > -0700 (PDT) > DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; > d=sewagesludgeactionnetwork.com; s=mail; t=1619438876; > bh=1M7F/uIS0bNG6cWjecy/a9QjskrHVwJHkjWRv+ffpM4=; > h=From:To:References:In-Reply-To:Subject:Date:From; > b=jXOswVZgFeHBB+sjIDqVkNBQqIbfZCj9ZUfpVwl10NQEkGaoxckPHNOKT6x9zIqsW > BZ7iZqqi2mWprVQ8LrK48Lp7gvCQ/ipqspMeLt3t+uljzTtryHmV6uJFEAU3hqM33Y > nQqX6Z8la8Ko40F9Ayb4h4e/MOfPdA4nadgf5hZzt/DzPFZvzUbG3V8lWcHuyJNA2y > SQkhbNubQ6iNEEB0SyBjoOjl3g3LVxjxY+9kMGGmX+1PFfW90CpDDShRmKkkscEWaA > NiV0fX6U5LENBBnc6Q9ImLgXuaLdCqlBRBumJBk+eUUr007rpXXVAPck2NvUzGyM2v > kNNGlT68hGzEg== > From: <christian(a)sewagesludgeactionnetwork.com> > To: <ssan(a)lists.naturalintelligence.us> > References: > In-Reply-To: > Subject: How US chemical industry lobbying and cash defeated > regulation in Trump era > Date: Mon, 26 Apr 2021 05:07:37 -0700 > Message-ID: > <020501d73a94$cbe17440$63a45cc0$(a)sewagesludgeactionnetwork.com> > MIME-Version: 1.0 > Content-Type: multipart/alternative; > boundary="----=_NextPart_000_0206_01D73A5A.1F831170" > Thread-Index: Adc6h7I/qzBKx1yOT6aPOuipppacoQACatZAAADW1wA= > Content-Language: en-us > > How US chemical industry lobbying and cash defeated regulation in > Trump era Industry's congressional allies defeated nearly all PFAS > legislation while the Trump EPA killed, watered down or slowalked new > rules > > https://www.theguardian.com/environment/2021/apr/26/us-chemical-compan > ies-lo > bbying-donation-defeated-regulation > > -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, April 26, 2021 5:54 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: user mail not accepted On 4/26/21 5:41 PM, Christian Stalberg via Mailman-users wrote: > No. there was no response received by the user a la "results of your > email commands" > message. Simply the original email sent to the list. I would still like to see the complete raw message as received by the user. That's the only thing that can tell me how it got to that user and provide clues as to why it didn't go to the other list members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ 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/

4 years, 2 months

Re: Language confusion in held mail notifications

by Mark Sapiro

On 9/22/21 2:16 AM, Henrik Rasmussen wrote: > I just upgraded from Mailman 3.2.0 (La Villa Strangiato) to Mailman 3.3.4 (Tom Sawyer) - Docker Mailman v0.3.12. As the language is not possible to set, and the default language is English, I set my user profile to Spanish and the list config to German, to figure out where the changes would take affect. > > After sending a mail to the list as the moderated list user, the resulting notification returned to the users email address is mostly in German, but the reason indicated is in Spanish "El mensaje proviene de un miembro moderado". I am unable to duplicate this in Mailman 3.3.5rc1. I set the list's language to German and a moderated user's language to Spanish. The held message notice to the user was entirely in Spanish and the notice to the admin was entirely in German. User Notice --------------------------------------------------- Date: Thu, 23 Sep 2021 17:12:50 -0700 From: test-bounces(a)msapiro.net To: mark(a)msapiro.net Subject: Su mensaje a test(a)msapiro.net espera la aprobación del moderador Su mensaje a la lista 'test(a)msapiro.net' con el asunto A test message Ha sido retenido hasta que el moderador de la lista pueda revisarlo y aprobarlo. El mensaje está siendo retenido por: El mensaje proviene de un miembro moderado O bien el mensaje será enviado a la lista, o bien recibirá una notificación con la decisión del moderador. --------------------------------------------------------------- Owner Notice -------------------------------------------------- Date: Thu, 23 Sep 2021 17:12:50 -0700 From: test-owner(a)msapiro.net To: test-owner(a)msapiro.net Subject: Der Beitrag test(a)msapiro.net von mark(a)msapiro.net muss genehmigt werden [-- Attachment #1 --] [-- Type: text/plain, Encoding: base64, Size: 0.5K --] Ihre Einwilligung als Administrator*in ist für folgende Nachricht an die Mailingliste nötig: Liste: test(a)msapiro.net Absender: mark(a)msapiro.net Betreff: A test message Die Nachricht wurde aus folgenden Gründen zurückgehalten: Die Nachricht kommt von einem moderierten Mitglied Besuchen Sie die Administrations-Seiten, um die Nachricht anzunehmen oder abzulehnen. [-- Attachment #2 --] [-- Type: message/rfc822, Encoding: 7bit, Size: 0.8K --] Date: Thu, 23 Sep 2021 17:12:48 -0700 From: Mark Sapiro <mark(a)msapiro.net> To: test(a)msapiro.net Subject: A test message User-Agent: Mutt/1.9.4 (2018-02-28) Give this a try. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan [-- Attachment #3 --] [-- Type: message/rfc822, Encoding: 7bit, Size: 0.9K --] Date: Thu, 23 Sep 2021 17:12:50 -0700 From: test-request(a)msapiro.net Subject: confirm b903b34955e0268e33b011ff9c9ccb7667dce4f2 Wenn Sie auf diese Nachricht antworten und den Subject: Header unverändert lassen wird Mailman die zurückgehaltene Nachricht verwerfen. Tun Sie dies, wenn es sich bei der Nachricht um Spam handelt. Wenn Sie auf die Nachricht antworten und einen Approved: Header mit dem Listenkennwort einfügen, wird Nachricht für die Veröffentlichung auf die Liste genehmigt. Der Approved: Header kann auch in der ersten Zeile des Textes der Antwort erscheinen. --------------------------------------------------------------- -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

Re: Mailing list welcome message won't update

by Mark Sapiro

On 1/15/25 14:29, via Mailman-users wrote: > Thanks Stephen and Mark. > > I checked whether group and world have 'x' permission on every directory in the path to the files and found below: > > root@lists:/var/lib/mailman3/templates# ll > total 12 > drwxr-xr-x 3 list list 4096 Oct 10 2018 ./ > drwxr-xr-x 12 list list 4096 Jan 9 05:08 ../ > drwxr--r-- 5 list list 4096 Mar 30 2021 lists/ > > > root@lists:/var/lib/mailman3/templates# cd lists/ > root@lists:/var/lib/mailman3/templates/lists# ll > total 20 > drwxr--r-- 5 list list 4096 Mar 30 2021 ./ > drwxr-xr-x 3 list list 4096 Oct 10 2018 ../ > drwxr--r-- 3 list list 4096 Jan 8 01:14 [redacted].lists.[redacted].org.au/ > > > root@lists:/var/lib/mailman3/templates/lists# cd p[redacted].lists.[redacted].org.au/ > root@lists:/var/lib/mailman3/templates/lists/[redacted].lists.[redacted].org.au# ll > total 12 > drwxr--r-- 3 list list 4096 Jan 8 01:14 ./ > drwxr--r-- 5 list list 4096 Mar 30 2021 ../ > drwxr--r-- 2 list list 4096 Jan 15 04:45 en/ > > So, group and world did not have 'x' permission to all the superordinate directories. I don't think that matters. As long as everything is running as user `list`. How are you testing. Are you running a `mailman` command and if so, are you running that as user `list`. Note that `mailman` commands should only ever be run as the Mailman user, `list` in your case. If that explains the issue, fine. Otherwise this seems to be an issue with the Debian package and should be reported to Debian. See https://wiki.list.org/x/12812344 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

Mailman-users search results for query "2021"