Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: Nevin Kapur <nkapur@bellatlantic.net>,
	ding@gnus.org, Nick Papadonis <nick@coelacanth.com>
Subject: Gnus FAQ bug report (was: Re: procmail/gnus problem?)
Date: 06 Nov 2000 11:55:36 +0100	[thread overview]
Message-ID: <vafwvehs72v.fsf_-_@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3g0l5o4ri.fsf@turing.dynodns.net>

Dear Justin,

the Gnus FAQ mentions the following Lisp code in `Q4.8 Procmail and
Gnus':

/----
| (setq
|  gnus-secondary-select-methods '((nnml ""))
|  nnmail-use-procmail t
|  nnmail-spool-file 'procmail            ; same as nnmail-use-procmail :-)
|  nnmail-procmail-directory "~/.incoming/"
|  nnmail-delete-incoming t
| )
\----

For Gnus 5.8, this should be changed as follows, I think:

/----
| (setq
|  gnus-secondary-select-methods '((nnml ""))
|  mail-sources '((directory :path "~/.incoming/" :suffix ".spool"))
|  mail-source-delete-incoming t
| )
\----

I'm not sure if it is necessary to also (setq nnmail-spool-file
mail-sources) to work around a bug in the officially released version
of Gnus.  Anyone?  This might have been fixed in 5.8.7 already.

kai
-- 
The arms should be held in a natural and unaffected way and never
be conspicuous. -- Revised Technique of Latin American Dancing



  parent reply	other threads:[~2000-11-06 10:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-05 18:59 procmail/gnus problem? 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     ` Kai Großjohann [this message]
2000-11-06 17:00       ` Gnus FAQ bug report (was: Re: procmail/gnus problem?) Justin Sheehy
2000-11-12 11:24   ` procmail/gnus problem? Randal L. Schwartz

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=vafwvehs72v.fsf_-_@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@gnus.org \
    --cc=nick@coelacanth.com \
    --cc=nkapur@bellatlantic.net \
    /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).