[Mailman-Users] Permission Denied errors

[Beyer, Clay]

> -----Original Message-----
> From: Mark Sapiro [mailto:mark at msapiro.net]
> Sent: Thursday, March 04, 2010 4:57 PM
> To: Beyer, Clay; mailman-users at python.org
> Subject: RE: [Mailman-Users] Permission Denied errors
> 
> Beyer, Claywrote:
> 
> >-rw------- 1 mailman crontab  /var/spool/cron/crontabs/mailman
> >-rw-r--r-- 1 root root /etc/cron.d/maiman
> >
> >Those are the two places you mentioned.
> 
> 
> So I'm just guessing, but I suspect that the crontab in
> /etc/cron.d/mailman (?) is correct and is running successfully and the
> one in /var/spool/cron/crontabs/mailman is causing the problems
> because it runs as user 'mailman' and not as user 'list'.
> 
> I think your problem will be solved if you just
> 
>  rm /var/spool/cron/crontabs/mailman
> 
> but I can't say for sure without seeing the contents of both files and
> also knowing what groups the 'mailman' user is in.

The mailman user belongs only to the group daemon

The contents of both files...

/etc/cron.d/mailman
# At 8AM every day, mail reminders to admins as to pending requests.
# They are less likely to ignore these reminders if they're mailed
# early in the morning, but of course, this is local time... ;)
0 8 * * * list [ -x /usr/lib/mailman/cron/checkdbs ] &&
/usr/lib/mailman/cron/checkdbs
#
# At 9AM, send notifications to disabled members that are due to be
# reminded to re-enable their accounts.
0 9 * * * list [ -x /usr/lib/mailman/cron/disabled ] &&
/usr/lib/mailman/cron/disabled
#
# Noon, mail digests for lists that do periodic as well as threshold
delivery.
0 12 * * * list [ -x /usr/lib/mailman/cron/senddigests ] &&
/usr/lib/mailman/cron/senddigests
#
# 5 AM on the first of each month, mail out password reminders.
0 5 1 * * list [ -x /usr/lib/mailman/cron/mailpasswds ] &&
/usr/lib/mailman/cron/mailpasswds
#
# Every 5 mins, try to gate news to mail.  You can comment this one out
# if you don't want to allow gating, or don't have any going on right
now,
# or want to exclusively use a callback strategy instead of polling.
# */5 * * * * list [ -x /usr/lib/mailman/cron/gate_news ] &&
/usr/lib/mailman/cron/gate_news
#
# At 3:27am every night, regenerate the gzip'd archive file.  Only
# turn this on if the internal archiver is used and
# GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py
27 3 * * * list [ -x /usr/lib/mailman/cron/nightly_gzip ] &&
/usr/lib/mailman/cron/nightly_gzip

/var/spool/cron/crontabs/mailman
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (crontab.in installed on Tue Feb 23 14:58:29 2010)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp
$)
# At 8AM every day, mail reminders to admins as to pending requests.
# They are less likely to ignore these reminders if they're mailed
# early in the morning, but of course, this is local time... ;)
0 8 * * * /usr/bin/python -S /var/lib/mailman/cron/checkdbs
#
# At 9AM, send notifications to disabled members that are due to be
# reminded to re-enable their accounts.
0 9 * * * /usr/bin/python -S /var/lib/mailman/cron/disabled
#
# Noon, mail digests for lists that do periodic as well as threshhold
delivery.
0 12 * * * /usr/bin/python -S /var/lib/mailman/cron/senddigests
#
# 5 AM on the first of each month, mail out password reminders.
0 5 1 * * /usr/bin/python -S /var/lib/mailman/cron/mailpasswds
#
# Every 5 mins, try to gate news to mail.  You can comment this one out
# if you don't want to allow gating, or don't have any going on right
now,
# or want to exclusively use a callback strategy instead of polling.
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/bin/python -S
/var/lib/mailman/cron/gate_news
#
# At 3:27am every night, regenerate the gzip'd archive file.  Only
# turn this on if the internal archiver is used and
# GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py
27 3 * * * /usr/bin/python -S /var/lib/mailman/cron/nightly_gzip
#
# At 4:30AM daily, cull old entries from the 'bad' and 'shunt' queues.
30 4 * * * /usr/bin/python -S /var/lib/mailman/cron/cull_bad_shunt

What I did was as you suggested, I did a rm
/var/spool/cron/crontabs/mailman

I also went into the /etc/cron.d/mailman file and uncommented the
gate_news line that was commented out. After about an hour, I have not
received an mail with error messages. Problem solved, unless of course,
something I did isn't correct.

Thanks for all your help Mark, really appreciated.

ClayB

> 
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan