Okay, I'm really at the end of my rope here. I have a mail server that I have set up which was supposed to be copy of a working machine. This machine runs Dovecot as a mail server and Postfix as an SMTP server. I use MySQL for the account information (and postfixadmin to administer).
The email server (IMAP) works, and I can receive email from the outside just fine. Anyone emails my address, I get the email. What is NOT working is using the server as my outbound SMTP server.
I am using a non-standard port, 2525 to send out, with authentication (obviously so it's not an open relay) and I have an SSL certificate, the same one as my web server.
When I attempt to send, it just times out. No specific error message, just seems to go nowhere and eventually on my mail client (Mac Mail.app in this case) it just comes back with a "can't send".
I can telnet to the server (telnet www.eightounce.com 2525) and it will respond, but then closes the connection when I do a test with ehlo. Files and logs below. I'm baffled. I do see TLS errors in the log file, but I don't know how to start to fix them.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
After check if you have the openssl package on your server and check if they match the same version on both machines.
There was a known problem with the Hello extension for OpenSSL during initialization of TLS channels, the suggestion is to get the latest version of OpenSSL and compile it from sources.
Reverse lookup is working, it shows the ISP instead of my domain but it is working (below). OpenSSL is actually newer (0.9.8g) on the machine that's not working than on the original I coped from (0.9.8b) that is working.
Server: 216.19.176.6
Address: 216.19.176.6#53
Non-authoritative answer:
53.176.19.216.in-addr.arpa
Authoritative answers can be found from:
176.19.216.in-addr.arpa nameserver = ns1.novuscom.net.
176.19.216.in-addr.arpa nameserver = ns2.novuscom.net.
ns1.novuscom.net internet address = 216.19.176.13
ns2.novuscom.net internet address = 216.19.176.16
Clearly seems to be a problem with the OpenSSL library, try to get it and recompile it entirely from sources.
Update to version 9.8K or try the beta 1.0.0
This is why i think so:
(Jul 4 20:28:27 www postfix/smtpd[20245]: warning: TLS library problem: 20245:error:140760FC:SSL routines:SSL23_GET_CLIENT_
Business Accounts
Answer for Membership
by: martino87rPosted on 2009-07-06 at 01:55:56ID: 24783500
Now, first question:
Your machine have a reverse DNS record? To check open a terminal and write:
nslookup [youripaddress]
if no reverse record is found in the dns, then you have to modify the config file to accept connections from host that doesn't have an FQDN
let me know