From: Nikolaus Rath <Nikolaus@rath.org>
To: ding@gnus.org
Subject: Re: [PATCH] Use IMAP MOVE extension if available
Date: Mon, 27 Jul 2015 09:10:39 -0700 [thread overview]
Message-ID: <87r3nta8e8.fsf@thinkpad.rath.org> (raw)
In-Reply-To: <878ua2cj3m.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 27 Jul 2015 12:36:29 +0800")
On Jul 27 2015, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> diff --git a/lisp/nnimap.el b/lisp/nnimap.el
> index 161a6b4..f8e6e3e 100644
> --- a/lisp/nnimap.el
> +++ b/lisp/nnimap.el
> @@ -489,11 +489,18 @@ textual parts.")
> (when (functionp (nth 2 credentials))
> (funcall (nth 2 credentials)))
> ;; See if CAPABILITY is set as part of login
> - ;; response.
> - (dolist (response (cddr login-result))
> - (when (string= "CAPABILITY" (upcase (car response)))
> - (setf (nnimap-capabilities nnimap-object)
> - (mapcar #'upcase (cdr response))))))
> + ;; response. If it wasn't, specifically request
> + ;; it.
> + (when
> + (catch 'caps
> + (dolist (response (cddr login-result))
> + (when (string= "CAPABILITY" (upcase (car response)))
> + (throw 'caps (setq capabilities (cdr response)))))
> + (let ((req (nnimap-command "CAPABILITY")))
> + (when (car req)
> + (throw 'caps (setq capabilities (cdaddr req))))))
> + (setf (nnimap-capabilities nnimap-object)
> + (mapcar #'upcase capabilities))))
> ;; If the login failed, then forget the credentials
> ;; that are now possibly cached.
> (dolist (host (list (nnoo-current-server 'nnimap)
This looks a lot more complex, but as far as I can tell it still
needlessy asks for capabilities if they have been supplied in the
response code of OK response instead of a in separate, untagged
response. So is it really worth the extra complexity, if in many cases
we still issue an explicit CAPABILITY command?
(For everyone unfamiliar with RFC3501, what I mean is that this:
* CAPABILITY IMAP4rev1 AND SOME MORE \r\n
1 OK Logged in\r\n
will be parsed correcly but this:
1 OK [CAPABILITY IMAP4rev1 AND SOME MORE] Logged in\r\n
will still cause Gnus to issue a separate CAPABILITY command).
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
next prev parent reply other threads:[~2015-07-27 16:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 0:29 Nikolaus Rath
2015-07-16 9:00 ` Eric Abrahamsen
2015-07-20 9:53 ` Eric Abrahamsen
2015-07-20 16:18 ` Nikolaus Rath
2015-07-27 4:36 ` Eric Abrahamsen
2015-07-27 16:10 ` Nikolaus Rath [this message]
2015-08-02 5:56 ` Eric Abrahamsen
2015-08-02 23:36 ` Nikolaus Rath
2015-08-03 0:40 ` Eric Abrahamsen
2015-08-03 1:08 ` Dan Christensen
2015-08-03 8:17 ` Steinar Bang
2015-08-03 17:18 ` Nikolaus Rath
2015-08-04 3:17 ` Eric Abrahamsen
2015-08-04 17:28 ` Nikolaus Rath
2015-08-05 1:53 ` Eric Abrahamsen
-- strict thread matches above, loose matches on Subject: below --
2015-05-25 19:59 Nikolaus Rath
2015-07-07 2:59 ` Eric Abrahamsen
2015-07-07 3:05 ` Eric Abrahamsen
2015-07-09 2:13 ` Nikolaus Rath
2015-07-09 2:18 ` Eric Abrahamsen
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=87r3nta8e8.fsf@thinkpad.rath.org \
--to=nikolaus@rath.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).