From: Erik Selberg <speed@cs.washington.edu>
Subject: Found No Mail! blues (19.30/0.16)
Date: Thu, 30 Nov 1995 14:17:03 PST [thread overview]
Message-ID: <199511302217.OAA20172@wally.cs.washington.edu> (raw)
I just tried to upgrade to 19.30 (successfully) and S 0.16 from 0.12
(unsuccessfully). The problem is that ding is giving me these "Found
No Mail!" errors causing everything to die.
In particular, this happens when I start up ding. It then using
nnmail-split-incoming and calls nnmail-process-unix-mail-format. While
looking for the deliminator (i.e. "From blab blah blah") it errors
out. Apparently, it's taking .gnus-crash-file and inserting the
contents of that into a buffer. Since .gnus-crash-file is empty,
there's no mail to be found.
Have I missed something in moving up to 0.16? I have no idea why this
would be happening, and I've seen no upgrade notices in the newsgroup.
Thanks,
-Erik
reply other threads:[~1995-11-30 22:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199511302217.OAA20172@wally.cs.washington.edu \
--to=speed@cs.washington.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).