[horde] Unclear error message - any hints?

[Jan Schneider]

Zitat von Michael J Rubinsky <mrubinsk at horde.org>:

> Quoting Jan Schneider <jan at horde.org>:
>
>> Zitat von Michael J Rubinsky <mrubinsk at horde.org>:
>>
>>> Quoting Oscar del Rio <delrio at mie.utoronto.ca>:
>>>
>>>> On 06/13/17 11:23 AM, Jens-U. Mozdzen wrote:
>>>>> I have three "external accounts" in my Horde webmail interface,  
>>>>> one of them generates an "interesting" error message.
>>>>>
>>>>> I have logged in to that account via Horde (as well as to the  
>>>>> other two) and see the corresponding "inbox" folder in the  
>>>>> navigation tree on the left of the IMP window. When clicking  
>>>>> that folder entry, the folder is opened in the right pane and I  
>>>>> see a red popup stating "contains hyphen at position three and  
>>>>> four" (original message is German: "Enthält Bindestrich an der  
>>>>> dritten und vierten Stelle"). Horde's log does not list any  
>>>>> messages when this happens.
>>>>>
>>>>> Any idea what component might be delivering that error message - and why?
>>>>>
>>>>
>>>> Source code:
>>>> https://github.com/horde/horde/blob/master/framework/Idna/locale/de/LC_MESSAGES/Horde_Idna.po#L32
>>>> #: lib/Horde/Idna.php:63
>>>> msgid "Contains hyphen in the third and fourth positions"
>>>> msgstr "Enthält Bindestrich an der dritten und vierten Stelle"
>>>>
>>>> https://github.com/horde/horde/blob/master/framework/Idna/lib/Horde/Idna.php#L82
>>>> * Checks if the $idna_info parameter of idn_to_ascii() or idn_to_utf8()
>>>> * contains errors.
>>>>
>>>> https://tools.ietf.org/html/rfc5891#section-4.2.3.1
>>>> 4.2.3.1. Hyphen Restrictions
>>>> The Unicode string MUST NOT contain "--" (two consecutive hyphens) in
>>>> the third and fourth character positions and MUST NOT start or end
>>>> with a "-" (hyphen).
>>>
>>> Exactly. One or more of the email addresses in the affected  
>>> mailbox contains a domain that contains hyphens in the 3rd and 4th  
>>> character positions.
>>
>> Though this should not keep the mailbox from getting loaded, and  
>> IIRC we fixed such an issue not long ago.
>
> This is what I was thinking of:
>
> https://github.com/horde/horde/commit/a0449e5a14e0766f7f427c7e335a1a5322bc4252
>
> It fixed the same issue, but not in the same place. Same root cause,  
> we are now throwing exceptions we were not throwing before, and some  
> of the libraries higher in the call chain leak the exception (which  
> can't currently be changed for BC reasons, since there is code in  
> IMP that relies on this).

I cannot reproduce this with the latest Horde/IMP release though.

-- 
Jan Schneider
The Horde Project
https://www.horde.org/