• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question How to use SSL for mail insatead of STARTTLS?

TurabG

Basic Pleskian
Hi,

I have set an SSL for mail and done settings properly. I can use my mail from outside through SMTP. But as far as I can see, it forces to use STARTTLS. There is a web client I have to use which is not compatible with STARTTLS and it has to use SSL. I don't see a place to set it in Plesk. Do I have to do it manually and if so, how can I?
 
Hi Dave. Thanks for the response. I think I didn't make it clear enough. This is not a port issue as far as I can see. When I test it through telnet, it still asks me to issue STARTTLS first.
 
Dave is correct

Your server will offer StartTLS on port 25 and 587 for SMTP, 110 for POP3 and 143 for IMAP
On the ports 465, 993 and 995 however, you are forced to use an SSL/TLS connection before issuing any commands.
 
Hi again. I do not think this is a port issue as I said before. Because, SMTP on port 587 with STARTTLS works very well but on port 465 with SSL gives auth failure with the same credentials. That means, if I configure a mail client with STARTTLS on port 587, it works but without changing any other thing I set the client to use SSL on port 465, it can not send mails.

Edit:
I found out the reason I think. I am typing the server IP address for auth address. Although it works with STARTTLS; it won't with SSL as it is complaining that the SSL name "domain.com" is not equal to the IP address. THe reason I am typing IP address instead of the domain is because the domain is behind Cloudflare and it wouldn't allow SMTP on free plans.

As a workaround I added an A record to Cloudflare DNS like "smtp.domain.com" to point to the server's IP address with "DNS Only" (i.e "Not proxied") but it didn't work. Now some clients still give auth error but some clients now say; "Expected response code 354 but got code "554", with message "554 5.5.1 Error: no valid recipients"
 
Last edited:
Then you should open a ticket with support becuase it should work on 465 with SSL as long as you are connecting to the domain name in the SSL.
 
Back
Top