[Mailman-Users] Cron errors
I'm getting a number of errors from cron scripts similar to this:- File /Users/mailman/cron/nightly_gzip, line 154, in ? main() File /Users/mailman/cron/nightly_gzip, line 110, in main mlist = MailList.MailList(name, lock=0) File /Users/mailman/Mailman/MailList.py, line 130, in __init__ self.Load() File /Users/mailman/Mailman/MailList.py, line 629, in Load dict, e = self.__load(file) File /Users/mailman/Mailman/MailList.py, line 595, in __load fp = open(dbfile) IOError: [Errno 13] Permission denied: '/Users/mailman/lists/e4um/config.pck' ls on /Users/mailman/lists/e4um gives -rw-rw 1 www mailman 46931 Feb 13 01:45 config.pck -rw-rw 1 mailman mailman 46895 Feb 13 01:37 config.pck.last drwxrwsr-x 4 mailman mailman264 Feb 5 12:44 en -rwxrwxr-x 1 mailman mailman 46 Feb 12 10:02 pending.pck -rwxrwxr-x 1 mailman mailman 24 Feb 12 10:02 request.pck Should config.pck be owned by mailman? or is there something else wrong? -- Bill Bedford -- 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] listname-leave - wrong response
On Feb 11, 2007, at 6:12 PM, Mark Sapiro wrote: Actually, I meant unsubscribe_policy, but that isn't it anyway.. There is an issue with subscribe_policy, but it doesn't impact your present issue. It seems the policy is likely set to None, but the mm_cfg option ALLOW_OPEN_SUBSCRIBE is set to No so the option doesn't appear on the page. Unless you really want open subscription without confirmation, I suggest setting the option you do want. That setting is intentional - this is a list with special needs (lots of cell phone subscribers who have much more trouble unsubbing than normal users). Is there anything in Mailman's 'vette' or 'subscribe' logs? Yes in vette: Feb 11 13:09:47 2007 (30321) replied and discard appears immediately when the request is received. The admin Autoresponder page has autorespond_requests set to Yes, w/discard so the response in autoresponse_request_text is sent and the request is discarded. Bingo - that was it! Many thanks Mark. Much appreciated. Scot -- Birdhouse Hosting Custom web and mail hosting services http://hosting.birdhouse.org -- 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] Cron errors
Bill Bedford wrote: I'm getting a number of errors from cron scripts similar to this:- File /Users/mailman/cron/nightly_gzip, line 154, in ? main() File /Users/mailman/cron/nightly_gzip, line 110, in main mlist = MailList.MailList(name, lock=0) File /Users/mailman/Mailman/MailList.py, line 130, in __init__ self.Load() File /Users/mailman/Mailman/MailList.py, line 629, in Load dict, e = self.__load(file) File /Users/mailman/Mailman/MailList.py, line 595, in __load fp = open(dbfile) IOError: [Errno 13] Permission denied: '/Users/mailman/lists/e4um/config.pck' ls on /Users/mailman/lists/e4um gives -rw-rw 1 www mailman 46931 Feb 13 01:45 config.pck -rw-rw 1 mailman mailman 46895 Feb 13 01:37 config.pck.last drwxrwsr-x 4 mailman mailman264 Feb 5 12:44 en -rwxrwxr-x 1 mailman mailman 46 Feb 12 10:02 pending.pck -rwxrwxr-x 1 mailman mailman 24 Feb 12 10:02 request.pck Should config.pck be owned by mailman? or is there something else wrong? The owner of config.pck will change depending on whether it was last updated via the web interface or via a qrunner. That is not the problem as it should always be group 'mailman' and all processes including the crons should run as group mailman. That is the question? Is the user running this cron in the mailman group. If so, is SELinux or some other security policy managment possibly involved? -- 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] Change hundreds of digest subscribers to non-digest
Thanks for any help on this. We have a mailman list set-up as a newsletter type list. We'd like to send basic html formatted email. This seems to work seamlessly for regular subscribers - they receive the html email that was sent. However, digest subscribers get a message about the html being scrubbed and are provided with a link to view the message - not good at all. So I'd like to resolve this problem by either 1 - Disabling the digest option (easy) and then changing all the digest subscribers to regular subscribers (this appears to be difficult - doing it by hand would be impossible - big list) How does one do this? 2 - Somehow prevent the digests from scrubbing html Any help would be great! Thanks. Jeff -- 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] Change hundreds of digest subscribers to non-digest
At 8:58 AM -0800 2/13/07, Jeff Pflueger wrote: So I'd like to resolve this problem by either 1 - Disabling the digest option (easy) and then changing all the digest subscribers to regular subscribers (this appears to be difficult - doing it by hand would be impossible - big list) How does one do this? Use withlist. There are plenty of examples in the FAQ Wizard and the archives. 2 - Somehow prevent the digests from scrubbing html That's not really feasible. The problem is that the process of creating the digest does all sorts of things to the message which is not compatible with HTML. So, while you technically could change the source code in your version of Mailman to remove the Scrubber component from the digest process, the result simply wouldn't work. Moreover, Mailman usually does a *lot* of things to messages as they are passing through, and even if you go out of your way to avoid most of them, you're still gambling that the input HTML will be formatted in such a way that the minimal modifcations won't hopelessly screw it up beyond recognition. That's a pretty big bet. -- Brad Knowles [EMAIL PROTECTED], Consultant Author Co-author of SAGE Booklet #15 Internet Postmaster: Duties and Responsibilities Founding Member and Platinum Individual Sponsor of LOPSA: http://www.lopsa.org Papers: http://tinyurl.com/tj6q4 LinkedIn Profile: http://tinyurl.com/y8kpxu -- 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] Group mismatch error
I am having a problem with Mailman. I have two test machines. On one (Sun Solaris 10) I installed Mailman 2.1.8 and then upgraded to 2.1.9. On the other (Ubuntu dapper), I installed the Mailman 2.1.5 package. Both installations worked after some simple fixups. As the Ubuntu Mailman package is 2.1.5 (i.e., some older version with Ubuntu/Debian changes that have not been sent back to the developers), I decided to build a Ubuntu/Debian package using the Mailman 2.1.9 source. After a few problems I built a package. I installed the package on Ubuntu, replacing the 2.1.5. When I sent mail to one of my test lists, I got this message: Diagnostic-Code: X-Postfix; Command died with status 2: /var/lib/mailman/mail/mailman post vm6bsftest3. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group daemon, but the system's mail server executed the mail script as group nogroup. Try tweaking the mail server to run the script as group daemon, or re-run configure, providing the command line option `--with-mail-gid=nogroup'. I then ran bin/check_perms -f, and this is the output: vm6%% sudo /usr/lib/mailman/bin/check_perms -f directory permissions must be 02775: /var/lib/mailman/icons (fixing) directory permissions must be 02775: /var/lib/mailman/cgi-bin (fixing) directory permissions must be 02775: /var/lib/mailman/Mailman (fixing) directory permissions must be 02775: /var/lib/mailman/bin (fixing) directory permissions must be 02775: /var/lib/mailman/cron (fixing) directory permissions must be 02775: /var/lib/mailman/mail (fixing) directory permissions must be 02775: /var/lib/mailman/scripts (fixing) directory permissions must be 02775: /var/lib/mailman/templates (fixing) directory permissions must be 02775: /var/lib/mailman/messages/zh_CN (fixing) directory permissions must be 02775: /var/lib/mailman/messages/ar (fixing) directory permissions must be 02775: /var/lib/mailman/messages/ia (fixing) directory permissions must be 02775: /var/lib/mailman/messages/vi (fixing) directory permissions must be 02775: /var/lib/mailman/messages/zh_TW (fixing) directory permissions must be 02775: /var/lib/mailman/messages/zh_CN/LC_MESSAGES (fixing) directory permissions must be 02775: /var/lib/mailman/messages/ar/LC_MESSAGES (fixing) directory permissions must be 02775: /var/lib/mailman/messages/ia/LC_MESSAGES (fixing) directory permissions must be 02775: /var/lib/mailman/messages/vi/LC_MESSAGES (fixing) directory permissions must be 02775: /var/lib/mailman/messages/zh_TW/LC_MESSAGES (fixing) /var/lib/mailman/data/aliases.db owned by root (must be owned by list (fixing) Problems found: 19 Re-run as list (or root) with -f flag to fix vm6%% sudo /usr/lib/mailman/bin/check_perms -f No problems found vm6%% I sent another test message to the same list, and I got this error messsage: Diagnostic-Code: X-Postfix; Command died with status 2: /var/lib/mailman/mail/mailman post vm6bsftest3. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group daemon, but the system's mail server executed the mail script as group list. Try tweaking the mail server to run the script as group daemon, or re-run configure, providing the command line option `--with-mail-gid=list'. The only differences between the first error and the second are Mailman expected the mail wrapper script to be executed as group daemon, but the system's mail server executed the mail script as group nogroup. (nogroup == list) ... or re-run configure, providing the command line option `--with-mail-gid=nogroup'. (nogroup == list) When I built the Ubuntu 2.1.9 package, the configure had --with-mail-gid=daemon and I assume that the same was true of the Ubuntu 2.1.5 package I had initially installed. My questions are these: 1) Where is this group test being made? 2) What in the check_perms run caused the change in the message from nogroup to list? 3) My MTA is Postfix. The /usr/lib/mailman/mail/mailman executable has ownership root:list in both the Ubuntu 2.1.9 and 2.1.5 installations. Is there some file whose ownership has to change to correct this mismatch reported in the error message? Thanks. -- 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:
Re: [Mailman-Users] Change hundreds of digest subscribers tonon-digest
Brad Knowles wrote: At 8:58 AM -0800 2/13/07, Jeff Pflueger wrote: 2 - Somehow prevent the digests from scrubbing html That's not really feasible. The problem is that the process of creating the digest does all sorts of things to the message which is not compatible with HTML. So, while you technically could change the source code in your version of Mailman to remove the Scrubber component from the digest process, the result simply wouldn't work. The above is correct as far as 'plain' format digests are concerned, but 'MIME' format digests aren't scrubbed because each individual messages MIME structure is maintained in the MIME format digest. So you could set mime_is_default_digest to MIME, and then use withlist as in Brad's answer to 1 to set all current subscribers to MIME. The problem with this is that different MUAs render the MIME digest differently. Users with non-MIME aware MUA's will not like it at all. Some other user's MUAs will show each message as an attachment which some find annoying. OTOH, you could just suggest that those users who don't like the scrubbed 'plain' digest try the MIME digest instead and choose for themselves which is better. -- 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] Group mismatch error
Barry Finkel wrote:
I decided to build a Ubuntu/Debian package using the Mailman 2.1.9
source. After a few problems I built a package.
I installed the package on Ubuntu, replacing the 2.1.5. When I sent
mail to one of my test lists, I got this message:
Diagnostic-Code: X-Postfix; Command died with status 2:
/var/lib/mailman/mail/mailman post vm6bsftest3. Command output:
Group mismatch error. Mailman expected the mail wrapper script to
be executed as group daemon, but the system's mail server executed
the mail script as group nogroup. Try tweaking the mail server
to run the script as group daemon, or re-run configure, providing
the command line option `--with-mail-gid=nogroup'.
I then ran bin/check_perms -f, and this is the output:
This is not a permissions issue. check_perms won't fix it.
I sent another test message to the same list, and I got this error
messsage:
Diagnostic-Code: X-Postfix; Command died with status 2:
/var/lib/mailman/mail/mailman post vm6bsftest3. Command output:
Group mismatch error. Mailman expected the mail wrapper script to
be executed as group daemon, but the system's mail server executed
the mail script as group list. Try tweaking the mail server to
run the script as group daemon, or re-run configure, providing
the command line option `--with-mail-gid=list'.
The only differences between the first error and the second are
Mailman expected the mail wrapper script to be executed as group
daemon, but the system's mail server executed the mail script as
group nogroup. (nogroup == list)
... or re-run configure, providing the command line option
`--with-mail-gid=nogroup'. (nogroup == list)
When I built the Ubuntu 2.1.9 package, the configure had
--with-mail-gid=daemon
and I assume that the same was true of the Ubuntu 2.1.5 package I had
initially installed.
See below for remark on packager magic.
My questions are these:
1) Where is this group test being made?
In the wrapper /usr/lib/mailman/mail/mailman.
2) What in the check_perms run caused the change in the message from
nogroup to list?
It changed the group of the Postfix aliases file that contains the
aliases for Mailman.
3) My MTA is Postfix. The
/usr/lib/mailman/mail/mailman
executable has ownership
root:list
Correct. It is also SETGID. See
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.016.htp.
With Postfix, the /usr/lib/mailman/data/aliases* files need to be in
mailman's group ('list' in your case) so that Mailman's Postfix
integration can update them. This causes Postfix to execute the pipe
to the wrapper as group 'list', thus the wrapper must expect to be
executed as group 'list', thus you must configure with
--with-mail-gid=list.
in both the Ubuntu 2.1.9 and 2.1.5 installations.
Is there some file whose ownership has to change to correct this
mismatch reported in the error message?
Postfix AFAIK is the only common MTA that uses ownership of the aliases
to determine user and group under which they run. This is the source
of the group in 'system's mail server executed the mail script as
group list'. In a source installation, the 'expected' group is
compiled into the wrapper as a result of configure's --with-mail-gid
option.
In a 'package' installation, the expected group is determined by what
ever magic the packager has resorted to to avoid having to recompile
the wrapper.
--
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] Best version of Python to use with Mailman
The esteemed Brad Knowles has said: Use the latest version of 2.4.x. As you've demonstrated, the 2.5 stuff is not yet fully baked, and Mailman 2.1.8 and earlier are not compatible with it. $DEITY-only-knows what else they're going to break in the process of trying to fix 2.5. I'll update the FAQ Wizard to reflect this. Thanks for the feedback. I think that for Mailman purposes, the good news is that the partial build of Python 2.5 using Sun's C compiler has been online production for several weeks and hasn't crashed yet. However, after assessing the Python build situation, I think that a back-down to 2.4.4 would be wise. I did post details of what I've done with the Python 2.4.4 and 2.5 build trees to the python-help mail list. What I got was a suggestion to take it to the python-dev list, which I've done. At this point, either I'm missing something pretty basic and reinventing the wheel, or I've smoked out some long-standing issues with Python build-install, not all of which are specific to Solaris. Hank -- 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 archive -small problem
I have mailman 2.19 installed with postfix and apache2. Almost everything is perfect except for the archives. I have 3 test list, only one with a couple messages. If you click on the link to go look at the archives for a list, instead of getting the archive list, you get a files listing (ie no index file for apache) of the public folder instead of the public/(list name). If you type in the list name in the url it takes you to the archives and you can browse them. This happens to any of the lists. Any suggestions? I think it might be in relation to the default-server.conf but I believe that the alias for pipermail is correct. I have the symbolic links for Apache otherwise I wouldn't be able to browse the archive folder. Something else? Maybe the info is wrong for the default-server.conf or maybe it's in the mm_conf.py Any help would be great Thanks, j ***CONFIDENTIALITY NOTICE*** This electronic message is intended only for the use of the addressee and may contain information that is privileged and confidential. Any dissemination, distribution or copying of this communication by unauthorized individuals is strictly prohibited. If you have received this communication in error, please notify the sender immediately by reply e-mail and delete the original and all copies from your system. -- 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 archive -small problem
Joe Comeau wrote: Almost everything is perfect except for the archives. I have 3 test list, only one with a couple messages. If you click on the link to go look at the archives for a list, instead of getting the archive list, you get a files listing (ie no index file for apache) of the public folder instead of the public/(list name). If you type in the list name in the url it takes you to the archives and you can browse them. I think you have an incorrect setting in mm_cfg.py for PUBLIC_ARCHIVE_URL. The default setting for this (in Defaults.py is PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/pipermail/%(listname)s' Perhaps you changed this for some reason and left off the /%(listname)s part. -- 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
