unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: RMAIL doesn't always recognize rmail-mime-charset-pattern
Date: Sun, 19 May 2002 16:27:11 +0300 (IDT)	[thread overview]
Message-ID: <Pine.SUN.3.91.1020519162451.18913B-100000@is> (raw)
In-Reply-To: <87y9egnv15.fsf@snail.pool>


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

  reply	other threads:[~2002-05-19 13:27 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
2002-05-19 13:27     ` Eli Zaretskii [this message]
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=Pine.SUN.3.91.1020519162451.18913B-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=bug-gnu-emacs@gnu.org \
    /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).