From: Jack Twilley <jmt+usenet@twilley.org>
Subject: Re: bbdb and nnmail-split-fancy
Date: Sat, 06 Apr 2002 12:46:59 -0800 [thread overview]
Message-ID: <86lmc05zcs.fsf@duchess.twilley.org> (raw)
In-Reply-To: <g08g028g2v9.fsf@zzz.cisco.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Michael" == Michael Cook <michael@waxrat.com> writes:
Jack> There are more sophisticated ways to get nnmail-split-fancy to
Jack> work with bbdb.
Jack> I have records for people that have gnus-private values and
Jack> records for mailing lists that have gnus-public values. It's
Jack> bbdb-gnus.el in bbdb. Very straightforward stuff.
Michael> the downside is that you need to manage those gnus-private
Michael> and gnus-public values in the bbdb records. which is a
Michael> little more work, at least.
Adding one line to one record that is from someone I know isn't too
much work for me. Especially when my bbdb gets the occasional bit of
litter in it as I add darn near every address I see.
Michael> the split-if-in-bbdb approach doesn't require you to edit any
Michael> of your bbdb records. and it makes for a nice spam detection
Michael> heuristic. if someone sends me mail, even if they address it
Michael> directly to me (like most spammers seem to do these days),
Michael> it'll still get split into my "other" folder instead of into
Michael> my "inbox" folder. i need to scan my other folder's
Michael> *summary* buffer occasionally to see if any non-spam ended up
Michael> there. but if that happens, i just select the non-spam
Michael> message and type `:' to add the sender to my bbdb. kinda
Michael> nice, i think.
This heuristic only works if you assume that no spammers are in your
bbdb. This is not necessarily true if all senders and recipients are
added to bbdb by default.
[...]
Jack.
(to each their own)
- --
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org
iD8DBQE8r17KGPFSfAB/ezgRAsBYAKDdXNiRwfUO5VDki5wfpCyB+RbJKgCfeYq7
5JT+io/1UK3QtVkVqrcGHMM=
=wFI8
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2002-04-06 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 22:58 Michael Cook
2002-04-04 0:49 ` David Z Maze
2002-04-06 7:07 ` Michael Cook
2002-04-06 7:39 ` Jack Twilley
2002-04-06 17:20 ` Michael Cook
2002-04-06 20:46 ` Jack Twilley [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=86lmc05zcs.fsf@duchess.twilley.org \
--to=jmt+usenet@twilley.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).