From: Nevin Kapur <nevin@jhu.edu>
Subject: nnimap silently ignores invalid mailboxes
Date: Wed, 10 Apr 2002 22:48:30 -0400 [thread overview]
Message-ID: <m3u1qj9cht.fsf@fermat.mts.jhu.edu> (raw)
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.
--
:: Nevin :: nevin@jhu.edu ::
next reply other threads:[~2002-04-11 2:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 2:48 Nevin Kapur [this message]
2002-04-11 8:00 ` Simon Josefsson
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=m3u1qj9cht.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).