Gnus development mailing list
 help / color / mirror / Atom feed
From: Nevin Kapur <nevin@jhu.edu>
Subject: Re: nnimap silently ignores invalid mailboxes
Date: Thu, 11 Apr 2002 09:25:59 -0400	[thread overview]
Message-ID: <m3lmbu9xjs.fsf@fermat.mts.jhu.edu> (raw)
In-Reply-To: <Pine.LNX.4.44.0204110957420.12805-100000@yxa.extundo.com> (Simon Josefsson's message of "Thu, 11 Apr 2002 10:00:31 +0200 (CEST)")

Simon Josefsson <jas@extundo.com> writes:

> On Wed, 10 Apr 2002, Nevin Kapur wrote:

[...]

>> I was hoping that there were some way that Gnus could warn me when
>> this situation occurred.  When I tried accessing the corrupted INBOX
>> with other IMAP clients (pine and Evolution), I was given clear
>> indication that something was wrong.
>
> Hm, Gnus's imap stuff doesn't care about From at all, it retrieves 
> articles using IMAP commands.  I guess the server was confused and didn't 
> return any messages, but I don't understand why other clients would work 
> in that case.  Could you delete the F in your spool file and experiment a 
> little to see what fails?

936 SELECT "INBOX"
936 NO SELECT failed: Can't open INBOX (file /var/spool/mail/kapur): not in valid mailbox format

I tried that.  Here are the relevant lines.  So the UW server does
give indication that something is amiss.

> Ah. Maybe the server does report something to the client, but Gnus doesn't 
> display it.  What does other clients display as error?

Both Evolution and PINE display something close to the second line as
the error message.

-- 
:: Nevin ::



  reply	other threads:[~2002-04-11 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-11  2:48 Nevin Kapur
2002-04-11  8:00 ` Simon Josefsson
2002-04-11 13:25   ` Nevin Kapur [this message]
2002-04-11 13:48     ` Simon Josefsson
2002-04-11 14:25       ` Nevin Kapur

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=m3lmbu9xjs.fsf@fermat.mts.jhu.edu \
    --to=nevin@jhu.edu \
    /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).