From: Simon Josefsson <jas@extundo.com>
Cc: jesseh@cs.kun.nl (Jesse F. Hughes)
Subject: Re: Oort gnus oddities....
Date: Mon, 19 Aug 2002 11:37:17 +0200 [thread overview]
Message-ID: <iluy9b3rxyq.fsf@latte.josefsson.org> (raw)
In-Reply-To: <871y8vjmr2.fsf@phiwumbda.localnet>
jesseh@cs.kun.nl (Jesse F. Hughes) writes:
>> This was reported earlier, and seemed like a server bug. Could you
>> show some more output from the *imap-log* buffer? In particular, the
>> previous commands sent to that server before command 145.
>
> I'll do that just as soon as I see it again.
Thanks.
> Even if it is a server bug, I'm surprised to see Gnus take down my
> xemacs. I reckon that there's a somewhat rare condition triggered by
> these events that's doing the dirty deed.
Have you reported it? Gnus can't prevent XEmacs from crashing.
>> Which server is this?
>
> In the earlier incident, we had this exchange.
>
> > * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS AUTH=PLAIN
> > AUTH=LOGIN] ***.***.kun.nl IMAP4rev1 2001.310 at Wed, 31 Jul
> > 2002 22:18:57 +0200 (MET DST)
>
> That looks like the UoW 2000 server, I'll forward as it is
> supposed to be the reference implementation. Thanks.
Ah, I remember now. :-)
Yes, I reported it, and there were some discussion about the other
problem, but the one you mentioned here now was a bug. Without more
information on what is earlier in the *imap-log* it is difficult to
work around the problem. It looks as if the server didn't let you
into the INBOX, and also returned a BAD which indicates a protocol
error in the client.
prev parent reply other threads:[~2002-08-19 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-18 20:20 Jesse F. Hughes
2002-08-19 0:33 ` Simon Josefsson
[not found] ` <871y8vjmr2.fsf@phiwumbda.localnet>
2002-08-19 9:37 ` Simon Josefsson [this message]
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=iluy9b3rxyq.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=jesseh@cs.kun.nl \
/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).