From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: Why is gnus not slurping *.in files
Date: Tue, 08 Aug 2017 19:13:21 -0700 [thread overview]
Message-ID: <87efslxzcu.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87379240c2.fsf@local.lan>
Harry Putnam <reader@newsguy.com> writes:
> I've used this code in gnus for a very long time:
>
> (Bunched for mail)
>
> (setq mail-sources
> '((file :path "/var/spool/mail/reader")
> (directory :path "/home/reader/spool/in/" :suffix ".in")))
>
> And gnus has faithfully slurped mail at /var/spool/mail/reader
> And from ~/spool/<any mbox files ending in *.in>
>
> I've moved operations to a new host and now when I tell gnus to scan
> news/mail (C-g) those files are ignored silently.
I don't have any idea why that might be happening, but do try edebugging
the function `nnmail-get-new-mail-1' and seeing what happens. Follow the
function through and see if anything strikes you as weird.
Sorry not to be more helpful...
Eric
prev parent reply other threads:[~2017-08-09 2:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 14:10 Harry Putnam
2017-08-09 2:13 ` Eric Abrahamsen [this message]
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=87efslxzcu.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).