[Mailman-Users] Unsure what to do with web page Bug in Mailman version 2.1.20

2015-07-06 Thread Teijo
Hello, After updating from Ubuntu 12.04 to 14.04 (Apache 2.2 to 2.4), only page content I seem to get is Bug in Mailman version 2.1.20. No matter if I navigate to my Mailman's main page or to the given list's page. One problem is that there seems to be nothing useful in error log, although

Re: [Mailman-Users] Unsure what to do with web page Bug in Mailman version 2.1.20

2015-07-06 Thread Teijo
Hello, I did that before writing my message - in fact I reinstalled Mailman and checked permissions. Best, Teijo 6.7.2015, 15:56, Mark Sapiro kirjoitti: On July 6, 2015 4:05:23 AM PDT, Teijo g.aloi...@gmail.com wrote: Hello, After updating from Ubuntu 12.04 to 14.04 (Apache 2.2 to 2.4),

[Mailman-Users] merging 2 mailing lists

2015-07-06 Thread Laura Creighton
2 somebodies I know want to merge their mailing lists. They are both lists for recipes for people who have impaired kidney function. A complication is that these lists are hosted on different machines, with completely different names, etc. But picking a third name and setting things up so that

Re: [Mailman-Users] Unsure what to do with web page Bug in Mailman version 2.1.20

2015-07-06 Thread Mark Sapiro
On July 6, 2015 4:05:23 AM PDT, Teijo g.aloi...@gmail.com wrote: Hello, After updating from Ubuntu 12.04 to 14.04 (Apache 2.2 to 2.4), only page content I seem to get is Bug in Mailman version 2.1.20. No matter if I navigate to my Mailman's main page or to the given list's page. One problem is

Re: [Mailman-Users] Full List of Lists

2015-07-06 Thread Peter Draksler
On 15-07-06 09:18 AM, McNutt Jr, William R wrote: Is there a report or accepted technique that I can use to get a list of all the lists on my server, even the unadvertised ones? You should be able to get this by running bin/list_lists. Peter

[Mailman-Users] Can't close a list

2015-07-06 Thread Bernie Cosell
Sorry to be posting another incredibly dumb question, but after my last go-round [wherein I learned that I had the RE just right but my #@#%$@#$% ISP runs spam assassing *after* mailman] I decided to try closing the list. So I checked thet FAQs and the manuals and did what I thought should do

Re: [Mailman-Users] Unsure what to do with web page Bug in Mailman version 2.1.20

2015-07-06 Thread Mark Sapiro
On July 6, 2015 6:06:15 AM PDT, Teijo g.aloi...@gmail.com wrote: Hello, I did that before writing my message - in fact I reinstalled Mailman and checked permissions. Have you looked in Mailman's error log (not just Apache's)? Also, in the FAQ Mailman FAQ: http://wiki.list.org/x/AgA3 there

Re: [Mailman-Users] Migrate 2.x - 3.x

2015-07-06 Thread JB via Mailman-Users
I for one run a number of server with cPanel/WHM. They are using the latest 2.x version of MM now. I was hoping that there would be a way for cPanel/WHM to update to he 3.x tree and have all existing list migrated to the new tree. On Mon, 7/6/15,

Re: [Mailman-Users] Nightly Messages Show Problems

2015-07-06 Thread Mark Sapiro
On 07/06/2015 08:10 AM, Steve Matzura wrote: On Sat, 04 Jul 2015 09:11:54 -0700, Mark Sapiro m...@msapiro.net wrote: In your case, the RedHat package has modified Mailman's crontab.in to be a system crontab and already installed it in /etc/cron.d/. It did, but the file is virtually empty

Re: [Mailman-Users] merging 2 mailing lists

2015-07-06 Thread Mark Sapiro
On 07/06/2015 07:25 AM, Barry S. Finkel wrote: I am not an expert in Mailman archives, and I do not have a machine on which to test. I think that if you take the two mbox archive files (probably after you have run your footer modification scripts) and combine them into one file - then you

Re: [Mailman-Users] spam filter not working

2015-07-06 Thread Mark Sapiro
On 07/06/2015 08:53 AM, Bernie Cosell wrote: I have confirmed with the sysadmins: There is no way to set it to use spam assassin first. Which means they run spamassassin against outgoing mail but not incoming mail. The mind boggles at the absurdity ... -- Mark Sapiro

Re: [Mailman-Users] Can't close a list

2015-07-06 Thread Mark Sapiro
On 07/06/2015 01:27 PM, Bernie Cosell wrote: Action to take for postings from non-members for which no explicit action is defined. to hold This should work to hold all messages from non-members, but more below. The membership list consists of a single address, and I sent a message to

Re: [Mailman-Users] merging 2 mailing lists

2015-07-06 Thread Bill Cole
On 6 Jul 2015, at 9:26, Laura Creighton wrote: 2 somebodies I know want to merge their mailing lists. Have they bothered asking each and every subscriber and received an affirmative reply? No? Imagine my shock... The correct answer to this is No, you can't. You don't have subscriber

[Mailman-Users] Full List of Lists

2015-07-06 Thread McNutt Jr, William R
Is there a report or accepted technique that I can use to get a list of all the lists on my server, even the unadvertised ones? Bill -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users

Re: [Mailman-Users] spam filter not working

2015-07-06 Thread Bernie Cosell
I have a spam filter set to 'hold': X-Spam-Level:\s*\*\*\* I would use ^X-Spam-Level:\s*\*\*\* but yours should match any with 3 or more stars, in particular the one above. I have confirmed with the sysadmins: There is no way to set it to use spam assassin first. So my

Re: [Mailman-Users] merging 2 mailing lists

2015-07-06 Thread Barry S. Finkel
On 7/6/2015 8:26 AM, Laura Creighton wrote: 2 somebodies I know want to merge their mailing lists. They are both lists for recipes for people who have impaired kidney function. A complication is that these lists are hosted on different machines, with completely different names, etc. But

Re: [Mailman-Users] Nightly Messages Show Problems

2015-07-06 Thread Steve Matzura
On Sat, 04 Jul 2015 09:11:54 -0700, Mark Sapiro m...@msapiro.net wrote: In your case, the RedHat package has modified Mailman's crontab.in to be a system crontab and already installed it in /etc/cron.d/. It did, but the file is virtually empty (only three or four comment lines warning not to