Actually, I beleive some of the latest Microsoft clients may actually
use correct MIME-types (I could be wrong though).
This is a dodge by microsoft so that proper mime tools STILL can't
recognize their files, even when it is a standard format rather than
some proprietary MS stuff. The use the 'extension' to determine what
the file is. Of course it works in an MS-to-MS environment, so if you
can't interpret in in your non-MS product, it must be the non-MS
system's fault..
Its appalling how far out of their way they will go to not be
interoperable with non-MS systems. (And if you think it isn't
intentional, then the only other explanation is ignorance and
inability to understand RFC text)
On Fri, 22 Dec 2000, Jeffrey Goldberg wrote:
> On Fri, 22 Dec 2000, Dan Lowe wrote:
>
> > Small point, but I know Philip isn't a Windows user.
> >
> > The Content-type: would contain the MIME type such as:
> >
> > application/msword
> > application/vnd.ms-excel
> > text/plain
>
> As a Unix user who gets a lot of mail from Windows users, I think I
> disagree. The content-type in those cases is almost always
>
> application/octet-stream
>
> -j
>
--
