From: Simon Josefsson <jas@extundo.com>
Cc: <ding@gnus.org>
Subject: Re: RFC822.PEEK in mail-source-fetch-imap
Date: Mon, 1 Oct 2001 17:21:56 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.33.0110011721210.9196-100000@lie.extundo.com> (raw)
In-Reply-To: <877kuf2z47.fsf@lynx.ionific.com>
On 1 Oct 2001, Hannu Koivisto wrote:
> 5 UID FETCH 1 RFC822.PEEK
> 5 BAD Bogus attribute list in UID FETCH
>
> That RFC822.PEEK seems to originate in mail-source-fetch-imap.
Try this:
Index: mail-source.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/mail-source.el,v
retrieving revision 6.9
diff -u -3 -p -c -r6.9 mail-source.el
cvs server: conflicting specifications of output style
*** mail-source.el 2001/08/30 18:40:37 6.9
--- mail-source.el 2001/10/01 15:11:44
*************** This only works when `display-time' is e
*** 901,907 ****
(push (cons from imap-password) mail-source-password-cache)))
;; if predicate is nil, use all uids
(dolist (uid (imap-search (or predicate "1:*") buf))
! (when (setq str (imap-fetch uid "RFC822.PEEK" 'RFC822 nil buf))
(push uid remove)
(insert "From imap " (current-time-string) "\n")
(save-excursion
--- 901,910 ----
(push (cons from imap-password) mail-source-password-cache)))
;; if predicate is nil, use all uids
(dolist (uid (imap-search (or predicate "1:*") buf))
! (when (setq str (if (imap-capability 'IMAP4rev1 buf)
! (imap-fetch uid "BODY.PEEK[]" 'BODYDETAIL
! nil buf)
! (imap-fetch uid "RFC822.PEEK" 'RFC822 nil buf)))
(push uid remove)
(insert "From imap " (current-time-string) "\n")
(save-excursion
prev parent reply other threads:[~2001-10-01 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 14:50 Hannu Koivisto
2001-10-01 15:21 ` Simon Josefsson [this message]
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=Pine.LNX.4.33.0110011721210.9196-100000@lie.extundo.com \
--to=jas@extundo.com \
--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).