[Mailman-Users] Mailman is being a processor sponge.... very slow delivery...

[Ecklund, Morgan]

I may have found it...
Man I should have known.
And Of course I do not know how to fix it.

Looks like we are receiving messages every 2 minutes or so from people not on the and mailman is busy filtering those out (totally my theory).

Sep 01 11:51:17 2014 (26561) -request/hold autoresponse discarded for: mailer-d
emon@"our symantec Brightmail Gateway"
Sep 01 11:51:17 2014 (26561) Mailman post from mailer-daemon@"our symantec Brightmail Gateway"  hed, message-id=<E1XOTgH-013p80-E0@"our symantec Brightmail Gateway" >: Post by non-member to a membrs-only list
Sep 01 11:53:49 2014 (26561) -request/hold autoresponse discarded for: mailer-d
emon@"our symantec Brightmail Gateway" 
Sep 01 11:53:49 2014 (26561) Mailman post from mailer-daemon@"our symantec Brightmail Gateway" hed, message-id=<E1XOTgH-00Jqig-A6@ "our symantec Brightmail Gateway ">: Post by non-member to a membrs-only list

Is this a valid assumption?
Should the server be able to handle this?
How can I see what list these are being sent too?
How can I stop them?
Thanks
Morgan

-----Original Message-----
From: Stephen J. Turnbull [mailto:stephen at xemacs.org] 
Sent: Saturday, August 30, 2014 12:44 AM
To: Ecklund, Morgan
Cc: 'mailman-users at python.org'
Subject: [Mailman-Users] Mailman is being a processor sponge.... very slow delivery...

Ecklund, Morgan writes:

 > The new environment is CentoOS 6.2 Postfix Mailman 2.1.16rc2.

If you have Yahoo! and/or AOL subscribers, you really want to upgrade to Mailman 2.1.18-1.

 > So we noticed right off the bat that Mailman was maxing the  > processor and filling memory and later I found that it was filling  > up the hard drive...

Why do you think it's Mailman and not Postfix or your virus checker etc?

None of these are normal behavior for Mailman, and I don't know of any common problem in Mailman that causes all three at once.  My guess is a configuration problem that is causing a mail loop or something like that, or a permission problem.

If it's a permission problem with Mailman, it can be detected and probably fixed with bin/check_perms.

 > Where is it hung up how can I clear it out?

It seems likely something's hung up writing to disk.  What is being written?  What do the logs of the applications in the pipeline say?

Regards,

Steve