From owner-freebsd-questions Thu Feb 7 3:17:56 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mobil.cz (diana.mobil.cz [195.39.16.12]) by hub.freebsd.org (Postfix) with ESMTP id E523E37B405 for ; Thu, 7 Feb 2002 03:17:48 -0800 (PST) Received: from ester.mobil.cz (ester.mobil.cz [194.213.62.23]) by mobil.cz (8.11.6/8.11.0) with ESMTP id g17BHll30925 for ; Thu, 7 Feb 2002 12:17:47 +0100 Received: from roman.mobil.cz ([10.2.0.89]) by ester.mobil.cz (Lotus Domino Release 5.0.7) with ESMTP id 2002020712144385:1601 ; Thu, 7 Feb 2002 12:14:43 +0100 Received: (from roman@localhost) by roman.mobil.cz (8.11.6/8.11.6) id g17BT7E19337 for freebsd-questions@freebsd.org; Thu, 7 Feb 2002 12:29:07 +0100 (CET) (envelope-from neuhauser@mobil.cz) X-Authentication-Warning: roman.mobil.cz: roman set sender to neuhauser@mobil.cz using -f Date: Thu, 7 Feb 2002 12:29:07 +0100 From: Roman Neuhauser To: freebsd-questions@freebsd.org Subject: Re: Example mime.types, and mailcap for mutt? Message-ID: <20020207112907.GQ99518@roman.mobil.cz> Mail-Followup-To: freebsd-questions@freebsd.org References: <200202062138.XAA64050@sima.sita.kiev.ua> <20020206220159.EDCF95D0D@ptavv.es.net> Mime-Version: 1.0 In-Reply-To: <20020206220159.EDCF95D0D@ptavv.es.net> User-Agent: Mutt/1.3.26i X-MIMETrack: Itemize by SMTP Server on ester/Mobil(Release 5.0.7 |March 21, 2001) at 02/07/2002 12:14:43 PM, Serialize by Router on ester/Mobil(Release 5.0.7 |March 21, 2001) at 02/07/2002 12:14:49 PM, Serialize complete at 02/07/2002 12:14:49 PM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > To: ay@sita.kiev.ua > Cc: freebsd-questions@freebsd.org > Subject: Re: Example mime.types, and mailcap for mutt? > Date: Wed, 06 Feb 2002 14:01:59 -0800 > From: "Kevin Oberman" > > > Date: Wed, 6 Feb 2002 23:38:29 +0200 (EET) > > From: ay@sita.kiev.ua > > Sender: owner-freebsd-questions@FreeBSD.ORG > > > > It's all nice, but how to manage application/octet-stream ? > > I do often receive msword attachments, labeled as octet-stream. > > > > More : catdoc fails to show nsworld files with exocic charsets. > > If they are just labeled as "application/octet-stream", the sender > messed up. They should be "application/msword". I believe some > versions used a bogus application type for all Office documents, but > application/octet-stream is wrong as it only says that the file > contains undefined binary data. That answer is true, but doesn't help nevertheless. :) Handling mislabled attachments is quite high on my todo (= should get to it before the end of the year :), and the scenario is as follows (warning: this will most probably be expensive as hell, and I will prolly just go back to editing the MIME types of attachments in mutt): - have my MDA parse the MIME structure of incoming messages, looking for any application/octet-stream parts - determine the MIME type from the suffix of the attachment - rewrite the message -- FreeBSD 4.4-STABLE 12:18PM up 17 days, 18:41, 11 users, load averages: 1.00, 1.01, 0.94 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message