|
Hi Dirk – Ok, I’ll (try to) remember
to stop SA prior to making changes to those. As for the SMTP timeout, it’s
something on that SMTP server that is taking way too long to respond. I had to run the timeout up to 35
seconds (a telnet session to this RAQ 3 SMTP takes 30 seconds to return the
banner) to get this to not fail the first time, now the check works correctly. Something is up with that RAQ 3 server though;
it shouldn’t take that long to respond… Thanks! -----Original Message----- If you edit these entries while SA is
doing a similar check it will sometimes "receive" the wrong
parameters. Dirk. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike McTee After digging a little deeper, I found
that the 2 checks had changed back to having the same settings under the Mail
Flow Check configuration. Does this
happen if you do an update without stopping SA? -----Original Message----- I have 2 mail servers that I am monitoring using Mail Flow
Check. I have these checks set with
Second Knock so that it doesn’t falsely notify. For some reason, SA alternates between
showing one server down on the first cycle, and then the next cycle shows that
server up and the second server down.
The next cycle that one shows up, yet the first one shows down
again. Neither of these servers are
“really” down. This
false reporting alternating between the two goes on continuously. Is this something wrong with the timing of using Mail Flow
Check too soon after the previous use by the other check or something? Thanks in advance. |
- RE: [SA-list] MailFlow Check Dirk Bulinckx
- RE: [SA-list] MailFlow Check Mike McTee
