From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/62003 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.gnus.general Subject: Re: Removing ignore-errors in mm-dissect-buffer Date: Thu, 16 Feb 2006 08:38:37 +0900 Organization: Emacsen advocacy group Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1140047062 12022 80.91.229.2 (15 Feb 2006 23:44:22 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 15 Feb 2006 23:44:22 +0000 (UTC) Original-X-From: ding-owner+m10531@lists.math.uh.edu Thu Feb 16 00:44:18 2006 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F9WJj-0003Om-Ch for ding-account@gmane.org; Thu, 16 Feb 2006 00:44:17 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu ident=lists) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1F9WJf-00061h-00; Wed, 15 Feb 2006 17:44:11 -0600 Original-Received: from nas02.math.uh.edu ([129.7.128.40]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1F9WEy-00061b-00 for ding@lists.math.uh.edu; Wed, 15 Feb 2006 17:39:20 -0600 Original-Received: from quimby.gnus.org ([80.91.224.244]) by nas02.math.uh.edu with esmtp (Exim 4.52) id 1F9WEt-000317-FF for ding@lists.math.uh.edu; Wed, 15 Feb 2006 17:39:19 -0600 Original-Received: from minsk.hostforweb.net ([66.225.201.21]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1F9WEs-0006Xj-00 for ; Thu, 16 Feb 2006 00:39:14 +0100 Original-Received: from [205.234.212.150] (helo=mail.yamaoka.cc) by minsk.hostforweb.net with esmtpa (Exim 4.52) id 1F9WEj-0008KW-Qw for ding@gnus.org; Wed, 15 Feb 2006 17:39:11 -0600 Original-To: ding@gnus.org X-Face: #kKnN,xUnmKia.'[pp`;Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu;B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) Cancel-Lock: sha1:tMPj7+6bsLT0bEsIfeHY635K3ns= X-Hashcash: 1:20:060215:ding@gnus.org::7gMLpyLPg+SMS/d0:0000183h X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - minsk.hostforweb.net X-AntiAbuse: Original Domain - gnus.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jpl.org X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: -2.5 (--) Precedence: bulk Original-Sender: ding-owner@lists.math.uh.edu Xref: news.gmane.org gmane.emacs.gnus.general:62003 Archived-At: >>>>> In Reiner Steib wrote: > Gnus errors out with "forward-sexp: Scan error: "Unbalanced > parentheses", 21, 32" when displaying the following spam article: I see. Though the article seems to have been cancelled. [...] > The culprit is the string =ABcharset=3D\"us-ascii\"=BB in the first MIME > part which might be invalid: > ,---- >| --fc55ff24ae7d5dde3b9cddf90cbc0f08 >| Content-Type: text/html; charset=3D\"us-ascii\" >| MIME-Version: 1.0 >| Content-Transfer-Encoding: quoted-printable > `---- > But Gnus should render the article despite of the broken charset > declaration, I think. Yes, I think so. The change I made aimed to cope with Thunderbird 1.5 which generates wrong name and filename parameters for an attachment of a long non-ASCII file name[1]. In such a case, now at least type/subtype will be extracted. > To reproduce (even from =ABemacs -Q=BB), eval the following code: > (require 'mail-parse) > (with-temp-buffer > (insert "Content-Type: text/html; charset=3D\\\"us-ascii\\\" > MIME-Version: 1.0 > Content-Transfer-Encoding: quoted-printable") > (setq ct (mail-fetch-field "content-type") > ctl (and ct (mail-header-parse-content-type ct)))) > Reverting mm-decode.el to revision 7.37 fixed the problem: [...] > If reverting the following changes is not the right thing, could you > suggest a better approach, Katsumi? I think mail-header-parse-content-type should never cause erros and it should extract at least type/subtype if it is possible. I will make an effort so that it might do so. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=3D323318