On 6/23/08, Fletcher Cocquyt wrote:
(and yes the spamassassin checks are the source of the 4-10 second delay -
now those happen in parallel x16 - so no spikes in the backlog...)
Search the FAQ for "performance". Do all such spam/virus/DNS/etc...
checking up front, and run a second copy of
Mike, many thanks for your (as always) very helpful response - I added the 1
liner to mm_cfg.py to increase the threads to 16.
Now I am observing (via memory trend graphs) an acceleration of what looks
like a memory leak - maybe from python - currently at 2.4
I am compiling the latest 2.5.2 to see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Resending with the correct subject (2.1.11rc2, not 2.1.11rc1). Sorry for
any confusion.
Mark Sapiro wrote:
| I am happy to announce the release of the second release candidate for
| Mailman 2.1.11.
|
| Mailman 2.1.11 is a cleanup of a few problems fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am happy to announce the release of the second release candidate for
Mailman 2.1.11.
Mailman 2.1.11 is a cleanup of a few problems found since the release of
Mailman 2.1.10. It fixes the issue of shunted email subscribe requests
and a few minor iss
Abdul Javid wrote:
>
>Reason is "Post by moderated member"
>
>Individual bit for all members is cleared off ( not to be moderated )
Actually, even though I suggested it, "Post by moderated member" is not
a reason. Possible reasons are "Post to moderated list" and "Posting
to a moderated newsgroup
Thanks
Reason is "Post by moderated member"
Individual bit for all members is cleared off ( not to be moderated )
am puzzled with this.
other lists are working fine.
thanks
--- On Sun, 6/22/08, Mark Sapiro <[EMAIL PROTECTED]> wrote:
From: Mark Sapiro <[EMAIL PROTECTED]>
Subject: Re: [Ma
