Tickets :: Comment on [#3565] Attachment modification (newline structure changes)

* Your Email Address
* Spam protection	Enter the letters below: .___.. ,. ..__ . , \| \./ \ /[__) \./ \| \| \/ [__) \|
Comment	> I finally had time to do a little bit research about the problem. > There are two parts about this. > > > > 1. If user has't for example Office application installed and tries > to send document attachment it gets sent as text/plain. This is > normal because browser doesn't know file type and sends > application/octet-stream. IE6, IE7, FF1.5 and FF2 behaves exactly > this way. Only Opera 9.1 has builtin MIME detection for my tested > Word Document Type. This means that you can't rely on user client/OS. > > > > 2. If you can't rely on user client/OS configuration then it means > that your server must be presicly configured to give Horde the right > mime type. However I tested 3 different installations of Fedora Core > 5, RedHat Enterprise 4 and RedHat Enterprise 5 beta 2. None of them > detected correct mime type with default installation. Even with > fileinfo PECL module installed they still reported text/plain. And > with only some hacking through config files I found this -> > http://mail-archives.apache.org/mod_mbox/httpd-cvs/199807.mbox/%3C19980718113554.10097.qmail@hyperreal.org%3E Seems like most of the office documents was dissabled by default in vanilla apache since 1998! This means that very large base of UNIX type OS'es that uses vanilla apache is affected by the problem most probably > too. > > > > Now back to the point. I know that it is faster to send plain text > attachments and plain text, and wiser used space way, and I agree > with you that having possibility to read those attachments in console > programs is good. BUT, for the sake of large user base without office > installed and for the sake of large admin base with vanilla apache > configuration, PLEASE revert IMP to encode all text/plain attachments > with base64 again.
Attachment
Watch this ticket

Saved Queries