At 10:22 AM +1030 11/21/03, Dat Bui wrote:
sorry, i should've said that this happens to me too.
doesn't hurt to try editing your Defaults.py or mm_cfg.py and try upping
the outgoing qrunners :)
stop then start the mailmanctl
So the saga ends- the system is Gentoo-based, and the build script
appare
sorry, i should've said that this happens to me too.
doesn't hurt to try editing your Defaults.py or mm_cfg.py and try upping
the outgoing qrunners :)
stop then start the mailmanctl
hope it helps.
Dat
On Fri, 2003-11-21 at 09:39, Brett Dikeman wrote:
> At 9:30 AM +1030 11/21/03, Dat Bui wrote:
At 9:30 AM +1030 11/21/03, Dat Bui wrote:
Hi,
the messages are most likely being queued up in the ~mailman/qfiles/out
directory.
try running like 5 outgoing qrunners and see if that helps.
I just shut down the qrunners(since I didn't understand the 'slice'
business) and ran outgoing by hand, with
At 9:30 AM +1030 11/21/03, Dat Bui wrote:
Hi,
the messages are most likely being queued up in the ~mailman/qfiles/out
directory.
try running like 5 outgoing qrunners and see if that helps.
Huh? -Nothing- is going out. Zip. Zilch. It's a P4 3ghz with 1GB
of ram, a massive pipe...and load is 0 t
Hi,
the messages are most likely being queued up in the ~mailman/qfiles/out
directory.
try running like 5 outgoing qrunners and see if that helps.
Dat
On Fri, 2003-11-21 at 09:19, Brett Dikeman wrote:
> After less than 24 hours operation, ALL our list mail just goes into
> a black hole; postfix
After less than 24 hours operation, ALL our list mail just goes into
a black hole; postfix hands it off to mailman successfully and then
it just disappears, save some messages show up in the archives.
It was working great up until about 2pm and then just everything
stopped- barely 12 hours wort
