[Clamdmail-users] Project Under Development Again

[Zachary K. <pro...@en...>]

I have recently re-started development of this project, and I will 
shortly begin a re-write to:
	A) add SMTP reject support
	B) stop linking directly against clamav
	C) Add runtime configuration through env variables

SMTP-reject support: I'm planning to add support to allow clamdmail to 
return appropriate exit codes it's smtpd caller to indicate that the 
message should be permanently rejected. For anyone that simply wants to 
stop viruses and doesn't want to get 4000 notifications every time a new 
worm comes out, this is a handy thing. This mode will not replace 
sender/admin notification or quarantine mode, but will be mutually 
exclusive.

Call binaries: I'm planning to use exec() calls to binary interfaces for 
ripmime, clamdscan and spamassassin to provide version independence and 
greater flexibility in tool choices. I understand the value in not 
forking 40 times, but adding a couple of fork/exec combos to simplify 
the code and provide tool/version independence seems like a good idea to 
me. If anyone has an objection to this please let me know.

Runtime config: Currently clamdmail allows basically no runtime 
configuration, particularly if you're calling it with qmail-call. I'm 
planning to support all of the current command-line options as 
environmental variables (and probably remove command-line support, but 
I'm open to suggestions here). This will allow not only easier 
re-configuration, but will allow different configurations with only one 
installation if you're using something like tcpserver.

I've looked through the feature request list and responded to most of 
the requests. Some of them are a moot point after the re-write, and a 
couple of them I want to do (like templates for notifications) but I'm 
not going to do right now. Are there any features you're dying to have 
right now? Anything you'd like to see in the long term?

	Zach Kotlarek