[imp] UNable to auth IDN in IMP - sanitized log data inline, full sanitized log attached

2014-08-12 Thread info


There's not much in the log:



Tue, 12 Aug 2014 13:15:50 +
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.

C: 4 LOGIN info@boîteauxlettres.net [PASSWORD]
info@boîteauxlettres.netC:  correctpassword

Slow Command: 6,007 seconds

S: 4 NO [AUTHENTICATIONFAILED] Authentication failed.

Command 4 took 6,0089 seconds.



the above repeats a half-dozen times.

Thanks for your help debugging this.

Ed
--
>> Tue, 12 Aug 2014 13:15:50 +
>> 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.
C: 4 LOGIN info@boîteauxlettres.net [PASSWORD]
info@boîteauxlettres.netC:  correctpassword
>> Slow Command: 6,007 seconds
S: 4 NO [AUTHENTICATIONFAILED] Authentication failed.
>> Command 4 took 6,0089 seconds.
C: 5 AUTHENTICATE PLAIN [INITIAL CLIENT RESPONSE (username: 
info@boîteauxlettres.net)]
>> Slow Command: 10,007 seconds
S: 5 NO [AUTHENTICATIONFAILED] Authentication failed.
>> Command 5 took 10,0071 seconds.
C: 6 LOGIN info@boîteauxlettres.net [PASSWORD]
info@boîteauxlettres.netC:  correctpassword
>> Slow Command: 17,017 seconds
S: 6 NO [AUTHENTICATIONFAILED] Authentication failed.
>> Command 6 took 17,0188 seconds.
C: 7 AUTHENTICATE PLAIN [INITIAL CLIENT RESPONSE (username: 
info@boîteauxlettres.net)]
>> Slow Command: 17,019 seconds
S: 7 NO [AUTHENTICATIONFAILED] Authentication failed.
>> Command 7 took 17,0192 seconds.
C: 8 LOGIN info@boîteauxlettres.net [PASSWORD]
info@boîteauxlettres.netC:  correctpassword
>> Slow Command: 17,017 seconds
S: 8 NO [AUTHENTICATIONFAILED] Authentication failed.
>> Command 8 took 17,0189 seconds.
C: 9 AUTHENTICATE PLAIN [INITIAL CLIENT RESPONSE (username: 
info@boîteauxlettres.net)]
>> Slow Command: 17,016 seconds
S: 9 NO [AUTHENTICATIONFAILED] Authentication failed.
>> Command 9 took 17,0161 seconds.
C: 10 LOGIN info@boîteauxlettres.net [PASSWORD]
info@boîteauxlettres.netC:  correctpassword
>> Slow Command: 17,018 seconds
S: 10 NO [AUTHENTICATIONFAILED] Authentication failed.
>> Command 10 took 17,02 seconds.
-- 
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org

Re: [imp] Removing "whitelist" and "blacklist" menu items

2014-08-12 Thread Brett Charbeneau
Michael Slusarz [slusarz  horde.org]: This is the correct  
way of disabling (except changes should be made in   
registry.local.php).



I'm grateful for the response! And please excuse my ignorance of PHP...
I've added

$_prefs['blacklist']['Locked'] = true;
$_prefs['whitelist']['Locked'] = true;

to registry.local.php, and it does seem to disable them for the  
user, but the preference would be to have this menu item not appear at  
all.
I tried additionally adding the chunk of code below as well, but  
I keep getting syntax errors - is this the correct approach to remove  
the "Blacklist" and "Whitelist" links from all menus?


   'ingo' => array(
'name' => _("Filters"),
'provides' => array(
'filter',
'mail/applyFilters',
'mail/canApplyFilters',
'mail/showFilters'
),
'menu_parent' => 'imp'
),


--

Brett Charbeneau
Network Administrator
Williamsburg Regional Library
7770 Croaker Road
Williamsburg, VA 23188-7064
(757)259-4044  www.wrl.org
(757)259-4079 (fax)br...@wrl.org



--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org


Re: [imp] Removing "whitelist" and "blacklist" menu items

2014-08-12 Thread Michael M Slusarz

Quoting Brett Charbeneau :

Michael Slusarz [slusarz  horde.org]: This is the correct  
way of disabling (except changes should be made in   
registry.local.php).



I'm grateful for the response! And please excuse my ignorance of PHP...
I've added

$_prefs['blacklist']['Locked'] = true;
$_prefs['whitelist']['Locked'] = true;

to registry.local.php, and it does seem to disable them for the  
user, but the preference would be to have this menu item not appear  
at all.
I tried additionally adding the chunk of code below as well, but  
I keep getting syntax errors - is this the correct approach to  
remove the "Blacklist" and "Whitelist" links from all menus?


   'ingo' => array(
'name' => _("Filters"),
'provides' => array(
'filter',
'mail/applyFilters',
'mail/canApplyFilters',
'mail/showFilters'
),
'menu_parent' => 'imp'
),


In registry.local.php, this will remove blacklist and whitelist and  
ensure that any additions to 'provides' in the future is automatically  
added without further admin intervention:


$this->applications['ingo']['provides'] = array_diff(
$this->applications['ingo']['provides'],
array(
'mail/blacklistFrom',
'mail/showBlacklist',
'mail/whitelistFrom',
'mail/showWhitelist'
)
);

Unfortunately, the 'provides' parameter isn't as clean to work via  
registry.local.php since it only contains hash values and no defined  
hash keys, so the PHP needs to be a bit more advanced (this is a  
historical remnant since this is the way registry.php was before we  
switched to *.local.php files).


michael

___
Michael Slusarz [slus...@horde.org]

--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org


Re: [imp] UNable to auth IDN in IMP - sanitized log data inline, full sanitized log attached

2014-08-12 Thread Michael M Slusarz

Quoting i...@interpost.biz:


There's not much in the log:



Tue, 12 Aug 2014 13:15:50 +
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

___
Michael Slusarz [slus...@horde.org]

--
imp mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: imp-unsubscr...@lists.horde.org