Re: [hobbit] Service SMTP on xxxxxx is not OK : Unexpected service response

["T.J. Yang" <tj_yang (at) hotmail.com>]

It is not just MS's smtp server, older sendmail versions will also trigger false alerts also.
I got a Solaris 2.6 running very old version of sendmail and keep triggering false alerts.
In the end, I gave up on monitoring that particular sendmail server. 

tj


From: White, Bruce 
Sent: Wednesday, June 25, 2008 5:06 PM
To: 'hobbit (at) hswn.dk' 
Subject: RE: [hobbit] Service SMTP on xxxxxx is not OK : Unexpected service response


We had a similar problem with our exchange server until I changed the bb-services file to be:

 

[smtp]

   send "helo\r\nquit\r\n"

   expect "220"

   options banner

   port 25

 

Now the exchange response to smtp is much more stable, but my linux sendmail servers complain more often.   I guess I need to make a smtpex with the above and restore the original smtp definition, which seemed to work better with Linux.   Why can't MS just do things to standards?

 

       ..Bruce

 

 


--------------------------------------------------------------------------------

From: Geoff Hallford [mailto:geoff.hallford (at) gmail.com] 
Sent: Wednesday, June 25, 2008 11:53 AM
To: hobbit (at) hswn.dk
Subject: Re: [hobbit] Service smtp on xxxxxx is not OK : Unexpected service response

 

I have also seen this happen when the response is slow from the mail server to show the 220 message. It does show it but is slow for some reason. I create a new service called smtp-slow by adding the following and then configure the bb-hosts entry with 'smtp-slow' instead of smtp. Just a thought.

 

This way it doesn't require a 220 response but if it gets a valid "connection" it is okay. If it can't open a connection, it goes red. It does limit the amount of app validation but it is the only thing that worked in my case.

 

[smtp-slow]
   send "mail\r\nquit\r\n"
   options banner
   port 25

On Wed, Jun 25, 2008 at 12:31 PM, Andrew Clarke <andrew (at) bccit.co.uk> wrote:

As it happens, there are PIXs between the hobbit server & all the
Exchange servers. However, they've all been there for ages (years in
some cases).

I'll have a chat with our resident Cisco guru & see if he made any
changes at our end around 6th June, when things stopped working.



Andrew Clarke
Support and Technical Development Officer
BCC IT Solutions
DDI: 0871 288 2036
Tel: +44 (0)1239 710823
http://www.bccit.co.uk/
Providers of business to business IT Solutions & Services
Back-up - Anti Virus - Security - Servers - Wireless Networks - VPN - Remote Monitoring - Project Consultation Hardware Provision Servers & Workstations - Disaster Recovery - Proactive Diagnostics - System Migration - Fibre CAT5e Server Administration - Forensics - Grant Appraisal - Network Management - System Appraisals - Support Contracts ...
For full e-mail terms & conditions of use, please follow the link to the bcc web site http://www.bccitsolutions.co.uk/index.php?option=com_content&amp;task=view&amp;id=24&amp;Itemid=1
BCC IT Solutions is a trading name of European Computer Units Limited, Registered in Cardiff, Company Registration No. 2651835
Registered Office: Unit B Station Road, Newcastle Emlyn, Carmarthenshire, Wales, SA38 9BX

-----Original Message-----

From: Rob MacGregor [mailto:rob.macgregor (at) gmail.com]

You wouldn't happen to have a Cisco PIX/ASA between the hobbit host and
the mail server, with it configured to do "fixup"?  Those are known for
breaking things ;)

Rob MacGregor


To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk






-- 
'If my answers frighten you then you should cease asking scary questions.' --Sam Jackson 




----------------------------------------------------

Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc.

----------------------------------------------------