From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: fetching mail for multiple servers
Date: Tue, 20 Jun 2000 14:12:15 +0200 [thread overview]
Message-ID: <vaf7lbk4km8.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Harry Putnam's message of "20 Jun 2000 03:24:30 -0700"
Harry Putnam <reader@newsguy.com> writes:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
> > Right now, the algorithm for fetching mail is to go through all
> > servers in order. For each server, check if it gets mail. If so,
> > fetch mail from mail-sources and split it according to
> > nnmail-split-methods.
> >
> > This means if there are two servers that get mail, Gnus fetches mail
> > for both of them but when processing the second one, no new mail is
> > left.
> >
> > I suggest to add the following backward-compatible feature to Gnus:
> > when fetching mail for a server, look at server parameters
> > mail-sources and nnmail-split-methods. If the server parameter is
> > set, use it, else use the value of the global variable instead.
> >
> > This means that people could do something like this:
> >
> > (setq gnus-secondary-select-methods
> > '((nnml "work"
> > (nnml-directory "~/workmail/")
> > (mail-sources '((pop :server "work.pop.server"))))
> > (nnml "play"
> > (nnml-directory "~/privatemail/")
> > (mail-sources '((pop :server "private.pop.server"))))))
> >
>
> 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.
kai
--
I like BOTH kinds of music.
next prev parent reply other threads:[~2000-06-20 12:12 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 [this message]
2000-06-20 13:23 ` Harry Putnam
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=vaf7lbk4km8.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@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).