From: Harry Putnam <reader@newsguy.com>
Subject: Re: fetching mail for multiple servers
Date: 20 Jun 2000 06:23:19 -0700 [thread overview]
Message-ID: <m2pupc7ago.fsf@reader.ptw.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 20 Jun 2000 14:12:15 +0200"
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> > That looks very useful. Its not clear from your post though, as to
> > what will happen with the splitting. Is it possible to make this
> > works so that each server can have its own split code too?
>
> That's what I meant. Like so:
>
> (setq gnus-secondary-select-methods
> '((nnml "work"
> (nnml-directory "~/workmail/")
> (nnmail-split-methods '(("" "mail.foo")))
> (mail-sources '((pop :server "work.pop.server"))))
> (nnml "play"
> (nnml-directory "~/privatemail/")
> (nnmail-split-methods '(("" "mail.bar")))
> (mail-sources '((pop :server "private.pop.server"))))))
>
> Here, all mail from work.pop.server will go to nnml+work:mail.foo,
> whereas mail from private.pop.server will go to nnml+play:mail.bar.
>
> Coming to think of it, it might be necessary to also allow
> nnmail-split-fancy as server parameter, too.
>
Oh-boy, that would be cool to the max.. Not as ultimately cool as nnir
was but still significant coolness.... he he.
Probably would require that split-fancy be allowed too.
While were on nnml-split-fancy .. Is it really required for the code
you wrote concerning splitting conversations?
Message-ID: <vafsnulibev.fsf@lucy.cs.uni-dortmund.de
on ding list.
Code now included in gnus I think..
That it, can it be used with normal splitting in force?
next prev parent reply other threads:[~2000-06-20 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-20 9:36 Kai Großjohann
2000-06-20 10:24 ` Harry Putnam
2000-06-20 12:12 ` Kai Großjohann
2000-06-20 13:23 ` Harry Putnam [this message]
2000-06-20 16:35 ` Kai Großjohann
2000-06-21 13:27 ` Conversation Splitting (Was: fetching mail for multiple servers) Arnd Kohrs
2000-06-20 13:55 ` fetching mail for multiple servers Bjørn Mork
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=m2pupc7ago.fsf@reader.ptw.com \
--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).