--=-CWsOVojYiDXZ9fICAZQn
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
I've integrated spamassissin into my setup by having evolution do the
work. I've add it as a filter that evolution uses, shoots the msg
through spamassassin and uses the returned value to judge as spam or
not. This takes the work off my poor little mail server and keeps
everything at the app level so I just have messages moved to "SPAM" and
deleted there, just in case I need an e-mail that really isn't spam/
On Mon, 2003-07-07 at 13:48, Lynn David Newton wrote:
> Greetings,
>=20
> Would someone kindly summarize in a few sentences how
> spamassassin does its work? I.e., I know *what* it does
> -- takes email input, and either judges it normal and
> elivers it, or dispatches it according to the rules,
> while keeping logs and all.
>=20
> More pertinently, what I don't know is: *how( does
> incoming mail get passed to spamassassin? I use
> fetchmail to POP my mail from Cox. I also have procmail
> running with a bunch of rules of its own. Where does
> spamassassin fit in there?
>=20
> Apparently it must do its job *before* procmail (or
> whatever one uses to make final delivery) gets ahold of
> it, right? My procmail filters mail according to a
> complex set of rules that includes some anti-spam rules
> (and which I could simplify with spamassassin working),
> and then handes it to one of seven spool files.
>=20
> I've seen I can take single email messages and run
>=20
> cat messagefile | spamassassin
>=20
> and get wonderful and interesting output.
>=20
> Does anyone have or can anyone point to an existing
> bullet list of steps to take to get spamassassin
> actually functioning on a system -- something short and
> simple, like step (a), step (b), step (c) ... and not
> much more.
>=20
> It exists on my system (version 2.44), and I have a
> directory ~/.spamassassin with a couple of generic
> files that were evidently copied in the first time I
> tried to execute it from a command line, namely
> auto-whitelist and user_prefs, obviously a local
> configuration file for the rules that apply.
>=20
> Maybe I've already done what's necessary? I'm just
> missing the vital piece of information about how to
> start the engine. :-)
>=20
> Thanks,
--=20
Bryce C <
Plug@BryceCo.Net>
CoBryce Communications
--=-CWsOVojYiDXZ9fICAZQn
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQA/CeVG/wbq/C6yyPcRAlAUAKCzcR3mPvubECDOdnzAwntQCpsiSgCdGY0Q
EHJ7B/R/yMBQbJgL7G/ESYo=
=imVf
-----END PGP SIGNATURE-----
--=-CWsOVojYiDXZ9fICAZQn--
(text/plain)