• 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.

Issue Mail issue: Remote server returned '554 5.7.4 < # 5.7.4 SMTP; 554 5.7.4 failed to deliver message via SSL/TLS. >' -lost connection after STARTTLS from

mcac

New Pleskian
Server operating system version
Almalinux 8
Plesk version and microupdate number
18.0.65 #2
Hello,
a customer has a problem receiving e-mail from only one sender.
The sender receives a bounce email with the error:
Remote server returned '554 5.7.4 < # 5.7.4 SMTP; 554 5.7.4 failed to deliver message via SSL/TLS. >'

I can see the error in the mail log:
lost connection after STARTTLS from subdomain.domain.com[XXX.XX.XXX.XX]

It seems that the sender's mail server has a problem with the SSL certificate on our mail server, right? But the certificate is correctly installed and valid. It also only affects the one sender.
Important to know, the domain has an A-record and AAAA-record to another web server. We have therefore set up a subdomain for mail communication: mails.domain.com

What could be the problem?
 
Hard to say without knowing the full context and how everything is set up, all I can say is make sure that the certificate that's installed supports the subdomain's DNS record (or you are using a wildcard) and is securing mail access.
 
Back
Top