October 2020 - Mailman-users - lists.mailman3.org

Cron error
by gordon＠dickens.com Oct. 25, 2020

Oct. 25, 2020

I recently upgraded to mailman3 on two Debian servers and I am getting a cron error periodically sent to me as depicted below. It looks like a permission problem, however, /var/lib/mailman3/locks and /var/lib/mailman3/* all have user = "list" and group = "list" and the cron job runs as user = "list" so I don't quite understand why I am getting these errors. Hopefully, someone might reply with what the problem is. Thanks, Gordon Here is some additional information: "ls -ld locks" output: drwxr-xr-x 2 list list 4096 Sep 28 08:51 locks ls -l locks" output: total 12 -rw-rw---- 1 list list 80 Sep 28 00:00 'dbcreate.lck|slc.mailhub4u.com|24435|4056142050254595815' -rw-rw---- 2 list list 77 Sep 28 2020 master.lck -rw-rw---- 2 list list 77 Sep 28 2020 'master.lck|slc.mailhub4u.com|5291|3708878559945320758' Here is the error message that is emailed to me: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 216, in lock os.link(self._claimfile, self._lockfile) FileExistsError: [Errno 17] File exists: '/var/lib/mailman3/locks/dbcreate.lck|slc.mailhub4u.com|24435|4056142050254595815' -> '/var/lib/mailman3/locks/dbcreate.lck' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/mailman", line 11, in <module> load_entry_point('mailman==3.2.1', 'console_scripts', 'mailman')() File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 716, in main with self.make_context(prog_name, args, **extra) as ctx: File "/usr/lib/python3/dist-packages/click/core.py", line 641, in make_context self.parse_args(ctx, args) File "/usr/lib/python3/dist-packages/click/core.py", line 1089, in parse_args rest = Command.parse_args(self, ctx, args) File "/usr/lib/python3/dist-packages/click/core.py", line 940, in parse_args value, args = param.handle_parse_result(ctx, opts, args) File "/usr/lib/python3/dist-packages/click/core.py", line 1477, in handle_parse_result self.callback, ctx, self, value) File "/usr/lib/python3/dist-packages/click/core.py", line 96, in invoke_param_callback return callback(ctx, param, value) File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in initialize_config initialize(value) File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 218, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 177, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/usr/lib/python3/dist-packages/mailman/database/factory.py", line 50, in create with Lock(os.path.join(config.LOCK_DIR, 'dbcreate.lck')): File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 334, in __enter__ self.lock() File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 248, in lock elif self._read() == self._claimfile: File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 442, in _read with open(self._lockfile) as fp: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/dbcreate.lck'

3 8

migration from 2.1 - owners and moderators
by Alex Schuilenburg Oct. 25, 2020

Oct. 25, 2020

We're migrating from 2.1 to 3.2.1 and an odd issue has popped up. It may be something different in the way mailman3 works, or a misconfiguration on my part. Most of the lists migrated so far don't have moderators, just owners. However, when these lists have messages requiring moderation, the owners dont get notified of held messages - unlike 2.1 where they did. Is this a change or is there something I am missing in the configuration? I have the minute/quarterly/hourly etc cron jobs running, although I have had to tune down the frequency of minute to hourly as it takes 6.5 minutes to run* - but I doubt this is the cause. While for the moment I have found the held messages in files in /var/lib/mailman3/messages and figured out which lists are in need of attention (and notified the owners), it seems I may have to do a bit of coding myself to walk through the lists and notify owners when their list is in need of attention. There must surely be something that does this already - or is this moderators only in mailman3? Guidance appreciated. Thanks -- Alex * From the list I realise this is because I am still using the default whoosh backend to haystack and need urgently to switch to xapian or solr, but the info on how to get this working for a noob like me is unfortunately lacking :-(

3 5

How to get Hyperkitty to show actual sender e-mail addresses?
by Hans-Martin Mosner Oct. 24, 2020

Oct. 24, 2020

Hi, I'd like to show actual sender e-mail addresses (basically to block spammers sending to a list that is used as a contact address, so it has no moderation for non-member postings). Hyperkitty just show the display name, which not very informative. Is there a setting to change this behavior? I did not find any using internet search and sifting through the various config files, but I could easily have missed something. Cheers, Hans-Martin

2 1

Alias Domains in postfix_domains wrong way around?
by Hans-Martin Mosner Oct. 24, 2020

Oct. 24, 2020

Hi, we have an "Unusual Postfix configuration" and use "Alias Domains" to work around. However, it looks like "mailman aliases" generates the postfix_domains map the wrong way around, resulting in postfix "Relay access denied" errors for mails received from outside. Didn't notice at first since I tried locally of course. Is my understanding correct that postfix_domains should have the true (externally visible) domains as keys, and values that basically don't matter, or should it have both the real domains and their alias names as keys? With such a convoluted setup, my brain twists a little. For now, I'm listing the real domains explicitly, that seems to work for the local and non-local cases. Cheers, Hans-Martin

2 1

Unsubscribe Notifications to List Owners and Members
by Brian Carpenter Oct. 22, 2020

Oct. 22, 2020

It seems that the only time an unsubscribe notification is sent to a list owner and/or list member is when a list member sends an email to lisname-unsubscribe@listdomain and that list member is not registered with Affinity/Postorius. Can anyone confirm this and if confirmed, is this considered a bug? -- Brian Carpenter Harmonylists.com Emwd.com

2 2

Re: Unsubscribe Notifications to List Owners and Members
by Brian Carpenter Oct. 22, 2020

Oct. 22, 2020

What list are you trying to unsubscribe from and how are you doing it? On 10/22/20 4:58 PM, Jerry Koutavas wrote: > > No offense but been trying to unsubscribe for months, nothing happens > > *From:*Brian Carpenter [mailto:brian_carpenter@emwd.com] > *Sent:* Thursday, October 22, 2020 4:56 PM > *To:* Mailman users <mailman-users(a)mailman3.org> > *Subject:* [MM3-users] Unsubscribe Notifications to List Owners and > Members > > It seems that the only time an unsubscribe notification is sent to a > list owner and/or list member is when a list member sends an email to > lisname-unsubscribe@listdomain <mailto:lisname-unsubscribe@listdomain> > and that list member is not registered > with Affinity/Postorius. Can anyone confirm this and if confirmed, is > this considered a bug? > > > > -- > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > ------------------------------------------------------------------------ > > *Total Control Panel* > > > > Login <https://asp.reflexion.net/login?domain=ascii.com> > > To: jk(a)ascii.com > <https://asp.reflexion.net/address-properties?aID=10188568&domain=ascii.com> > > From: mailman-users-bounces+jk=ascii.com(a)mailman3.org > <mailto:mailman-users-bounces+jk=ascii.com@mailman3.org> > > > > Message Score: 70 > > > > High (60): Fail > > My Spam Blocking Level: Medium > > > > Medium (75): Pass > > > > > Low (90): Pass > > Block > <https://asp.reflexion.net/FooterAction?ver=3&bl-sender-address=1&hID=458079…> > this sender / Block > <https://asp.reflexion.net/FooterAction?ver=3&ent=1&bl-sender-address=1&hID=…> > this sender enterprise-wide > > > > Block > <https://asp.reflexion.net/FooterAction?ver=3&bl-sender-domain=1&hID=4580794…> > mailman3.org / Block > <https://asp.reflexion.net/FooterAction?ver=3&ent=1&bl-sender-domain=1&hID=4…> > mailman3.org enterprise-wide > > > > /This message was delivered because the content filter score did not > exceed your filter level./ > -- Brian Carpenter Harmonylists.com Emwd.com

1 0

Confirm and Moderate Unsubscribe Requests
by Brian Carpenter Oct. 22, 2020

Oct. 22, 2020

If you set the unsubscription policy to confirm then moderate for a list and someone unsubscribes, they receive a confirmation request. That is good. They respond to it. That is also working fine. However the list owner/moderator than gets a request to approve the unsubscribe request and well, unless I am missing something, I don't see an interface to handles such requests via Postorius. How does one handle an unsubscribe request that requires moderator approval? -- Brian Carpenter Harmonylists.com Emwd.com

3 6

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