From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Pulling in mbox files made by procmail no longer works
Date: Tue, 26 Jan 2021 12:51:41 -0500 [thread overview]
Message-ID: <87ft2nd1si.fsf@local.lan> (raw)
I'm not getting any clues why gnus has stopped pulling in procmail
created mbox mail when I press `g'. Gnus seems to completely ignore
them without any complaint or errors. Nothing spell binding in
\*Messages\*
I've been doing this for quite some time and not seeing whey it fails now
My .gnus code below has not changed for quite a long time. These two
stanzas should be creating nnml groups from the mbox files.
They have not changed for a long while other than to being comment out
from time to time.
(setq mail-sources
'((file :path "/var/spool/mail/reader")
(directory :path "/spool/in/" :suffix ".in")))
(setq gnus-secondary-select-methods
'((nnml "")))
/spool/in both `spool' and `in' have full permissions of my user
reader > ls -la /spool/in
total 840
drwxr-xr-x 3 reader nfsu 4096 Jan 26 10:40 .
drwxr-xr-x 3 reader nfsu 4096 Jan 23 13:58 ..
-rw------- 1 reader nfsu 194606 Jan 24 18:22 all-but-cron_.in
-rw------- 1 reader nfsu 8674 Jan 24 02:22 AsteriskBS_spam_tr.in
-rw------- 1 reader nfsu 194794 Jan 24 18:22 bogo-unsure.in
-rw------- 1 reader nfsu 3678 Jan 23 18:22 cron_tr.in
-rw------- 1 reader nfsu 57555 Jan 24 12:22 oi-discuss.in
drwxr-xr-x 5 reader nfsu 4096 Jan 23 17:51 Saved
-rw------- 1 reader nfsu 359303 Jan 24 19:49 zfs-discuss.in
Just in case /spool/in means ~/spool/in to gnus I also have a symlink
in ~
reader > ls -l ~/spool
lrwxrwxrwx 1 reader nfsu 6 Jan 23 14:31 /home/reader/spool -> /spool
reader > ls -l ~/spool/
total 4
drwxr-xr-x 3 reader nfsu 4096 Jan 26 10:40 in
Any ideas what would likely be stopping gnus from working on these
mbox files?
reply other threads:[~2021-01-26 17:52 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=87ft2nd1si.fsf@local.lan \
--to=reader@newsguy.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).