Gnus development mailing list
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: ding@gnus.org
Subject: Re: procmail/gnus problem?
Date: 12 Nov 2000 03:24:49 -0800	[thread overview]
Message-ID: <m1ofzlsa9q.fsf@halfdome.holdit.com> (raw)
In-Reply-To: Nevin Kapur's message of "05 Nov 2000 15:00:45 -0500"

>>>>> "Nevin" == Nevin Kapur <nkapur@bellatlantic.net> writes:

Nevin> Here is the relevant portion of my procmail setup. I think you might be
Nevin> using some obsolete variables.

Nevin> (setq 
Nevin>       gnus-secondary-select-methods
Nevin>       '((nnml ""))			; Incoming Mail
Nevin>       nnml-get-new-mail t
Nevin>       mail-sources
Nevin>       '((directory
Nevin> 	 :path "~/.spool/"
Nevin> 	 :suffix "")))

NP> My mailing lists are spooled into ~/incoming/ and have extensions
NP> like 'list.gnus.spool'.

And here's mine.  I'm not sure now why I needed the "don't look at
empty files" predicate (but I do recall going to great pains to insert
it for some reason).  But it's here:

(setq
 mail-sources '((directory
		 :path "~/.incoming/"
		 :predicate (lambda (f)
			      (not (zerop (nth 7 (file-attributes f)))))
		 )) ; terry gnus
 mail-source-delete-incoming t		; terry gnus
)

For nnml:FOO, I have my incoming handler drop it into ~/.incoming/FOO.spool

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!



      parent reply	other threads:[~2000-11-12 11:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-05 18:59 Nick Papadonis
2000-11-05 20:00 ` Nevin Kapur
2000-11-06  8:59   ` Nick Papadonis
2000-11-06  9:49     ` Kai Großjohann
2000-11-06 10:08       ` Nick Papadonis
2000-11-06 10:55     ` Gnus FAQ bug report (was: Re: procmail/gnus problem?) Kai Großjohann
2000-11-06 17:00       ` Justin Sheehy
2000-11-12 11:24   ` Randal L. Schwartz [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=m1ofzlsa9q.fsf@halfdome.holdit.com \
    --to=merlyn@stonehenge.com \
    --cc=ding@gnus.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).