Gnus development mailing list
 help / color / mirror / Atom feed
From: Florian Weimer <fw@cygnus.stuttgart.netsurf.de>
Cc: ding@gnus.org
Subject: Re: Really confused about using gnus-0.80 & procmail
Date: 19 Mar 1999 21:13:41 +0100	[thread overview]
Message-ID: <m3yaktutje.fsf@deneb.cygnus.stuttgart.netsurf.de> (raw)
In-Reply-To: Marc Nozell's message of "Fri, 19 Mar 1999 13:31:41 -0500"

Marc Nozell <marc@nozell.com> writes:

> I've just tried to upgrade from an oldish pgnus version to pgnus-0.80
> with the new fancy mail spool stuff.

Perhaps this one will help you:

| > Subject: Q4.8 Procmail and Gnus
| > 
| >    Randal Schwartz <merlyn@stonehenge.com> writes:
| >    With procmail, you cannot write directly into the nnml directories.
| >    You must create spool files that will be merged into the nnml
| >    directories at times of Gnus' choosing. Asynch delivery just isn't in
| >    the cards.
| >    
| >    I just posted my setup a week ago. Here it is one more time:
| > (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
| > )
| 
| This doesn't work with Pterodactyl Gnus. You have to use something
| like this instead:
| 
| (setq
|  gnus-secondary-select-methods '((nnml ""))
|  nnmail-spool-file '((directory :path "~/.incoming/"
|                                 :suffix ".spool")))

(The FAQ won't get updated to reflect changes in alpha code, which is
quite reasonable.)


      parent reply	other threads:[~1999-03-19 20:13 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
1999-03-19 20:13 ` Florian Weimer [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=m3yaktutje.fsf@deneb.cygnus.stuttgart.netsurf.de \
    --to=fw@cygnus.stuttgart.netsurf.de \
    --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).