<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>IMP does not recognize ICS attachments on CentOS/RHEL 6</title> 
  <pubDate>Thu, 09 Apr 2026 19:17:32 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/13164</link> 
  <atom:link rel="self" type="application/rss+xml" title="IMP does not recognize ICS attachments on CentOS/RHEL 6" href="https://bugs.horde.org/ticket/13164/rss" /> 
  <description>IMP does not recognize ICS attachments on CentOS/RHEL 6</description> 
 
   
   
  <item> 
   <title>attached invitation email was generated using open-xchange. </title> 
   <description>attached invitation email was generated using open-xchange. gmail / OX will recognize it, however horde will not on our system - will display HTML contents instead.

however, same email sent to a friend who is running horde on latest stable debian had no trouble viewing + accepting the invitation, so probably this is (besides the strange unicode mail encoding problem I reported earlier) another case of Horde vs RHEL 6 / php incompatibility?

Is there anything that could be done to improve this (other than waiting for CentOS 7? ;)

thanks,

   guenter
</description> 
   <pubDate>Tue, 06 May 2014 21:23:19 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13164#t83551</link> 
  </item> 
   
  <item> 
   <title>screenshot of RHEL 6 invitation display</title> 
   <description>screenshot of RHEL 6 invitation display</description> 
   <pubDate>Tue, 06 May 2014 21:24:30 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13164#t83552</link> 
  </item> 
   
  <item> 
   <title>screenshot of Debian invitation display
</title> 
   <description>screenshot of Debian invitation display
</description> 
   <pubDate>Tue, 06 May 2014 21:25:00 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13164#t83553</link> 
  </item> 
   
  <item> 
   <title>This seems to indicate that you simply don&#039;t have IMP config</title> 
   <description>This seems to indicate that you simply don&#039;t have IMP configured to handle itip data on your CentOS system.  It is instead displaying the previous alternative (the HTML part).

The Debian screenshot is of a system setup to handle itip (i.e. text/calendar) data.

text/calendar data has nothing to do with HTML (libxml2) parsing, so this is not the same issue as #13122.</description> 
   <pubDate>Tue, 06 May 2014 21:34:42 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13164#t83554</link> 
  </item> 
   
  <item> 
   <title>&gt; This seems to indicate that you simply don&#039;t have IMP conf</title> 
   <description>&gt; This seems to indicate that you simply don&#039;t have IMP configured to 
&gt; handle itip data on your CentOS system.  It is instead displaying the 
&gt; previous alternative (the HTML part).
&gt;
&gt; The Debian screenshot is of a system setup to handle itip (i.e. 
&gt; text/calendar) data.
&gt;
&gt; text/calendar data has nothing to do with HTML (libxml2) parsing, so 
&gt; this is not the same issue as #13122.

good.

however, how would I configure that? would that be in

/var/www/horde/imp/config/mime_drivers.php ?

that file is untouched, i.e.


    /* ITIP (iCalendar Transport-Independent Interoperability Protocol)
     * display. */
    &#039;itip&#039; =&gt; array(
        &#039;inline&#039; =&gt; true,
        &#039;handles&#039; =&gt; array(
            &#039;text/calendar&#039;,
            &#039;text/x-vcalendar&#039;
        ),
        &#039;icons&#039; =&gt; array(
            &#039;default&#039; =&gt; &#039;itip.png&#039;
        ),

        /* How event replies are handled when a user opens the message.
         *   - false: Reply status is never automatically updated; requires
         *            explicit action by the user.
         *   - true: Reply status is always automatically updated.
         *   - Array: An array of domains for which replies are always
         *            automatically updated. All other domains require the
         *            reply status to be explicitly updated by user action. */
        &#039;auto_update_eventreply&#039; =&gt; false,

        /* How free/busy publish data is handled when a user opens the
         * message.
         *   - false: Free/busy data is never automatically updated; requires
         *            explicit action by the user.
         *   - true: Free/busy data is always automatically updated.
         *   - Array: An array of domains for which free/busy data is always
         *            automatically updated. All other domains require the
         *            free/busy data to be explicitly updated by user
         *            action. */
        &#039;auto_update_fbpublish&#039; =&gt; false,

        /* How free/busy replies are handled when a user opens the message.
         *   - false: Free/busy data is never automatically updated; requires
         *            explicit action by the user.
         *   - true: Free/busy data is always automatically updated.
         *   - Array: An array of domains for which free/busy data is always
         *            automatically updated. All other domains require the
         *            free/busy data to be explicitly updated by user
         *            action. */
        &#039;auto_update_fbreply&#039; =&gt; false
    ),




</description> 
   <pubDate>Tue, 06 May 2014 21:52:38 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13164#t83556</link> 
  </item> 
   
  <item> 
   <title>just to be sure:

