Re: [Mailman-Users] restarting a blocked list
i'm actually working with 2.1.3 (always the latest version is good ;-) ) No problems found with checkperms. Now, i'm going to write my little experiment with mailman, i don't know if somebody did it before, look the /usr/local/mailman in machine1 bash-2.03$ cd /usr/local/mailman/ bash-2.03$ ls -la total 54 drwxrwsr-x 18 mailman mailman 512 Oct 22 10:42 . drwxr-xr-x 11 root other512 Sep 19 12:00 .. lrwxrwxrwx 1 root mailman 26 Jul 3 12:50 archives - /dirarcon/mailman/archives drwxrwsr-x 2 root mailman 1024 Oct 7 12:23 bin drwxrwsr-x 2 root mailman 512 Oct 7 12:23 cgi-bin -rw-r- 1 root mailman 4133 Oct 22 10:42 config.pck drwxrwsr-x 2 root mailman 512 Oct 7 12:25 cron drwxrwsr-x 2 root mailman 2048 Oct 21 12:09 data drwxrwsr-x 2 root mailman 512 Oct 7 12:23 icons lrwxrwxrwx 1 root mailman 23 Jul 3 12:50 lists - /dirarcon/mailman/lists drwxrwsr-x 2 root mailman 512 Oct 23 13:25 locks drwxrwsr-x 2 root mailman 512 Oct 1 08:26 logs drwxrwsr-x 2 root mailman 512 Oct 7 12:23 mail drwxrwsr-x 11 root mailman 1536 Oct 7 12:23 Mailman drwxrwsr-x 24 root mailman 512 Oct 7 11:27 messages drwxrwsr-x 6 root mailman 512 Jul 1 12:41 pythonlib drwxrwsr-x 11 root mailman 512 Oct 7 11:34 qfiles drwxrwsr-x 2 root mailman 512 Oct 7 12:42 scripts drwxrwsr-x 2 root mailman 512 Jul 1 12:40 spam drwxrwsr-x 26 root mailman 512 Oct 7 11:27 templates drwxrwsr-x 4 root mailman 512 Oct 7 12:23 tests As you can see mailman is working in machine1 and writting the lists information into a networkapplyant (dirarcon) Now, machine2 has another mailman writting into dirarcon too, with same lists, and in DNS i put machine1 and machine2 with one name, mailmans.domain.es... so roundrobin of DNS sometimes send messages to lists by machine1 and sometimes by machine2... no problem... all work fine but the most traffic lists ([EMAIL PROTECTED]) sometimes stops (once per a couple of weeks)... theory of unix says that two diferents tasks can open and write a file at same time, so i thought that was posible... Now machine2 is stoped, and DNS only has a mailmans.domain.es - machine1, at momment [EMAIL PROTECTED] is working good, so i'm beginning to think that theory of unix is my problem, and if only one machine is working with mailman, comunicaciones @cedex.es won't stop... anyway, i'll study qfiles, thank you very much jonc, and hope you to enjoy my experiment :-) Jon Carnes wrote: On Tue, 2003-10-21 at 05:40, javier wrote: hello... one of the ten lists i have working stoped sending messages,. Ok, at moment i have to rmlist blocked list, saving the config file, and i have to create the same new list again, with same config file, and without removing archives... but... i don't know if i could solve this problem better... i can't find why the list stops sending messages, may the cron process of sending digest is the reason, i've send a HELP message yesterday with the output cron command. thank you very much Javier, Look in the FAQ for Mailman (3.14) might be helpful. If you are not running the latest version of your Mailman branch, then you should consider upgrading: For 2.0. that would be 2.0.13 For 2.1 that would be 2.1.3 In general, check for a locking file problem first, then check the qfiles to see what is stuck in the queue. It may be that one of your users on that list has a do-it-yourself email program that is sending out corrupt headers. You should NEVER need to delete the existing list. If this solves the problem for you, then try running check_perms -f and see if that finds any problems. This will check the rights on most of the key files needed for Mailman to run properly. Good 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/b.englefield%40uel.ac.uk -- Javier Romero Casado tel.913357274 Dep. Comunicaciones CEDEX -- 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] restarting a blocked list
On Thu, 2003-10-23 at 07:37, javier wrote: i'm actually working with 2.1.3 (always the latest version is good ;-) ) theory of unix says that two diferents tasks can open and write a file Do you have the ~mailman/locks directory shared as well? That should do a fair job of keeping the processes (even on multiple machines) from writing to the files simultaneously. at same time, so i thought that was posible... Now machine2 is stoped, and DNS only has a mailmans.domain.es - machine1, at momment [EMAIL PROTECTED] is working good, so i'm beginning to think that theory of unix is my problem, and if only one machine is working with mailman, comunicaciones @cedex.es won't stop... anyway, i'll study qfiles, thank you very much jonc, and hope you to enjoy my experiment :-) Cool. I've used LVS to do something similar. In my case, I run a separate process in the background that keeps the background servers synchronized (and creates a lock file during the sync). In the end, I think that is a simpler setup, as each server can operate independently. Originally I set it up so that only one of the background servers handled the Web-requests - that removed any latency issues from users who expect to see the changes instantly propagated. Good 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
Re: [Mailman-Users] restarting a blocked list
Interesting... something similar happened to us (currently running version 2.1.2). Two of our lists were not responsive and had to be re-built, after migrating from 2.0.x. Now, another list is only partially responsive, and might have been that way for a while: if I send from Outlook or Eudora to that list, the message appears waiting to be Accepted, as it should; however, if I send the message via a ColdFusion program the message appears to be sent to the list, but never shows up on the list. Meanwhile, the same ColdFusion code can send the same email to other lists in the same Mailman installation just fine. Our network administrator left for another job last week, and his replacement has not been hired yet. I would like to solve this before a new person gets up to speed... perhaps I will indeed remove the whole bad list, since it is only a test list and only has about six entries in it. Is it as simple as finding one file and using rm? I wonder if going to 2.1.3 might help with this problem David Alexander New York Software Industry Association At 09:13 AM 10/21/2003 -0400, Jon Carnes wrote: On Tue, 2003-10-21 at 05:40, javier wrote: hello... one of the ten lists i have working stoped sending messages,. Ok, at moment i have to rmlist blocked list, saving the config file, and i have to create the same new list again, with same config file, and without removing archives... but... i don't know if i could solve this problem better... i can't find why the list stops sending messages, may the cron process of sending digest is the reason, i've send a HELP message yesterday with the output cron command. thank you very much Javier, Look in the FAQ for Mailman (3.14) might be helpful. If you are not running the latest version of your Mailman branch, then you should consider upgrading: For 2.0. that would be 2.0.13 For 2.1 that would be 2.1.3 In general, check for a locking file problem first, then check the qfiles to see what is stuck in the queue. It may be that one of your users on that list has a do-it-yourself email program that is sending out corrupt headers. You should NEVER need to delete the existing list. If this solves the problem for you, then try running check_perms -f and see if that finds any problems. This will check the rights on most of the key files needed for Mailman to run properly. Good 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/dalexander%40nysia.org David Alexander President, Opal Computing (718) 343-4054 -- 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] restarting a blocked list
hello... one of the ten lists i have working stoped sending messages,. Ok, at moment i have to rmlist blocked list, saving the config file, and i have to create the same new list again, with same config file, and without removing archives... but... i don't know if i could solve this problem better... i can't find why the list stops sending messages, may the cron process of sending digest is the reason, i've send a HELP message yesterday with the output cron command. thank you very much -- Javier Romero Casado tel.913357274 Dep. Comunicaciones CEDEX -- 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] restarting a blocked list
On Tue, 2003-10-21 at 05:40, javier wrote: hello... one of the ten lists i have working stoped sending messages,. Ok, at moment i have to rmlist blocked list, saving the config file, and i have to create the same new list again, with same config file, and without removing archives... but... i don't know if i could solve this problem better... i can't find why the list stops sending messages, may the cron process of sending digest is the reason, i've send a HELP message yesterday with the output cron command. thank you very much Javier, Look in the FAQ for Mailman (3.14) might be helpful. If you are not running the latest version of your Mailman branch, then you should consider upgrading: For 2.0. that would be 2.0.13 For 2.1 that would be 2.1.3 In general, check for a locking file problem first, then check the qfiles to see what is stuck in the queue. It may be that one of your users on that list has a do-it-yourself email program that is sending out corrupt headers. You should NEVER need to delete the existing list. If this solves the problem for you, then try running check_perms -f and see if that finds any problems. This will check the rights on most of the key files needed for Mailman to run properly. Good 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
Re: [Mailman-Users] restarting a blocked list
On Tue, 2003-10-21 at 10:02, David Alexander wrote: Interesting... something similar happened to us (currently running version 2.1.2). Two of our lists were not responsive and had to be re-built, after migrating from 2.0.x. Now, another list is only partially responsive, and might have been that way for a while: if I send from Outlook or Eudora to that list, the message appears waiting to be Accepted, as it should; however, if I send the message via a ColdFusion program the message appears to be sent to the list, but never shows up on the list. Meanwhile, the same ColdFusion code can send the same email to other lists in the same Mailman installation just fine. Our network administrator left for another job last week, and his replacement has not been hired yet. I would like to solve this before a new person gets up to speed... perhaps I will indeed remove the whole bad list, since it is only a test list and only has about six entries in it. Is it as simple as finding one file and using rm? I wonder if going to 2.1.3 might help with this problem David Alexander New York Software Industry Association In your case, I recommend that you change the mailman alias to point to a local mailbox and then have the cold fusion program send off an email. That mail will be captured in the local mailbox and you can then examine the headers with a critical eye. In particular, I would look for white space that extends beyond end characters and any non-ascii character that might be in the header (even X-headers). Good Luck. It will be interesting to see what you come up with. 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
Re: [Mailman-Users] restarting a blocked list
Jon, Thanks for the suggestion. I just find it strange that the seem procedure is working with other lists on the same Mailman installation. Are there any other restrictions I should know about concerning the header or configurations? For example, maybe there is a configuration option that is controllable about what gets put in the headers, and that is set differently on the different lists. I have tried playing with a few of the settings and comparing between lists, but so far have not had any luck. Plus, while I am at it :--), each time the announcements go out, there is now a CC: line going to the list address, that all recipients receive. I have played with that as well, but it still shows up, ever since we moved to 2.1.2. Regards, David Alexander NYSIA At 10:29 AM 10/21/2003 -0400, Jon Carnes wrote: On Tue, 2003-10-21 at 10:02, David Alexander wrote: Interesting... something similar happened to us (currently running version 2.1.2). Two of our lists were not responsive and had to be re-built, after migrating from 2.0.x. Now, another list is only partially responsive, and might have been that way for a while: if I send from Outlook or Eudora to that list, the message appears waiting to be Accepted, as it should; however, if I send the message via a ColdFusion program the message appears to be sent to the list, but never shows up on the list. Meanwhile, the same ColdFusion code can send the same email to other lists in the same Mailman installation just fine. Our network administrator left for another job last week, and his replacement has not been hired yet. I would like to solve this before a new person gets up to speed... perhaps I will indeed remove the whole bad list, since it is only a test list and only has about six entries in it. Is it as simple as finding one file and using rm? I wonder if going to 2.1.3 might help with this problem David Alexander New York Software Industry Association In your case, I recommend that you change the mailman alias to point to a local mailbox and then have the cold fusion program send off an email. That mail will be captured in the local mailbox and you can then examine the headers with a critical eye. In particular, I would look for white space that extends beyond end characters and any non-ascii character that might be in the header (even X-headers). Good Luck. It will be interesting to see what you come up with. 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
