Gnus development mailing list
 help / color / mirror / Atom feed
From: Markus Dickebohm <m.dickebohm@uni-koeln.de>
Subject: Using procmail with Gnus
Date: 06 Jun 1997 09:46:02 +0200	[thread overview]
Message-ID: <m33eqwi37p.fsf@franck.pc.Uni-Koeln.DE> (raw)

Recently I switched to procmail to filter some mails from high volume
mailinglists out of my inbox (I don't like my mail notifier do blink
every few seconds).

Personal mails and mails from some low volume lists stay in
/var/spool/mail/$USER.

I set "nnmail-use-procmail" and both the personal mails and the
procmail-filtered mails are incorporated to Gnus. That's exactly the
way I like it.

Today I started Gnus and to new nnml groups showed up. The reason was
that the procmail rule produced a file "ding.spool" while the nnml
group I used for this list via the nnml-split-method variable was
"Ding".

This behaviour shows that Gnus doesn't split the procmail filtered
mails again. I understand the manual that the variable
"nnmail-resplit-incoming" is responsible for that. Do I have to set
this variable or is it OK to get the procmail rule and
nnmail-split-method in sync?

  The manual says..
    "This also means that you probably don't want to set
     `nnmail-split-methods' either, which has some, perhaps, unexpected
     side effects."

This is not what I want, since the remaining mails in /var/spool/mail/$USER
should be split further by Gnus. Do I really have to decide to use
procmail _or_ nnmail-split-method or is it justified to get the best
from both?

Many thanks for any advice on this,
Markus

-- 
Markus Dickebohm            E-Mail: m.dickebohm@uni-koeln.de
Physical Chemistry           WWW  : http://www.uni-koeln.de/~acp66/


             reply	other threads:[~1997-06-06  7:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-06-06  7:46 Markus Dickebohm [this message]
1997-06-06 17:38 ` Lars Magne Ingebrigtsen

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=m33eqwi37p.fsf@franck.pc.Uni-Koeln.DE \
    --to=m.dickebohm@uni-koeln.de \
    /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).