• 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!
  • 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 SmarterMail 16.x disabled domains block inbound emails

Joe Payne

New Pleskian
We recently upgraded to Onyx and then upgraded to SM 16.

Due to a change in how SM 16 handles inbound mail for disabled email domains, SM 16 will not accept email from a domain that is listed in SM and marked as disabled. This means that any hosting account who hosts the website in Plesk but keeps the email with another provider (gmail or anyone else) cannot email anybody on that SM server. SM will respond "550 domain is disabled"

Has this been addressed in Plesk?

Why is Plesk even creating an email domain when email services are not enabled for the website? This consumes a SM mailbox license and it creates a massive number of unnecessary email domains in the SM install.

You can get around the issue by manually deleting the disabled domain in the SM admin UI. But doing that breaks the Plesk email setup - you can no longer activate email services for that domain within Plesk.
 
Hello Joe

You can also set the domain manually inside Smartermail 16 to "external" for incoming mails and than it's working.

cheers chris
 
Hello

It would be great if there where a solution direclty inside plesk and not manually change config inside smartermail. in earlier version of plesk or smartermail the domain in smartermail was just renamed to youdomain.com.d and that worked great.

best regards chris
 
Back
Top