Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Fredrik Staxeng <fstx+u@update.uu.se>
Subject: Re: Why can't I use procmail
Date: 30 Sep 2002 20:17:14 +0200	[thread overview]
Message-ID: <1m7kh3s5p1.fsf@Tempo.Update.UU.SE> (raw)
In-Reply-To: <v9heg7idwo.fsf@marauder.physik.uni-ulm.de>

Reiner Steib <4uce.02.r.steib@gmx.net> writes:

> On Mon, Sep 30 2002, Fredrik Staxeng wrote:
> 
> > This has been irritating me ever since I started to use GNUS. It is 
> > mentioned in the FAQ, but I find the explanation less than satisfying.
> 
> Which point in the FAQ do you mean?
> <URL:http://my.gnus.org/FAQ/#id2753901> (8. Procmail and Gnus)?

Of course. I didn't see the first sentence. It could mean that it now
works, but I can't find anything about it in the manual. Does it 
in fact work? 

> > Could somebody that knows please explain? Also please explain why
> > procmail/mh can do it, but gnus can't? 
> 
> ,----[ <info://gnus/MH+Spool> ]
> |    `nnmh' is just like `nnml', except that is doesn't generate NOV
> | databases and it doesn't keep an active file or marks file.  This makes
> | `nnmh' a _much_ slower back end than `nnml', but it also makes it
> | easier to write procmail scripts for.
> `----

But I really want to use nnml.

-- 
Fredrik Stax\"ang | rot13: sfgk@hcqngr.hh.fr


  parent reply	other threads:[~2002-09-30 18:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30 16:47 Fredrik Staxeng
     [not found] ` <v9heg7idwo.fsf@marauder.physik.uni-ulm.de>
2002-09-30 18:17   ` Fredrik Staxeng [this message]
2002-09-30 18:25     ` David S Goldberg
2002-09-30 18:38       ` Fredrik Staxeng
     [not found]     ` <m3fzvopygg.fsf@multivac.cwru.edu>
2002-10-02 21:20       ` Fredrik Staxeng
2002-10-03 16:47         ` Paul Jarc

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=1m7kh3s5p1.fsf@Tempo.Update.UU.SE \
    --to=fstx+u@update.uu.se \
    /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).