From: Harry Putnam <reader@newsguy.com>
Subject: Re: mail split with multiple backends
Date: 20 Oct 2000 18:01:51 -0700 [thread overview]
Message-ID: <m2n1fznh1c.fsf@pgnus-5.8.8-cvs.now.playing> (raw)
In-Reply-To: joules@writeme.com's message of "Fri, 20 Oct 2000 15:38:07 -0400"
joules@writeme.com writes:
> Re: mail...
>
> I like using nnfolder but it can be annoying for large lists. So, I
> want to have one group set to nnml and the rest in nnfolder. I was
> able to do this without problems. (Yes, I changed nnml-directory to be
> different than nnfolder-directory.) Now, I want to split some messages
> to nnml:foo and others to nnfolder:bar. nnmail-split-methods doesn't
> seem to like if I add the nn*: stuff.
>
> Any thoughts?
The short answer is to use nnml for everthing. Else you get into the
complexities that Kai draws out in some detail.
Do you have a special need for nnfolder groups? One thing might be to
make them available to other mailers such as 'mutt' that cannot read
nnml groups.
I find it handy to use nnml as the only backend, but still use
`procmail' for some things. The procmail spool files are snarfed up
by gnus and put in nnml groups *WITHOUT* going through what ever is
set for nnmail split methods.
That is the normal functioning of a gnus/procmail combo.
prev parent reply other threads:[~2000-10-21 1:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-20 19:38 joules
2000-10-20 21:16 ` Kai Großjohann
2000-10-20 21:41 ` Rob Browning
2000-10-21 0:51 ` Harry Putnam
2000-10-21 4:45 ` Rob Browning
2000-10-21 11:09 ` Harry Putnam
2000-10-21 14:58 ` Rob Browning
2000-10-21 16:39 ` Kai Großjohann
2000-10-21 17:27 ` Rob Browning
2000-10-21 18:18 ` Kai Großjohann
2000-10-23 9:46 ` Didier Verna
2000-10-23 10:54 ` Kai Großjohann
2000-10-23 12:03 ` Didier Verna
2000-10-23 12:25 ` Kai Großjohann
2000-10-26 17:34 ` Toby Speight
2000-10-26 21:19 ` Kai Großjohann
2000-10-26 21:57 ` Simon Josefsson
2000-10-21 1:01 ` Harry Putnam [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=m2n1fznh1c.fsf@pgnus-5.8.8-cvs.now.playing \
--to=reader@newsguy.com \
/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).