From: Adrian Lanz <lanz@wsl.ch>
To: ding@gnus.org
Subject: Re: pop3-read-response
Date: Sun, 03 Jul 2011 14:46:37 +0200 [thread overview]
Message-ID: <yova8vsfmt02.fsf@sampling.wsl.ch> (raw)
In-Reply-To: <m3vcwm7el8.fsf@quimbies.gnus.org>
>>>>> On Sat, 04 Jun 2011 00:08:35 +0200
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Daniel Dehennin <daniel.dehennin@baby-gnu.org> writes:
>> Here is the output
>>
>> #v+
>> 1 IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS CHILDREN
>> BINARY UNSELECT SORT CATENATE URLAUTH LANGUAGE ESEARCH ESORT
>> THREAD=ORDEREDSUBJECT THREAD=REFERENCES ENABLE CONTEXT=SEARCH
>> CONTEXT=SORT WITHIN SASL-IR SEARCHRES XSENDER X-NETSCAPE
>> XSERVERINFO X-SUN-SORT ANNOTATE-EXPERIMENT-1 X-UNAUTHENTICATE
>> X-SUN-IMAP X-ANNOTATEMORE XUM1 AUTH=PLAIN
> Uhmn. That's the contents of an IMAP buffer. How did that end up
> in the POP buffer?
[...]
I use the following hack to make pop3.el work with my ISP (yes, it
offers no IMAP). I consider it as a hack. Any comments, recommendations?
*** /usr/share/emacs/24.0.50/lisp/gnus/pop3.el.gz
--- /emacs/lisp/gnus/pop3.el
***************
*** 313,318 ****
--- 313,321 ----
(lambda (capabilities)
(and (string-match "\\bSTLS\\b" capabilities)
"STLS\r\n"))))
+
+ (sit-for 1)
+
(when result
(let ((response (plist-get (cdr result) :greeting)))
(setq pop3-timestamp
next prev parent reply other threads:[~2011-07-03 12:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 10:32 pop3-read-response Daniel Dehennin
2011-05-24 8:22 ` pop3-read-response Adrian Lanz
2011-05-24 16:40 ` pop3-read-response Daniel Dehennin
2011-05-30 20:48 ` pop3-read-response Lars Magne Ingebrigtsen
2011-05-31 7:16 ` pop3-read-response Daniel Dehennin
2011-05-31 18:49 ` pop3-read-response Lars Magne Ingebrigtsen
2011-06-01 7:05 ` pop3-read-response Daniel Dehennin
2011-06-03 22:08 ` pop3-read-response Lars Magne Ingebrigtsen
2011-07-03 12:46 ` Adrian Lanz [this message]
2011-07-05 20:55 ` pop3-read-response Lars Magne Ingebrigtsen
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=yova8vsfmt02.fsf@sampling.wsl.ch \
--to=lanz@wsl.ch \
--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).