On Fri, Jul 12, 2002 at 06:34:00PM -0700, Brandon Knitter wrote: | Did I read something about a spamd process that the spamassassin client (perhaps | a this client) can talk to? If so, am I to assume that this thin client would | send the mail to spamd and spamd would send back the results. Meaning that I | could have REALLY light weight mail machines which send the message to a spamd | on a beefier machine for processing?
Correct, except that the thin client is called "spamc" and is written
in C (to avoid perl's startup overhead).
| Also, if this *is* the case, and I apologize I've not had time to crack open the
| code yet:
| 1. What is the transport protocol and format (is it proxy-able)?
Use tcpflow (or the source) to find out. It looks fairly simple, and
is an in-band protocol (unlike FTP).
| 2. What happens if the spamd server is down?
spamc returns the message unfiltered.
You could, of course, modify it to exit with a certain exit code, and
then configure your delivery system to defer the message in that
situation.
-D
--
In his heart a man plans his course,
but the Lord determines his steps.
Proverbs 16:9
http://dman.ddts.net/~dman/
msg07361/pgp00000.pgp
Description: PGP signature
