From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Dave Korn <dave.korn.cygwin@googlemail.com>
Cc: Thread TITTTL'd <cygwin-talk@cygwin.com>
Subject: Re: [OT] Re: Problem [1.7]: gzip missing in brand new install
Date: Sat, 14 Nov 2009 13:47:00 -0000 [thread overview]
Message-ID: <4AFEB876.2060709@gmail.com> (raw)
In-Reply-To: <4AFEB49A.8030606@gmail.com>
Dave Korn wrote:
> Dave Korn wrote:
>> Dave Korn wrote:
>>> Dave Korn wrote:
>>>> Dave Korn wrote:
>>>>> Meow.
>>>> Meow.
>>> Meow.
>> Meow.
> Meow.
Meow.
> Ta-daaa indeed, but it occurs to me I can probably even remove the
> mail.file_attach_binary setting now that I've not got a bogus mime type being
> specified. Let's see:
>
> http://cygwin.com/ml/cygwin-talk/2009-q4/msg00036.html
Ok, that worked. Here's the recipe, for Eric, and Fergus, and The Record:
#1. Set mail.content_disposition_type to 1. Necessary to get the correct
Content-Disposition: header, but not sufficient.
#2. Get MIME types database under control. I used an extension called
MimeEDIT(*), but it only works on series 2 Tbird. OTOH the database is stored
in a plain-text xml format in a file called mimeTypes.rdf in your T'bird
profile directory, and it looks easy enough to manually edit. Whichever
method you choose, BACK IT UP FIRST!(**)
T'bird will select a mime Content-Type: header for your attachment based on
the fileExtension settings listed in here; in my case, the extension .out had
become associated with message/news somehow, and the archive displays
message/* attachments inline even if the content-disposition says not to.
Some sources recommend simply deleting mimeTypes.rdf wholesale, but I chose
just to tweak the content so that it now thinks .msg is the extension for
message/news. YMMV (Your Mimetypes.rdf May Vary), but as long as it's not
choosing a bogus mime type based on your file extension, you'll get a default
of text/plain, which the archive won't expand inline.
cheers,
DaveK
--
(*) - https://addons.mozilla.org/en-US/thunderbird/addon/4498
(**) - Just because something goes without saying, doesn't mean folk will
actually do it when the time comes. So I said it anyway. Not that that
generally makes a lot of difference ... :-)
prev parent reply other threads:[~2009-11-14 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AFE8BA6.8000505@bonhard.uklinux.net>
[not found] ` <4AFEA645.40508@gmail.com>
[not found] ` <4AFEA92A.6010801@gmail.com>
2009-11-14 12:56 ` Dave Korn
2009-11-14 13:11 ` Dave Korn
2009-11-14 13:19 ` Dave Korn
2009-11-14 13:26 ` Dave Korn
2009-11-14 13:31 ` Dave Korn
2009-11-14 13:35 ` Eric Blake
2009-11-14 13:47 ` Dave Korn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AFEB876.2060709@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).