• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Issue SMTPUTF8 is required, but was not offered by host

A separate message. My job involves finding and fixing interoperation problems.

Based on this thread, I suspect that there's a bug somewhere in the vicinity of Plesk that leads to some messages being labelled as "this message requires SMTPUTF8" even though there's no really good reason to do that. I'd like to locate the source of those message and fix that bug. If anyone sees the problem, I'd be grateful for a pointer or any relevant data.
The only times where I ran into this problem, xn-- domains were involved, so there was a reason to do that.
 
Well, if you didn't say "duh, of course" when you saw it, then the error was surprising enough that I'd like to see an example of such a message, if it's possible for you to show me one. My private email address has no retention or anything: arnt@gulbrandsen.priv.no
 
Well, if you didn't say "duh, of course" when you saw it, then the error was surprising enough that I'd like to see an example of such a message, if it's possible for you to show me one. My private email address has no retention or anything: arnt@gulbrandsen.priv.no
Too long ago, we have SMTPUTF8 off for quite some time now, but it was an ümläüt-domain, so pretty obvious.
 
Back
Top