From: Harry Putnam <reader@newsguy.com>
To: info-gnus-english@gnu.org
Subject: gnus not slurping mbox files
Date: Mon, 01 Feb 2021 17:28:00 -0500 [thread overview]
Message-ID: <87ft2f5spb.fsf@local.lan> (raw)
I've had these lines in gnus for years:
(setq mail-sources
'((file :path "/var/spool/mail/reader")
(directory :path "/spool/in/" :suffix ".in")))
And then I have procmail splitting incomming mail by provmail rules
into mbox files ending with the suffix `in' (`in') like
friend-name.in
Its an mbox file with whatever number of messages, there may be
several created or added too each time I pull mail from pop3 box.
gnus slurps the mbox messages but never deletes the empty file.
I've forgotten which part of the manual covers this.
That has worked for quite a few years. But ever since I made a major
move to a new host and have to get mail working smoothly. Gnus has
refused to slurp from the files procmail creates for that purpose.
I don't see any errors and nothing in \*Messages\* that seems to
indicate anything untoward is happening.... just seem gnus flat
ignores the mbox files.
How can I get to the bottom of what is causing this?
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next reply other threads:[~2021-02-01 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 22:28 Harry Putnam [this message]
2021-02-08 2:41 ` reader
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=87ft2f5spb.fsf@local.lan \
--to=reader@newsguy.com \
--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).