[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] whatnow: can't attach because no header field name was
From: |
Ronald F. Guilmette |
Subject: |
Re: [Nmh-workers] whatnow: can't attach because no header field name was given. |
Date: |
Thu, 15 Mar 2012 16:39:22 -0700 |
In message <address@hidden>,
Jon Steinhart <address@hidden> wrote:
>However, change seems to be in the wind. I would be perfectly happy to have
>this behavior become the default.
What behavior? Having attach set the proper MIME type, based on the
actual content of the file?
That would seem like a reasonable choice to me.
>Oh yeah, of course it tries to determine the correct MIME content type.
Apparently, yes. Conveying that into the Content-Type header would also
be Good, in my personal estimation.
- Re: [Nmh-workers] whatnow: can't attach because no header field name was given., Ronald F. Guilmette, 2012/03/15
- Re: [Nmh-workers] whatnow: can't attach because no header field name was given., Ronald F. Guilmette, 2012/03/15
- Re: [Nmh-workers] whatnow: can't attach because no header field name was given., Ronald F. Guilmette, 2012/03/15
- Re: [Nmh-workers] whatnow: can't attach because no header field name was given., Ronald F. Guilmette, 2012/03/15
- Re: [Nmh-workers] whatnow: can't attach because no header field name was given., Ken Hornstein, 2012/03/15
- Re: [Nmh-workers] whatnow: can't attach because no header field name was given., Ken Hornstein, 2012/03/15
- Re: [Nmh-workers] whatnow: can't attach because no header field name was given., Ken Hornstein, 2012/03/15
Re: [Nmh-workers] whatnow: can't attach because no header field name was given., Jon Steinhart, 2012/03/15