From: brendan.halpin@ul.ie (Brendan Halpin)
To: info-gnus-english@gnu.org
Subject: Sudden nnml problem
Date: Fri, 13 Feb 2015 11:18:31 +0000 [thread overview]
Message-ID: <87wq3mgiuw.fsf@ul.ie> (raw)
In the course of the morning, my gnus (v5.13) stopped reading nnml
files. When I logged on it read what was there, I released some
false-positive spam from the university's web-interface and it read
that, but when more mail arrived and fetchmail put it in the
xxx.mailinglist files, it began to ignore it.
Restarting gnus has no effect
Restarting emacs has no effect
Deleting the group and re-subscribing has no effect (except forgetting
what is read and ticked :-( )
It throws no errors.
Any ideas re how to debug?
Brendan
--
Brendan Halpin, Head, Department of Sociology, University of Limerick, Ireland
Tel: w +353-61-213147 f +353-61-202569 h +353-61-338562; Room F1-002 x 3147
mailto:brendan.halpin@ul.ie ULSociology on Facebook: http://on.fb.me/fjIK9t
http://teaching.sociology.ul.ie/bhalpin/wordpress twitter:@ULSociology
next reply other threads:[~2015-02-13 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 11:18 Brendan Halpin [this message]
2015-02-13 11:43 ` Brendan Halpin
2015-02-13 12:58 ` Peter Münster
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=87wq3mgiuw.fsf@ul.ie \
--to=brendan.halpin@ul.ie \
--cc=info-gnus-english@gnu.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).