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: Tue, 24 May 2011 18:40:22 +0200	[thread overview]
Message-ID: <87boys6oi1.fsf@hati.baby-gnu.org> (raw)
In-Reply-To: <yovalixwwlr0.fsf@sampling.wsl.ch> (Adrian Lanz's message of "Tue, 24 May 2011 10:22:59 +0200")

Adrian Lanz <lanz@wsl.ch> writes:

>>>>>> On Wed, 04 May 2011 12:32:56 +0200
>>>>>> Daniel Dehennin <daniel.dehennin@baby-gnu.org> writes:
>
> [...]
>
>     > It looks like pop3-read-response is called too fast
>
>
> [...]
>
> The same here. Edebugging pop3-user and working down the function
> step-by-step is fine (mail messages are retrieved from the pop server of
> my ISP without error). However, pop3 retrieval mail messages the normal
> (fast) way without debugging does not work (gives me an error: user no
> known, or similar).

Personally I switched to an imap mail-source as I have the choice and no
idea how to debug this.

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



  reply	other threads:[~2011-05-24 16:40 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   ` Daniel Dehennin [this message]
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           ` 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=87boys6oi1.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).