From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: nnimap silently ignores invalid mailboxes
Date: Thu, 11 Apr 2002 10:00:31 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0204110957420.12805-100000@yxa.extundo.com> (raw)
In-Reply-To: <m3u1qj9cht.fsf@fermat.mts.jhu.edu>
On Wed, 10 Apr 2002, Nevin Kapur wrote:
> Recently we had problems with our mail system so that my spool file
> was no longer a valid mbox file (it started with rom_ instead of
> From_).
>
> I use nnimap-split-fancy to split all incoming mail. Following the
> corruption, I got no indication that INBOX was corrupted and mail just
> kept piling up in there. I got suspicious after seemingly not
> receiving any email for a day!
>
> 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?
Ah. Maybe the server does report something to the client, but Gnus doesn't
display it. What does other clients display as error? If you use Gnus,
how does the *imap-log* (see imap-log) buffer look around the error
message?
next prev parent reply other threads:[~2002-04-11 8:00 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 [this message]
2002-04-11 13:25 ` Nevin Kapur
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=Pine.LNX.4.44.0204110957420.12805-100000@yxa.extundo.com \
--to=jas@extundo.com \
--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).