In response to your #1, below, dovecot has no problems with IDN's I
am told. I tried installing pecl/idn extension - but it is very old
and will not install with newer version of php 5. (I saw your exchange
with Steffan in february of this year late). I am running php 5.4.26,
and using sql authentication backend in horde.
Have you considered trying a php class for idn and horde/imp:
http://www.phpclasses.org/package/1509-PHP-Convert-from-and-to-IDNA-Punycode-domain-names.html
?
I don't know what to try. You never responded to my earlier querries
re mbstring - or setting intl to use UTF-8?
You mentioned that horde doesn't accept UTF-8 as input for
authentication, that it must be ascii. Is there only one table I need
to check in the horde db? Will modification of any of the character
sets in the horde DB resolve this problem?
Has anyone, to your knowledge, ever gotten horde AND imp to
authenticate a login using an IDN?
Thanks,
ed
Tue, 12 Aug 2014 13:15:50 +0000
Connection to: imap://localhost/
Server connection took 0,0008 seconds.
S: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID
ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
C: 1 STARTTLS
S: 1 OK Begin TLS negotiation now.
Command 1 took 0,0017 seconds.
Successfully completed TLS negotiation.
C: 2 CAPABILITY
S: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
IDLE AUTH=PLAIN AUTH=LOGIN
S: 2 OK Pre-login capabilities listed, post-login capabilities have more.
Command 2 took 0,0022 seconds.
C: 3 AUTHENTICATE PLAIN [INITIAL CLIENT RESPONSE (username:
info@bo?teauxlettres.net)]
S: 3 NO [AUTHENTICATIONFAILED] Authentication failed.
Command 3 took 1,5036 seconds.
This is correct. IMP is sending the "AUTHENTICATE PLAIN" client
response using the full-IDN e-mail domain. If Dovecot is rejecting
this, then this is an issue with the authentication and/or
configuration on the Dovecot side. Are you sure the underlying
authentication backend in Dovecot can handle these IDN names?
C: 4 LOGIN info@bo?teauxlettres.net [PASSWORD]
info@bo?teauxlettres.netC: correctpassword
Slow Command: 6,007 seconds
S: 4 NO [AUTHENTICATIONFAILED] Authentication failed.
This is actually incorrect behavior on Horde_Imap_Client's part.
LOGIN supports ASCII strings only. We should catch this in
Horde_Imap_Client so that we don't waste a server round-trip, and the
corresponding wait time for the server to reject auth, when we know it
can never be successful (it's still going to throw an error - it's
just going to happen much faster).
michael
--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org
