From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/10544 Path: main.gmane.org!not-for-mail From: jason@mastaler.com (Jason R. Mastaler) Newsgroups: gmane.emacs.gnus.general Subject: procmail and nnfolder Date: 05 Apr 1997 01:51:48 -0500 Sender: jason@mastaler.com Message-ID: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII X-Trace: main.gmane.org 1035150397 25015 80.91.224.250 (20 Oct 2002 21:46:37 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:46:37 +0000 (UTC) Return-Path: Original-Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.8.5/8.8.5) with SMTP id XAA07013 for ; Fri, 4 Apr 1997 23:02:35 -0800 Original-Received: from claymore.vcinet.com (claymore.vcinet.com [208.205.12.23]) by ifi.uio.no with SMTP (8.6.11/ifi2.4) id for ; Sat, 5 Apr 1997 08:51:56 +0200 Original-Received: (qmail 10279 invoked by uid 504); 5 Apr 1997 06:49:25 -0000 Original-Received: (qmail 10276 invoked from network); 5 Apr 1997 06:49:24 -0000 Original-Received: from ashanti.vcinet.com (208.205.15.58) by claymore.vcinet.com with SMTP; 5 Apr 1997 06:49:24 -0000 Original-Received: (from jason@localhost) by ashanti.vcinet.com (8.8.4/8.8.5) id BAA11428; Sat, 5 Apr 1997 01:51:48 -0500 (EST) Original-To: ding@gnus.org Original-Lines: 53 X-Mailer: Gnus v5.4.40/XEmacs 19.15 Xref: main.gmane.org gmane.emacs.gnus.general:10544 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:10544 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