Redownload it from http://beta.woodstone.nu/soft/setupsmtp2pop3com.exe With this version you can select the operating mode: SMTP2POP3: cycle_n it will SMTP (send) and cycle_n+1 it will POP3 (receive) <- this is how it worked before SMTP: it will only send a message POP3: it will only retrieve messages <- you'll get an UP if within the received messages there is at least ONE that is send by the SMTP2POP3 Com check. (we checked the X-Sender)
dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Thu Nov 06 12:32 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP2POP3 com check The textfile think is too much of a bypass and not a solution. What I would suggest is that IF you're doing not doing an SMTP2POP3 but just an SMTP and/or just an POP3 that the POP3 will not check the subject but will check if there is a mail within the mailbox and if this mail was send by the smtp2pop3-com-check. What do you think? dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Kruithof Sent: Thu Nov 06 12:25 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP2POP3 com check You're right, it wouldn't know the subject line, good catch as usual. The SMTP iteration would have to dump the subject out to a textfile after it successfully sends the SMTP message. On the POP3 iteration, it would have to check that textfile first to know what subject to expect. Kevin Kevin Kruithof Class 3 Systems Administrator, Section 21b, Type 42, Platinum Edition Center for Useless Classification Expert Tech Group 916-677-1032 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Wednesday, November 05, 2003 2:59 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP2POP3 com check So an option in SMTP2POP3 to do SMTP2POP3 <- meaning first SMTP, next time POP3 -> that's how it works now SMTP only <- will only check a send POP3 only <- will only do a retrieve * * QUESTION: and how will it know what subject to see as being OK? Or is it just doing a POP3 logon without actualy checking if a mail was received correctly? dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Kruithof Sent: Wed Nov 05 11:54 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP2POP3 com check Sorry if that was confusing... Split SMTP2POP3 into two programs. Setup a check for SMTP and a separate check for POP3. Configure both of the checks to check on every other cycle. For this to work, there would need to be an option to have POP3 delay one cycle when SA starts checking so SMTP and POP3 would alternate. Because the checks are on alternate cycles, this should give the message plenty of time to move through the MTA to the mailbox. The affect would be: Cycle1: SMTP checked, POP3 not checked Cycle2: SMTP not checked, POP3 checked Cycle3: SMTP checked, POP3 not checked Cycle4: SMTP not checked, POP3 checked repeat... It'd be really really cool to have a check delay X number of cycles before it begins checking. You could configure a stream of checks that look for a trail of events. You could do neat things like this--configure the checks to check every third cycle, set MAPI Receive to wait 1 cycle, set POP3 to wait 2 cycles: Cycle1: SMTP checked, MAPI Receive not checked, POP3 not checked Cycle2: SMTP not checked, MAPI Receive checked, POP3 not checked Cycle3: SMTP not checked, MAPI Receive not checked, POP3 checked repeat... I hope that helps, Kevin Kevin Kruithof Confuser of Dirk Expert Tech Group 916-677-1032 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Wednesday, November 05, 2003 2:25 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP2POP3 com check Not sure to understand your question. dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Kruithof Sent: Wed Nov 05 11:21 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP2POP3 com check Dirk, Could you put in an option that works with the "one out of two cycles" functionality to make SA delay one cycle? Maybe another pulldown box that says on which cycle to start on? That way you could separate SMTP2POP3 into two programs for each check and not have to worry about adding all of that logic. This would help also in other scenarios--for instance, you could use MAPI Send / MAPI Receive in addition to the SMTP/POP3 checking to check that the MTA is working properly. Kevin Kevin Kruithof Class 3 Systems Administrator, Section 21b, Type 42, Platinum Edition Center for Useless Classification Expert Tech Group 916-677-1032 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Wednesday, November 05, 2003 8:47 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP2POP3 com check And have the SMTP/POP3 depend on the SMTP check... dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook Sent: Wed Nov 05 5:35 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP2POP3 com check Here's a possibility, what if you broke this into 2 checks? The first simply does the SMTP check, the second does the SMTP/POP3 check. If you get both alerts, it's a SMTP problem, only one from the 2nd check it's a POP3 problem. Mike >>> [EMAIL PROTECTED] 11/05/03 11:06AM >>> 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
