From: "Harold Paulson" <[EMAIL PROTECTED]> > Danny, Hi Paul.
> Here are some ways I have discovered of making Mailman really painfully slow: > > 1) Use Sendmail for your outgoing MTA and have it do DNS checks on > relayed mail. Pick an email address out on the net and test it from > your Mailman machine with something like 'mail -v > [EMAIL PROTECTED]'. By the way, turning off DNS checks in > sendmail usually makes it an open relay. Yeah! [root@lnx root]# mail -v [EMAIL PROTECTED] Subject: Test Cc: [EMAIL PROTECTED] Connecting to xx.xx.xx. via relay... 220 xx.xx.xx Ready for action (Mailtraq 1.1.6.1177/SMTP) >>> EHLO lnx.xx.xx.xx 250 xx.xx.xx >>> MAIL From:<[EMAIL PROTECTED]> 250 receiving from [EMAIL PROTECTED] >>> RCPT To:<[EMAIL PROTECTED]> 250 will send to [EMAIL PROTECTED] >>> DATA 354 send the message, terminate with "." >>> . 250 received the message, thanks [EMAIL PROTECTED] Sent (received the message, thanks) Closing connection to xx.xx.xx. >>> QUIT 221 have a nice day (SMTP Closing) [root@lnx root]# Very fast. No problem here. > 2) Have slow or broken DNS. What happens when you do something like, > 'nslookup hotmail.com' from your Mailman server? [root@lnx root]# nslookup hotmail.com Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from appearing. Server: 192.168.0.1 Address: 192.168.0.1#53 Non-authoritative answer: Name: hotmail.com Address: 64.4.54.7 Name: hotmail.com Address: 64.4.43.7 Name: hotmail.com Address: 64.4.44.7 Name: hotmail.com Address: 64.4.45.7 Name: hotmail.com Address: 64.4.52.7 Name: hotmail.com Address: 64.4.53.7 [root@lnx root]# And with dig : [root@lnx root]# dig hotmail.com ; <<>> DiG 9.1.3 <<>> hotmail.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24642 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;hotmail.com. IN A ;; ANSWER SECTION: hotmail.com. 3600 IN A 64.4.54.7 hotmail.com. 3600 IN A 64.4.43.7 hotmail.com. 3600 IN A 64.4.44.7 hotmail.com. 3600 IN A 64.4.45.7 hotmail.com. 3600 IN A 64.4.52.7 hotmail.com. 3600 IN A 64.4.53.7 ;; AUTHORITY SECTION: hotmail.com. 3600 IN NS ns1.hotmail.com. hotmail.com. 3600 IN NS ns2.hotmail.com. hotmail.com. 3600 IN NS ns3.hotmail.com. hotmail.com. 3600 IN NS ns4.hotmail.com. ;; ADDITIONAL SECTION: ns1.hotmail.com. 3600 IN A 216.200.206.140 ns2.hotmail.com. 3600 IN A 216.200.206.139 ns3.hotmail.com. 3600 IN A 209.185.130.68 ns4.hotmail.com. 3600 IN A 64.4.29.24 ;; Query time: 189 msec ;; SERVER: 192.168.0.1#53(192.168.0.1) ;; WHEN: Sat Apr 27 02:48:49 2002 ;; MSG SIZE rcvd: 261 [root@lnx root]# Is this good or bad? > 3) Leave old lock files lying around in ~mailman/locks/. This works > especially well on really old versions of mailman. No old lock files there. > 4) Populate your mailing lists with email addresses from the corners of > the earth with the worst connections and shakiest DNS. :-) I am in holland and only dutch and some belgium people subscribed. So no strange corners here also :-) > Good luck! > >I did change the default values to : > > > >SMTP_MAX_RCPTS = 1 > >LIST_LOCK_LIFETIME = minutes(5) > >LIST_LOCK_TIMEOUT = seconds(10) > >QRUNNER_LOCK_LIFETIME = minutes(10) > >QRUNNER_PROCESS_LIFETIME = minutes(5) > >QRUNNER_MAX_MESSAGES = 5 But are these fine or not? What are good value's? Danny. ------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
