From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Using procmail with Gnus
Date: 06 Jun 1997 19:38:29 +0200 [thread overview]
Message-ID: <m2vi3rhbsa.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Markus Dickebohm's message of 06 Jun 1997 09:46:02 +0200
Markus Dickebohm <m.dickebohm@uni-koeln.de> writes:
> 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?
Whatever would be most convenient is what you should do. If you want
Gnus to control what groups get created, you should set
`nnmail-resplit-incoming' to t. If you want procmail to control that,
you shouldn't.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1997-06-06 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-06-06 7:46 Markus Dickebohm
1997-06-06 17:38 ` Lars Magne Ingebrigtsen [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=m2vi3rhbsa.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@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).