From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: 8bit mails via POP mail-source
Date: 13 Dec 2000 18:02:57 -0500 [thread overview]
Message-ID: <5b66knc4bi.fsf@brandy.cs.rochester.edu> (raw)
In-Reply-To: <m3elzcc5j4.fsf@snowwhite.suse.cz>
Pavel@Janik.cz (Pavel Janík ml.) writes:
> From: Stainless Steel Rat <ratinox@peorth.gweep.net>
> Date: 12 Dec 2000 16:36:17 -0500
>
> Hi,
>
> > * Pavel@Janik.cz (Pavel Janík ml.) on Tue, 12 Dec 2000
> > | These default coding systems were tried:
> > | iso-8859-2
> > | However, none of them safely encodes the target text.
> >
> > Of course it doesn't. POP3 is a binary data stream, not text. It will
> > break if you try to treat it as text. pop3.el *should* do the right thing,
> > but I haven't maintained that code since the FSF *and* XEmacs developers
> > yanked it out from under me.
>
> OK, so is there any solution or not?
Try (setq pop3-movemail-file-coding-system 'binary).
ShengHuo
next prev parent reply other threads:[~2000-12-13 23:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-12 15:28 Pavel Janík ml.
2000-12-12 21:36 ` Stainless Steel Rat
2000-12-13 22:36 ` Pavel Janík ml.
2000-12-13 23:02 ` ShengHuo ZHU [this message]
2000-12-14 0:51 ` Stainless Steel Rat
2000-12-14 7:42 ` Vladimir Volovich
2000-12-14 18:55 ` Stainless Steel Rat
2000-12-14 19:08 ` Kai Großjohann
2000-12-14 21:01 ` Stainless Steel Rat
2000-12-15 10:59 ` vvv
2000-12-15 14:20 ` Stainless Steel Rat
2000-12-15 15:01 ` Stainless Steel Rat
2000-12-15 15:16 ` ShengHuo ZHU
2000-12-21 23:36 ` Dave Love
2000-12-22 1:01 ` Stainless Steel Rat
2000-12-16 9:07 ` vvv
2000-12-16 9:43 ` vvv
2000-12-17 5:57 ` Stainless Steel Rat
2000-12-15 11:54 ` Kenichi Handa
[not found] <eyu286f3ga.fsf@video.uic.vsu.ru>
[not found] ` <rzqwvct5qs7.fsf@djlvig.dl.ac.uk>
2000-12-22 9:05 ` vvv
2000-12-22 22:47 ` Stainless Steel Rat
2000-12-23 19:35 ` Miles Bader
2000-12-24 7:21 ` Stainless Steel Rat
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5b66knc4bi.fsf@brandy.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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.
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 NNTP newsgroup(s).