From: Nick Papadonis <nick@coelacanth.com>
Cc: ding@gnus.org
Subject: Re: procmail/gnus problem?
Date: 06 Nov 2000 03:59:13 -0500 [thread overview]
Message-ID: <m3g0l5o4ri.fsf@turing.dynodns.net> (raw)
In-Reply-To: <m3g0l69ok2.fsf@fermat.mts.jhu.edu>
Thanks Nevin,
This worked... i ended up respooling most of my mail because I messed
my directories. Who knows if switching over to procmail was
productive in any way.
This brings up the question, why does the FAQ say to insert the
following in the startup file? :
(setq
gnus-secondary-select-methods '((nnml ""))
nnmail-spool-file 'procmail
nnmail-procmail-directory "~/incoming/"
nnmail-delete-incoming t
)
Should the maintainer be contacted? Is the previous valid and I made a
mistake?
- Nick
>>>>> "Nevin" == Nevin Kapur <nkapur@bellatlantic.net> writes:
>>>>> "NP" == Nick Papadonis <nick@sturgeon.coelacanth.com> writes:
NP> Recently I set up procmail, and attempted to change the gnus
NP> startup file to import my procmail directory. I added the
NP> following: (setq gnus-secondary-select-methods '((nnml ""))
NP> nnmail-spool-file 'procmail nnmail-procmail-directory
NP> "~/incoming/" nnmail-delete-incoming t )
Nevin> Here is the relevant portion of my procmail setup. I think
Nevin> you might be using some obsolete variables.
Nevin> (setq gnus-secondary-select-methods '((nnml "")) ; Incoming
Nevin> Mail nnml-get-new-mail t mail-sources '((directory :path
Nevin> "~/.spool/" :suffix "")))
NP> My mailing lists are spooled into ~/incoming/ and have
NP> extensions like 'list.gnus.spool'.
Nevin> You should change the path and suffix parameter
Nevin> accordingly.
NP> I thought they would be imported to -> list.gnus, etc...
Nevin> Yes. This is what will happen. -- Nevin
--
.. Nick Papadonis
next prev parent reply other threads:[~2000-11-06 8:59 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 [this message]
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 ` 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=m3g0l5o4ri.fsf@turing.dynodns.net \
--to=nick@coelacanth.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).