Hi,
Dovecot allows practically everything even if you don’t enable UTF8=ACCEPT. From memory there are only two differences:
Dovecot’s handling of unexpected Unicode is so liberal that some clients protest
😉
Arnt
From:
"John R. Levine" <johnl@iecc.com>
Date: Monday, 27 January 2025 at 18:18
To: Arnt Gulbrandsen <arnt.gulbrandsen@icann.org>, Dr Ajay Data <ajay@data.in>, "ua-eai@icann.org" <ua-eai@icann.org>
Subject: Re: [UA-EAI] Re: [Ext] Re: Dovecot 2.4 released today
On Mon, 27 Jan 2025, Arnt Gulbrandsen wrote:
Sorry, I assumed that John’s question was about IMAP clients. I agree that there are more UA-ready mail clients in general, even if I’m a little surprised by that list. Last time I tested the ios app (Apple’s, I assume) it was unable to reply correctly, and since I’m typing this into Outlook, let’s test… nope, can’t add a Unicode address to this message, see screenshot. The previous version could do it, and OWA can too.
When I was testing EAI software a while ago, I found almost no IMAP
clients or servers that had the EAI extensions, but it hardly mattered
since they handled EAI messages and UTF-8 folder names using the regular
non-EAI methods. Dovecot, at least up to 2.3, only allows ASCII user
names and passwords (I looked at the code.) In 2.4 it should allow them
if your client turns on the extension. Any idea if it does even if you
don't?
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail.
https://urldefense.com/v3/__https://jl.ly__;!!PtGJab4!_Btry1e7PUX8kBueTJCm7ekOnLeX0ksLCuPYAXi2tjyy2OiX7a3L7T76gEwl2jqmXZQE7FzzyALJh7NEVKAAjCw$ [jl[.]ly]