From: Chris Halverson <cdh@CompleteIS.com>
Cc: Marc Nozell <marc@nozell.com>, ding@gnus.org
Subject: Re: Really confused about using gnus-0.80 & procmail
Date: 19 Mar 1999 14:09:16 -0600 [thread overview]
Message-ID: <wpvhfx44yb.fsf@CompleteIS.com> (raw)
In-Reply-To: merlyn@stonehenge.com's message of "19 Mar 1999 11:22:47 -0800"
merlyn@stonehenge.com (Randal L. Schwartz) writes:
> and spread the clue around. All I recall is that some recent
> pterrygnus broke the thing I'm quoted as saying in the FAQ. And I
> don't know what I'll have to do if I go from Q to P now.
I used that advice to setup my Gnus eons ago :)
Note that I haven't done this yet (I'm a little nervous about
upgrading past my Pgnus 0.66 :), but Scott Hoffmann posted his setup
back in Feb. He has:
;; gnus customizations
(setq gnus-procmail-suffix ".spool"
gnus-nntp-server nil;; required to use gnus-select-method
gnus-select-method (list 'nntp "news.mindspring.com")
gnus-secondary-select-methods '((nnml ""))
gnus-uncacheable-groups "^nnml"
)
;; this stuff should make us work with procmail nicely
(setq nnml-directory "/home/shofmann/Mail/spool"
nnml-nov-is-evil t
)
(setq nnmail-use-procmail t
nnmail-spool-file '((directory :path "/home/shofmann/Mail/spool"
:suffix ".spool"))
)
Modify to suit obviously.
Hope that helps, let me know so I can fearlessly upgrade :)
Chris
--
Chris D. Halverson Complete Internet Solutions
PGP mail accepted, finger for public key http://www.CompleteIS.com/~cdh/
next prev parent reply other threads:[~1999-03-19 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-19 18:31 Marc Nozell
1999-03-19 19:22 ` Randal L. Schwartz
1999-03-19 20:08 ` David S. Goldberg
1999-03-29 12:05 ` Randal L. Schwartz
1999-04-02 13:59 ` Lars Magne Ingebrigtsen
1999-03-19 20:09 ` Chris Halverson [this message]
1999-03-19 20:13 ` Florian Weimer
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=wpvhfx44yb.fsf@CompleteIS.com \
--to=cdh@completeis.com \
--cc=ding@gnus.org \
--cc=marc@nozell.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).