Michael Parker wrote: > > On Wed, Oct 06, 2004 at 02:11:19PM -0700, [EMAIL PROTECTED] wrote: > > > > Is there any documentation for the spamd client interface? > > MIMEDefang can talk to clamd.sock directly, using the commands in man > > clamd, rather than spawning `clamdscan` processes. I checked man > > spamd and man spamc but couldn't find anything. I tried browsing the > > spamc source code but it's pretty hard going. > > > > Can anyone illustrate the spamc<->spamd conversation, so I can have > > MIMEDefang emulate spamc (talking to the socket directly using > > IO::Socket perl commands?) > > I've actually started a project to write a pureperl based client, to > hopefully be included in the SA source. I haven't been able to put as > much time as I would like into it, but you're welcome to take a stab. > > The protocol is documented in spamd/PROTOCOL in the 3.0 tarball, > you'll probably have to follow along in the spamd source as well. >
As long as people are thinking about new implementations of spamc/spamd, I'd like to make a couple suggestions: 1) make room for passing a reference to a message instead of the message itself, to reduce network latency when it is not necessary (for example, if the spamd chosen just happens to be on localhost (because it's part of a list of servers that are being balanced), then you'll waste a lot of time transfering the message through the socket, instead of just transfering the path to the file that contains the message). 2) make room for using other tools in addition to spam assassin (for example, running an external virus scanner), making spamc/spamd a possible nice general purpose means of distributing the load for email scanning (not just for spam marking type scanning) and even email delivery.
