Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Dehennin <daniel.dehennin@baby-gnu.org>
To: ding@gnus.org
Subject: Re: pop3-read-response
Date: Wed, 01 Jun 2011 09:05:30 +0200	[thread overview]
Message-ID: <87ipsq58w5.fsf@hati.baby-gnu.org> (raw)
In-Reply-To: <m3tycaemd0.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 31 May 2011 20:49:47 +0200")

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:


[...]

> If you apply the following patch, pop3 should message what's in the
> buffer, and that might give us a clue what's failing precisely,
>
> pop3-read-point is supposed to be before the "+OK", so waiting for the
> \r\n should have given the complete line.  I'm thinking pop3-read-point
> is somewhere earlier in the buffer for some reason or other.

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

.

#v-

Regards.
-- 
Daniel Dehennin
Récupérer ma clef GPG:
gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2011-06-01  7:05 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       ` Daniel Dehennin [this message]
2011-06-03 22:08         ` pop3-read-response Lars Magne Ingebrigtsen
2011-07-03 12:46           ` pop3-read-response Adrian Lanz
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=87ipsq58w5.fsf@hati.baby-gnu.org \
    --to=daniel.dehennin@baby-gnu.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).