On Sun, 20 Feb 2005 09:00:23 -0800, Mark Sapiro <[EMAIL PROTECTED]> wrote:
>
> Two things you could look at are Mailman's 'error' log and
> bin/check-perms
I did check the error log and sure enough it's a permissions problem:
Uncaught runner exception: [Errno 13] Permission denied:
'/var/lib/mai
I posted a previous thread on this topic :
http://www.mail-archive.com/mailman-users@python.org/msg29658.html
I thought that the bin/arch -wipe {list} fixed my problem. But no
messages posted to the list are actually added to the archives.
I checked my mailman qrunner log and I can see the archi
The arch --wipe fixed the problem.
thank you.
On Wed, 19 Jan 2005 07:48:15 -0800, Mark Sapiro <[EMAIL PROTECTED]> wrote:
> Jeffery Cann wrote:
> >
> >Here's the problem: messages posted to the new lists (archive option
> >is on -- I confirmed this tonight)
t.
Jeff
On Wed, 19 Jan 2005 13:09:39 +0100, Brad Knowles
<[EMAIL PROTECTED]> wrote:
> At 11:39 PM -0700 2005-01-18, Jeffery Cann wrote:
>
> > Here's the problem: messages posted to the new lists (archive option
> > is on -- I confirmed this tonight) do not get
We moved our mailman lists from one server to another. We also went
from mailman 2.0.6 (?) to 2.1.5. So, I didn't fiddle with moving the
lists, but simply recreated them and imported users. I also copied
the archive mbox files to their respective new locations and ran the
'arch' command to gener
I have seen several threads related to the genalias command. The idea
is that with postfix, when you run genalias (and you have added the
mailman alias files to your postfix main.cf), it will automatically
update your mailman alias file.
The problem for me on Fedora Core 3 is that when I set my
M
ran the 'senddigest' script by hand and viola -
digests were sent.
Maybe a FAQ addition?
HTH -
--- Jeffery Cann <[EMAIL PROTECTED]> wrote:
> I posted an earlier message regarding a senddigest
> memory problem.
>
>
-http://mail.python.org/pipermail/mailman-users/2004-J
I posted an earlier message regarding a senddigest
memory problem.
-http://mail.python.org/pipermail/mailman-users/2004-January/033772.html
This problem continues to happen and I think the only
way I can work around it is to clear the digest queue.
Anyone know how to clear a 2.0.13 digest queue?
Greetings.
Our server which hosts our 2.0.13 mailman lists moved
and the HOSTNAME was changed, but /etc/hosts was not
updated. So, it's been about 3 weeks that the
'senddigest' cron job has failed.
After fixing the host problem, I get a Memory Error
when I run senddigest:
Jan 05 16:10:33 2004 (
