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

Resolved Plesk POP3 Server via Cloudflare not reachable

ChrisCP

Basic Pleskian
I have the following problem. I use a domain with various email addresses. Everything works fine. Email client (Outlook) is set up in such a way that messages are queried via pop3 in encrypted form. As I said, everything works fine. Now the domain is passed through Coudflare because the traffic increases. Now Outlook can no longer retrieve the emails because the IP of the domain is handled via Cloudflare and the pop3 mailserver (domain.com) can no longer be reached.
I can send and receive emails via webmail. DNS entries at cloudflare are only the CNAME and A entry proxied via Coudflare.
Is there a solution for this?
 
This would clearly be a question for the Cloudflare support.
Have you seen this article?
 
I've already read the article. Webmail and mail as well as mx entries are not proxied via cloudflare. That's why I receive emails and can also send them. But only via webmail. Pop3 incoming mail server in plesk is the domain name. Right!? And that's exactly where the problem is, since the domain and the IP runs over cloudflare.
 
Have you made sure that the mail-in and mail-out server names that your email software is using, have A-records in Cloudflare? Many users are using names like smtp.<mydomain> or pop3.<mydomain>, imap.<mydomain>, but forget that they need to have either a specific A-record to resolve these names to their destination or to have a wildcard subdomain entry with Cloudflare to resolve the names.
 
I've already read the article. Webmail and mail as well as mx entries are not proxied via cloudflare. That's why I receive emails and can also send them. But only via webmail. Pop3 incoming mail server in plesk is the domain name. Right!? And that's exactly where the problem is, since the domain and the IP runs over cloudflare.
On the plesk server, dovecot listens on 0.0.0.0:995 etc., which means on all IPs.
Have you tried connecting to webmail. via pop3?
(Plesk letsencrypt requests the webmail. name with the certificate for the main domain, so this should work.)
 
Back
Top