FreeBSD 4.7-Rel
Python 2.2.1
Sendmail 8.12.6
I'm still getting this daily on a number of
cron driven jobs.
Running the ~mailman/bin/list_lists script by hand as
user mailman also returns the same error.
Is there a way to repair the pickle file?
> cPickle.UnpicklingError: member is not safe for
I'm a newbie, so please don't flame me.
Two queries:
1. What should my crontab look like? What jobs should it be running and
how often?
2. My lists are (nominally) working, but when I send a message out, it
gets stopped to wait for moderator approval. But, when I go into the
administrative inter
Jordan Dahlke <[EMAIL PROTECTED]> wrote:
> I hope I'm not troubling anyone, and that this isn't answered
> anywhere. And I apologize if you don't feel this to be a mailman
> issue. Since mailman has a cron script run every minute, and cron, on
> Debian anyways, uses pam, and pam uses the pam_unix m
> "DP" == Dan Phillips <[EMAIL PROTECTED]> writes:
DP> Tried that and it reported no problems. The problem definitely
DP> seems to be in digest.mbox, although I can't see anything
DP> wrong.
If it isn't too late, can you submit a bug report with the mbox file
attached? If you do
Dan,
Incidentally, as I mentioned in the first message, I cleaned up the
headers within digests by commenting out some lines in
/handlers/ToDigest.py, excluding everything but date, to, from and
subject. Is that likely to gum up the works somewhere along the line? I
suppose that breaks rfc115
Thanks. I've done that once before, and as you said, the problem was
obvious. My difficulty this time is that every message in the box went
out just fine as individual emails. There were a couple that were
content-transfer-encoding: quoted-printable, which on my old system
caused multiple probl
I've had to go into Mbox before and delete a few messages that were
gumming up the works. What I normally do is simply look at the last
message to be processed and then delete the next message from the Mbox.
At that point it normally becomes obvious what the problem with the
offending mail message
Tried that and it reported no problems. The problem definitely seems to
be in digest.mbox, although I can't see anything wrong. I renamed it
and sent a test message to create a new one, the ran cron/senddigests
-l, and it went out fine. when I moved the original mbox back it
generated the same
Hi folks,
Thanks for your help. It turns out that I needed to make user mailman a
member of group list, and I needed to give the list group write
permissions on the mailman locks directory. Once I did that, all was
fixed.
Then I had a problem accessing the list archives, but that was easy: I
nee
> On 3/1/01 12:11 PM, "Robert Brandtjen" <[EMAIL PROTECTED]> wrote:
>
> Ok, let me clarify a little more (after looking through the crontab), is it
> necessary for qrunner to try resending every minute or can this be changed
> to once every 30 minutes?
qrunner doesn't "try to resend"; it's the
On 3/1/01 12:11 PM, "Robert Brandtjen" <[EMAIL PROTECTED]> wrote:
Ok, let me clarify a little more (after looking through the crontab), is it
necessary for qrunner to try resending every minute or can this be changed
to once every 30 minutes?
Also, what is gated_news ? I found nothing in FAQ on
Hi all,
The error has been solved, of course it was the admin's (my) fault and not good ol'
Mailman's.
It's too ridiculous to be described, so please just forgive me for bothering you!
Regs
Gergely
--
Mailman-Users maillist - [EMAIL PROTE
12 matches
Mail list logo
