[Mailman-Users] Tool to diagnose qfiles?
Hi all, I'm running mailman 2.0.8, and I've noticed that there are a number of messages in the qfiles that are not being processed. Some are for an internal mailing list where I know there should be no delivery problems. Is there a tool to diagnose/monitor the qfiles directory, to find out: - the status of a message - why it hasn't been processed yet - when was it last looked at by qrunner Any other tips you have to deal with misbehaving queue process would be appreciated. I've had a look through this list's archives but I haven't found exactly what I was after. Many thanks in advance, Warren -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Support for filtering list postings thru external tools?
Hi, I have searched through the Mailman documentation and the source code for a way of invoking an external mail filter. My main interest is to integrate SpamAssassin (http://spamassassin.org/) into Mailman so that some/most spam mail will get held for approval. Has anybody done any work to add this functionality? I'm Python illiterate unfortunately, but I'm assuming that adding some extra configuration directives and an os.pipe() call in one of the Handlers would do the trick. Many thanks in advance, Warren -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] High CPU Usage After Mailman 2.1 Upgrade
Hi all, I upgraded to Mailman 2.1.26 on my Ubuntu 18.04 server yesterday. Now when a new list posting arrives, this process goes to 100% and stays there: /usr/bin/python /var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s What I'm also seeing is in the /var/lib/mailman/qfiles/out directory, there is a single file whose name keeps changing rapidly (more than once a second): -rw-rw 1 list list 6620 May 2 07:51 1588366105.234102+30d2fb4556d99a0ae3967d4f156a9e37069f2b14.bak -rw-rw 1 list list 6620 May 2 07:51 1588366105.234102+16609e67dc7e96df4c609daa7fb191d95ff88c1e.bak -rw-rw 1 list list 6620 May 2 07:51 1588366105.234102+244bef1ee56e03c655a25be85f32f52fe024f490.bak -rw-rw 1 list list 6620 May 2 07:51 1588366105.234102+47968ab9ef49616d8cf56ebbadf7b7e9bb8d1215.pck -rw-rw 1 list list 6620 May 2 07:51 1588366105.234102+26bf2448f8506ed3bb742443a11c585206734e5d.bak -rw-rw 1 list list 6620 May 2 07:51 1588366105.234102+c0e083e1150af6689df9f2cf37106fbac46ff70a.bak -rw-rw 1 list list 6620 May 2 07:51 1588366105.234102+fb9e3a19e7b44b94aa8069f5e15115dcef5d8553.pck.tmp -? ? ?? ?? 1588366105.234102+d304ac33f4e60a5f00a437a0a28ad5d9c86b.bak -rw-rw 1 list list 6620 May 2 07:51 1588366105.234102+f6744d91674f74b69f9b87769d70b8b127910e58.pck.tmp -rw-rw 1 list list 6620 May 2 07:51 1588366105.234102+71590cfc364222b97078ab1ed1a289a435d25800.bak -rw-rw 1 list list 6620 May 2 07:51 1588366105.234102+a7c3a89487a2c3dd1a69b8a7178508f6a70a7e8d.bak -rw-rw 1 list list 6620 May 2 07:51 1588366105.234102+ce6fa22d1f4071a2d6d42e0e49ce1770323cbc97.bak -rw-rw 1 list list 6620 May 2 07:51 1588366105.234102+17f5ce08abd8a27a9a05f721e4704848ff8ce960.bak -rw-rw 1 list list 6620 May 2 07:51 1588366105.234102+205cbad43f5e65fce34a4068cbe0dfb8c2cb174e.bak -rw-rw 1 list list 6620 May 2 07:51 1588366105.234102+4abd3744c6c5a471df7c0e6489d2253e9b47dea8.bak I can't see anything amiss in the log file. In fact, no output is being added to them while this process is racing. Does anybody have suggestions as to what the cause might be, or what I can do to diagnose the issue? For now I'm shutting down the mailman service, removing the queue file and restarting the service. Many thanks in advance, Warren P.S. The list has been running since 1994 :-) -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: High CPU Usage After Mailman 2.1 Upgrade
> On 5/1/20 3:01 PM, Warren Toomey wrote: > > Hi all, I upgraded to Mailman 2.1.26 on my Ubuntu 18.04 server yesterday. On Sat, May 02, 2020 at 10:12:55AM -0700, Mark Sapiro wrote: > There is an issue in 2.1.26 only that can cause this. See > <https://bugs.launchpad.net/mailman/+bug/1762871>. The fix for this is > <https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1750>. Thanks Mark. I think I worked out what happened, but I'm not 100% sure. Yes, I upgraded to 2.1.26 using Ubuntu's package management system. However, two years ago I had applied the patch you mentioned to the previous Mailman installation. I had also put the original python source files into version control using RCS, just in case the patch needed to be backed out. What I think has happened is that some sub-component of the upgrade process (e.g. make) has checked out the old source files back out from the RCS storage. Thus, I ended up with those two source files before the patch was applied. Anyway, I've restored the files to the current version and Mailman is working normally again. I've also checked in the patched files so it won't happen again. Cheers, Warren -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
