From: mdb@cdc.noaa.gov (Mark Borges)
Cc: ding@ifi.uio.no
Subject: Re: Gnus5, procmail, and reading mail lists.
Date: Mon, 13 Nov 1995 17:24:19 -0700 [thread overview]
Message-ID: <9511140024.AA00658@suomi.cdc.noaa.gov> (raw)
In-Reply-To: Joe Hildebrand's message of 13 Nov 1995 13:16:19 -0700
Thanks for the tips, Joe and Steven...
>>>>> "j" == Joe Hildebrand <hildjj@fuentez.com> writes:
j> you will have less difficulty if you use:
j> $HOME/mail/spool/foo.spool $HOME/mail/spool/bar.spool
OK. I gave up and used the extension. I also gave up and used ~/Mail
instead of ~/mail. Gnus was stubborn about using the former for some
reason. Perhaps I was setting it too late, I don't know. I was setting
it in my `gnus-init-file', but it was being over-ridden. Is there a
preferred place for setting nnmail-directory (I assume that's the
correct variable to set)?
j> fine. gnus uses movemail, which does locking. I have this at
j> the top of my .procmailrc, though:
j> # use lockfiles that Emacs movemail honours... otherwise you
j> may lose mail LOCKEXT=+
OK. It sounds like it should be fine, then. I haven't had a problem
with VM w/o the LOCKEXT above, but what the heck, I'll add it to my
.procmailrc, too.
j> try (setq nnmail-spool-file 'procmail)
Yes, I suspected that but the doc-string wasn't clear to me.
j> this was the old way. don't worry about it. Gnus takes care
j> of everything, the way you are doing it.
OK.
Here are the nnmail related variables I explicitly set, in case anyone
cares:
------------------------------------------------------------------------------
;; mail reading stuff
(setq
nnmail-use-procmail t
nnmail-directory (expand-file-name "~/Mail") ; this is the default anyway
nnmail-spool-file 'procmail
nnmail-split-methods nil
nnmail-procmail-directory (expand-file-name "~/Mail/spool")
;nnmail-procmail-suffix nil ; just use the group name? I
nnml-get-new-mail t
;nnmail-keep-last-article t ; supposed to be important
)
------------------------------------------------------------------------------
procmail delivers like into
~/Mail/spool/lists.foo.spool
using recipes like:
### ---------------------------------------
## foo
#
:0 :
* ^TOfoo-digest
lists.foo.spool
although it wasn't clear whether I should deliver into
~/Mail/spool/lists/foo.spool, (which turns out to be wrong)
instead, since the group resides in ~/Mail/lists/foo.
Anyway, then all one needs to do is follow the info page:
------------------------------------------------------------------------------
Go to the group buffer and type `G m'. When prompted, answer `foo'
for the name and `nnmh' for the method. Repeat twice for the two other
groups, `bar' and `mail.baz'. Be sure to include all your mail groups.
That's it. You are now set to read your mail. An active file for
this method will be created automatically.
------------------------------------------------------------------------------
i.e., I typed `G m' and answered `lists.foo' for the name and `nnml'
for the method. Amazingly enough, it works!
Thanks again.
-mb-
next prev parent reply other threads:[~1995-11-14 0:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-13 17:48 Mark Borges
1995-11-13 20:16 ` Joe Hildebrand
1995-11-14 0:24 ` Mark Borges [this message]
1995-11-15 6:19 ` Mark Borges
1995-11-15 8:17 ` Steven L. Baur
1995-11-13 20:33 Steven L. Baur
1995-11-13 22:43 ` Joe Hildebrand
1995-11-14 19:52 ` Edward J. Sabol
1995-11-13 22:21 Steven L. Baur
1995-11-14 1:43 Steven L. Baur
1995-11-14 13:04 ` Per Abrahamsen
1995-11-15 2:42 ` Steven L. Baur
1995-11-14 16:27 ` Joe Hildebrand
1995-11-14 17:22 ` Scott Blachowicz
1995-11-14 21:35 ` Joe Hildebrand
1995-11-15 6:58 ` Sudish Joseph
1995-11-15 18:46 ` Scott Blachowicz
1995-11-15 4:37 ` Sudish Joseph
1995-11-15 14:32 ` Per Abrahamsen
1995-11-15 15:50 ` Kai Grossjohann
1995-11-15 16:13 ` Per Abrahamsen
1995-11-15 17:50 ` Steven L. Baur
1995-11-17 21:18 ` Jason L Tibbitts III
1995-11-17 21:40 ` Joe Hildebrand
1995-11-14 1:55 Steven L. Baur
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=9511140024.AA00658@suomi.cdc.noaa.gov \
--to=mdb@cdc.noaa.gov \
--cc=ding@ifi.uio.no \
/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).