- Mailman-users - lists.mailman3.org

UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 1: ordinal not in range(128)
by r.woithe＠callassoftware.com Oct. 21, 2020

Oct. 21, 2020

Hello, System: Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.8.5 (default, Jul 28 2020, 12:59:40) [GCC 9.3.0] all this runs on Ubuntu 20.04. Our mailman3-web.log file is full of this error.Traceback: 00:00:17 [Q] ERROR reincarnated pusher Process-1:731365 after sudden death 00:00:17 [Q] INFO Process-1:731366 pushing tasks at 3061233 Process Process-1:731366: Traceback (most recent call last): File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap self.run() File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run self._target(*self._args, **self._kwargs) File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 300, in pusher task = SignedPackage.loads(task[1]) File "/usr/lib/python3/dist-packages/django_q/signing.py", line 28, in loads return signing.loads(obj, File "/usr/lib/python3/dist-packages/django_q/core_signing.py", line 38, in loads return serializer().loads(data) File "/usr/lib/python3/dist-packages/django_q/signing.py", line 44, in loads return pickle.loads(data) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 1: ordinal not in range(128) Is there a patch or workaround for this error or we are the one and only?

2 2

debian's 3.2.1 mailman package too unreliable in production - Mail held occasionally causes server errors, and unexplained queue/bad messages -
by Alex Schuilenburg Oct. 21, 2020

Oct. 21, 2020

We have an issue where a mailing list has had a message sent to it from a non-member, so the message has been held, but when the list owner or I attempt to list the held messages for the list we get a Server Error: "An error occurred while processing your request.". I see the mail being held in the mailman log with the non-subscriber reason, and followed the suggestions in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… which worked to look at and discard that held message. The problem is, there are more and we have over 900 mailing lists FYI, we are running:Mailman Core VersionGNU Mailman 3.2.1 (La Villa Strangiato)Mailman Core API Version3.0Mailman Core Python Version3.7.3 (default, Jul 25 2020, 13:03:44) [GCC 8.3.0] So we are looking at setting up a virtualenv to run the latest mailman3 3.3.1 as the 3.2.1 package from debian is looking unstable - barely usable. For example, while poking around I found 641 messages in queue/bad , but when I inspect them they look fine. If, as mentioned elsewhere, I rename them to .pck, put them in queue/shunt, and "mailman unshunt" the mail finally gets delivered. Why work now? Some kind of transient bug? Is 3.3.1 the way to go? On that last error, I've now enabled debug and hope to catch why messages are being dropped into queue/bad instead of being delivered. Already I have found errors in the mailman log such as: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/out/1603233694.919073+d907eb9512ce11fda515c19d 723537fc4cb15da2.pck'Oct 20 23:41:35 2020 (9793) Skipping and preserving unparseable message: 1603233694.919073+d907eb9512ce11fda515c19d723537fc4cb15da2Oct 20 23:41:35 2020 (9787) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/archive/1603233694.9209244+a0c1f3aab51d3d202aa 37911ab453f094b50b450.pck'Oct 20 23:41:35 2020 (9793) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/out/1603233694.9260252+138142eeb15b16b5da16934 954d1d3aeb1331198.pck'Oct 20 23:41:35 2020 (9793) Traceback (most recent call last): File "/usr/lib/python3/dist- packages/mailman/core/runner.py", line 158, in _one_iteration msg, msgdata = self.switchboard.dequeue(filebase) File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue with open(filename, 'rb') as fp:PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/out/1603233694.9260252+138142eeb15b16b5da16934 954d1d3aeb1331198.pck'Oct 20 23:41:35 2020 (9790) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/in/1603233694.9129462+8be9ab12e5dfeab086a1ab8b 3917550aea313505.pck'Oct 20 23:41:35 2020 (9793) Skipping and preserving unparseable message: 1603233694.9260252+138142eeb15b16b5da16934954d1d3aeb1331198Oct 20 23:41:35 2020 (9793) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/out/1603233694.9269004+5f8572edfb07e0e28b9f0b7 928a1184b8c8048ba.pck'Oct 20 23:41:35 2020 (9793) Traceback (most recent call last): File "/usr/lib/python3/dist- packages/mailman/core/runner.py", line 158, in _one_iteration msg, msgdata = self.switchboard.dequeue(filebase) File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue with open(filename, 'rb') as fp:PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/out/1603233694.9269004+5f8572edfb07e0e28b9f0b7 928a1184b8c8048ba.pck'Oct 20 23:41:35 2020 (9793) Skipping and preserving unparseable message: 1603233694.9269004+5f8572edfb07e0e28b9f0b7928a1184b8c8048ba The mailman3 user, "list", owns and has full rights all the way down: # ls -ld /var/lib/mailman3/queue/*drwxrwx--- 2 list list 4096 Oct 21 01:45 /var/lib/mailman3/queue/archivedrwxrwx--- 2 list list 77824 Oct 21 00:15 /var/lib/mailman3/queue/baddrwxrwx--- 2 list list 4096 Oct 19 10:44 /var/lib/mailman3/queue/bouncesdrwxrwx--- 2 list list 4096 Oct 5 17:18 /var/lib/mailman3/queue/commanddrwxrwx--- 2 list list 4096 Oct 21 00:00 /var/lib/mailman3/queue/digestdrwxrwx--- 2 list list 4096 Oct 21 00:20 /var/lib/mailman3/queue/indrwxrwx--- 2 list list 4096 Aug 11 18:44 /var/lib/mailman3/queue/nntpdrwxrwx--- 2 list list 4096 Oct 21 01:45 /var/lib/mailman3/queue/outdrwxrwx--- 2 list list 4096 Oct 21 01:45 /var/lib/mailman3/queue/pipelinedrwxrwx--- 2 list list 4096 Aug 11 18:44 /var/lib/mailman3/queue/retrydrwxrwx--- 2 list list 69632 Oct 21 01:45 /var/lib/mailman3/queue/shuntdrwxrwx--- 2 list list 4096 Oct 21 00:20 /var/lib/mailman3/queue/virgin so I'm kinda running out of options why this particular problem is happening. Any pointers? Or just toss the mailman 3.2.1 debian package out and go for a virtualenv 3.3.1 mailman? Thanks -- Alex

2 1

Messages in var/queue/shunt
by Brian Carpenter Oct. 20, 2020

Oct. 20, 2020

I have a large number of messages in the shunt directory due to some testing done. What is the proper method of dealing with them? Is there a way to release them again to the archiver or can I safely delete them? -- Brian Carpenter Harmonylists.com Emwd.com

2 2

Mailman 3 - docker container - sync_members
by holman＠uw.edu Oct. 20, 2020

Oct. 20, 2020

I would like to populate list members via the Mailman 3 sync_members script. However, I am using Mailman 3 in docker containers and it doesn't appear to have this command. How are others completing this synchronization? Searching this list I found a reasonable approach: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Is there a different/preferred solution?

3 2

mailman import21
by Brian Carpenter Oct. 20, 2020

Oct. 20, 2020

Does the import21 script also import custom templates? Are these custom templates contained in the config.pck file? Are there any known issues with the importing of mm2 templates into a mm3 environment? -- Brian Carpenter Harmonylists.com Emwd.com

2 4

I don't get my posts with Gmail
by blackout69 Oct. 18, 2020

Oct. 18, 2020

Hello everybody, I noticed that if I use a Gmail account to write to a Mailman3 list, the list receives my post and hyperkitty also archives the post, but I don't receive my own post. I have read that it is Gmail's will to automatically discard my post. Is there any way around this insane choice? Thank you in advance Max

5 9

Wrong info in moderation mail when held due to match of a header rule
by Torge Riedel Oct. 18, 2020

Oct. 18, 2020

Hi, today I got the first time a moderation mail for a mail which was held due to a match of a header rule: The message is being held because: Header "Yes" matched a header rule At your convenience, visit your dashboard to approve or deny the request. I think this is wrong, it should read 'Header "x-spam" matched a header rule'. Cause the header rule is configured for header "x-spam" and pattern "Yes". I haven't found a bug report for this yet on gitlab. If someone of the developers confirm this is wrong, I will file a bug on gitlab for it. Kind regards Torge

3 7

Mailman Core 3.3.2rc2 Released
by Abhilash Raj Oct. 17, 2020

Oct. 17, 2020

Hi Everyone, I am pleased to announce that Mailman Core 3.3.2rc2 is now out. This release includes both bug fixes and some new features. Some notable changes include: - Support for inviting users to join mailing lists. - New `adddmembers`, `delmembers` and `syncmembers` command to manage membership from CLI. - Addition of new REST API endpoints that return the count of held messages and subscription requests of much faster page loads in Postorius. - Addition of support for filtering in some API endpoints like Members and Subscription requests. - Support for `address=` option in email join command to subscribe an address other then sending address. - Addition of `who` email command to lookup memberships. - Expose emergency field for MailingList resource in REST API. - Several bug fixes to support new major version of libraries like dnspython, flufl.* etc. Since this is a pre-release, you can install it using: $ pip install --pre --upgrade mailman If there are no new major bugs, 3.3.2 will be released in 2 weeks time. We are now in strings freeze, so if you would like to help with translations to your native language, now is the time. We use Weblate for translations [1] and see here[2] for more documentation about i18n process in Mailman. There are a couple of new templates and more user friendly email templates & subjects for Mailman generated emails that could use translations. [1]: https://hosted.weblate.org/projects/gnu-mailman/mailman/ [2]: https://docs.mailman3.org/en/latest/translation.html -- thanks, Abhilash Raj (maxking)

1 0

Adding members to a mailman3 mailing list
by Onyeibo Oku Oct. 17, 2020

Oct. 17, 2020

Greetings I am testing mailman3 on Fedora Linux (32 and Rawhide). I installed it from the distribution's repositories and I am following the documentation at https://docs.mailman3.org/ I have created a mailing list on my instance but for I am unable to add members to it. Please, consider the following session: COMMAND: sudo -u mailman mailman3 lists OUTPUT: 1 matching mailing lists found: list(a)example.com COMMAND: sudo -u mailman mailman3 members --add members.txt list(a)example.com OUTPUT: usage: mailman members [OPTIONS] LISTSPEC Try 'mailman members -h' for help. Error: Invalid value for '--add' / '-a': Could not open file: members.txt: Permission denied When I try to use '-' instead of passing a file, I find no intuitive way to exit the standard input. What kind of permission is mailman expecting on the input file? I have tried changing ownership to the mailman user -- same output still. How does one use standard input to add members conclusively? Much regards Onyeibo

3 9

Postorius password resets
by Andrew Hodgson Oct. 16, 2020

Oct. 16, 2020

Hi, I am having an issue with our system where password resets are giving the users an email with a http://localhost:8000 URL. I have made sure settings in settings_local.py (and even settings.py) are as follows: POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.hodgsonfamily.org' However emails are still coming through with the wrong URL. What have I missed? Thanks. Andrew.

2 4