[root@mail ~]# cat /var/www/horde/imp/co</title> 
   <description>just to be sure:

[root@mail ~]# cat /var/www/horde/imp/config/mime_drivers.local.php 
&lt;?php
$mime_drivers[&#039;html&#039;][&#039;inline&#039;] = true;
</description> 
   <pubDate>Tue, 06 May 2014 22:12:31 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13164#t83557</link> 
  </item> 
   
  <item> 
   <title>&gt; just to be sure:
&gt;
&gt; [root@mail ~]# cat /var/www/horde/i</title> 
   <description>&gt; just to be sure:
&gt;
&gt; [root@mail ~]# cat /var/www/horde/imp/config/mime_drivers.local.php
&gt; &lt;?php
&gt; $mime_drivers[&#039;html&#039;][&#039;inline&#039;] = true;

This is irrelevant for displaying the calendar data.

$mime_drivers[&#039;itip&#039;][&#039;inline&#039;] = true;

is the line that needs to be in there (although it shouldn&#039;t be needed since itip parts should be displayed inline by default).

I can verify that the sample message attached displays the itip data on my installation.
</description> 
   <pubDate>Wed, 07 May 2014 20:58:37 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13164#t83568</link> 
  </item> 
   
  <item> 
   <title>Verified that this works fine on a CentOS 6.5 server with fr</title> 
   <description>Verified that this works fine on a CentOS 6.5 server with freshly installed horde-webmail 5.1.6.</description> 
   <pubDate>Thu, 08 May 2014 00:52:01 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13164#t83571</link> 
  </item> 
   
  <item> 
   <title>Same thing here. ics files are not shown when received in an</title> 
   <description>Same thing here. ics files are not shown when received in an e-mail. But if I reply to the e-mail, now the ics is displayed correctly. 

Attached you will find 2 images showing this. Everything else works fineas far as tested, in horde, IMP and kronolith.

 On the same Centos i have a working installation of (horde) 3.3.10, IMP H3 (4.3.10) and (kronolith) H3 (2.3.4) . There are no problems with ICS files in that installation.

Horde 6 installation was made via PEAR. There are no errors in log


/etc/redhat-release
CentOS release 6.5 (Final)
</description> 
   <pubDate>Thu, 11 Sep 2014 00:38:14 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13164#t85706</link> 
  </item> 
   
  <item> 
   <title>The other image</title> 
   <description>The other image</description> 
   <pubDate>Thu, 11 Sep 2014 00:38:58 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13164#t85707</link> 
  </item> 
   
  <item> 
   <title>Someone who is experiencing this has to track down the under</title> 
   <description>Someone who is experiencing this has to track down the underlying cause.

As mentioned previously, I installed CentOS 6.5 and could not reproduce on a default setup so there&#039;s nothing more us developers can do to track this down.</description> 
   <pubDate>Thu, 11 Sep 2014 01:13:41 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13164#t85708</link> 
  </item> 
   
  <item> 
   <title>Michael:

Thanks for your answer. I really want to solve t</title> 
   <description>Michael:

Thanks for your answer. I really want to solve this. 

Can you tell me the php and PEAR versionsyou had in the working centos installation?

Thanks again.

Ivan

&gt; Someone who is experiencing this has to track down the underlying cause.
&gt;
&gt; As mentioned previously, I installed CentOS 6.5 and could not 
&gt; reproduce on a default setup so there&#039;s nothing more us developers 
&gt; can do to track this down.
</description> 
   <pubDate>Thu, 11 Sep 2014 01:25:01 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13164#t85709</link> 
  </item> 
   
  <item> 
   <title>&gt; Can you tell me the php and PEAR versionsyou had in the wo</title> 
   <description>&gt; Can you tell me the php and PEAR versionsyou had in the working 
&gt; centos installation?

[root@centos ~]# php --version
PHP 5.3.3 (cli) (built: Aug  6 2014 05:54:27)
Copyright (c) 1997-2010 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies

PEAR version is irrelevant.  It is a package manager and has nothing to do with display code.</description> 
   <pubDate>Fri, 12 Sep 2014 16:38:03 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13164#t85719</link> 
  </item> 
   
  <item> 
   <title>I have exactly the same versions. Dont know what else could </title> 
   <description>I have exactly the same versions. Dont know what else could be.

&gt;&gt; Can you tell me the php and PEAR versionsyou had in the working
&gt;&gt; centos installation?
&gt;
&gt; [root@centos ~]# php --version
&gt; PHP 5.3.3 (cli) (built: Aug  6 2014 05:54:27)
&gt; Copyright (c) 1997-2010 The PHP Group
&gt; Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies
&gt;
&gt; PEAR version is irrelevant.  It is a package manager and has nothing 
&gt; to do with display code.
</description> 
   <pubDate>Tue, 16 Sep 2014 02:27:33 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13164#t85751</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
