The web interface works fine on https -
I think that SSL err might have been a red herring.
So I downgraded to 6.1c-1 - the next previous version I found on
ftp.netwinsite
- and connections on port 587 are being accepted. I TOOK NO OTHER
ACTION, no changes to surgemail.ini, and this email is being sent
via port 587.
?!?
On 5/12/2013 2:03 PM, surgemail-support wrote:
I'm not aware of any changes between those versions that
would cause that. It appears to
be the same version of SSL and I don't see any ssl changes
from our end.
It may be an expired ssl certificate (try removing it so
surgemail regenerates a new one) also try another email client
to see if that helps.
Also check using https from a browser to the web interface to
see if it is reporting anything unusual, it's the same
protocol/library so it should give you the same problem.
As a last resort you may want to try downgrading to that
previous build to see if that repairs the problem, let me know
if you want me to investigate further directly after you've
tried the above...
ChrisP.
I'm in a Panic.
I upgraded from 6.2c-1 to 6.3c2-2 Linux 64, and I can no
longer receive connections on port 587. I MADE NO OTHER
CHANGES.
The only pertinent entry I can find in the logs is in
mail.err:
2013-05-12 10:28:13.00:Err:1101576512: Security error send
(ÿÿÿÿ)
2013-05-12 10:29:14.00:Err:1101576512: Security error send
(ÿÿÿÿ)
2013-05-12 10:30:21.00:Err:1103526208: SSL:
336151576:handaccept
2013-05-12 10:30:21.00:Err:1103526208: SSL:
336151576:handaccept r=SSL routines f=SSL3_READ_BYTES d=tlsv1
alert unknown ca
2013-05-12 10:30:21.00:Err:1103526208: pop: stls ssl failed
SSL could not start, unknown reason (0)(handaccept SSL
routines SSL3_READ_BYTES tlsv1 alert unknown ca)
I did not change the (self-signed) certificate at all - it
would seem SM is requiring a new setting????
