From: simon@josefsson.org
Cc: ding@gnus.org
Subject: Re: 8bit mails via POP and IMAP mail-source
Date: 09 Aug 2000 15:56:10 +0200 [thread overview]
Message-ID: <iluhf8uv8qt.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <200008091327.PAA02018@SnowWhite.inet.cz>
Pavel@Janik.cz (Pavel Janík ml.) writes:
> Via IMAP, the mail is stored in \202X/202Y and is then viewed as such :-(
`coding-system-for-write' seem to be bound to nil in pop3.el, here's a
similar (untested) patch for mail-source.el.
Does it work? (Assuming asking the user for character sets can be
regarded as "work". Should the variable, and the one in pop3.el,
default to 'raw-text instead?)
Index: mail-source.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/mail-source.el,v
retrieving revision 5.38
diff -w -u -u -w -r5.38 mail-source.el
--- mail-source.el 2000/05/15 14:14:42 5.38
+++ mail-source.el 2000/08/04 13:53:48
@@ -649,6 +649,9 @@
(autoload 'imap-list-to-message-set "imap")
(autoload 'nnheader-ms-strip-cr "nnheader"))
+(defvar mail-source-imap-file-coding-system nil
+ "Coding system for the crashbox made by `mail-source-fetch-imap'.")
+
(defun mail-source-fetch-imap (source callback)
"Fetcher for imap sources."
(mail-source-bind (imap source)
@@ -662,7 +665,7 @@
user (or (cdr (assoc from mail-source-password-cache))
password) buf)
(imap-mailbox-select mailbox nil buf))
- (let (str (coding-system-for-write 'binary))
+ (let (str (coding-system-for-write mail-source-imap-file-coding-system))
(with-temp-file mail-source-crash-box
;; remember password
(with-current-buffer buf
next prev parent reply other threads:[~2000-08-09 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-09 13:27 Pavel Janík ml.
2000-08-09 13:56 ` simon [this message]
2000-08-04 17:29 ` Pavel Janík ml.
2000-08-09 18:41 ` simon
2000-08-09 14:39 ` Kai Großjohann
2000-08-09 18:45 ` simon
2000-08-09 20:49 ` Stainless Steel Rat
2000-08-09 15:11 ` 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=iluhf8uv8qt.fsf@barbar.josefsson.org \
--to=simon@josefsson.org \
--cc=ding@gnus.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.
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).