The way to compensate at this point is when 2 of the last 3 checks fail send the alert. THis should be considered only a work around.
---- Original Message ---- From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP2POP3 com check Date: Wed, 5 Nov 2003 17:06:03 +0100 >Correct about the alert. >For the alert there is maybe a solution. To be tested although, it's >just an idea... >Set the alert to send on 1 down and backup AND enable the option that >says "when host is down the "extra..."" and give as string POP3 >That way (if my logic is good enough) you will get the down alert >when >the POP3 isn't working correctly AND you'll only get the UP alert >when >the POP3 part is working again. The status within the interface will >flip between up/down although. And setting the alert to only send >after >2 downs (for example) won't work correctly since it will go >up/down/up >all the time (if SMTP works fine and POP3 isn't). If the POP3 isn't >working correctly because the POP3 server is down for example then it >should be a real problem since your smtp2pop3 test should depend on a >test of the SMTP and/or POP3 server. (OK I feel this one coming how >can >I make it depend on 2 entries, knowing that the 2 entries don't >depend >on each other...well for the moment you can't do this). > > > > >dirk. > > > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >Behalf Of Jason Passow >Sent: Wed Nov 05 4:20 PM >To: [EMAIL PROTECTED] >Subject: RE: [SA-list] SMTP2POP3 com check > > >Ok so I understood correctly initially. > > So if the POP3 cycle Fails but the SMTP cycle succeeds and I have an >alert set to Send an alert "when one time down and when backup" If >the >SMTP cycle is working (send successfully) and the POP3 cycle fails >will >I get an alert every cycle on the POP3 cycle saying mail is down and >on >the SMTP cycle saying mail is back up? > >If so I reiterate my point that the check should stay in a down state >until both cycles succeed. The GUI should reflect what is really >happening for example send successfully but until that mail is >received >it should stay ina down state. > >Does that make more sense? > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >Behalf Of Dirk Bulinckx >Sent: Wednesday, November 05, 2003 8:42 AM >To: [EMAIL PROTECTED] >Subject: RE: [SA-list] SMTP2POP3 com check > >SMTP is sending mail >POP3 is receiving it. > >SMTP2POP3 will be in an SMTP cycle until a mail is send successfully. >Then it will go to a POP3 cycle. >If the POP3 is successful or not, the next cycle will be an SMTP >cycle. > > > >dirk. > > > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >Behalf Of Jason Passow >Sent: Wed Nov 05 3:38 PM >To: [EMAIL PROTECTED] >Subject: RE: [SA-list] SMTP2POP3 com check > > >In your first example what happens if the second SMTP cycle gives a >down? Does it just run another SMTP followed by another SMTP until it >receives the >mail it sent in the pop3 cycle? How many SMTP cycles does the com >check do >before another POP3 cycle? If it does just continue to do SMTP cycles >is >there a way to force it (put into maintenance and back off again?) to >do >a POP3 again followed by an SMTP and back to normal (Hopefully >anyway)? > > > >In the second example if the pop3 gives a down I assume it continues >to >check SMTP then POP3 then SMTP then POP3 until it works again >correct? > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >Behalf Of Dirk Bulinckx >Sent: Wednesday, November 05, 2003 8:29 AM >To: [EMAIL PROTECTED] >Subject: RE: [SA-list] SMTP2POP3 com check > >If the SMTP cycle gives a down, the next cycle will again be an SMTP >cycle. If the POP3 cycle gives a down then the next cycle will be an >SMTP cycle. SA as such doesn't know if it's a POP3 or SMTP cycle. > > > >dirk. > > > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >Behalf Of Jason Passow >Sent: Wed Nov 05 3:23 PM >To: [EMAIL PROTECTED] >Subject: RE: [SA-list] SMTP2POP3 com check > > >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 > > > >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 > > > >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
