From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Uh oh. IMAP and ifile-gnus
Date: Tue, 20 Jul 2004 10:36:22 -0400 [thread overview]
Message-ID: <4n658irbix.fsf@lifelogs.com> (raw)
In-Reply-To: <874qo23jt3.fsf@phiwumbda.org>
On Tue, 20 Jul 2004, jesse@phiwumbda.org wrote:
> I have installed and configured an imap server (Courier). I have
> begun to move my mail over to it and to use procmail to deliver to it
> and then it hit me when I was doing some testing.
>
> ifile-gnus doesn't do nnimap. Damn. I really like using ifile to
> pre-sort my mail.
Maybe you or someone else can make it work with the Gnus registry?
It should offer enough functionality to make tracking of articles
possible, the way the current ifile-gnus does for nnml (IIRC).
spam.el offers an ifile backend which will send articles to the place
ifile thinks they should go. That could also be helpful, although of
course you don't have to use spam.el.
Ted
parent reply other threads:[~2004-07-20 14:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <874qo23jt3.fsf@phiwumbda.org>]
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=4n658irbix.fsf@lifelogs.com \
--to=tzz@lifelogs.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).