That's what $mime_drivers['horde']['default']['icons'] is for.  Just 
put the various MS word MIME types in there (i.e. 
'application/vnd.ms-word' => 'msword.png') to get the desired icons 
while still using the default viewer.

If you comment out the msword, etc entries from 
$mime_drivers_map['horde']['registered'], you get a generic icon and 
are only offered the download link.



I can see situations where people might want to have the "word" icon 
be displayed for word attachments but not want to have a viewer 
registered.  There are several mime types that can invoke a server 
side viewer, and the default configuration assumes that they're all 
installed (or at leasted, they're all enabled in the conf files).  I 
think it would be a more reasonable stance that if the view's location 
isn't populated, that the user sees the mime-type specific icon 
(rather than the generic icon) and is only offered the download link.

You have to comment out all lines that begin with 
$mime_drivers['horde']['msword'], etc.  Simply commenting out the 
'location' entry is not enough.  This is because the 'msword' viewer 
is still registered to the MSWord MIME types so it is still attempting 
to use the msword MIME_Viewer driver.  If you would rather have MSWord 
(etc.) types be downloaded only (i.e. viewed using the default 
viewer), then you should only need to remove the 'msword', 'msexcel', 
etc. entries from the $mime_drivers_map['horde']['registered'] array.

This is sort of related to..



http://bugs.horde.org/ticket/?id=1847



I've commented out..



//$mime_drivers['horde']['msword']['location'] = '/usr/bin/wvHtml';

//$mime_drivers['horde']['msexcel']['location'] = '/usr/local/bin/xlhtml';

//$mime_drivers['horde']['mspowerpoint']['location'] = 
'/usr/local/bin/ppthtml';



IMP is still making



           2          sample.doc          [application/msword]          44 KB          Download



"sample.doc" a link, and when follow it, it reports:



     The program used to view this data type () was not found on the system.



In ticket 1847, it sounded like if a mime_driver definition didn't 
have a valid ['location'] defined, then it wouldn't create the file 
name link, forcing the user to follow the download link if they wanted 
to retrieve the attachment.



This is with Horde 3.0.4, though I've seen the same behavior with 3.0.3



Liam