Date:  Wed, 11 Mar 2009 13:20:12 -0600
From:  "Gerald Waugh" <gwaugh (at mark) frontstreetnetworks.com>
Subject:  [coba-e:15287] Re: SMTP showing 'red' in GUI since update
To:  <coba-e (at mark) bluequartz.org>
Cc:  "BlueOnyx General Mailing List" <blueonyx (at mark) blueonyx.it>
Message-Id:  <7382044031F7496EBEE1106ADC0ECC2B@raqware>
References:  <49b72ece.1e048e0a.2809.7f79 (at mark) mx.google.com> <C72AE6FE837141BC9C6A83AB68445F0A (at mark) OfficeKen> <865832496E8C47FBAB60C1DFF75F0654 (at mark) OfficeKen> <45DACA7BE1DEA245AF6C95E5B94E531B0D07A62CCB (at mark) datastore.mainline.local>
X-Mail-Count: 15287

Colin wrote;
>
> You're not really losing it - I am having problems with both SMTP and FTP 
> ... a server that has been stable for years has suddenly started sending 
> me 'not working' messages every now and then. SMTP was totally broken (FTP 
> flakey) after the update but then it suddenly started working. Now it just 
> falls over about two or three times a day.
>
> There is something fishy going on in that update :-/
>
> Hopefully someone more knowledgeable than me will work out what it is.
>
Seems like the problem is on BlueOnyx also, I never had it on BQ
Here is what I did on BX

/usr/sausalito/swatch/bin/am_ftp.exp
Seems to have an issue with ftp.
Not sure tht it is a good fix but, I commented these lines out, as "send 
QUIT\r" does not seem to work.
It still will indicate if ftp is listening and responding with the '220'.

# send "QUIT\r"
# expect {
#    "221 " {}
#    default { # fail if we're not ack-ed properly
#       puts -nonewline $env(redMsg);
#       flush stdout;
#       exit $AM_STATE_RED
#    }
# }