From: Dmitry Bely <dbely@mail.ru>
Cc: ding@gnus.org
Subject: Re: Debugging POP3
Date: 26 Feb 2002 12:34:23 +0300 [thread overview]
Message-ID: <pu2sy4bk.fsf@mail.ru> (raw)
In-Reply-To: <vafd6yug3ys.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Groъjohann) writes:
> > Yes, I know that. As I already told you, the problem almost certainly is
> > with my provider's POP3 server, not with gnus. But to prove that I need to
> > show full "sent commands+server responses" log to their admin, not only
> > server responses that are present in gnus' "trace of POP session" by
> > default. Is it possible to get such log without rewriting the lisp code?
>
> Ayee. I see. I'm afraid that you do have to rewrite the Lisp code.
> Does the log have to have the commands and the responses in the right
> order? You could do a quick hack with pop3-send-command which just
> invokes `message' on the command. Then you can pick the commands off
> of the *Messages* buffer.
>
> But you'd need to get the sequences right.
They have already fixed the problem with POP3-server without me. But I
still think the tracing code in gnus should be corrected. An exapmle is VM
which does it right. Maybe I will modify gnus tracing some day...
Hope to hear from you soon,
Dmitry
next prev parent reply other threads:[~2002-02-26 9:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 18:24 Dmitry Bely
2002-02-23 11:39 ` Kai Großjohann
2002-02-23 11:39 ` Kai Großjohann
2002-02-24 16:48 ` Dmitry Bely
2002-02-24 17:54 ` Kai Großjohann
2002-02-26 9:34 ` Dmitry Bely
2002-02-26 9:34 ` Dmitry Bely [this message]
2002-02-24 17:54 ` Kai Großjohann
2002-02-24 16:48 ` Dmitry Bely
-- strict thread matches above, loose matches on Subject: below --
2002-02-22 18:24 Dmitry Bely
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=pu2sy4bk.fsf@mail.ru \
--to=dbely@mail.ru \
--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).