From: Jake Colman <colman@ppllc.com>
Subject: Re: Spam Management When Using nnimap
Date: Thu, 15 May 2003 17:19:31 -0400 [thread overview]
Message-ID: <76of23di1o.fsf@newjersey.ppllc.com> (raw)
In-Reply-To: <m365obhqe8.fsf@radon.sfeng.sourcefire.com> (Chris Green's message of "Thu, 15 May 2003 17:05:35 -0400")
>>>>> "CG" == Chris Green <cmg@sourcefire.com> writes:
CG> http://lifelogs.com/spam/spam.html seems to be the best tutorial for
CG> this.
But where is the determination of what constitutes a spam email? Unless I
missed something, there is nothing in that tutorial that shows me how/what to
use as hook in gnus so that messages are automatically clasified as spam or
ham.
--
Jake Colman
Principia Partners LLC Phone: (201) 209-2467
Harborside Financial Center Fax: (201) 946-0320
902 Plaza Two E-mail: colman@ppllc.com
Jersey City, NJ 07311 www.principiapartners.com
next prev parent reply other threads:[~2003-05-15 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 20:10 Jake Colman
2003-05-15 21:05 ` Chris Green
2003-05-15 21:19 ` Jake Colman [this message]
2003-05-16 16:43 ` David Z Maze
2003-05-16 19:10 ` Jake Colman
2003-05-17 23:38 ` David Abrahams
2003-05-20 18:45 ` Ted Zlatanov
2003-05-20 18:41 ` Ted Zlatanov
2003-05-20 18:39 ` Ted Zlatanov
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=76of23di1o.fsf@newjersey.ppllc.com \
--to=colman@ppllc.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).