Re: [Mailman-Users] Admin access for list creator
Mark Dale wrote: Is there a way for a list-creator to access the admin section of different lists? Only with the list's admin password or the Mailman site password. The list-creator password conveys no additional authority. Of course, when you create a list, you know the admin password because you specified it, but after you turn the list over to an admin who changes the password, you either need that password or the site password to admin the list. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman refusing to stop/start with errors PID unreadable
On 1 Aug 2007 at 13:15, Brad Knowles wrote: Unfortunately, you're using a lot of other software that we are not generally familiar with, and from our perspective we can't think of anything that might cause these problems from within our code, but of course we can't be 100% certain. You really need to find someone who has deep knowledge of those other bits of code, as well as knowledge of how those interface to Mailman. Hi Brad! Thanks for your reply. I suppose I was hoping that one or other of the wiser list members might be able to say: That issue is typically caused by such and such and the normal method of resolving is to do so and so... Even agreement that reinstalling Mailman is the only option would help - slightly :-) But you're right... The Webmin/Virtualmin factor does make it a slightly more complex mix. If I discover anything through the other enquiries I've made I'll post back here and, in the meantime, if anyone has inspiration then I'm all ears. Andrew -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] inqury
hulo l was asking to know if there similar codes in php and mysql that l acn implement the mailing list in and if any please post for me one or give me a link and the other thing is that l have some codes in realtion to the mailing list creation could add for me more functionality so that every member subscribed to aminling list acn be able to communicate to each other thanks hope to hear from you [EMAIL PROTECTED] Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Admin access for list creator
The site admin password gives you full web admin access, at least as far as Mailman goes. You can access any list you want -- this is the Mailman equivalent of root password, and should be treated with great care. -- Brad Knowles [EMAIL PROTECTED] Sent from my iPhone On Aug 2, 2007, at 12:45 AM, Mark Dale [EMAIL PROTECTED] wrote: Hello Mailman Users Is there a way for a list-creator to access the admin section of different lists? My password allows me to create lists, but not access the admin section of various lists whose administrators have their own passwords. Thanks in advance for any clues. regards Mark Dale -- Mark Dale phone: 02 6112 8632 mobile: 0403 831 748 email: [EMAIL PROTECTED] -- -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/brad%40shub-internet.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] URL to obtain List overview page...
We are experimenting with hosting our Mailman installation alongside the Webmin/Virtualmin control panel. By default this presumes that list management will take place within the Virtualmin area but this 'hides' the normal Mailman URLs for viewing lists etc etc. Mostly these can be recovered by discovering the appropriate new aliases to create. However, there is one URL that I cannot figure out... Viewing the standard List Overview for a domain. In the traditional approach http://domain/mailman/listinfo/list-name takes a user to the user preferences and information screen for the list called [EMAIL PROTECTED] Equally http://domain/mailman/listinfo/ provides the standard rosta of lists at domain. The URL we have for the first situation is in the form: https://domain/virtualmin-mailman/unauthenticated/listinfo.cgi/list-name This works just fine. https://domain/virtualmin-mailman/unauthenticated/listinfo.cgi might be expected to produce the rosta of lists but does not do so. However, put a non-existent list name at the end as in .../unauthenticated/listinfo.cgi/noexist-list and the lists of lists appears (but with a brief message saying the nonexistent list does not exist). Does anyone know what, if any, argument can go after listinfo.cgi to generate the list of lists? The same issue with the admin list or lists. Andrew -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] I don't get the message saying that your message is pending to be approved
Hello. I've got a problem with my mailman list. When I send a message to the list I usually got a mail saying that I had a message pending to be approved and that I had to go to a url to accept this message. Now, I don't get this message, but if I go through the administrator's list menu I can accept (or reject or discard) the delivery and it's been delivered to all the recipients. So, do you know how could I mend it? Is there any process that should be running or something like that? Thank you very much -- View this message in context: http://www.nabble.com/I-don%27t-get-the-message-saying-that-your-message-is-pending-to-be-approved-tf4204626.html#a11959879 Sent from the Mailman - Users mailing list archive at Nabble.com. -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Is it possible to filter what is archived?
Mark Sapiro wrote: Mike Peachey wrote: What I would like to do is filter what gets archived so that if a message originates in mailman (ie from an umbrella list) it doesn't get archived. I'm pretty sure this isn't what you're asking for, but you could just turn off archiving on all the umbrella lists so the posts are only archived in the 'final' lists. I know this results in duplicate archived messages for different 'final' lists, but if I'm a member of listx, I want to see listx posts in listx's archive regardless of whether they came directly or via one or more umbrellas. If only it were that easy, the problem I have is that I have list admins complaining to me (and my boss' boss) that their archive is polluted with messages from top-level lists and they want their archive to just contain messages sent directly to their list. -- Kind Regards, __ Mike Peachey, IT Tel: +44 114 281 2655 Fax: +44 114 281 2951 Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK Comp Reg No: 3191371 - Registered In England http://www.jennic.com __ -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] rare problem
Sorry for delay, it was holidays time and today i've returned. When i try to send a mail with a from like this: From: test [EMAIL PROTECTED] It works fine and mail arrived to list. Problem seems to appear when From line exceeds certain number of characters (50) and contains accents, when it occurs From line splits in two, and mail didn't arrive to destiny list. Another problem comes when system tries to send returned mail to sender and From line didn't exist, then sender never knows that its mail hasd not arrived to list. Thanks! Mark Sapiro escribió: Jesús Oliván wrote: Yes, patch is installed. Sorry, pattern was [EMAIL PROTECTED], but we own uab.es too. When message is sent, we receive this response: El missatge adjunt ha estat automàticament descartat. Asunto: De: test12345á6789-12345á6789-12345á6789-12345á6789-12345á6789- [EMAIL PROTECTED] So it appears that with the patch installed, Mailman is properly unfolding and decoding the the folded RFC 2047 encoded From: header in the post. Fecha: Wed, 04 Jul 2007 13:57:02 +0200 Para: [EMAIL PROTECTED] However, I find it very curious that this 'forwarded post' seems to be missing the Date:, From:, Subject and To: headers from the original post and the User-Agent: header has been changed to 'Agente de usuario::'. What happens if you attempt to post a message with simply From: test [EMAIL PROTECTED] instead of the RFC 2047 encoded and folded From: header? -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Admin access for list creator
Thanks. sudo mmsitepass did the trick. regards Mark Dale Brad Knowles wrote: The site admin password gives you full web admin access, at least as far as Mailman goes. You can access any list you want -- this is the Mailman equivalent of root password, and should be treated with great care. --Brad Knowles [EMAIL PROTECTED] Sent from my iPhone On Aug 2, 2007, at 12:45 AM, Mark Dale [EMAIL PROTECTED] wrote: Hello Mailman Users Is there a way for a list-creator to access the admin section of different lists? My password allows me to create lists, but not access the admin section of various lists whose administrators have their own passwords. Thanks in advance for any clues. regards Mark Dale -- Mark Dale phone: 02 6112 8632 mobile: 0403 831 748 email: [EMAIL PROTECTED] -- -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/brad%40shub-internet.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- -- Mark Dale phone: 02 6112 8632 mobile: 0403 831 748 email: [EMAIL PROTECTED] -- -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] 550 User Unknown when trying to post tomailman/sendmail list
Mark, Can you do it another way? I heard talk of setting up aliases? I really only have a few lists that I need setup I don't mind manual intervention. Andy From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Thu 8/2/2007 12:39 AM To: Melick Andy; Bryan Carbonnell Cc: mailman-users@python.org Subject: RE: [Mailman-Users] 550 User Unknown when trying to post tomailman/sendmail list Melick Andy wrote: I added an entry to virtusertable and now I get this error when trying to send messages to my list. Before I was getting user doesn't exist. Mailman is a subdomain on my domain. I did this from looking at someone else example, but not certain if its right. my virtusertable: mailman.domain.com[EMAIL PROTECTED] =20 #5.0.0 smtp;554 5.0.0 rewrite: excessive recursion (max 50), ruleset canonify All I know about mm-handler is what I read in README.mm-handler. I know even less about Sendmail. This is contributed software provided as-is without support be the Mailman project. See the README file in the contrib directory. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] mailman, attachment and digital sign
Hello, we have installed Mailman, the GNU Mailing List Manager version 2.1.5 If we send a digital signed e-mail *with attachment* to a list we obtain the following message: Digital Signature Is Not Valid This message includes a digital signature, but the signature is invalid. The signature does not match the message content correctly. The message appears to have been altered after the sender signed it. You should not trust the validity of this message until you verify its contents with the sender. Without attachment, digital sign is OK. In the past we have had the same problem even send simply digital signed e-mail (without attachment), but in the past mailman was used to add a message footer in all e-mail. We have modifed mailman so now it not add the message footer anymore. Now we still have this problem only when we send digital signed e-mail *with attachment*. Thanks. Marco De Rossi -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] URL to obtain List overview page...
Andrew Steele wrote: https://domain/virtualmin-mailman/unauthenticated/listinfo.cgi might be expected to produce the rosta of lists but does not do so. What does it produce? However, put a non-existent list name at the end as in .../unauthenticated/listinfo.cgi/noexist-list and the lists of lists appears (but with a brief message saying the nonexistent list does not exist). Does anyone know what, if any, argument can go after listinfo.cgi to generate the list of lists? How about just a trailing slash? -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] I don't get the message saying that your message ispending to be approved
miguel8883 wrote: When I send a message to the list I usually got a mail saying that I had a message pending to be approved and that I had to go to a url to accept this message. Now, I don't get this message, but if I go through the administrator's list menu I can accept (or reject or discard) the delivery and it's been delivered to all the recipients. So, do you know how could I mend it? Is there any process that should be running or something like that? There are two possibilities. If VirginRunner is not running, no Mailman generated messages will be delivered and they will all sit in qfiles/virgin/ (see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.078.htp for more information). The other possibility is General Options-admin_immed_notify is set to 'No'. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] 550 User Unknown when trying to post tomailman/sendmail list
Melick Andy wrote: Can you do it another way? I heard talk of setting up aliases? I really only have a few lists that I need setup I don't mind manual intervention. 1) Undo everything you did for mm-handler. 2) Be sure that the Defaults.py setting MTA = 'Manual' is not overridden in mm_cfg.py (You may have put MTA = None in mm_cfg.py for mm-handler). 3) Run Mailman's bin/genaliases. This will give you a list of 10 aliases per list. Add these exact aliases to /etc/aliases. 4) Run Sendmail's /usr/bin/newaliases command. That's it. After that, each time a list is created or deleted, you will get a notice of the aliases to be added or deleted in /etc/aliases. Make the change and run newaliases again. If you want to automate this process, see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.049.htp, but if list creation/deletion is rare, it may not be worth it. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Is it possible to filter what is archived?
Mike Peachey wrote: If only it were that easy, the problem I have is that I have list admins complaining to me (and my boss' boss) that their archive is polluted with messages from top-level lists and they want their archive to just contain messages sent directly to their list. Make a custom handler (see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.067.htp) that checks mlist.umbrella_list, and if true add an X-No-Archive: header to the message. E.g. def process(mlist, msg, msgdata): if mlist.umbrella_list: msg['X-No-Archive'] = 'Yes' The handler has to be in the pipeline prior to 'ToArchive'. The header X-Archive: No also works. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] URL to obtain List overview page...
Andrew Steele wrote: Thanks for replying... It simply produces an invalid URL message within the Webmin/Virtualmin interface as if it is looking for an undeclared variable - which it finds if the trailing list name is provided. I looked at your examples. It seems that the https://domain/virtualmin-mailman/unauthenticated/listinfo.cgi URI gets 'errored' in the Webmin/Virtualmin interface and never gets to Mailman. I also tried things like https://domain/virtualmin-mailman/unauthenticated/listinfo.cgi?junk=none and https://domain/virtualmin-mailman/unauthenticated/listinfo.cgi/?junk=none and they don't work either. If you can't convince Webmin/Virtualmin that https://domain/virtualmin-mailman/unauthenticated/listinfo.cgi and https://domain/virtualmin-mailman/unauthenticated/listinfo.cgi/ are valid URIs, I think you're stuck. I don't think there's any X that you can put in https://domain/virtualmin-mailman/unauthenticated/listinfo.cgi/X that won't be interpreted by Mailman as a list name. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] rare problem
Jesús Oliván wrote: When i try to send a mail with a from like this: From: test [EMAIL PROTECTED] It works fine and mail arrived to list. Problem seems to appear when From line exceeds certain number of characters (50) and contains accents, when it occurs From line splits in two, and mail didn't arrive to destiny list. Another problem comes when system tries to send returned mail to sender and From line didn't exist, then sender never knows that its mail hasd not arrived to list. Have you installed the patch I gave you in an earlier reply and which can be found at http://mail.python.org/pipermail/mailman-users/attachments/20070709/c08e6575/attachment.txt, and did you restart mailman (bin/mailmanctl restart) after installing the patch? -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Migrating from 1.0 to 2.1.9
Looks like I jumped to a conclusion on the dumpdb script. The mailman/bin directory on the old server does not contain a dumpdb script however, I just realized that it may be due to the fact that someone may have deleted it and not that there was no such script for Mailman 1.0. Will a dumpdb script from a newer version of Mailman work on the old 1.0 version? It appears there was no dumpdb in Mailman 1.0 or 1.1. There is one in Mailman 2.0, but I don't know it it will work. You could try it. However, even Mailman 1.0 has a withlist which might be useful. Here are some other thoughts. There's no way to convert the list admin and moderator passwords. See the 2.1.9 change_pw for why and what to do about it. There's code in Mailman/versions.py that goes back to 1.0. Instead of creating new lists in the new installation, you could try just moving the old lists/listname/config.db, at least for one test to see what happens. It might work. It won't solve the password problem, but if it works, it should save you a bunch of work. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan I moved the config.db file from a test list to the new server. I logged in to the web interface and all the members were there and the settings looked good. Moving the archives over and rebuilding them even worked. However, if I try to run dumpdb on the newly migrated list I get this error: NameError: global name 'DumperSwitchboard' is not defined Although there are other posts in the mailman-users archives where people saw this problem; there was no resolution. So it seems that even though the list appears to function properly and the web intercase works, something is not quite right with the config.db file and Mailman version 2.1.9. It makes me a little nervous to run the migrated lists in production knowing that I can never run dumpdb and I don't know what else might be broken. I think I will go with my original plan of pre-creating each list on the new server, importing the list member's email addresses and manually setting up the list. With 150 lists, I think I can do it in a week. I'd like to try the transfer of config data programatically using withlist but I can't seem to find any comprehensive documentation on the use this command. There are lots of posts in the archives and on google concerning specific uses of the command but no comprehensive usage instructions in one place. I'll keep searching. -- We've Got Your Name at http://www.mail.com! Get a FREE E-mail Account Today - Choose From 100+ Domains -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Fw: problem in Makefile for mailman
In a flurry of recycled electrons, Mark Sapiro wrote: This is not our Makefile. I can only guess that it is a FreeBSD port Makefile. But after installation (FreeBSD 6.2, /usr/ports/mail/mailman) when I send Yep, it's a FreeBSD port. While I run both free and open bsd, I've found that there are a few things better installed from original source. Mailman is one of them. The only thing that the port really gives is the uname/group consistent with fbsd standards. You can easily pull that out of the makefile. (ISTR that the tcl port lags the actual release a bit, too. Can't think of the others off hand.) z! -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Fw: problem in Makefile for mailman
Yep, it's a FreeBSD port. While I run both free and open bsd, I've found that there are a few things better installed from original source. Mailman is one of them. Look at the changes that FreeBSD has made. You will probably find some that you do not understand. I did the same with Ubuntu, and most of the changes were not documented, so I had no idea why they were made. -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Sanity-checking individual lists for health?
On Jul 24, 2007, at 10:46 PM, Mark Sapiro wrote: Chris Waltham wrote: I have been tasked with moving a Mailman 2.0.12 installation from a Solaris (SPARC) server to a Linux (x86) server. The Linux server will be receiving a copy of Mailman 2.1.9, so obviously I am making the 2.0.x - 2.1.x jump in there. Also, on Solaris, Mailman lives in / home/mailman but on Linux I will be putting it in /blender/mailman (and thus using move_list to update archives, fix_url, etc.) What makes this migration slightly tricky is that the server hosts around 840 lists. Therefore, going through each list pre- and post- migration by hand would be a little time-consuming for me, so I want to avoid that where possible :-)I noticed that, when doing a make update when installing 2.1.9, a couple of lists from 2.0.12 failed the update process and I had to Control-C them for the process to continue. I'm not sure what the exact problem was, hence I'm wondering if there is any kind of check that I can run in a FOR loop to verify a list's integrity. And, yes, I've run check_db and check_perms and neither report problems, this just seems to be a handful of lists out of the 800-odd that seem a little flaky. There is little you can do to verify the integrity of a list other than trying to instantiate it which will also update it if necessary (and possible). check_perms only checks permissions (and it has a bug regarding archives/private). check_db only checks that list data can be loaded from lists/listname/config.* files. It doesn't sanity check the result. Do you know which lists failed in bin/update (run by make update)? If so do these lists have lists/listname/config.pck files which are converted from the config.db files and indicate the conversion of the list data was probably successful. In any case, are there any lists that don't have lists/listname/config.pck files? These would be the problem lists. One list that failed both make update and the below-mentioned config_list is named bowsun. Here is a copy of its contents: drwxrwsr-x2 mailman mailman 4096 Jul 24 11:03 ./ drwxrwsr-x 844 mailman mailman 65536 Jul 24 11:01 ../ -rwxr-xr--1 mailman mailman 1692 Jul 30 2003 admindbpreamble.html* -rwxr-xr--1 mailman mailman357 Jan 19 2001 archives.html* -rw-rw1 rootmailman 15076 Jul 23 15:37 config.db -rw-rw1 mailman mailman 15075 Jun 29 07:03 config.db.last -rw-rw1 rootmailman 12578 Jul 24 11:03 config.pck -rw-rw1 rootmailman 12578 Jul 24 10:51 config.pck.last -rwxr-xr--1 mailman mailman189 Jan 19 2001 handle_opts.html* -rwxr-xr--1 mailman mailman 1026 Jan 19 2001 headfoot.html* -rwxr-xr--1 mailman mailman 3136 Jan 19 2001 listinfo.html* -rwxr-xr--1 mailman mailman 4106 Jan 19 2001 options.html* -rw-rw-r--1 rootmailman 443875 Jul 24 08:41 request.pck -rwxr-xr--1 mailman mailman 1169 Jan 19 2001 roster.html* -rwxr-xr--1 mailman mailman198 Jan 19 2001 subscribe.html* I'm not sure how to start troubleshooting that one..? One way to do a better sanity check or problem detection on these (or even on all) lists is bin/config_list -i /dev/null listname This will attempt to instantiate the list and if it's a 2.0.12 list convert the data in config.db and save as config.pck. Okay great, I'm giving that a try now in the background. One bit of advice. Once the lists are all converted, remove the config.db and config.db.last files from the lists/listname/ directories. If you don't do this, it is possible that at some future time, the config.pck and config.pck.last files could become corrupt and cause Mailman to fall back to the then ancient config.db. Good tip, I'll be sure to use it! One thing I've noticed is a problem with genaliases. Going off this URL: http://acd.ucar.edu/~fredrick/ linux/mailman/upgrading.html it suggests running genaliases, saving the output to a text file, and merging that with my current /etc/ aliases. However, when I run genaliases, it returns no output and no errors. Is there a place I should start troubleshooting that from? Thanks! Chris -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Digest not being sent
At least a couple (maybe all) of my lists are not sending out the digest automatically. I can see the digest.mbox file and it is up to date, but a couple of weeks old. Subscribers who have chosen digest mode alerted me that they weren't getting messages. I looked at one list and the threshold is set to 200 KB and daily if the threshold is not reached. I know there is a senddigests cron, but how does this actually work, and what could be the reason that no lists are sending the digest unless I manually choose that it be sent? -- Christopher Adams [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Weird problem data format error. Command output Mailbox does'nt exist
HI, I have an odd problem. I have over a hundred lists and all but one is working properly. The initial support call was a complaint that the mail server was bouncing back the emails sent to the list claiming that there was no such user (list-name). I thought it was odd, so I rmlist -a and recreated it using newlist. I tested the list, mail went to the user and everyone was happy. Oddly, the mailserver bounced that night (we aren't sure why) but the next day I got another call about the same list. I thought that it was a fluke, maybe some weird setting had been reverted when the server bounced, so again I removed the list (rmlist but without removing the archives) and recreated the list using newlist. I tested the list by sending an email and everyone (except the administrator who now had to repopulate the list was happy) It is day 3. I got phone call today. The same list is broken again. All the other lists work fine but this one seems to be unrecognized by the system: Aug 2 13:36:36 mail postfix/smtpd[5008]: NOQUEUE: reject: RCPT from sjc.mailserver.com[63.80.14.252]: 550 qvc- [EMAIL PROTECTED]: Recipient address rejected: User unknown in local recipient table; from=[EMAIL PROTECTED] to=[EMAIL PROTECTED] proto=ESMTP helo=[172.16.246.5] Aug 2 13:42:02 mail postfix/smtpd[5066]: NOQUEUE: reject: RCPT from sjc.mailserver.com[63.80.14.252]: 550 qvc- [EMAIL PROTECTED]: Recipient address rejected: User unknown in local recipient table; from=[EMAIL PROTECTED] to=[EMAIL PROTECTED] proto=ESMTP helo=[172.16.246.5] Aug 2 13:45:31 mail postfix/pipe[6401]: 9E219166485D: to=qvc- [EMAIL PROTECTED], relay=cyrus, delay=0, status=bounced (data format error. Command output: qvc-requests: Mailbox does not exist ) Aug 2 13:57:17 corp-admin2 postfix/pipe[7594]: 222591665614: to=qvc- [EMAIL PROTECTED], relay=cyrus, delay=0, status=bounced (data format error. Command output: qvc-requests: Mailbox does not exist ) Aug 2 14:05:45 mail postfix/pipe[7722]: 34A081666003: to=qvc- [EMAIL PROTECTED], relay=cyrus, delay=0, status=bounced (data format error. Command output: qvc-requests: Mailbox does not exist ) I have spent the better part of 6 hours looking for a reason. I've checked permissions, not just with checkperms but manually, step by step, directory by directory comparing the broken list to a list that is known to be working. /private/var/mailman/archives/private/qvc-requests/database other perms must be 000 (fixing) drwxrwsr-x3 root mailman 102 Jun 18 13:30 production drwxrwsr-x2 root mailman68 Jun 18 13:30 production.mbox drwxrwsr-x 10 root mailman 340 Aug 1 11:18 qvc-requests drwxrwsr-x3 root mailman 102 Jul 26 09:02 qvc-requests.mbox /var/mailman/lists root# ls -l qvc-requests total 56 -rw-rw 1 mailman mailman 3777 Aug 2 11:25 config.pck -rw-rw 1 mailman mailman 3778 Aug 2 11:24 config.pck.last -rw-rw 1 mailman mailman 11089 Aug 1 14:16 digest.mbox -rw-rw 1 mailman mailman131 Aug 1 10:24 pending.pck -rw-rw-r-- 1 www mailman 24 Aug 1 11:18 request.pck /var/mailman/archives/private/qvc-requests root# ls -l total 160 drwxrwsr-x 10 mailman mailman340 Aug 1 14:16 2007-August -rw-rw-r--1 mailman mailman 2476 Aug 1 14:16 2007-August.txt drwxrwsr-x 28 mailman mailman952 Jul 31 15:08 2007-July -rw-rw-r--1 mailman mailman 66954 Jul 31 15:08 2007-July.txt drwxrwsr-x7 root mailman238 Aug 1 11:59 attachments drwxrwx--- 12 mailman mailman408 Aug 1 14:16 database -rw-rw-r--1 root mailman 1465 Aug 1 14:16 index.html -rw-rw1 mailman mailman892 Aug 1 14:16 pipermail.pck I've checked the alias file in /var/mailman/data/aliases: (Everything looks ok) # STANZA START: qvc-requests # CREATED: Wed Aug 1 09:09:12 2007 qvc-requests: |/usr/share/mailman/mail/mailman post qvc- requests qvc-requests-admin: |/usr/share/mailman/mail/mailman admin qvc- requests qvc-requests-bounces: |/usr/share/mailman/mail/mailman bounces qvc-requests qvc-requests-confirm: |/usr/share/mailman/mail/mailman confirm qvc-requests qvc-requests-join:|/usr/share/mailman/mail/mailman join qvc- requests qvc-requests-leave: |/usr/share/mailman/mail/mailman leave qvc- requests qvc-requests-owner: |/usr/share/mailman/mail/mailman owner qvc- requests qvc-requests-request: |/usr/share/mailman/mail/mailman request qvc-requests qvc-requests-subscribe: |/usr/share/mailman/mail/mailman subscribe qvc-requests qvc-requests-unsubscribe: |/usr/share/mailman/mail/mailman unsubscribe qvc-requests # STANZA END: qvc-requests I've checked locks: - nothing regarding this list there. main.cf shows: alias_maps = hash:/etc/postfix/lmail/ company.aliases,hash:/var/mailman/data/aliases Where else can I check? Thank you --
Re: [Mailman-Users] mailman, attachment and digital sign
On 8/2/07, Marco De Rossi wrote: We have modifed mailman so now it not add the message footer anymore. Now we still have this problem only when we send digital signed e-mail *with attachment*. I can see two likely possibilities: 1. The digital signature is being done against the whole message, headers included. When the message passes through Mailman, some headers end up getting changed or added, and the signature is no longer valid. 2. Mailman is still stripping or changing some of the attachment MIME types or filenames, which causes the signature to be invalidated. Problem is, cryptographic signatures on messages are extremely fragile. If even the slightest thing is changed, the signature is likely to be broken. If you make the signature process more robust, then you increase the possibility that an attacker could slip something through that would still appear to be correct, but where they've actually secretly modified something. Try turning off all filtering, HTML conversion, etc... within Mailman. See if that fixes the signature problem. If so, then you have to decide which is more important -- the signature on some messages or the probability that some malware could get through the system and sent out to all recipients of the list, because you'd turned off the filtering. Unfortunately, this is a binary decision. There is no option to leave signed messages unfiltered and to apply the filtering rules only to unsigned messages. Even if there were such a method, the attackers could get through by simply forging fake signatures that look valid. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Digest not being sent
On 8/2/07, Christopher Adams wrote: I know there is a senddigests cron, but how does this actually work, and what could be the reason that no lists are sending the digest unless I manually choose that it be sent? Did you search the FAQ wizard on this matter? -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Digest not being sent
Actually, I have read the FAQ, but didn't seem to reap any useful information in this regard. I did find something in my search of the mailman-users list that talks about a corrupt digest.mbox file. Before I had a chance to check that out, the digest was sent. Odd. So, what controls the time that the daily digest is sent out if the threshold hasn't been reached? There is a 'senddigests' script in the /mailman/cron directory, but I am at a loss as to when it is fired off. I can generate digests based on threshold with no problem, and I know the daily delivery problem is happening with more than one list, so what else to look for? On 8/2/07, Brad Knowles [EMAIL PROTECTED] wrote: On 8/2/07, Christopher Adams wrote: I know there is a senddigests cron, but how does this actually work, and what could be the reason that no lists are sending the digest unless I manually choose that it be sent? Did you search the FAQ wizard on this matter? -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Christopher Adams [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Digest not being sent
On 8/2/07, Christopher Adams wrote: So, what controls the time that the daily digest is sent out if the threshold hasn't been reached? There is a 'senddigests' script in the /mailman/cron directory, but I am at a loss as to when it is fired off. You have to put that cron job in your crontab, usually for the root user. If not for root, then at least for the mailman user. If your digest exceeds the maximum size you set, then Mailman will go ahead and fire off a digest anyway, even if you haven't reached the deadline. If you've got problems with digests, the first thing to look for is the cron jobs. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Sanity-checking individual lists for health?
Chris Waltham wrote: One list that failed both make update and the below-mentioned config_list is named bowsun. Here is a copy of its contents: drwxrwsr-x2 mailman mailman 4096 Jul 24 11:03 ./ drwxrwsr-x 844 mailman mailman 65536 Jul 24 11:01 ../ -rwxr-xr--1 mailman mailman 1692 Jul 30 2003 admindbpreamble.html* -rwxr-xr--1 mailman mailman357 Jan 19 2001 archives.html* -rw-rw1 rootmailman 15076 Jul 23 15:37 config.db -rw-rw1 mailman mailman 15075 Jun 29 07:03 config.db.last -rw-rw1 rootmailman 12578 Jul 24 11:03 config.pck -rw-rw1 rootmailman 12578 Jul 24 10:51 config.pck.last -rwxr-xr--1 mailman mailman189 Jan 19 2001 handle_opts.html* -rwxr-xr--1 mailman mailman 1026 Jan 19 2001 headfoot.html* -rwxr-xr--1 mailman mailman 3136 Jan 19 2001 listinfo.html* -rwxr-xr--1 mailman mailman 4106 Jan 19 2001 options.html* -rw-rw-r--1 rootmailman 443875 Jul 24 08:41 request.pck -rwxr-xr--1 mailman mailman 1169 Jan 19 2001 roster.html* -rwxr-xr--1 mailman mailman198 Jan 19 2001 subscribe.html* I'm not sure how to start troubleshooting that one..? What did bin/config_list do when you ran it on this list? Did it issue any sort of error or traceback? If it gave you no information (I don't know why this would be), you could try running bin/dumpdb on the config.pck (and maybe the config.pck.last), and also on a good lists config.pck and compare the two. Obviously, the output will be different, but what you are looking for is whether or not the actual attribute names and the types (string, list of strings, list of tuples, numbers) of the attribute values correspond between the two lists. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Digest not being sent
Christopher Adams wrote: So, I have installed the mailman crontab and the digests that haven't been sent by reaching the threshold should now be sent out at 12 am every night. Actually, with the default Mailman crontab, they will be sent at noon. If you want them at midnight, you need to change the 12 in the senddigests crontab entry to 0. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Migrating from 1.0 to 2.1.9
[EMAIL PROTECTED] wrote: I moved the config.db file from a test list to the new server. I logged in to the web interface and all the members were there and the settings looked good. Moving the archives over and rebuilding them even worked. However, if I try to run dumpdb on the newly migrated list I get this error: NameError: global name 'DumperSwitchboard' is not defined Although there are other posts in the mailman-users archives where people saw this problem; there was no resolution. So it seems that even though the list appears to function properly and the web intercase works, something is not quite right with the config.db file and Mailman version 2.1.9. Once you move the config.db to the new server and visit the list via the web interface, the config.db is converted to a config.pck, and the config.db (and config.db.last) should be discarded at that point, and you should only be looking at the config.pck. As far as bin/dumpdb throwing the NameError is concerned, this is a known (to me at least) error in every version of dumpdb from 2.1.5 through 2.1.9 that prevents it from dumping Marshals. I can't explain why it hasen't been fixed before, but I will fix it for 2.1.10. The following patch should allow you to dump .db files. --- bin/dumpdb 2007-06-18 08:35:57.0 -0700 +++ bin/dumpdb 2007-08-02 17:45:42.18750 -0700 @@ -49,6 +49,7 @@ import sys import getopt import pprint +import marshal from cPickle import load from types import StringType @@ -121,9 +122,7 @@ # Handle dbs pp = pprint.PrettyPrinter(indent=4) if filetype == 1: -# BAW: this probably doesn't work if there are mixed types of .db -# files (i.e. some marshals, some bdbs). -d = DumperSwitchboard().read(filename) +d = marshal.load(open(filename)) if doprint: pp.pprint(d) return d It makes me a little nervous to run the migrated lists in production knowing that I can never run dumpdb and I don't know what else might be broken. I think I will go with my original plan of pre-creating each list on the new server, importing the list member's email addresses and manually setting up the list. With 150 lists, I think I can do it in a week. As I said, the configuration of the migrated list is the config.pck. The config.db should be removed after migration and creation of the config.pck. You can dump the config.pck with an unmodified bin/dumpdb and you can dump the config.db with bin/dumpdb patched as above. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Changing the received time on anoutgoingauthorized email message?
Paul Key [EMAIL PROTECTED] wrote: Thanks - can't see the forward option - any ideas? Mailman V 2.1.3 Use the forward this message feature in the admindb page to forward the message to yourself. On the admindb page, in the left box of the held messages item, underneath Action to take on all these held messages: there are a few checkboxes. The first two of these are Preserve messages for the site administrator and Forward messages (individually) to:. It is the latter of these that is referred to. However, you don't need to do that. If the list's admin_immed_notify is Yes, you already have a copy of the message in the admin notice. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Follow-up Weird problem data format error. Command output Mailbox does'nt exist
Hi, I've just been updated by more of the users/list admins. It seems that every-time the mail-server bounces/restarts, configurations are lost. Members fall off lists, lists stop running, or are no longer recognized by the mail server. Is there a central DB or something that is rolling back to an earlier version? I haven't made any changes to lists since they moved - but then again - this could be a result of the move since our mail server really doesn't get restarted often. Any ideas? Begin forwarded message: From: carconni [EMAIL PROTECTED] Date: August 2, 2007 3:14:12 PM PDT To: mailman-users@python.org Subject: [Mailman-Users] Weird problem data format error. Command output Mailbox does'nt exist HI, I have an odd problem. I have over a hundred lists and all but one is working properly. The initial support call was a complaint that the mail server was bouncing back the emails sent to the list claiming that there was no such user (list-name). I thought it was odd, so I rmlist -a and recreated it using newlist. I tested the list, mail went to the user and everyone was happy. Oddly, the mailserver bounced that night (we aren't sure why) but the next day I got another call about the same list. I thought that it was a fluke, maybe some weird setting had been reverted when the server bounced, so again I removed the list (rmlist but without removing the archives) and recreated the list using newlist. I tested the list by sending an email and everyone (except the administrator who now had to repopulate the list was happy) It is day 3. I got phone call today. The same list is broken again. All the other lists work fine but this one seems to be unrecognized by the system: Aug 2 13:36:36 mail postfix/smtpd[5008]: NOQUEUE: reject: RCPT from sjc.mailserver.com[63.80.14.252]: 550 qvc- [EMAIL PROTECTED]: Recipient address rejected: User unknown in local recipient table; from=[EMAIL PROTECTED] to=[EMAIL PROTECTED] proto=ESMTP helo= [172.16.246.5] Aug 2 13:42:02 mail postfix/smtpd[5066]: NOQUEUE: reject: RCPT from sjc.mailserver.com[63.80.14.252]: 550 qvc- [EMAIL PROTECTED]: Recipient address rejected: User unknown in local recipient table; from=[EMAIL PROTECTED] to=[EMAIL PROTECTED] proto=ESMTP helo= [172.16.246.5] Aug 2 13:45:31 mail postfix/pipe[6401]: 9E219166485D: to=qvc- [EMAIL PROTECTED], relay=cyrus, delay=0, status=bounced (data format error. Command output: qvc-requests: Mailbox does not exist ) Aug 2 13:57:17 corp-admin2 postfix/pipe[7594]: 222591665614: to=qvc- [EMAIL PROTECTED], relay=cyrus, delay=0, status=bounced (data format error. Command output: qvc-requests: Mailbox does not exist ) Aug 2 14:05:45 mail postfix/pipe[7722]: 34A081666003: to=qvc- [EMAIL PROTECTED], relay=cyrus, delay=0, status=bounced (data format error. Command output: qvc-requests: Mailbox does not exist ) I have spent the better part of 6 hours looking for a reason. I've checked permissions, not just with checkperms but manually, step by step, directory by directory comparing the broken list to a list that is known to be working. /private/var/mailman/archives/private/qvc-requests/database other perms must be 000 (fixing) drwxrwsr-x3 root mailman 102 Jun 18 13:30 production drwxrwsr-x2 root mailman68 Jun 18 13:30 production.mbox drwxrwsr-x 10 root mailman 340 Aug 1 11:18 qvc-requests drwxrwsr-x3 root mailman 102 Jul 26 09:02 qvc-requests.mbox /var/mailman/lists root# ls -l qvc-requests total 56 -rw-rw 1 mailman mailman 3777 Aug 2 11:25 config.pck -rw-rw 1 mailman mailman 3778 Aug 2 11:24 config.pck.last -rw-rw 1 mailman mailman 11089 Aug 1 14:16 digest.mbox -rw-rw 1 mailman mailman131 Aug 1 10:24 pending.pck -rw-rw-r-- 1 www mailman 24 Aug 1 11:18 request.pck /var/mailman/archives/private/qvc-requests root# ls -l total 160 drwxrwsr-x 10 mailman mailman340 Aug 1 14:16 2007-August -rw-rw-r--1 mailman mailman 2476 Aug 1 14:16 2007-August.txt drwxrwsr-x 28 mailman mailman952 Jul 31 15:08 2007-July -rw-rw-r--1 mailman mailman 66954 Jul 31 15:08 2007-July.txt drwxrwsr-x7 root mailman238 Aug 1 11:59 attachments drwxrwx--- 12 mailman mailman408 Aug 1 14:16 database -rw-rw-r--1 root mailman 1465 Aug 1 14:16 index.html -rw-rw1 mailman mailman892 Aug 1 14:16 pipermail.pck I've checked the alias file in /var/mailman/data/aliases: (Everything looks ok) # STANZA START: qvc-requests # CREATED: Wed Aug 1 09:09:12 2007 qvc-requests: |/usr/share/mailman/mail/mailman post qvc- requests qvc-requests-admin: |/usr/share/mailman/mail/mailman admin qvc- requests qvc-requests-bounces: |/usr/share/mailman/mail/mailman bounces qvc-requests qvc-requests-confirm: |/usr/share/mailman/mail/mailman confirm qvc-requests
Re: [Mailman-Users] Digest not being sent
Okay, I think I found it. I'm not sure how I missed it during install. I didn't find the answer in the FAQ, but rather in the Mailman install doc: http://www.gnu.org/software/mailman/mailman-install/node41.html So, I have installed the mailman crontab and the digests that haven't been sent by reaching the threshold should now be sent out at 12 am every night. On 8/2/07, Christopher Adams [EMAIL PROTECTED] wrote: Actually, I have read the FAQ, but didn't seem to reap any useful information in this regard. I did find something in my search of the mailman-users list that talks about a corrupt digest.mbox file. Before I had a chance to check that out, the digest was sent. Odd. So, what controls the time that the daily digest is sent out if the threshold hasn't been reached? There is a 'senddigests' script in the /mailman/cron directory, but I am at a loss as to when it is fired off. I can generate digests based on threshold with no problem, and I know the daily delivery problem is happening with more than one list, so what else to look for? On 8/2/07, Brad Knowles [EMAIL PROTECTED] wrote: On 8/2/07, Christopher Adams wrote: I know there is a senddigests cron, but how does this actually work, and what could be the reason that no lists are sending the digest unless I manually choose that it be sent? Did you search the FAQ wizard on this matter? -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Christopher Adams [EMAIL PROTECTED] -- Christopher Adams [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Follow-up Weird problem data format error. Commandoutput Mailbox does'nt exist
carconni wrote: I've just been updated by more of the users/list admins. It seems that every-time the mail-server bounces/restarts, configurations are lost. Members fall off lists, lists stop running, or are no longer recognized by the mail server. Is there a central DB or something that is rolling back to an earlier version? Could be, but it is pretty clear to me that the problem is with your MTA, not with mailman. Since your MTA is Postfix, and delivery is via aliases, this can't be a Mailman (other than aliases) issue because the mail is being bounced by Postfix because Recipient address rejected: User unknown in local recipient table which means that somehow the aliases for this list are being lost. When the problem occurs, are the aliases still in /var/mailman/data/aliases? What is the mod time on /var/mailman/data/aliases.db? Are all the list's (working and non-working) aliases in /var/mailman/data/aliases and nowhere else (eg /etc/postfix/lmail/company.aliases or /etc/aliases)? I have spent the better part of 6 hours looking for a reason. I've checked permissions, not just with checkperms but manually, step by step, directory by directory comparing the broken list to a list that is known to be working. Nothing in Mailman is causing this. It is postfix that 'forgets' how to deliver to [EMAIL PROTECTED] Apparently deleting and recreating the list fixes the problem because it runs Postfix's /usr/sbin/postalias command abd rebuilds /var/mailman/data/aliases.db from /var/mailman/data/aliases. Probably just running postalias would fix it too without the pain of recreating the list. stuff not relevant to the issue snipped I've checked the alias file in /var/mailman/data/aliases: (Everything looks ok) # STANZA START: qvc-requests # CREATED: Wed Aug 1 09:09:12 2007 qvc-requests: |/usr/share/mailman/mail/mailman post qvc- requests qvc-requests-admin: |/usr/share/mailman/mail/mailman admin qvc- requests qvc-requests-bounces: |/usr/share/mailman/mail/mailman bounces qvc-requests qvc-requests-confirm: |/usr/share/mailman/mail/mailman confirm qvc-requests qvc-requests-join:|/usr/share/mailman/mail/mailman join qvc- requests qvc-requests-leave: |/usr/share/mailman/mail/mailman leave qvc- requests qvc-requests-owner: |/usr/share/mailman/mail/mailman owner qvc- requests qvc-requests-request: |/usr/share/mailman/mail/mailman request qvc-requests qvc-requests-subscribe: |/usr/share/mailman/mail/mailman subscribe qvc-requests qvc-requests-unsubscribe: |/usr/share/mailman/mail/mailman unsubscribe qvc-requests # STANZA END: qvc-requests I've checked locks: - nothing regarding this list there. Mailman locks aren't relevant to this. main.cf shows: alias_maps = hash:/etc/postfix/lmail/ company.aliases,hash:/var/mailman/data/aliases Looks OK to me, but I'm not a postfix guy? Where else can I check? Something is happening when Postfix is restarted that is causing this, but I don't know what or why. I'm guessing the /var/mailman/data/aliases.db file gets modified somehow using data other than that in /var/mailman/data/aliases, but I have no idea how this can happen. But, I can tell you, look to Postfix, not Mailman. Other than /var/mailman/data/aliases*, there's nothing in Mailman that's relevant to this issue. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Is it possible to filter what is archived?
Mark Sapiro wrote: Make a custom handler (see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.067.htp) that checks mlist.umbrella_list, and if true add an X-No-Archive: header to the message. E.g. def process(mlist, msg, msgdata): if mlist.umbrella_list: msg['X-No-Archive'] = 'Yes' The handler has to be in the pipeline prior to 'ToArchive'. I should know better than to post code when I'm in a hurry, but ... The above is a bit too simple. Something like def process(mlist, msg, msgdata): if mlist.umbrella_list: del msg['x-no-archive'] msg['X-No-Archive'] = 'Yes' is probably better to avoid creating multiple X-No-Archive: headers. Also, if you insert the handler prior to 'ToArchive', the message (any message to an umbrella list) will not be archived at all. If you insert the handler after 'ToArchive' but prior to 'ToOutgoing', the message will be archived in the archive of the first umbrella list it hits, but won't be archived in any subsequent lists which is probably more like what you want. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] How to change [EMAIL PROTECTED] address inmailman
BugsBunny wrote: Hi,I installed mailman 2.1.9 on fedora core 5. My host name was originally set as mydomain.net. Everything seemed working fine. Then I changed my host name to mydomain.com. (from .net to .com).I changed this from /etc/sysconfigure/network.I also checked my mm_cfg.py and default.py to make sure no mydomain.net specified. But whenever I get mailing list email, the email header still says it comes from mydomain.net instead of mydoamin.com. This caused my email going into spam folder like yahoo.Can anyone help me on where I can change this? Do I have to re-install mailman ?Thanks-- James No, you don't have to reinstall Mailman. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp. Don't overlook the part about running fix_url on existing lists. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] How to change [EMAIL PROTECTED] address in mailman
Hi,I installed mailman 2.1.9 on fedora core 5. My host name was originally set as mydomain.net. Everything seemed working fine. Then I changed my host name to mydomain.com. (from .net to .com).I changed this from /etc/sysconfigure/network.I also checked my mm_cfg.py and default.py to make sure no mydomain.net specified. But whenever I get mailing list email, the email header still says it comes from mydomain.net instead of mydoamin.com. This caused my email going into spam folder like yahoo.Can anyone help me on where I can change this? Do I have to re-install mailman ?Thanks-- James _ 使用下一代的 MSN Messenger。 http://imagine-msn.com/messenger/launch80/default.aspx?locale=zh-cnsource=wlmailtagline-- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Follow-up Weird problem data format error. Commandoutput Mailbox does'nt exist
Hi Mark, Thank you for your advice and I will certainly look into what postfix is doing. In addition, I'll try your suggestion to run postalias to see if that corrects the problem. I've now had 3 more lists become undeliverable. They are all in the /var/mailman/data/alias file, so I'll keep digging. The other thing that troubles me is that I can't figure out why lists are loosing members. When the mailserver bounced tuesday, users added several days beforehand disappeared from the list. The users were re-added, only for the problem to reoccur after a server restart. I should point out this isn't occurring with the lists that became undeliverable, maybe it's a coincidence, and the 2 are unrelated. I'll update the list with what I find - and thank you again for taking the time help me. Carconni On Aug 2, 2007, at 6:40 PM, Mark Sapiro wrote: carconni wrote: I've just been updated by more of the users/list admins. It seems that every-time the mail-server bounces/restarts, configurations are lost. Members fall off lists, lists stop running, or are no longer recognized by the mail server. Is there a central DB or something that is rolling back to an earlier version? Could be, but it is pretty clear to me that the problem is with your MTA, not with mailman. Since your MTA is Postfix, and delivery is via aliases, this can't be a Mailman (other than aliases) issue because the mail is being bounced by Postfix because Recipient address rejected: User unknown in local recipient table which means that somehow the aliases for this list are being lost. When the problem occurs, are the aliases still in /var/mailman/data/aliases? What is the mod time on /var/mailman/data/aliases.db? Are all the list's (working and non-working) aliases in /var/mailman/data/aliases and nowhere else (eg /etc/postfix/lmail/company.aliases or /etc/aliases)? I have spent the better part of 6 hours looking for a reason. I've checked permissions, not just with checkperms but manually, step by step, directory by directory comparing the broken list to a list that is known to be working. Nothing in Mailman is causing this. It is postfix that 'forgets' how to deliver to [EMAIL PROTECTED] Apparently deleting and recreating the list fixes the problem because it runs Postfix's /usr/sbin/postalias command abd rebuilds /var/mailman/data/aliases.db from /var/mailman/data/aliases. Probably just running postalias would fix it too without the pain of recreating the list. stuff not relevant to the issue snipped I've checked the alias file in /var/mailman/data/aliases: (Everything looks ok) # STANZA START: qvc-requests # CREATED: Wed Aug 1 09:09:12 2007 qvc-requests: |/usr/share/mailman/mail/mailman post qvc- requests qvc-requests-admin: |/usr/share/mailman/mail/mailman admin qvc- requests qvc-requests-bounces: |/usr/share/mailman/mail/mailman bounces qvc-requests qvc-requests-confirm: |/usr/share/mailman/mail/mailman confirm qvc-requests qvc-requests-join:|/usr/share/mailman/mail/mailman join qvc- requests qvc-requests-leave: |/usr/share/mailman/mail/mailman leave qvc- requests qvc-requests-owner: |/usr/share/mailman/mail/mailman owner qvc- requests qvc-requests-request: |/usr/share/mailman/mail/mailman request qvc-requests qvc-requests-subscribe: |/usr/share/mailman/mail/mailman subscribe qvc-requests qvc-requests-unsubscribe: |/usr/share/mailman/mail/mailman unsubscribe qvc-requests # STANZA END: qvc-requests I've checked locks: - nothing regarding this list there. Mailman locks aren't relevant to this. main.cf shows: alias_maps = hash:/etc/postfix/lmail/ company.aliases,hash:/var/mailman/data/aliases Looks OK to me, but I'm not a postfix guy? Where else can I check? Something is happening when Postfix is restarted that is causing this, but I don't know what or why. I'm guessing the /var/mailman/data/aliases.db file gets modified somehow using data other than that in /var/mailman/data/aliases, but I have no idea how this can happen. But, I can tell you, look to Postfix, not Mailman. Other than /var/mailman/data/aliases*, there's nothing in Mailman that's relevant to this issue. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
