From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/67453 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.gnus.general Subject: Re: message-idna problem Date: Fri, 26 Sep 2008 08:11:00 +0900 Organization: Emacsen advocacy group Message-ID: References: <87skronpc8.fsf@marauder.physik.uni-ulm.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1222384351 16108 80.91.229.12 (25 Sep 2008 23:12:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 25 Sep 2008 23:12:31 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M15903@lists.math.uh.edu Fri Sep 26 01:13:28 2008 connect(): Connection refused Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1Kj01R-0005Oq-5S for ding-account@gmane.org; Fri, 26 Sep 2008 01:13:21 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1Kizzu-0004GT-39; Thu, 25 Sep 2008 18:11:46 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1Kizzs-0004GG-VS for ding@lists.math.uh.edu; Thu, 25 Sep 2008 18:11:44 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1Kizzp-0003Kp-Ku for ding@lists.math.uh.edu; Thu, 25 Sep 2008 18:11:44 -0500 Original-Received: from orlando.hostforweb.net ([216.246.45.90]) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1Kizzu-0004qA-00 for ; Fri, 26 Sep 2008 01:11:46 +0200 Original-Received: from localhost ([127.0.0.1]:35749) by orlando.hostforweb.net with esmtpa (Exim 4.69) (envelope-from ) id 1KizzG-0005lW-MO for ding@gnus.org; Thu, 25 Sep 2008 18:11:07 -0500 X-Hashcash: 1:20:080925:ding@gnus.org::FqWk8kxgYyuqcd2Q:0000Enhc 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.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:UJCqDyimiBVYEYz8b9ZOQJmBVIU= X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - orlando.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.6 (--) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:67453 Archived-At: >>>>> Reiner Steib wrote: > On Thu, Sep 25 2008, Katsumi Yamaoka wrote: >> When I send a mail containing the From header like >> >> From: =E5=B1=B1=E5=B2=A1 =E5=85=8B=E7=BE=8E >> >> the *Messages* buffer collects the following warnings: >> >> Unknown symbol: =E5=B1=B1 >> Unknown symbol: =E5=B2=A1 >> Unknown symbol: =E5=85=8B >> Unknown symbol: =E7=BE=8E >> >> I've never noticed this since I rarely use Japanese names in the >> message header. It arises if `message-use-idna' is non-nil and >> there is a name of which the first letter is a non-ASCII character >> in the header. > I get "Unknown symbol: =C3=84" independent on the value of > `message-use-idna': ELISP> (let ((message-use-idna nil)) > (mail-header-parse-addresses "=C3=84pfel Birne = ")) > (("foo@bar.invalid" . "pfel Birne")) ELISP> (let ((message-use-idna t)) > (mail-header-parse-addresses "=C3=84pfel Birne = ")) > (("foo@bar.invalid" . "pfel Birne")) >> Those warnings are the ones that `ietf-drums-parse-addresses' >> (a.k.a. `mail-header-parse-addresses') that >> `message-idna-to-ascii-rhs-1' uses issues. Assuming there will >> potentially be non-ASCII names when `message-idna-to-ascii-rhs-1' >> runs, how about using `mail-extract-address-components' rather >> than an ietf-drums- function that does not support non-ASCII >> characters? This problem might not cause a real harm, though. > Fine with me. Thanks. I've modified `message-idna-to-ascii-rhs-1' so as to use `mail-extract-address-components' rather than `mail-header-parse-addresses'. Regards,