Re: [Mailman-Users] List users get a 'rejected' error, but the messages are posted
Ah-Ha! Sounds like you have a mailman list subscribed to *your* list. Take a look at your list membership and see if one of the subscribed emails is going back to the server. Happy hunting! Jon Carnes On Thu, 2003-10-02 at 23:54, pod wrote: Jon Carnes escribi: What email address did you send the message to initially? To the post address of my (in this case, [EMAIL PROTECTED]). All those messages reaches the list, but at the same time we get the error message. This seems to happens to *all* the users of the list. The message indicates that you sent mail to a mailman list that you were not authorized to send to. Yes, but which list? The messages are really posted to my list, and the error comes from other direction. Send a note to the request address of the list and put as the subject: info listname[EMAIL PROTECTED] This will send back information about the list - including it's real name and description. If these don't match with *your* list, then there is a problem on the server with the aliases. This is a problem that the admin of the server would have to fix. I did it. I get two messages, one with the information of my list (from [EMAIL PROTECTED]) and one from [EMAIL PROTECTED] The later message contains the following headers: List-Id: Mailman site list mailman.es.urbenalia.com X-List-Administrivia: yes Since es.urbenalia.com is the internal name of the main server, this list should be created by the admin, but he said that he didn't. The problem might be that those two list recive all the emails, so mailman.es.urbenalia.com rejectes its copy. If it is a problem with aliases, I don't know if the server admins knows how to fix it. Where in the documentation is this issue explained? If it comes back with your list information, then the problem is with your configuration of the list. Make sure that your email address is valid and that you have rights to post. Make sure you don't have any global filters that are denying folks. Since the messages reaches the list, I think that this can't be the error. Good Luck - Jon Carnes Thank you :) On Thu, 2003-10-02 at 20:29, pod wrote: Hi, I'm the webmaster of http://fisica.urbenalia.com, which is hosted in a cPanel based server, urbenalia.com. That control panel comes with mailman 2.1.2. I've a list called 'Canalfisica' (with internal name canalfisica_fisica.urbenalia.com). Since a week ago, the list users get a rejected message (which I copy for you bellow), but the messages are posted correctly. This is strange because the rejection message comes from es.urbenalia.com (as you will see bellow) instead of fisica.urbenalia.com. The server's administrator said that es.urbenalia.com is the internal name of the server. I looked at the mailman logs, but I didn't found the lines corresponding to the rejected messages. I wasn't able to found the answer in the documentation, nor in the faq. I think that this can't be a misconfiguration of the list, because it worked fine for two months and I didn't change anything. The servers runs linux, kernel 2.4.20-20.7, with apache 1.3.28. The rejection message that my users get, with the headers (I only have deleted the IP's of the private users), are like this: *** Return-Path: [EMAIL PROTECTED] Received: from tsmtp5.mail.isp ([xxx.xxx.xxx.xxx]) by mb32.terra.es (terra.es) with ESMTP id HM1SQB01.EJF for [EMAIL PROTECTED]; Wed, 1 Oct 2003 00:20:35 +0200 Received: from es.urbenalia.com ([xxx.xxx.xxx.xxx]) by tsmtp5.mail.isp (terra.es) with ESMTP id HM1SQ500.ATZ for [EMAIL PROTECTED]; Wed, 1 Oct 2003 00:20:29 +0200 Received: from localhost ([127.0.0.1] helo=es.urbenalia.com) by es.urbenalia.com with esmtp (Exim 4.20) id 1A4Ss4-mI-6K for [EMAIL PROTECTED]; Wed, 01 Oct 2003 00:21:28 +0200 Subject: JavaChat y Mensajes devueltos From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary026969976932705197== Message-ID: [EMAIL PROTECTED] Date: Wed, 01 Oct 2003 00:21:02 +0200 Precedence: bulk X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.2 List-Id: Mailman site list mailman.es.urbenalia.com X-List-Administrivia: yes Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - es.urbenalia.com X-AntiAbuse: Original Domain - fisica.urbenalia.com X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - es.urbenalia.com --===026969976932705197== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit You are not allowed to post to this mailing list, and
[Mailman-Users] [mailman hit by a bug error in 2.0.8]
Hi all I had a server crashed yesterday and i recovered my mail server running on exim with mailman 2.0.8 which has over 50 mailing list. There was too many mails in the mailman queue and i ran them manually and cleared. Since its a moderated list, when i got to the web interface for approval i get the following error Bug in Mailman version 2.0.8 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. hen i looked into the error file, the error message is as below Oct 03 18:10:02 2003 qrunner(17985): Traceback (most recent call last): Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/cron/qrunner, line 282, in ? Oct 03 18:10:02 2003 qrunner(17985): kids = main(lock) Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/cron/qrunner, line 195, in main Oct 03 18:10:02 2003 qrunner(17985): lock.refresh() Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/Mailman/LockFile.py, line 204, in refresh Oct 03 18:10:02 2003 qrunner(17985): raise NotLockedError Oct 03 18:10:02 2003 qrunner(17985): Mailman.LockFile . NotLockedError Oct 03 18:10:05 2003 qrunner(18082): Traceback (most recent call last): Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman//cron/qrunner, line 282, in ? Oct 03 18:10:05 2003 qrunner(18082): kids = main(lock) Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman//cron/qrunner, line 195, in main Oct 03 18:10:05 2003 qrunner(18082): lock.refresh() Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman/Mailman/LockFile.py, line 204, in refresh Oct 03 18:10:05 2003 qrunner(18082): raise NotLockedError Oct 03 18:10:05 2003 qrunner(18082): Mailman.LockFile . NotLockedError Oct 03 18:10:06 2003 qrunner(18092): Traceback (most recent call last): Oct 03 18:10:06 2003 qrunner(18092): File /home/mailman/cron/qrunner, line 275, in ? Oct 03 18:10:06 2003 qrunner(18092): lock.lock(timeout=0.5) Oct 03 18:10:06 2003 qrunner(18092): File /home/mailman/Mailman/LockFile.py, line 272, in lock how do i resolve this problem, am actually struck here... THanks in advance Regards Ganeshh -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] [mailman hit by a bug error in 2.0.8]
You might consider upgrading to version 2.0.13... It's been quite awhile since I played with 2.0.8, but it looks like a locking problem. You might want to check for any older lock files that are still in the ~mailman/locks directory. If there are, the lock files have the number of the running process as part of their name. You can use ps -ax |grep number to try and find the process that created the lock file. If you do not find the process, delete the lock file. Also, as a long-shot, you might want to run ~mailman/bin/check_perms -f to make sure that the rights for your locks directory is setup properly. Good Luck - Jon Carnes On Fri, 2003-10-03 at 09:38, Ganeshh wrote: Hi all I had a server crashed yesterday and i recovered my mail server running on exim with mailman 2.0.8 which has over 50 mailing list. There was too many mails in the mailman queue and i ran them manually and cleared. Since its a moderated list, when i got to the web interface for approval i get the following error Bug in Mailman version 2.0.8 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. hen i looked into the error file, the error message is as below Oct 03 18:10:02 2003 qrunner(17985): Traceback (most recent call last): Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/cron/qrunner, line 282, in ? Oct 03 18:10:02 2003 qrunner(17985): kids = main(lock) Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/cron/qrunner, line 195, in main Oct 03 18:10:02 2003 qrunner(17985): lock.refresh() Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/Mailman/LockFile.py, line 204, in refresh Oct 03 18:10:02 2003 qrunner(17985): raise NotLockedError Oct 03 18:10:02 2003 qrunner(17985): Mailman.LockFile . NotLockedError Oct 03 18:10:05 2003 qrunner(18082): Traceback (most recent call last): Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman//cron/qrunner, line 282, in ? Oct 03 18:10:05 2003 qrunner(18082): kids = main(lock) Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman//cron/qrunner, line 195, in main Oct 03 18:10:05 2003 qrunner(18082): lock.refresh() Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman/Mailman/LockFile.py, line 204, in refresh Oct 03 18:10:05 2003 qrunner(18082): raise NotLockedError Oct 03 18:10:05 2003 qrunner(18082): Mailman.LockFile . NotLockedError Oct 03 18:10:06 2003 qrunner(18092): Traceback (most recent call last): Oct 03 18:10:06 2003 qrunner(18092): File /home/mailman/cron/qrunner, line 275, in ? Oct 03 18:10:06 2003 qrunner(18092): lock.lock(timeout=0.5) Oct 03 18:10:06 2003 qrunner(18092): File /home/mailman/Mailman/LockFile.py, line 272, in lock how do i resolve this problem, am actually struck here... THanks in advance Regards Ganeshh -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] DirecPC, MailShield and VERP
In their infinite wisdom, DirecWay/DirecPC appear to be using a program that rejects VERP'd from addresses. The non-VERP'd messages are delivered by exim... 2003-10-03 08:38:38 1A5Q8F-0005zh-00 = [EMAIL PROTECTED] R=lookuphost T=remote_smtp H=mx1.direcpc.com [66.82.4.72] C=250 2.5.0 Ok. (relayed by MailShield) The VERP'd messages are rejected... 2003-10-03 08:35:43 1A5Q5u-0005vu-02 ** [EMAIL PROTECTED] R=lookuphost T=remote_smtp: SMTP error from remote mailer after MAIL FROM:[EMAIL PROTECTED] SIZE=4682: host mx1.direcpc.com [66.82.4.72]: 550 SMTP session aborted; 2 Is there anyway to disable VERP (which has proved very useful in handling bounces) on a per recipient or per list basis Thanks! -Jeff -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] [mailman hit by a bug error in 2.0.8]
Hi Jon I did the steps as you mentioned, i dont find any such process ids or lock files under locks directory... check_perms gave result as No Errors Found. The problem persists, what should i do next Regards Ganeshh Jon Carnes wrote: You might consider upgrading to version 2.0.13... It's been quite awhile since I played with 2.0.8, but it looks like a locking problem. You might want to check for any older lock files that are still in the ~mailman/locks directory. If there are, the lock files have the number of the running process as part of their name. You can use ps -ax |grep number to try and find the process that created the lock file. If you do not find the process, delete the lock file. Also, as a long-shot, you might want to run ~mailman/bin/check_perms -f to make sure that the rights for your locks directory is setup properly. Good Luck - Jon Carnes On Fri, 2003-10-03 at 09:38, Ganeshh wrote: Hi all I had a server crashed yesterday and i recovered my mail server running on exim with mailman 2.0.8 which has over 50 mailing list. There was too many mails in the mailman queue and i ran them manually and cleared. Since its a moderated list, when i got to the web interface for approval i get the following error Bug in Mailman version 2.0.8 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. hen i looked into the error file, the error message is as below Oct 03 18:10:02 2003 qrunner(17985): Traceback (most recent call last): Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/cron/qrunner, line 282, in ? Oct 03 18:10:02 2003 qrunner(17985): kids = main(lock) Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/cron/qrunner, line 195, in main Oct 03 18:10:02 2003 qrunner(17985): lock.refresh() Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/Mailman/LockFile.py, line 204, in refresh Oct 03 18:10:02 2003 qrunner(17985): raise NotLockedError Oct 03 18:10:02 2003 qrunner(17985): Mailman.LockFile . NotLockedError Oct 03 18:10:05 2003 qrunner(18082): Traceback (most recent call last): Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman//cron/qrunner, line 282, in ? Oct 03 18:10:05 2003 qrunner(18082): kids = main(lock) Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman//cron/qrunner, line 195, in main Oct 03 18:10:05 2003 qrunner(18082): lock.refresh() Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman/Mailman/LockFile.py, line 204, in refresh Oct 03 18:10:05 2003 qrunner(18082): raise NotLockedError Oct 03 18:10:05 2003 qrunner(18082): Mailman.LockFile . NotLockedError Oct 03 18:10:06 2003 qrunner(18092): Traceback (most recent call last): Oct 03 18:10:06 2003 qrunner(18092): File /home/mailman/cron/qrunner, line 275, in ? Oct 03 18:10:06 2003 qrunner(18092): lock.lock(timeout=0.5) Oct 03 18:10:06 2003 qrunner(18092): File /home/mailman/Mailman/LockFile.py, line 272, in lock how do i resolve this problem, am actually struck here... THanks in advance Regards Ganeshh -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] [mailman hit by a bug error in 2.0.8]
If I recall correctly, the next step is to look in the qfiles directory and move any files in there into a backup directory. Then test to see if a new message goes through. If that works, you can feed the waiting files back into that directory a few at a time and let them be delivered. At some point it will break again and that will help you find which one was corrupted (then delete that one - or set of files). Again, Good Luck! On Fri, 2003-10-03 at 11:21, Ganeshh wrote: Hi Jon I did the steps as you mentioned, i dont find any such process ids or lock files under locks directory... check_perms gave result as No Errors Found. The problem persists, what should i do next Regards Ganeshh Jon Carnes wrote: You might consider upgrading to version 2.0.13... It's been quite awhile since I played with 2.0.8, but it looks like a locking problem. You might want to check for any older lock files that are still in the ~mailman/locks directory. If there are, the lock files have the number of the running process as part of their name. You can use ps -ax |grep number to try and find the process that created the lock file. If you do not find the process, delete the lock file. Also, as a long-shot, you might want to run ~mailman/bin/check_perms -f to make sure that the rights for your locks directory is setup properly. Good Luck - Jon Carnes On Fri, 2003-10-03 at 09:38, Ganeshh wrote: Hi all I had a server crashed yesterday and i recovered my mail server running on exim with mailman 2.0.8 which has over 50 mailing list. There was too many mails in the mailman queue and i ran them manually and cleared. Since its a moderated list, when i got to the web interface for approval i get the following error Bug in Mailman version 2.0.8 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. hen i looked into the error file, the error message is as below Oct 03 18:10:02 2003 qrunner(17985): Traceback (most recent call last): Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/cron/qrunner, line 282, in ? Oct 03 18:10:02 2003 qrunner(17985): kids = main(lock) Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/cron/qrunner, line 195, in main Oct 03 18:10:02 2003 qrunner(17985): lock.refresh() Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/Mailman/LockFile.py, line 204, in refresh Oct 03 18:10:02 2003 qrunner(17985): raise NotLockedError Oct 03 18:10:02 2003 qrunner(17985): Mailman.LockFile . NotLockedError Oct 03 18:10:05 2003 qrunner(18082): Traceback (most recent call last): Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman//cron/qrunner, line 282, in ? Oct 03 18:10:05 2003 qrunner(18082): kids = main(lock) Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman//cron/qrunner, line 195, in main Oct 03 18:10:05 2003 qrunner(18082): lock.refresh() Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman/Mailman/LockFile.py, line 204, in refresh Oct 03 18:10:05 2003 qrunner(18082): raise NotLockedError Oct 03 18:10:05 2003 qrunner(18082): Mailman.LockFile . NotLockedError Oct 03 18:10:06 2003 qrunner(18092): Traceback (most recent call last): Oct 03 18:10:06 2003 qrunner(18092): File /home/mailman/cron/qrunner, line 275, in ? Oct 03 18:10:06 2003 qrunner(18092): lock.lock(timeout=0.5) Oct 03 18:10:06 2003 qrunner(18092): File /home/mailman/Mailman/LockFile.py, line 272, in lock how do i resolve this problem, am actually struck here... THanks in advance Regards Ganeshh -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] List Archive Link broken / not working
I am using Mailman 2.1.2. All the lists I have the Archive link takes me to a link link http://lists.serverone.co.uk/pipermail/bfm/ and I get the error 'The requested URL /pipermail/bfm/ was not found on this server.'. A friend of mine also has similar problems. Is this a known issue with a workaround. One think that may be relevent is we have changed the name of the server, alouth as the URL has lists. at the beginning I guess things are ok (the main domain on the server is oak.serverone.co.uk). Ben -- * Ben Edwards Tel +44 (0)1179 553 551 ICQ 42000477 * * Homepage - nothing of interest here http://gurtlush.org.uk * * Webhosting for the masses http://www.serverone.co.uk * * Critical Site Builderhttp://www.criticaldistribution.com * * online collaborative web authoring content management system * * Get alt news/views films online http://www.cultureshop.org * * i-Contact Progressive Video http://www.videonetwork.org * * Fun corporate graphics http://www.subvertise.org * * Bristol Indymedia http://bristol.indymedia.org * * Bristol's radical news http://www.bristle.org.uk * -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Problem after python upgrade
I upgraded python to version 2.2.2. Now, for _every_ message that hits any of our lists, we get an entry in the error file of something like: Oct 03 11:48:00 2003 (712) lost data files for filebase: 1065106187.152128+c53e6c32d2697be42fa4c19addd64fc104d934a7 The messages still get out, but really, 20mb of log file in one day is a bit much. Jerry Spaulding. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] [mailman hit by a bug error in 2.0.8]
Hi Jon The solution was finally simple, i renamed the error file to some other name and my web interface came up and i approved the tons of list mails. Thanks a lot for you help Regards Ganeshh Jon Carnes wrote: If I recall correctly, the next step is to look in the qfiles directory and move any files in there into a backup directory. Then test to see if a new message goes through. If that works, you can feed the waiting files back into that directory a few at a time and let them be delivered. At some point it will break again and that will help you find which one was corrupted (then delete that one - or set of files). Again, Good Luck! On Fri, 2003-10-03 at 11:21, Ganeshh wrote: Hi Jon I did the steps as you mentioned, i dont find any such process ids or lock files under locks directory... check_perms gave result as No Errors Found. The problem persists, what should i do next Regards Ganeshh Jon Carnes wrote: You might consider upgrading to version 2.0.13... It's been quite awhile since I played with 2.0.8, but it looks like a locking problem. You might want to check for any older lock files that are still in the ~mailman/locks directory. If there are, the lock files have the number of the running process as part of their name. You can use ps -ax |grep number to try and find the process that created the lock file. If you do not find the process, delete the lock file. Also, as a long-shot, you might want to run ~mailman/bin/check_perms -f to make sure that the rights for your locks directory is setup properly. Good Luck - Jon Carnes On Fri, 2003-10-03 at 09:38, Ganeshh wrote: Hi all I had a server crashed yesterday and i recovered my mail server running on exim with mailman 2.0.8 which has over 50 mailing list. There was too many mails in the mailman queue and i ran them manually and cleared. Since its a moderated list, when i got to the web interface for approval i get the following error Bug in Mailman version 2.0.8 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. hen i looked into the error file, the error message is as below Oct 03 18:10:02 2003 qrunner(17985): Traceback (most recent call last): Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/cron/qrunner, line 282, in ? Oct 03 18:10:02 2003 qrunner(17985): kids = main(lock) Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/cron/qrunner, line 195, in main Oct 03 18:10:02 2003 qrunner(17985): lock.refresh() Oct 03 18:10:02 2003 qrunner(17985): File /home/mailman/Mailman/LockFile.py, line 204, in refresh Oct 03 18:10:02 2003 qrunner(17985): raise NotLockedError Oct 03 18:10:02 2003 qrunner(17985): Mailman.LockFile . NotLockedError Oct 03 18:10:05 2003 qrunner(18082): Traceback (most recent call last): Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman//cron/qrunner, line 282, in ? Oct 03 18:10:05 2003 qrunner(18082): kids = main(lock) Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman//cron/qrunner, line 195, in main Oct 03 18:10:05 2003 qrunner(18082): lock.refresh() Oct 03 18:10:05 2003 qrunner(18082): File /home/mailman/Mailman/LockFile.py, line 204, in refresh Oct 03 18:10:05 2003 qrunner(18082): raise NotLockedError Oct 03 18:10:05 2003 qrunner(18082): Mailman.LockFile . NotLockedError Oct 03 18:10:06 2003 qrunner(18092): Traceback (most recent call last): Oct 03 18:10:06 2003 qrunner(18092): File /home/mailman/cron/qrunner, line 275, in ? Oct 03 18:10:06 2003 qrunner(18092): lock.lock(timeout=0.5) Oct 03 18:10:06 2003 qrunner(18092): File /home/mailman/Mailman/LockFile.py, line 272, in lock how do i resolve this problem, am actually struck here... THanks in advance Regards Ganeshh -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem after python upgrade
On Fri, 2003-10-03 at 12:01, Jerry Spaulding wrote: I upgraded python to version 2.2.2. Now, for _every_ message that hits any of our lists, we get an entry in the error file of something like: Oct 03 11:48:00 2003 (712) lost data files for filebase: 1065106187.152128+c53e6c32d2697be42fa4c19addd64fc104d934a7 The messages still get out, but really, 20mb of log file in one day is a bit much. Jerry Spaulding. Hope you saved you source tree for mailman. If you did, then simply redo: ./configure options; make install Best of luck - Jon Carnes -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Internal vs. external mail addresses
I have some internal mailing lists that are trying to be closed (only members can post without moderator approval). Unfortunately, we have different email addresses for internal vs. external mail, and our Exchange (:-/) server rewrites our addresses for mail we send internally to be from the internal address, even if we have a From: line etc. using the external address. So, when people send mail to the list part of the time it looks like it comes from their external address, and part of the time it looks like it comes from their internal address. When the mail looks like it comes from the other address and it's addressed to a closed list, the moder has to approve it (or they have to allow every user's alternate address individually). This is a major pain! I'm wondering if there's any capability in Mailman to have it understand that two different mail domains are really equivalent, so that [EMAIL PROTECTED] is the same as [EMAIL PROTECTED] (for example)? Anyone else have any ideas (not including changing the way our email or Exchange servers work... believe me I'd love to do that but...) -- --- Paul D. Smith [EMAIL PROTECTED] HASMAT--HA Software Mthds Tools Please remain calm...I may be mad, but I am a professional. --Mad Scientist --- These are my opinions---Nortel Networks takes no responsibility for them. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] List users get a 'rejected' error, but the messages are posted
Jon Carnes escribi: Ah-Ha! Sounds like you have a mailman list subscribed to *your* list. Take a look at your list membership and see if one of the subscribed emails is going back to the server. Happy hunting! Jon Carnes I manually send a mail to every subscriber of the list, and I didn't get the same error, so it seems that there is no a list subscribed to my list. I also looked at the lists in the subdomain es.urbenalia.com (where errors come from, instead of my subdomain fisica.urbenalia.com) and there wasn't any list created. Is Mailman site list mailman.es.urbenalia.com an internal list? I think that the answer could be the other possibility that you mentioned in the first message, an error with aliases. I told that to the admin, and he promised to me that next monday he'll try to fix it. What kind of error can cause this false rejections from another subdomain? Thank you a lot for your help, Be happy ;) Jaume -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] not allowing mass-subscription (web interface)
Is there an option to disable mass-subscription from the web interface, so that users can't add non-confirmed addresses themselves? Is there an option to require re-confirmation for addresses added (I guess only allowing invite but not subscribe would take care of this. Lastly, is there a way to get Mailman to record information about confirmation of a subscription (if a link was clicked, from what IP; if via an email message, the headers of the message)? Is there a way to tell whether a user was mass-subscribed or confirmed their subscription to the list? -- Since when is skepticism un-American? Dissent's not treason but they talk like it's the same... (Sleater-Kinney - Combat Rock) -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] affecting public name of list
Is it possible to change the public email address of a list (that reported in the rfc2369 headers, message footers, etc.) while maintaining a different name internally? Would there be any obvious problems I'm missing with such a feature? For our virtually hosted lists, we need independent namespaces on a per-domain basis. This isn't really something that Mailman currently handles AFAICT. So we might have: [EMAIL PROTECTED] (or [EMAIL PROTECTED]) forwarding to [EMAIL PROTECTED] Obviously this looks ugly, and encourages people to send to the wrong address; it's a simple matter, of course, to alias [EMAIL PROTECTED] to [EMAIL PROTECTED] This hack (if it worked) wouldn't be perfect, but would at least improve the virtual hosting situation for our purposes. For various reasons, it's not practical to do a unique installation of Mailman for each account or domain, and requiring unique listnames globally will also not work for our purposes. If not, consider this an RFE (I can submit one on the site if requested). If someone wanted to provide a patch for this (against 2.1.3), I might even be able to give them some money if it worked properly. -- Since when is skepticism un-American? Dissent's not treason but they talk like it's the same... (Sleater-Kinney - Combat Rock) -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] not allowing mass-subscription (web interface)
This would be a fairly simple hack to the source. You would simply grep for the option you want to comment out and when you find it in the source, comment it out. Then it won't appear in the web pages (that would be for every list). On Fri, 2003-10-03 at 18:31, Will Yardley wrote: Is there an option to disable mass-subscription from the web interface, so that users can't add non-confirmed addresses themselves? Is there an option to require re-confirmation for addresses added (I guess only allowing invite but not subscribe would take care of this. Lastly, is there a way to get Mailman to record information about confirmation of a subscription (if a link was clicked, from what IP; if via an email message, the headers of the message)? Is there a way to tell whether a user was mass-subscribed or confirmed their subscription to the list? -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Re: not allowing mass-subscription (web interface)
On Fri, Oct 03, 2003 at 07:07:54PM -0400, Jon Carnes wrote: This would be a fairly simple hack to the source. You would simply grep for the option you want to comment out and when you find it in the source, comment it out. Then it won't appear in the web pages (that would be for every list). Right. I was hoping that it was configurable in some way so that we don't have to end up maintaining too many local changes, but I'll keep this in mind. Now that Mailman is more suited to announce-only lists, it would make sense to have an option like this, as a site administrator may want to prevent users from abusing Mailman to send spam. -- Since when is skepticism un-American? Dissent's not treason but they talk like it's the same... (Sleater-Kinney - Combat Rock) -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Rebuilding message archive
I need to clean up a private archive, and followed the instructions someone posted in a previous thread here: edited the mbox file to remove the messages not wanted in the archive, deleted the html files in the listname/2003 directory, and then ran ./arch listname. It recreates the html files (except for the linked index.html-thread.html that used to be there), but there are still references to deleted messages on the Web page for the archive. What am I missing? Thanks, Allan -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Customizing Mailman
I really like the way Mailman is configured here: mail.python.org/mailman/listinfo/mailman-users. Users can add their real name (optionally). And when they change email addresses, it allows them to CHANGE, not unsub and resub (the way my own list works). I'd like to add these two features to my installation. Do I need to write the code to do that myself or has someone described how to do this somewhere? Thanks for any help! Allan Trick -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Customizing Mailman
Ah. We're on 2.0.13! I think I read that 2.1.2 is the latest stable release. Has that now been upgraded to 2.1.3? We just started using Mailman. Is an upgrade from where I'm at to 2.1.x going to be pretty straightforward? Thx, Allan -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Rebuilding message archive
Shame on me. I didn't read the FAQ thoroughly enough: Q. I want to get rid of some messages in my archive. How do I do this? A. David Rocher posts the following recipe: # remove $prefix/archives/private/listname # edit $prefix/archives/private/listname.mbox/listname.mbox [optional] # run $prefix/bin/arch listname I didn't delete the whole listname directory in archives/private before. Now I have, re-ran ./arch and the database is all updated! Allan -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
