On 19.03.2018 07:58, Alexander Dalloz wrote:> Am 18.03.2018 um 23:25 schrieb Andr? Rodier: >> Every other alias works, but not those with accents. They are correctly >> stored in the LDAP database, using base64. > > Why do you even think a character like '?' would be legal in the local > part of an email address? > > Alexander >Hi! This is slightly more complicated than that. UTF-8 is legal part of local part of an email address, if SMTPUTF8 is used (as per RFC 6532). Dovecot does not yet fully support UTF-8 in certain parts, particularly we do not yet support RFC 6855 (IMAP Support for UTF-8), but we are working on getting that to work, after which you can log in with UTF-8 usernames and passwords reliably. Aki
On 19/03/18 06:30, Aki Tuomi wrote:> > > On 19.03.2018 07:58, Alexander Dalloz wrote: >> Am 18.03.2018 um 23:25 schrieb Andr? Rodier: >>> Every other alias works, but not those with accents. They are correctly >>> stored in the LDAP database, using base64. >> >> Why do you even think a character like '?' would be legal in the local >> part of an email address? >> >> Alexander >> > Hi! > > This is slightly more complicated than that. UTF-8 is legal part of > local part of an email address, if SMTPUTF8 is used (as per RFC 6532). > Dovecot does not yet fully support UTF-8 in certain parts, particularly > we do not yet support RFC 6855 (IMAP Support for UTF-8), but we are > working on getting that to work, after which you can log in with UTF-8 > usernames and passwords reliably. > > Aki >Thank you, Aki, Does it means Dovecot LMTP supports querying the LDAP server using UTF-8 characters? In this case, the problem might not be Dovecot, but OpenLDAP. I had to use base64 encoding to store email addresses, because they are rejected otherwise, with an error message of illegal characters. I also noticed that some of the fields, like 'dn' and 'cn' where automatically encoded in base64 when stored when including accentuated chars. Regarding logging in with international characters, I have not tested it yet, but I am happy to test and to provide feedback if you are interested. Thanks again for this excellent software, I have been using it for more than a decade, now... Kind regards, Andr?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 19 Mar 2018, Andr? Rodier wrote:> I had to use base64 encoding to store email addresses, because they are > rejected otherwise, with an error message of illegal characters. I alsoyou are using the stock "mail" attribute in LDAP as: olcAttributeTypes: ( 0.9.2342.19200300.100.1.3 NAME ( 'mail' 'rfc822Mailbox' ) DESC 'RFC1274: RFC822 Mailbox' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{256} ) http://www.oid-info.com/get/1.3.6.1.4.1.1466.115.121.1.26 https://en.wikipedia.org/wiki/IA5STRING IA5 :- 7bit> noticed that some of the fields, like 'dn' and 'cn' where automatically > encoded in base64 when stored when including accentuated chars.you mean when you use ldapsearch or similiar tool to export data? LDIF traditionally encode all data in 7bit ASCII, which is noted by the double "::" after the LDAP attribute name. The data in LDAP is UTF8 and binary connections need not encode it either. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWq9lWMQnQQNheMxiAQL3ywgAtbWsT1U+PQgdK0D3StI9c44r8KgEG7dr AXhIvFPowuD3U0KH0ZJ8VHc+/WN0DMqCONvuaUyueaGY8bgqx+cNw8z01zMC9hTF xfs8x1lQsgikacyyjo3o9WehOJzgnlGvt33LLwjsI62WOLFE8PXnkZFXpkAWI1f4 yTWoTFOxPnAA90CDBS4aBHdBaFI0TwbiGP5oIyjGCvI1aHJSTy5lNKfwUkvTdI+L tH4Z0JDkB3YBnRVIL6ST5W7p0VvBAQo+ia+UXpsZ4b1t3/xYCKtNV0ls9jIoqVzg dEFeyUoKQe8k5N8k6/vVVElzwtW6fxzQUJQXj01u03udqVMmTqXhrw==8rp9 -----END PGP SIGNATURE-----