Just for the test we did a loop of sending 200 mails via the queue. What we see is that between the generation of the mail and the actual send of the last mail (mail 200 that is) we have about 16 minutes. We're using a remote mailserver (mailserver on the internet). That means that the queue was able to send about 12 mails per minute. When using a local mailserver we will be able to send more mails.
Developper of the component will have a look at the component to see if it's possible to change the sender into using several sender threads. We do have to see what impact this would have on the code and if we can via a parameter limit the number of threads. I can imagine that some SMTP server only want a few connections from the same system…. Will get back on this beginning next week. dirk From: Servers Alive Discussion List [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, September 22, 2011 5:46 PM To: Servers Alive Discussion List Subject: [SA-list] mail delay when checks are DOWN? Hi, we had 166 DOWN checks this morning, normally we have some 0 to 5. This were all PING checks (SK) each with 2 dependant checks (1 NT process, 1 NT service). Yes, that was bad! The systems were „not existent“, so the PING was not executed: ERR: problem resolving the name (BKKXENAPP077) ERR: problem resolving the name (Winsock could not resolve the host name (11004)) The alert is configured to send SMTP mail when 1 time down (and when up again), the checking schedule starts 5:45. Check times: every 3 minutes. The status summary mail is configured to be sent “approximately at” 5:50, our normal check cycle lasts about 10-12 minutes, so I expect the status mail to be there around 6:05. According to the logfile, the check cycle ( 567- 567) started at 05:48:39, the next one ( 568- 568) at 06:07:07. Now we had this effect: The 1st alert mail: generated 05:48:50, received 05:48:55 The 10th alert mail: generated 05:57:55, received 05:58:38 The ~100th alert mail: generated, 06:01:34 received 06:14:54 The last alert mail: generated 06:03:32 , received 06:23:35 The status summary mail: generated 06:04:05, received 06:23:45, the header is looking like this: Received: from BKKSALIVE002.bkk-mobiloil.de (10.96.65.5) by bkkmail003.bkk-mobiloil.de (10.96.65.132) with Microsoft SMTP Server id 14.1.289.1; Thu, 22 Sep 2011 06:23:45 +0200 To: <[email protected]> From: <[email protected]> Subject: Servers Alive: down: 166 - up: 823 - maintenance: 60 Date: Thu, 22 Sep 2011 04:23:45 +0000 Message-ID: <[email protected]> X-Mailer: Woodstone Servers Alive version 6.3.2407 X-Priority: 2 X-Info: http://www.woodstone.nu/salive (http://www.woodstone.nu/salive) X-WSSAID: 44540120110922.SA632407-1 MIME-Version: 1.0 Content-Type: text/plain Return-Path: [email protected] X-MS-Exchange-Organization-AuthSource: bkkmail003.bkk-mobiloil.de X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AVStamp-Mailbox: MSFTFF;1;0;0 0 0 X-OLX-Disclaimer: Done X-Auto-Response-Suppress: DR, OOF, AutoReply Who is generating this delay? The mailserver admin says: it wasn’t me! SA version is 6.3.2407, but in january we had the same effect on our old system, with 6.2.2279.3. Mit freundlichen Grüßen Ralf Minuth Teamleitung Server/Anwendungen Mobil BETRIEBSKRANKENKASSE Hühnerposten 2, 20097 Hamburg www.bkk-mobil-oil.de (www.bkk-mobil-oil.de) Telefon: 040 3002-60301 Telefax: 040 3002-960301 E-Mail: [email protected] (mailto:[email protected]) Auch 2012 kein Zusatzbeitrag – jetzt Mitglieder werben und belohnt werden. Nähere Infos finden Sie hier: www.bkk-mobil-oil.de/mitgliederwerbung (http://www.bkk-mobil-oil.de/mitgliederwerbung) To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
