> I just noticed our firewall was blocking egress traffic on tcp port 2703 > which SA uses for razor. Once I opened this port on the firewall, > things seemed to speed up. I'm not completely sure, but I suspect this > may be only part of the problem.
After opening up port 2703 on the firewall SA could talk to razor, today I went back to compare the performance of qmail and was amazed to see the difference. I think this was my only configuration problem... I may be talking out of my ass here, but perhaps if SA isn't able to talk to/resolve the razor servers maybe it should log the problem and give up for a while so the system can continue operate optimally, and only try back every so-often until razor servers/DNS is available again. In the case of DNS failure or if the razor servers become unavailable for some reason, SA seems to back up the mail queues and eat up all the system memory. Is this expected SA behavior? Notice the difference in the average message qtime, xdelay, and average xdelay, and Average concurrency (definitions follow at the end): ------------------------- SA able to talk to Razor: ------------------------- Completed messages: 3704 Recipients for completed messages: 4222 Total delivery attempts for completed messages: 4274 Average delivery attempts per completed message: 1.15389 Bytes in completed messages: 50974112 Bytes weighted by success: 45318425 Average message qtime (s): 27.7059 Total delivery attempts: 6291 success: 3602 failure: 884 deferral: 1805 Total ddelay (s): 37576.571967 Average ddelay per success (s): 10.432141 Total xdelay (s): 66334.680286 Average xdelay per delivery attempt (s): 10.544378 Time span (days): 0.554984 Average concurrency: 1.3834 --------------------------- SA unable to talk to Razor: --------------------------- Completed messages: 4578 Recipients for completed messages: 5037 Total delivery attempts for completed messages: 5079 Average delivery attempts per completed message: 1.10944 Bytes in completed messages: 46039454 Bytes weighted by success: 43072620 Average message qtime (s): 492.89 Total delivery attempts: 7101 success: 3981 failure: 1061 deferral: 2059 Total ddelay (s): 2133766.488631 Average ddelay per success (s): 535.987563 Total xdelay (s): 325547.260610 Average xdelay per delivery attempt (s): 45.845270 Time span (days): 0.685022 Average concurrency: 5.50042 FYI: qtime: the time spent by a message in the queue. ddelay: the latency for a successful delivery to one recipient---the end of successful delivery, minus the time when the message was queued. xdelay: the latency for a delivery attempt---the time when the attempt finished, minus the time when it started. The average concurrency is the total xdelay for all deliveries divided by the time span; this is a good measure of how busy the mailer is. later, j ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
