Re: [Mailman-Users] Mailman admin question
On Thu, 21 Apr 2011, Mark Sapiro wrote: Ognen Duzlevski wrote: How do I find out what mailman join blah resolves to? I guess my question is ultimately - where do I look to find out who gets the join and subscribe requests? The MTA processes that ... I guess the OP did not want to know how mailman works, but who is the list administrator for list blah ... after all he inherited a system set up by somebody else. I hope somebody told him the master password ! I guess that doing http://hiswebaddress/mailman/admin he can see all the publicly advertised lists, and then enter each list administration panel. And if the list is not public, he should be able to do http://hiswebaddress/mailman/admin/blah Is that what the OP was asking ? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman admin question
On Thu, Apr 21, 2011 at 3:02 PM, Mark Sapiro m...@msapiro.net wrote: Ognen Duzlevski wrote: I have not played much with mailman but I am curious about something. I inherited a machine that runs mailman and one of the lists is setup through postfix aliases to do the following: blah-subscribe /usr/lib/mailman/mail/mailman subscribe blah blah-join /usr/lib/mailman/mail/mailman join blah Actually, I suspect those aliases look like blah-subscribe: |/usr/lib/mailman/mail/mailman subscribe blah blah-join: |/usr/lib/mailman/mail/mailman join blah How do I find out what mailman join blah resolves to? I guess my question is ultimately - where do I look to find out who gets the join and subscribe requests? The MTA processes that alias by piping the message to say 'blah-join' to the command '/usr/lib/mailman/mail/mailman join blah'. /usr/lib/mailman/mail/mailman is a wrapper which will ultimately deliver the message in this case to a script named (probably) /usr/lib/mailman/scripts/join which in turn will queue the message for Mailman's CommandRunner which will ultimately process the subscription request. For fun I subscribed to the blah list and never received a reply. I looked at the mail logs on the same machine and found an entry along the lines of: Apr 19 20:19:07 (242320 blah: pending name email ip That specific entry looks like an entry from Mailman's 'subscribe' log which says the subscription request for the blah list was received via the web from ip and a confirmation request was sent to email and Mailman is waiting for the user to confirm. If in fact it had an IP address, it resulted from a web subscribe and had nothing to do with an email to blah-join. If you didn't receive the confirmation request, check the MTA logs to see what happened to it. Also, check the MTA logs to see what happened to the mail to blah-join. There are a bunch of lines below mentioning other users subscribing to the same list and their requests being approved. I realize each machine can be set up differently to process mail but ultimately I am curious as to what mailman join list name actually does. As described above, it causes Mailman to process the message as a request from the sender to join list name. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan Mark, Thank you very much for the detailed reply - this is exactly what I was looking for! Ognen -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] disaster recovery help
My filesystem recently crashed, breaking some aspects of my mailman installation. The email portion of the list itself is still functioning (for non-digest subscribers), and all the archives are intact. But I seem to be missing some config pickles that are preventing digest delivery, emergency moderation, and probably other features that I haven't stumbled upon yet. All of the broken items generate the following message in the logs: Apr 21 09:00:01 2011 (29813) couldn't load config file /var/lib/mailman/lists/.keep/config.pck Apr 21 09:00:01 2011 (29813) couldn't load config file /var/lib/mailman/lists/.keep/config.pck.last [Errno 2] No such file or directory: '/var/lib/mailman/lists/.keep/config.pck.last' Apr 21 09:00:01 2011 (29813) couldn't load config file /var/lib/mailman/lists/.keep/config.db [Errno 2] No such file or directory: '/var/lib/mailman/lists/.keep/config.db' Apr 21 09:00:01 2011 (29813) couldn't load config file /var/lib/mailman/lists/.keep/config.db.last EOF read where object expected Apr 21 09:00:01 2011 (29813) All .keep fallbacks were corrupt, giving up Indeed, these files were lost in the filesystem crash, and I do not have backups of them. What are my options here? Can I do something like: - export list of users - move the broken list out of the way - create a new list with the same name - resubscribe members - copy the old archives back into the new list What gotchas am I going to run across trying to do something like the above? Any other suggestions? Appreciate any guidance ... Cheers, -C- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] disaster recovery help
Chris Haumesser wrote: My filesystem recently crashed, breaking some aspects of my mailman installation. The email portion of the list itself is still functioning (for non-digest subscribers), and all the archives are intact. But I seem to be missing some config pickles that are preventing digest delivery, emergency moderation, and probably other features that I haven't stumbled upon yet. All of the broken items generate the following message in the logs: Apr 21 09:00:01 2011 (29813) couldn't load config file /var/lib/mailman/lists/.keep/config.pck Apr 21 09:00:01 2011 (29813) couldn't load config file /var/lib/mailman/lists/.keep/config.pck.last [Errno 2] No such file or directory: '/var/lib/mailman/lists/.keep/config.pck.last' Apr 21 09:00:01 2011 (29813) couldn't load config file /var/lib/mailman/lists/.keep/config.db [Errno 2] No such file or directory: '/var/lib/mailman/lists/.keep/config.db' Apr 21 09:00:01 2011 (29813) couldn't load config file /var/lib/mailman/lists/.keep/config.db.last EOF read where object expected Apr 21 09:00:01 2011 (29813) All .keep fallbacks were corrupt, giving up Indeed, these files were lost in the filesystem crash, and I do not have backups of them. If there are or were any config.db* files, they were left after migration from Mailman 2.0.x to 2.1.x and contained old data from before the migration. Normally it is good to remove them because if they exist and are useable, in a situation such as this Mailman may fall back to using one which is not what you want. The above seems to indicate that there is a /var/lib/mailman/lists/.keep/config.pck, but it can't be unpickled for some reason. Is that the case? Given the above, I am amazed that the .keep list works at all, or is it some other list? What are my options here? Can I do something like: - export list of users - move the broken list out of the way - create a new list with the same name - resubscribe members - copy the old archives back into the new list What gotchas am I going to run across trying to do something like the above? If the list you are talking about is the list named .keep, I don't think you will even be able to export a list of users. If it is some other list, I suggest you move the /var/lib/mailman/lists/.keep/ directory somewhere else (out of the /var/lib/mailman/lists/ directory), or, if .keep was not one of your lists, maybe just remove the /var/lib/mailman/lists/.keep/ directory and its contents. That in itself may be sufficient to fix the digests problem with other lists (because cron/senddigests is dying on the .keep list and doesn't get to the others). I'm not sure about emergency moderation, but at least (re)move that .keep/ directory, and then see what problems remain and what error log messages might be associated with them. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] disaster recovery help
On 4/22/11 7:52 AM, Mark Sapiro wrote: If there are or were any config.db* files, they were left after migration from Mailman 2.0.x to 2.1.x and contained old data from before the migration. There are no config.db files in /var/lib/mailman, they are only mentioned in the log. The above seems to indicate that there is a /var/lib/mailman/lists/.keep/config.pck, but it can't be unpickled for some reason. Is that the case? Veritably so. It is an empty file (0 bytes). Given the above, I am amazed that the .keep list works at all, or is it some other list? I never created a list called .keep, and indeed the problems are with a different list called 'camp', which is not mentioned anywhere in the error log. I was assuming the .keep folder had something to do with mailman internals. After reading your message, I infer that is not the case, and now suspect it is perhaps a remnant from running fsck on the filesystem. Interestingly, none of my actual lists seem to be missing their config.pck file. Gotta love filesystem corruption. (New backup plan is now in place ... ) If it is some other list, I suggest you move the /var/lib/mailman/lists/.keep/ directory somewhere else (out of the /var/lib/mailman/lists/ directory) ... Seems reasonable, I'll give it a shot. That in itself may be sufficient to fix the digests problem with other lists (because cron/senddigests is dying on the .keep list and doesn't get to the others). That could certainly explain the digests problem, anyway. Thanks for your help! -C- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] disaster recovery help
Chris Haumesser writes: I was assuming the .keep folder had something to do with mailman internals. That looks like a distro device to make sure that the data directories don't get deleted if you delete the package. Possibly what is happening is that the distro's version is patched to ignore distro housekeeping. Or perhaps the disk corruption flipped the I am a directory bit on that, and the recovery process (fsck) actually populated it. Then mailman decided it was a list, and created a config.pck (empty) for it. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
