Ok, well, on the one hand, great, that certainly explains
the problem, you must have ,587 in the g_smtp_port settings...
And you must 'restart' surgemail after changing that to make
it work....
But, upgrading doesn't generally speaking, adjust any
configuration settings...
Time to examine the old ini*.rec files which exist for
exactly this reason, lets see what the matching settings were a
few days back..
ChrisP.
Now I'm REALLY confused. :-)
The "new" [6.1c-1] surgemail.ini contains the following
entries:
g_smtp_delay_stamp "TRUE"
g_smtp_log_protocol "TRUE"
g_smtp_port "25, 587"
g_smtp_secure_port "465"
Note that entering 587 for g_smtp_portauth in 6.1c-1 and
saving in the web interface does not result in a
g_smtp_portauth entry in the .ini
compare to the saved .ini in 6.3.c2-2 that was not working:
g_smtp_log_protocol "TRUE"
g_smtp_port "25"
g_smtp_portauth "587"
g_smtp_secure_port "465"
I had also tried adding 587 to the g_smtp_port field, but
that did not help.
-------- Original Message --------
Subject: Re: [SurgeMail List] Panic: Connections on port
587 not accepted after upgrade
Date: Sun, 12 May 2013 14:48:51 -0700
Organization: Computer Variations
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????
