Scott Haneda wrote:
As a test, I have disabled authenticated SMTP on port 25. I just fired
up thunderbird, set the SMTP port to 25, and enabled SSL. Sending a
test email, and I get an error back from the Thunderbird.
Thunderbird chewed on this for a long time. My concern is what was in
the logs. If a customer of mine is on the phone with me, and I tell
them to make a connection, and the server is rather busy, I am not
seeing anything I am going to be able to use form the logs, to help them
out
Apr 24 18:13:17 catalyst postfix/smtpd[831]: connect from
c-76-102-xx1-xx.hsd1.ca.comcast.net[76.102.xx1.xx]
Apr 24 18:14:21 catalyst postfix/smtpd[831]: lost connection after
UNKNOWN from c-76-102-xx1-xx.hsd1.ca.comcast.net[76.102.xx1.xx]
Apr 24 18:14:21 catalyst postfix/smtpd[831]: disconnect from
c-76-102-xx1-xx.hsd1.ca.comcast.net[76.102.xx1.xx]
I think I would have to ask them to locate their IP, then I could help
them out.
Suggestions?
Yes, when you attempt an SSL connection to a non-SSL port, the
only thing postfix sees is an SSL handshake, which mostly just
looks like garbage. I don't know if it's even possible for
postfix to log something more meaningful in this case.
Your best bet in this case (and many others) is to point the
user to a web site with screen shots of a "proper"
configuration for their mail client.
And yes, for a number of connection problems, you will need to
know the IP the client is coming from. For internet users,
you can point them to http://whatsmyip.net or another of the
many similar services.
-- Noel Jones
