Gnus development mailing list
 help / color / mirror / Atom feed
From: Arnd Kohrs <kohrs@acm.org>
Subject: automatically splitting conversations
Date: 09 Jun 2000 13:04:12 +0200	[thread overview]
Message-ID: <xljr9a7azf7.fsf@houle.eurecom.fr> (raw)

Hi,

I usually keep all my mail (other than mailing lists and archives) in
one folder.

However, sometimes it occurs that I want to keep some activities in
dedicated groups.  Examples are:

- discussions with a small group of friends on a particular subject (not
  the header!)
- mail exchanged for various job-related or personal projects.
- mail exchanged for online auction transactions

AFAIK, splitting these activities to other groups than my regular
mailbox, cannot be achieved automatically. 

Actually, I would want to declare something which corresponds
semantically to the following:

¨Split all the INCOMING mail, which refers to a given PARENT mail or group of
mails, in s DEDICATED folder.¨

In order to implement this there are some possibilities that I can
think of:

[Dirty Hack]
- when sending a mail from a DEDICATED folder, this folder name is
  encoded in the message-id of the outgoing mail.  All the responses
  will carry the information in the references header, and a splitting
  rule can be specified which identifies references with encoded folder
  names and splits it accordingly.

[Complex Hack]
- the previous scheme fails in the case when a thread was initiated by
  someone else, then manual interaction is necessary.  A better method
  would be, that splitting would check for incoming messages if they are
  descendents of any of the messages contained in the dedicated folder.
  This would of course be computational complex, but sometimes very
  convenient for the user:
  - the user identifies a discussion thread
  - he creates a dedicated group
  - and customizes it thus it received all descendents of contained
    mails via group-split.

Before I try to implement such functionality I just wanted to poll on this
list, if others think that it would be useful. Or even better, maybe it
is possible to achieve such a behavior with the existing means.  On the
other hand, how could this be best implemented?  

Cheers,
Arnd.
-- 
Arnd Kohrs  -  Institut Eurecom - http://www.eurecom.fr/~kohrs
              
The Active WebMuseum: Your personalized access to art paintings.
 Visit now ->  http://www.eurecom.fr/~kohrs/museum.html



             reply	other threads:[~2000-06-09 11:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-09 11:04 Arnd Kohrs [this message]
2000-06-10 19:27 ` Kai Großjohann
2000-06-11 20:22   ` Arnd Kohrs
2000-06-12 12:30     ` Arnd Kohrs

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=xljr9a7azf7.fsf@houle.eurecom.fr \
    --to=kohrs@acm.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).