From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: Re: RMAIL doesn't always recognize rmail-mime-charset-pattern Date: Sun, 19 May 2002 16:27:11 +0300 (IDT) Sender: bug-gnu-emacs-admin@gnu.org Message-ID: References: <87y9egnv15.fsf@snail.pool> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: main.gmane.org 1021815002 29785 127.0.0.1 (19 May 2002 13:30:02 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 19 May 2002 13:30:02 +0000 (UTC) Cc: bug-gnu-emacs@gnu.org Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 179Ql7-0007ju-00 for ; Sun, 19 May 2002 15:30:01 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 179QlW-00064x-00; Sun, 19 May 2002 09:30:26 -0400 Original-Received: from is.elta.co.il ([199.203.121.2]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 179QkB-0005rs-00 for ; Sun, 19 May 2002 09:29:04 -0400 Original-Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id QAA19005; Sun, 19 May 2002 16:27:12 +0300 (IDT) X-Sender: eliz@is Original-To: David Kuehling In-Reply-To: <87y9egnv15.fsf@snail.pool> Errors-To: bug-gnu-emacs-admin@gnu.org X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.bugs:1450 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:1450 On 19 May 2002, David Kuehling wrote: > Today I made a copy of my inbox file, before using Emacs' pop3 mail > retrieval. The bug is now reproducable, when receiving that mail box > via pop3 (2nd mail in the mailbox file). But it won't occur, when I use > C-u g savedmailbox . That's cool! This probably means that the culprit is something related to process I/O, not file I/O. Do you read your pop3-fetched mail by receiving output of some process, or does that process create a file which you then direct RMAIL to read? > And I just discovered another mysterious bug. The last mailinglist mail > in the mailbox (from debian-japanese) contains a > > Content-Type: TEXT/PLAIN; charset=iso-8859-1 > > header, although its contents are obviously iso-2022-jp (7bit) encoded. > When receiving the mailbox via pop3, the japanese characters in the mail > show up correctly, and an > > X-Coding-System: iso-2022-jp-unix > > header is generated. How can that happen? The same mail, however, read > via C-u g ... will be decoded as iso-8859-1 (as it should be). Probably due to the same factor: somehow, when RMAIL reads your mail ``as usual'', it applies some other default. I will dwell on this and see what can I come up with.