From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: mail splitting to another backend
Date: Fri, 18 Apr 2003 13:12:45 -0400 [thread overview]
Message-ID: <4nr87zivaq.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <ilu7k9snpzk.fsf@latte.josefsson.org> (Simon Josefsson's message of "Fri, 18 Apr 2003 10:56:15 +0200")
On Fri, 18 Apr 2003, jas@extundo.com wrote:
> I take back my idea -- nnimap cannot split mail from mail-sources,
> only from a IMAP mailbox. This is probably not very difficult to
> fix, though. Just replace the part that fetches mail from the
> INBOX, before it is splitted, with some code that gets mail from a
> mail-source. But to not interfer with normal mail-sources, I think
> this would mean adding a nnimap-mail-sources.
While your idea has its uses, I'm not sure it helps here. What I want
is very simple, and can't be achieved for the general case with the
one-time cross-splitting you demonstrate. I just want users to say
"split to destination nnxyz+abc:mail" in nn{mail|imap}-split-fancy and
have it work, like users would reasonably expect since the rest of
Gnus works with this convention.
What's below is generic enough that any backend can use it when
splitting, not just nnmail/nnimap - I only looked at nnmail.el though
so please correct any inaccuracies.
1) if nnmail-article-group returns a normal (non-prefixed) group name
do normal splitting (incidentally, should the ":" character be
allowed in group names?)
2) if nnmail-article-group returns a prefixed group name outside the
current server, put the message in a "split-queue" group and
remember the article number and the destination, perhaps with an
extra header inside the article body to make the destination
persistent even if the queue redistribution fails. Once mail
splitting is done, the queue group is redistributed by moving the
articles to their destination; this is fairly easy and any failed
moves will simply remain in the queue group until the user creates
the destination or deletes the articles.
3) if nnmail-article-group returns a prefixed group name that refers to
our own server (I have not yet figured out how to detect this),
either strip off the prefix and proceed as in (1) or just do (2),
it shouldn't make a difference.
I'd be happy to help implement the above, but I doubt I can do the
whole thing on my own.
Thanks
Ted
next prev parent reply other threads:[~2003-04-18 17:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 16:59 Ted Zlatanov
2003-04-17 18:56 ` Paul Jarc
2003-04-17 19:09 ` Ted Zlatanov
2003-04-17 19:53 ` Paul Jarc
2003-04-17 19:41 ` Simon Josefsson
2003-04-17 20:22 ` Ted Zlatanov
2003-04-17 20:31 ` Paul Jarc
2003-04-18 8:56 ` Simon Josefsson
2003-04-18 10:06 ` Kai Großjohann
2003-04-18 21:33 ` server parameter vs. server variable (was: mail splitting to another backend) Reiner Steib
2003-04-18 23:03 ` server parameter vs. server variable Paul Jarc
2003-04-20 14:35 ` Kai Großjohann
2003-04-20 15:11 ` Jesper Harder
2003-04-21 20:23 ` texinfo markup fixes (was: server parameter vs. server variable) Reiner Steib
2003-04-21 22:05 ` texinfo markup fixes Jesper Harder
2003-04-22 0:31 ` François Pinard
2003-04-22 0:36 ` Jesper Harder
2003-04-22 0:53 ` François Pinard
2003-04-18 17:12 ` Ted Zlatanov [this message]
2003-04-18 22:48 ` mail splitting to another backend Paul Jarc
2003-04-18 23:00 ` Ted Zlatanov
2003-04-27 3:09 ` Lars Magne Ingebrigtsen
2003-04-29 18:42 ` Ted Zlatanov
2003-05-01 6:55 ` Lars Magne Ingebrigtsen
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=4nr87zivaq.fsf@lockgroove.bwh.harvard.edu \
--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).