From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: [Q] multiple mail backends ?
Date: 27 Aug 1999 22:20:24 +0200 [thread overview]
Message-ID: <m3vha10yd3.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Kai =?iso-8859-1?q?Gro=DFjohann's?= message of "20 Jul 1999 16:41:14 +0200"
Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
> There has been a discussion about this previously. The upshot was, I
> think, to make the mail fetching mechanism take place in multiple
> steps. First, you fetch mail from a number of sources and put it all
> into the same backend. Subsequent steps may fetch from a specific
> group in a specific backend (rather than from a POP server, say) and
> put it into a second (third, fourth, ...) backend.
>
> I think Lars has said he's thinking about maybe implementing this.
> Correct me if I'm wrong, Lars.
I've been thinking, and I'm still thinking that it's a pretty marginal
functionality for quote a lot of work.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-08-27 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-20 12:41 Didier Verna
1999-07-20 14:41 ` Kai Großjohann
1999-08-27 20:20 ` 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=m3vha10yd3.fsf@quimbies.gnus.org \
--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).