From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: ding@lists.math.uh.edu
Subject: Re: using nnimap-split-fancy to split mail on server?
Date: Tue, 27 Jan 2015 11:55:38 +1100 [thread overview]
Message-ID: <87ioftdotx.fsf@building.gnus.org> (raw)
In-Reply-To: <85egqhdfiq.fsf@stephe-leake.org> (Stephen Leake's message of "Mon, 26 Jan 2015 04:04:29 -0600")
Stephen Leake <stephen_leake@stephe-leake.org> writes:
> It might make sense for the nnml imap interface to also split mail on
> the server, as long as it does not talk to the server after that
> splitting. I can see there could be problems with that.
If you're using IMAP as a mail source, then Gnus will download the
messages and delete them from the server, right? So there's nothing to
"split" on the server.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2015-01-27 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 16:48 Stephen Leake
2015-01-26 3:29 ` Lars Ingebrigtsen
2015-01-26 10:04 ` Stephen Leake
2015-01-27 0:55 ` Lars Ingebrigtsen [this message]
2015-01-27 9:25 ` Stephen Leake
2015-01-27 10:16 ` Stephen Leake
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=87ioftdotx.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=ding@lists.math.uh.edu \
--cc=stephen_leake@stephe-leake.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).