[Tickets #13164] Re: IMP does not recognize ICS attachments on CentOS/RHEL 6

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13164
------------------------------------------------------------------------------
  Ticket             | 13164
  Updated By         | guenter.bartsch at sl-rasch.de
  Summary            | IMP does not recognize ICS attachments on CentOS/RHEL 6
  Queue              | IMP
  Version            | 6.1.7
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


guenter.bartsch at sl-rasch.de (2014-05-06 21:52) wrote:

> This seems to indicate that you simply don'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.

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. */
     'itip' => array(
         'inline' => true,
         'handles' => array(
             'text/calendar',
             'text/x-vcalendar'
         ),
         'icons' => array(
             'default' => 'itip.png'
         ),

         /* 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. */
         'auto_update_eventreply' => 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. */
         'auto_update_fbpublish' => 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. */
         'auto_update_fbreply' => false
     ),