From: Christian Lynbech <christian.lynbech@ericsson.com>
Subject: Re: Fight spam with BBDB database?
Date: Thu, 27 May 2004 09:57:59 +0200 [thread overview]
Message-ID: <87ekp6fgjc.fsf@dhcp229.ted.dk.eu.ericsson.se> (raw)
In-Reply-To: <y68k6yyix1j.fsf@multics.mit.edu>
>>>>> "David" == David Z Maze <dmaze@mit.edu> writes:
David> Richard Wellum <rwellum@cisco.com> writes:
>> It's just an idea, wanted to see if it was possible. Could I filter all
>> email from users not in my BBDB database into a SPAM folder? That way I
>> could run through the SPAM folder periodically, if there is a legitimate
>> email in there I simply add to my BBDB database, and the next time it
>> will go into my Inbox?
David> That's not a great way to hunt for spam
I agree, however BBDB can still be very helpfull.
What I do is that I split mail into various mailinglist folders and
then I have two folders for the rest.
One folder is for personal mail and I use the BBDB for that. If the
sender has an entry in BBDB, the mail goes to "personal", otherwise
it goes to "misc". This means that I get all important mail separated
from the rest with all the spam winding up in "misc" (and the mailing
list folders).
------------------------+-----------------------------------------------------
Christian Lynbech | christian #\@ defun #\. dk
------------------------+-----------------------------------------------------
Hit the philistines three times over the head with the Elisp reference manual.
- petonic@hal.com (Michael A. Petonic)
next parent reply other threads:[~2004-05-27 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <y5au4qq2j3eg.fsf@irp-view5.cisco.com>
[not found] ` <y68k6yyix1j.fsf@multics.mit.edu>
2004-05-27 7:57 ` Christian Lynbech [this message]
[not found] ` <y5au65aho3z1.fsf@irp-view5.cisco.com>
2004-05-28 3:17 ` Paul Johnson
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=87ekp6fgjc.fsf@dhcp229.ted.dk.eu.ericsson.se \
--to=christian.lynbech@ericsson.com \
/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).