And this is correct.  This is a gzip'd file.  How can 'file' know what 
is inside the file without uncompressing it?  'file' simply guess what 
kind of data is in the file.
The browser/OS.
Technically, there is nothing wrong with application/x-gzip.  Because 
that is exactly what the file is.  On OS's like windows, there can 
only be a single extension.  So the MIME type 'application/x-gzip' is 
correct.  I realize Thunderbird is sending something different, but I 
don't necessarily agree with what they are doing (x-compressed-tar 
does not seem to be used by many people.).



So I think the previous analysis in this ticket remains.

Should have done the same test on the ".tgz" file in the previous 
post, but here it is:



# file archive.tgz

archive.tgz: gzip compressed data, from Unix, last modified: Mon Dec   
8 11:28:54 2008



Not much of a difference. So where is the MIME type sent to HORDE/IMP 
coming from?



For a ".tgz", IMP receives "application/x-gtar" and for a ".tar.gz", 
it receives "application/x-gzip"



Can someone shed some light on this?

Silly me, I tested with a ".tgz" instead of a ".tar.gz". So the 
problem is still there, and the "file" command on Linux reports this 
for a ".tar.gz" file:



# file archive.tar.gz

archive.tar.gz: gzip compressed data, from Unix, last modified: Mon 
Dec  8 11:28:54 2008



So it's probably the right behavior. Can someone confirm?

Since I reported this, I re-installed my OS from scratch, and now I 
don't experience the MIME type discrepancy anymore. So it seems there 
was something mis-configured with the MIME types in my previous 
environment.



Thanks for this precision, Michael!

Is this what the browser is sending to Horde/IMP?  We use the MIME 
type information provided to us by the user's browser/OS.

More details for the problem when trying to view the content listing 
of a tar.gz file within IMP:



- a .tar.gz attachment sent using Horde/IMP has a MIME type of 
"application/x-gzip"

- a .tar.gz attachment sent using Thunderbird has a MIME type of 
"application/x-compressed-tar"



Which probably explain the problem (and is probably caused by a 
limitation in the MIME library, as Chuck already mentioned)

I tested again, and it really needs to be a compressed TAR  FILE, not 
just a compressed FILE.

OK, but I really meant "tar.gz" files, not just gzipped files.

No. Individual gzipped files are different from tar files.

So, are you saying the problem happens with Horde's MIME library WHEN 
UPLOADING the gzipped attachment? Otherwise, If you're saying it's 
only when OPENING the attachment, then it would not explain why this 
does not happen with an attachment in an email created OUTSIDE of Horde.

I can't reproduce this.
This is a limitation of the current MIME lib and can't be fixed until IMP 5.

Reproduce method:



- enable "$conf[compress_pages]" in horde config

- upload a gzip/bzip2 file in IMP compose window

- send that email to yourself

- open the email you just sent

- download the gzip/bzip2 file to local disk

- the file will be compressed TWICE



Also, independantly of the setting above, any uploaded .tgz (or .tbz) 
file cannot be

opened in IMP (gives error: "Content type of compressed file: Unknown")



If I receive an email that contains a .tgz/tbz file (and that email 
has not been created with IMP), the attached compressed tar file 
content can be read within IMP, which leads me to believe there is a 
link with the upload bug above.