• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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: [email protected]
 
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: [email protected]
Too long ago, we have SMTPUTF8 off for quite some time now, but it was an ümläüt-domain, so pretty obvious.
 
Back
Top