On Wed, Feb 09, 2011 at 08:26:03PM +, Chris G wrote:
On Wed, Feb 09, 2011 at 01:49:33PM -0500, Ed Blackman wrote:
You can tell Mutt to use RFC2047 decoding on MIME file names with
set rfc2047_parameters=yes
Would that be in addition to the 'normal' decoding which works with most
attachme
On Wed, Feb 09, 2011 at 01:49:33PM -0500, Ed Blackman wrote:
> On Wed, Feb 09, 2011 at 11:06:52AM +, Chris G wrote:
> >I had something *vaguely* similar yesterday, a supplier sent me a note
> >about an order I had placed and it was:-
> >
> > [-- application/octet-stream is unsupported (use 'v
On Wed, Feb 09, 2011 at 11:06:52AM +, Chris G wrote:
I had something *vaguely* similar yesterday, a supplier sent me a note
about an order I had placed and it was:-
[-- application/octet-stream is unsupported (use 'v' to view this part) --]
... which is OK[ish], but the file name was:-
On Wed, Feb 09, 2011 at 09:04:34AM +0100, Jan-Herbert Damm wrote:
> hello all,
>
> please skip this mail and excuse the noise if you hate slightly OT posts.
>
> I recently got attachments which were really pdfs but couldn't be detected as
> such because they had strange content-type names:
>
> a
hello all,
please skip this mail and excuse the noise if you hate slightly OT posts.
I recently got attachments which were really pdfs but couldn't be detected as
such because they had strange content-type names:
application/x-coremedia-dynamic
application/force-download
I wrote .mailcap-entrie
