Gnus development mailing list
 help / color / mirror / Atom feed
From: jason@mastaler.com (Jason R. Mastaler)
Subject: procmail and nnfolder
Date: 05 Apr 1997 01:51:48 -0500	[thread overview]
Message-ID: <x7912yq7wb.fsf@mastaler.com> (raw)

I'm still trying to find the "right" relationship between Gnus and
procmail.  I currently use procmail to shuffle my incoming mail info
different folders, one mail folder for each mailing list.  So the ding
list goes into ~/Mail/lists/ding for example.  I use Gnus to read
these lists with nnfolder as the backend.  So, my group for the ding
list is 'nnfolder:lists.ding' .  Reading through the Gnus manual today
I noticed in the "Mail and Procmail" section:

  If you use nnfolder or any other backend that store more than a
  single article in each file, you should never have procmail add mails
  to the file that Gnus sees. Instead, procmail should put all
  incoming mail in nnmail-procmail-directory. To arrive at the file
  name to put the incoming mail in, append nnmail-procmail-suffix to
  the group name. The mail backends will read the mail from these
  files. 

So does this mean I've been doing what the manual says not to?  (It
looks like it)  If so, why is this bad?  I've never noticed any side
effects from this combination.  I'm also a bit confused with at the
proposed solution of having procmail filter incoming mail in a 
nnmail-procmail-directory instead.

Here is the included example:

  (setq nnfolder-directory "~/fMail/")
  (setq nnmail-spool-file 'procmail)
  (setq nnmail-procmail-directory "~/incoming/")
  (setq gnus-secondary-select-methods '((nnfolder "")))
  (setq nnmail-procmail-suffix "")

Why are nnfolder-directory and nnmail-procmail-directory two different
directories if nnmail-procmail-directory will contain the mail boxes
that procmail appends to and nnfolder-directory is supposed to be
"All the nnfolder mail boxes will be stored under this directory"?

Is the idea to have Gnus use nnmail-procmail-directory as a temporary
directory that it draws from to process and then deposit nnfolder
mailboxes in the nnfolder-directory?  In this case, I guess I would
have procmail filter like this (for example):

ding list --> ~/incoming/lists/ding
bind list --> ~/incoming/lists/bind

Then, if I define (setq nnfolder-directory "~/Mail/lists/") + 
(setq nnmail-procmail-directory "~/incoming/lists/") would Gnus
automagically know that the group 'nnfolder:lists.ding' should be
drawn from ~/incoming/lists/ding and stored as ~/Mail/lists/ding ?

Thanks,

-- 
Jason R. Mastaler                                 jason@mastaler.com


             reply	other threads:[~1997-04-05  6:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-05  6:51 Jason R. Mastaler [this message]
1997-04-05  8:36 ` Jason L Tibbitts III
1997-04-05 19:07   ` Jason R. Mastaler
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=x7912yq7wb.fsf@mastaler.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).