From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs99733ebc; Thu, 4 Feb 2010 00:11:43 -0800 (PST) Received: by 10.224.123.196 with SMTP id q4mr764622qar.117.1265271102218; Thu, 04 Feb 2010 00:11:42 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 7si6039694qwb.52.2010.02.04.00.11.41; Thu, 04 Feb 2010 00:11:42 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 888B418582F6; Thu, 4 Feb 2010 03:11:41 -0500 (EST) Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168]) by rubyforge.org (Postfix) with ESMTP id 6551D18582C3 for ; Thu, 4 Feb 2010 03:07:42 -0500 (EST) Received: by kuovi.tilus.net (Postfix, from userid 1000) id CCDF36011; Thu, 4 Feb 2010 10:07:41 +0200 (EET) From: Tero Tilus To: Sup users Date: Thu, 04 Feb 2010 10:07:41 +0200 Message-Id: <1265270433-sup-3334@tilus.net> User-Agent: Sup/git Subject: [sup-talk] Fixing broken attachment mimetypes X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org I occasionally receive RTF-documents marked as application/msword which misguides sup to (based on mailcap) launch wrong viewer. How do I fix the mimetype (after the mail has been indexed)? Mutt could edit attachment mimetype. How would I go about implementing the same to sup? Or would there be a more general feature that would solve this problem? Obviously this kind of edits would not persist over index rebuilds. -- Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk