Mike wrote:
>It may also be difficult to properly recover the digest.
>
>
>
Hi Mike - problem solved and it had nothing to do with python, Mailman
or any
of the mail clients. When I went to edit the digest.mbox file I noticed
it was 1.4 gigabytes
in size (!). And this from a list that was jus
>Also, can you do either bin/dumpdb or bin/show_qfiles on the shunt
>queue entry and perhaps see what the problem with the message is?
>
>
>
OK Mike - here is the dumbdb (the names were changed to protect the
innocent). I don't
see anything unusual, and I should point out that this list has bee
Hello all,
Of our 770+ lists, a couple have some shunting problems (the unshunt
command fails
to release queued up messages in the shunt directory). We are still
running v2.1.5 with
plans to upgrade in May, but I was hoping to get a fix for this before then.
The error message we get is:
Hi all,
I was wondering if there is a way to silently subscribe people to a
list via the -request command processor (ie sending email commands to
listname-request)?
If I send the command:
subscribe password nodigest [EMAIL PROTECTED]
it works fine, but [EMAIL PROTECTED] is then se
I showed an example of one way to do this from the command line a
couple of months back:
http://mail.python.org/pipermail/mailman-users/2004-June/037287.html
(Although that particular message shows how to moderate from
the command line, so you'll want to change the mm_cfg.Yes to
mm_cfg.No to make
Hi all,
I am running Mailman v2.1.2 on a Linux Enterprise box.
The membership of a number of our lists is dynamic and needs
to be changed daily. I run a cronjob each morning that
unsubscribes everyone and then re-subscribes the new members.
Works fine with one slight hassle: I can't figure o
