Hey Stephen, Thanks for responding. We do have a lot of public lists. The majority of the subscribers are google users (domain) though. So we started getting the " Multiple destination domains per transaction is unsupported" error. So I had to enable the "single connection per email Will the update help with that issue? I can imagine that is problem for delivery performance. We also have internal subscribers only lists. Subscribers are all on exchange server which is behind a Symantec Bright Mail Gateway (do they consider that a smart relay, cause man it is pain in my a$$?) The delivery delay occurs with all of our lists internal and external. When I send a message. I can see that it is received by the list serve server in the Maillog. Then 3 hours later I see in the mailman log that the message (confirmation that my message is awaiting moderation) was sent. I approve it for delivery it takes another 2-3 hours to hit my inbox. The only reason I think it is related to mailman is because whenever I look I see that mailman is taking a ton of processor and memory. When I run Check perm it says "no errors found". I can attach my config files, which would you like to see? Thanks Again Morgan
-----Original Message----- From: Stephen J. Turnbull [mailto:step...@xemacs.org] Sent: Saturday, August 30, 2014 12:44 AM To: Ecklund, Morgan Cc: 'mailman-users@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 ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
