Hi, all.

I was going over in my mind how best I could improve the proxy.  Then it
hit me:  Why not do things the same way that spamc/spamd do?  That way,
only one process really chews up memory, and all the proxy does is field
the message, then send it through spamd rather than doing all the checks
within the script itself.

Thing is, I would rather avoid the expense of forking an external process,
like spamc.  Has someone written a Perl client that'll talk to spamd like
spamc does in C?

Thanks for any help.

--Ian.


_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to