On Thu, 2003-09-11 at 16:47, John Lange wrote:
> my recommendation would be that mailman should report a
> failed connection attempt to localhost as a serious problem and log it
> in syslog, or at the very minimum it's own logs. quietly burning 100%
> CPU should not be acceptable.
>
Quite right!
I think I have the problem solved. Acting on a hunch from what Jon Carns
said about the postfix configuration I completely stopped postfix and
restarted it.
Previously I had simply done a postfix reload.
Just for the benefit of anyone reading this thread in the future, I
believe the setting that
I don't think those errors mean too much (unless you upgraded and it
hasn't finished the upgrade...)
If your MTA is Postfix, be sure that you have followed all the advise in
the README.POSTFIX file. Specifically make sure that local bounces are
not set to a 4xx error code (which means retry and r
I'm new to Mailman and I'm having a major problem getting it to start.
I had it setup and working and then I needed to reboot the server for a
kernel upgrade.
Now when I start mailman it causes python to burn 100% CPU until mailman
is stopped.
logs show nothing out of the ordinary.
logs/qrunner
