Ok so if I have the new com check set to send an alert on 1 down I assume it will alert me when either the send or the receive fails. However if only one of them is failing and I have it set to send an alert on 1 down and when back up will I then get an alert every check cycle one saying expected mail not received and one saying send successful followed by another saying expected mail not received?
Or does SAlive distinguish between the n and n+1 cycles for alerting purposes? I think it should stay down until both cycles succeed again. The GUI should show the send successful (That way we would know that was still working). Could you clarify how it works now and how if any changes might be made? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Tuesday, November 04, 2003 2:14 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP2POP3 com check Beta is updated and should show what exactly caused the error: ERR SMTP <= sending part ERR POP3 <= receiving part You can get it in the alerts by using the %e parameter. dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Passow Sent: Tue Nov 04 8:54 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP2POP3 com check So when an alert is sent does it distinguish between which cycle caused the down? Not that if we got an alert we couldn't test it ourselves to figure where it is failing but nevertheless does the check tell us if it was the receiving of the mail or the sending of the mail that failed? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Tuesday, November 04, 2003 8:41 AM To: [EMAIL PROTECTED] Subject: [SA-list] SMTP2POP3 com check Just posted a new beta which add SMTP authentication.... A while ago a lot of people were asking for a way to get a faster check cycle. One of the remarks was that SMTP2POP3 took too long. Based on that we decided to rewrite SMTP2POP3 into a COM based check. Were in cycle_n we would send the SMTP message and in cycle_n+1 we would try to retrieve the message we just send. This means that in cycle_n an UP means that the message was send correctly (SMTP working fine) And in cycle_n+1 an UP means that the mail send in cycle_n+1 was retrieved correctly (POP3 works fine AND the mailflow too). You do need at least build 4.0.1533 (http://Beta.woodstone.nu) of Servers Alive for this COM check to work correctly. The check itself can be downloaded from http://beta.woodstone.nu/soft/setupsmtp2pop3com.exe dirk. To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
