From: Jake Colman <colman@ppllc.com>
To: ding@gnus.org
Subject: Re: Auto-Filing Replies to an Email
Date: Thu, 17 Jan 2008 08:51:08 -0500 [thread overview]
Message-ID: <76zlv4blwz.fsf@dev-d01.ppllc.com> (raw)
In-Reply-To: <86myr5zl1q.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 16 Jan 2008 12:23:45 -0600")
>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
TZ> On Wed, 16 Jan 2008 11:27:45 -0500 Dave Goldberg <david.goldberg6@verizon.net> wrote:
>>>>>>> On Wed, 16 Jan 2008 09:55:08 -0500, Jake Colman <colman@ppllc.com> said:
>>> I use message groups to organize my email. Incoming emails that
>>> cannot be automatically sorted are manually moved into an appropriate
>>> group. I use gcc-self so that messages sent from a specific group are
>>> viewable in that folder. Is there a way for replies to an email sent
>>> from a group to be automatically moved to that group?
DG> You mean if someone replies to your message gnus should automatically
DG> process the reply into the "right" group, is that correct? You can
DG> try nnmail-split-fancy-with-parent. I've never tried it myself - the
DG> last time I looked it didn't support imap and so was not useful to me.
TZ> The Gnus registry will do it, see gnus-registry.el for setup
TZ> instructions. I'm in the process of cleaning it up and will write
TZ> proper docs when it's done.
TZ> It supports nnimap among others.
Well this looks exactly like what I'm looking for. I'll try and it and see.
Thanks!
--
Jake Colman
Director of Development
Principia Partners LLC
101 West Elm Street
Suite 620
Conshohocken, PA 19428
+1 (610) 755-9786
www.principiapartners.com
prev parent reply other threads:[~2008-01-17 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 14:55 Jake Colman
2008-01-16 15:42 ` Tassilo Horn
2008-01-16 16:27 ` Dave Goldberg
2008-01-16 18:23 ` Ted Zlatanov
2008-01-17 13:51 ` Jake Colman [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=76zlv4blwz.fsf@dev-d01.ppllc.com \
--to=colman@ppllc.com \
--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).