Hi.
> Hello,
> although you don't give information about the system (OS etc),
> the best candidate, for the heavy load is the mailscanner - spamassasin
> combo. I suspect that you are noticing this when the message is being
> processed by these two ...
Sorry about that - it is fresh inst
Hi again.
> You fail to say what version of Mailman you are running but it looks
> like Mailman 2.1.x.
> MM 2.1.x runs a number of daemon processes, started by
> $prefix/bin/mailmanctl. Each of these daemons handles a different
> aspect of MM's operation, being responsible for handling mail tha
On Friday, July 18, 2003, at 11:17 AM, Nejc Skoberne wrote:
Hi.
mailman 25332 0.0 0.1 7420 276 ?SJul14 0:00
/usr/bin/python bin/mailmanctl start
mailman 25333 0.0 1.4 7916 3708 ?SJul14 0:13 qrunner
/usr/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
mailman
Hello,
although you don't give information about the system (OS etc),
the best candidate, for the heavy load is the mailscanner - spamassasin
combo. I suspect that you are noticing this when the message is being
processed by these two ...
I suspect you have the classic two queue configura
Hi.
mailman 25332 0.0 0.1 7420 276 ?SJul14 0:00 /usr/bin/python
bin/mailmanctl start
mailman 25333 0.0 1.4 7916 3708 ?SJul14 0:13 qrunner
/usr/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
mailman 25334 0.0 1.0 7516 2784 ?SJul14 0:01 qrunne
I've recently moved a 50,000 user list from some web-based newsletter
software over to Mailman. This list is purely a newsletter where the users
cannot post messages to the list. First of all, are there any optimizations
I can use for a newsletter-type list? Second, since I've moved to Mailman,
