From: "Jason R. Mastaler" <jason@mastaler.com>
Subject: Re: procmail and nnfolder
Date: Sat, 05 Apr 1997 14:07:39 -0500 [thread overview]
Message-ID: <199704051907.OAA14936@ashanti.vcinet.com> (raw)
In-Reply-To: Your message of "05 Apr 1997 02:36:10 CST." <ufag1x5oohx.fsf@sina.hpc.uh.edu>
Jason L Tibbitts III <tibbs@hpc.uh.edu> writes:
> You have Procmail stuff mail in spool files, pre-sorted and filtered. Gnus
> then picks these up and stuff the messages in the appropriate groups. Gnus
> uses movemail to actually move the mail out of the spool, and movemail uses
> locking that Procmail understands, so there is no danger of mail loss.
Ok, thanks for clearing this up. However, this isn't working for
me. When I fire up Gnus, it isn't moving any mail over to my
'nnfolder-directory'. Here is what I added to .gnus
(setq nnmail-use-procmail t)
(setq nnfolder-directory "~/gMail/")
(setq nnmail-spool-file 'procmail)
(setq nnmail-procmail-directory "~/incoming/lists/")
(setq gnus-secondary-select-methods '((nnfolder "")))
(setq nnmail-procmail-suffix "")
Procmail is adding incoming mail to ~/incoming/lists/listname.
The nnfolder groups I subscribed to are named "nnfolder:lists.listname"
Gnus does create the ~/gMail/lists directory with a zero lengh file
in this directory for each list, but doesn't move any mail over and
so it thinks I have "No more unread newsgroups".
I'm using Gnus v5.4.40/XEmacs 19.15. What am I missing here?
--
Jason R. Mastaler jason@mastaler.com
next prev parent reply other threads:[~1997-04-05 19:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-05 6:51 Jason R. Mastaler
1997-04-05 8:36 ` Jason L Tibbitts III
1997-04-05 19:07 ` Jason R. Mastaler [this message]
1997-04-06 17:37 ` Lars Magne Ingebrigtsen
1997-04-06 22:35 ` Jason R. Mastaler
1997-04-08 20:58 ` Lars Magne Ingebrigtsen
1997-04-07 6:51 Jason R. Mastaler
1997-04-07 18:30 ` Jason R. Mastaler
1997-04-08 21:00 ` Lars Magne Ingebrigtsen
1997-04-09 2:13 ` Jason R. Mastaler
1997-04-10 17:29 ` Lars Magne Ingebrigtsen
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=199704051907.OAA14936@ashanti.vcinet.com \
--to=jason@mastaler.com \
/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).