Re: Mime type recognition when there's a space in filename
- To: mutt-users@xxxxxxxx
- Subject: Re: Mime type recognition when there's a space in filename
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Mon, 6 Aug 2007 09:57:25 -0500
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=0.5; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=received:date:from:to:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; q=dns/txt; s=default; bh=eHqURH17YT9OPB1iAklI0VttrM8=; b=dExAem4EjK4zvBNUTIyE6Rphv5MP5uGse8WUOD8E1CgiDggw1+KNQ9IwMA0bQfLXLofS1FOSYLx307MZheyu8R/ktj7T8EJgnBXn1Na0Hm+/rDqk2FASq9ZZvl1Gi2HL0iBhehBk8Mc2uni8u0jYk+3oN0ig3Sc8PySm8cwfu2o=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=bg7BWog9WGu5UcOy41TJnzpgidQiWaaRSmdjetW3gcJ4R0jUAFpYBdUP58viEJyGAWZm4AHABOvBKmhzhIn+G0N1YjsrVVTuORVo5az3qcfnlmbPIWCLdONHrstis1V8pnmhhhM2e+0GCeiYFNziCymCoBXiuSM+B7YktKY2CQ4=; h=Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:User-Agent;
- In-reply-to: <20070806143421.GA19465@xxxxxxxxxxxxxxxxxxxxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- References: <20070806143421.GA19465@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.13 (2006-08-11)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday, August 6 at 03:34 PM, quoth Jocelyn Etienne:
>I get a wrong filetype recognized in mutt attachments whenever
>there is a space in the filename. Files are always thought to be
>"octetstream" even for file types which get correctly recognized
>for attachement without space character in the filename.
>
>Any workaround for that...?
Works just fine for me. I use mutt 1.5.13, but I've never had that
problem, even back in 1.5.10 days.
Perhaps the filename isn't being encoded properly? When mutt sends an
attachment with a space in the filename, it ends up being encoded in
the email like this:
filename="foo bar.txt"
How is it being encoded in the emails where mutt is choking?
~Kyle
- --
It is only possible to live happily ever after on a day-to-day basis.
-- Margaret Bonnano
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFGtzbVBkIOoMqOI14RAgr1AJ43LY/4QqT7dFxwkvqvoPOUG2O7GwCglwLM
bf0Zmnoxv4B+m6BH/kkZOl8=
=VZux
-----END PGP SIGNATURE-----