unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kuehling <dvdkhlng@gmx.de>
Subject: Re: RMAIL doesn't always recognize rmail-mime-charset-pattern
Date: 19 May 2002 15:09:58 +0200	[thread overview]
Message-ID: <87y9egnv15.fsf@snail.pool> (raw)
In-Reply-To: <2427-Sat18May2002192636+0300-eliz@is.elta.co.il>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

>>>>> "Eli" == Eli Zaretskii <eliz@is.elta.co.il> writes:

> Do you still have the original mailbox retrieved by pop3?

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 <Ret>.  That's cool!

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).

I attach the full mailbox: savedmailbox.gz.

David Kühling
-- 
GnuPG public key: http://user.cs.tu-berlin.de/~dvdkhlng/dk.gpg
Fingerprint: B17A DC95 D293 657B 4205  D016 7DEF 5323 C174 7D40


[-- Attachment #2: savedmailbox.gz --]
[-- Type: application/octet-stream, Size: 16121 bytes --]

  parent reply	other threads:[~2002-05-19 13:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-18 13:18 RMAIL doesn't always recognize rmail-mime-charset-pattern David Kuehling
2002-05-18 16:26 ` Eli Zaretskii
2002-05-18 17:52   ` David Kuehling
2002-05-19 13:09   ` David Kuehling [this message]
2002-05-19 13:27     ` Eli Zaretskii
2002-05-19 15:24       ` David Kuehling
2002-05-19 15:28       ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y9egnv15.fsf@snail.pool \
    --to=dvdkhlng@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).