here anything in mailman which can explain this behavior? Does mailman
lookup
DNS/MX entrys before contacting the MTA. Or dos mailman has a internal state
of
already failed messages?
--
-------
Wim Bonis ,+'^'
On Mon, 2003-10-06 at 17:46, Jon Carnes wrote:
> On Mon, 2003-10-06 at 06:26, Wim Bonis wrote:
> > Hello List,
> >
> > I just upgrades my Server to mailman 2.1.3, and it basicly works, but some
> > messages trigger a 98% load of qrunner.
> >
> > The mes
with over 90% CPU" subject.
But in that thread the people blame the MTA reporting a 451. I straced and
tcpdumped the qrunner, and it does not try to contact the MTA.
What else can i try to get more useful debugging output?
--
-----
