From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/947 Path: news.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.user Subject: Re: Oort gnus oddities.... Date: Mon, 19 Aug 2002 11:37:17 +0200 Message-ID: References: <874rdr9ax2.fsf@phiwumbda.localnet> <871y8vjmr2.fsf@phiwumbda.localnet> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138667807 9062 80.91.229.2 (31 Jan 2006 00:36:47 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:36:47 +0000 (UTC) Cc: jesseh@cs.kun.nl (Jesse F. Hughes) Original-X-From: nobody Tue Jan 17 17:28:23 2006 Original-Path: quimby.gnus.org!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: 178.230.13.217.in-addr.dgcsystems.net Original-X-Trace: quimby.gnus.org 1029751465 26884 217.13.230.178 (19 Aug 2002 10:04:25 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: 19 Aug 2002 10:04:25 GMT X-Hashcash: 0:020819:jesseh@cs.kun.nl:99a3f97e762c956e User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.3.50 (i686-pc-linux-gnu) Cancel-Lock: sha1:src0Cto5eXHBI7GgsDzF1qXCg0o= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:1087 Original-Lines: 35 X-Gnus-Article-Number: 1087 Tue Jan 17 17:28:23 2006 Xref: news.gmane.org gmane.emacs.gnus.user:947 Archived-At: 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.