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

Emails Issue between 365 Cloud and Linux Plesk

bradz

Regular Pleskian
- Domain abc.com is not able to send emails to email accounts on Linux Plesk servers (I tested an email on 3 different servers).
- The Linux Plesk servers all receive and send emails to others and receive from other 365 Cloud emails.
- The emails@abc.com are able to send to other emails, but error out, saying no response when sending to the emails on the 3 tested Linux Plesk Servers.
- I have tried white listing *@abc.com, but this did not help.
- I did not see an issue with the Header info when emails@abc.com were sent to gmail as a test.

Question: What test can we run to determine the communications or lookup issue?
 
Hi bradz,

some Cloud providers block ports in initial states. Please consider contacting your provider and ask him, if he blocks any ports by default in your virtual environment.


Second you could try to investigate possible ( false?!? ) firewall settings and please check, that you opened all needed ports:


Log - files and configuration files help to investigate issues:

 
Had not thought of ports being involved, but maybe. I will research these thoughts. Thanks!
 
Back
Top