[horde] sent mails are not saved in sent-mail

[Lukas Gradl]

Am 2012-11-21 13:27, schrieb Jan Schneider:
>
> Zitat von Jens Grüntjes <jens.gruentjes at ebira.de>:
>
>> Zitat von steffo76 at gmx.de:
>>
>>> -------- Original-Nachricht --------
>>>> Datum: Wed, 21 Nov 2012 09:09:01 +0000
>>>> Von: "Jens Grüntjes" <jens.gruentjes at ebira.de>
>>>> An: horde at lists.horde.org
>>>> Betreff: Re: [horde] sent mails are not saved in sent-mail
>>>
>>>> Zitat von steffo76 at gmx.de:
>>>>
>>>>> -------- Original-Nachricht --------
>>>>>> Datum: Wed, 21 Nov 2012 07:55:01 +0000
>>>>>> Von: "Jens Grüntjes" <jens.gruentjes at ebira.de>
>>>>>> An: horde at lists.horde.org
>>>>>> Betreff: Re: [horde] sent mails are not saved in sent-mail
>>>>>
>>>>>> Zitat von Michael M Slusarz <slusarz at horde.org>:
>>>>>>
>>>>>> > Quoting Jens Grüntjes <jens.gruentjes at ebira.de>:
>>>>>> >
>>>>>> >> Hello list,
>>>>>> >>
>>>>>> >> after running a pear upgrade yesterday a couple of Horde_*
>>>>>> packages
>>>>>> >> were upgraded.
>>>>>> >>
>>>>>> >> After those upgrades I encounter an error every time I send mail a
>>>>>> >> mail saying "Message sent successfully, but not saved to
>>>>>> >> sent-mail". The horde-log shows
>>>>>> >>
>>>>>> >> 2012-11-21T07:14:12+00:00 INFO: HORDE [imp] 192.168.0.160 Message
>>>>>> >> sent to Jens Gruentjes <jens.gruentjes at provider.de> from jens [pid
>>>>>> >> 31751 on line 866 of "/var/www/horde/imp/lib/Compose.php"]
>>>>>> >> 2012-11-21T07:14:12+00:00 ERR: HORDE [imp] Der E-Mail-Server
>>>>>> konnte
>>>>>> >> den Inhalt der Nachricht nicht auswerten. Can not process the
>>>>>> >> binary data [pid 31751 on line 382 of
>>>>>> >> "/var/www/horde/imp/lib/Imap.php"]
>>>>>> >>
>>>>>> >> The error message "Can not process the binary data" seems to be an
>>>>>> >> error code from the cyrus mail server we're running.
>>>>>> >>
>>>>>> >> I tried sendign with and without signature, with empty mail-body,
>>>>>> >> with text, but no difference. Saving sent messages always worked
>>>>>> >> but seems to be broken after the upgrades from yesterday.
>>>>>> >> Unfortunately I don't have the output from the pear upgrade
>>>>>> command.
>>>>>> >>
>>>>>> >> Can someone help me out?
>>>>>> >
>>>>>> > Sounds like your IMAP server is broken.  An IMAP log is needed to
>>>>>> > confirm this.
>>>>>> >
>>>>>> Yesterday I only upgraded horde packages and there were no changes on
>>>>>> the IMAP server. I rather thought something in the upgrades was
>>>>>> broken.
>>>>>>
>>>>>> I'm using Debian squeeze and cyrus-imapd-2.2 Version:
>>>> 2.2.13-19+squeeze3
>>>>>>
>>>>>> Here is a line from my cyrus-log when I send a mail through imp
>>>>>> Nov 21 08:50:45 boromir in.imapproxyd[2114]: cmd_logout: IMAP_Write()
>>>>>> to client failed on sd [7]: Broken pipe
>>>>>>
>>>>>> I found furthermore a lot of lines like the following but those
>>>>>> messages already occurred before I upgraded yesterday:
>>>>>> Nov 21 08:50:04 boromir in.imapproxyd[2114]: IMAP_Line_Read():
>>>>>> connection closed prematurely.
>>>>>
>>>>> I'm not sure if 2.2 supports this but could you try to turn on
>>>>> telemetry logging in cyrus ? Basically you just create a directory
>>>>> which has the name of the user you are testing this with and make it
>>>>> writeable for the uid cyrus runs under:
>>>>>
>>>>> http://wiki.kolab.org/index.php/Cyrus_imap_telemetry_logging
>>>>>
>>>> Telemetry logging is turned on but it creates quite big log files. I
>>>> *think* that this is the interesting part, but if you say I should
>>>> better post the whole log file, I will do so.
>>>>
>>>> <snip>
>>>>
>>>> <1353488808<6 STATUS "user.eug" (RECENT)
>>>>> 1353488808>* STATUS user.eug (RECENT 0)
>>>> 6 OK Completed
>>>> <1353488808<C64 UNSELECT
>>>>> 1353488808>C64 BAD Please select a mailbox first
>>>> <1353488817<2 APPEND "INBOX.sent-mail" (\seen) ~{577+}
>>>>> 1353488817>2 NO [UNKNOWN-CTE] Can not process the binary data
>>>
>>> This is a problem in cyrus. I have no idea if this is the same
>>> problem as in 2.4.16 but apparently changes in the imap_client
>>> library in horde hit a but in cyrus. According to the cyrus people
>>> this will be fixed soon in 2.4.17. I have no idea about the debian
>>> 2.2 packages. Maybe it is possible to downgrade the imap_client
>>> library until cyrus gets fixed to get things up and running ?
>>
>> I don't hope that the Debian-package of cyrus gets fixed soon. So I
>> think the only way is to downgrade the horde packages. Can you please
>> tell me which package exactly has to be downgraded?
>>
>> If I downgrade that means that I should no longer use pear upgrade
>> until either the Debian package is fixed or the horde library no
>> longer triggers the particular bug in cyrus?
>> --
>> Viele Grüße
>> Jens
>
> We're discussing this on the dev mailing list, hopefully we can work
> around this bug in Cyrus, since I don't expect this bug fix to land in
> any distribution soon.

Are there any news on that topic? It's a total showstopper.

Unfortunatly changing the cyrus-server is not an option as it works for 
over 500 users with different clients and can't be touched for a handful 
of horde-users on that installation....

It worked with the first horde5/imp6 stable packages - is there a chance 
to downgrade the installation?

regards
Lukas