From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: using bbdb in split methods
Date: Tue, 27 Sep 2011 16:39:38 -0500 [thread overview]
Message-ID: <87sjnhsm05.fsf@lifelogs.com> (raw)
In-Reply-To: <87hb4rsa22.fsf@ucl.ac.uk>
On Mon, 05 Sep 2011 08:49:41 +0100 Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
ESF> I get way too much email (don't we all?) but using gnus with splitting
ESF> helps tremendously in tackling this problem. I use fancy splitting and
ESF> everything works just fine. The majority of my emails get sent to
ESF> appropriate mail folders (work colleagues, mailing lists, etc.) and I'm
ESF> pretty happy with his. However, I still have a "catch all" folder that
ESF> takes any emails that have not been split off. This still ends up being
ESF> too big and I'm forced to look at it more often than I would like.
ESF> I would like to further split emails that would end up here without
ESF> having to write any more rules based on specific "from" entries. What I
ESF> would like ideally is to be able to split off emails if the "from" or
ESF> even the "to" addresses are one that are known to BBDB, implying
ESF> messages from or to people I know or that I have corresponded with in
ESF> the past.
Eric, after the BBDB split you can split further with the Gnus registry,
using the parent message-ID from the references, then the subject and
the sender and the recipients. It works well for me though of course I
still have leftovers. The parent splitting is absolutely essential.
Ted
next prev parent reply other threads:[~2011-09-27 21:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 7:49 Eric S Fraga
2011-09-05 10:13 ` Eric Abrahamsen
2011-09-05 13:02 ` Eric S Fraga
2011-09-06 7:55 ` Eric S Fraga
2011-09-07 2:24 ` Eric Abrahamsen
2011-09-07 8:08 ` Eric S Fraga
2011-09-07 11:00 ` Rasmus
2011-09-07 15:03 ` David Engster
2011-09-27 21:39 ` Ted Zlatanov [this message]
2011-09-28 15:10 ` Eric S Fraga
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=87sjnhsm05.fsf@lifelogs.com \
--to=tzz@lifelogs.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).