Török Edwin wrote: > > Thanks for the suggestion. I've opened an enhancement bug: > https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1437
Nice ! 8-) > > >> Either way, nCOMMANDS still remain interesting when using a telnet >> client for, e.g., debug purposes. > > Yes, that is one of the reasons why I say that nCOMMANDs aren't likely > to go away anytime soon. > > If you want your app to support both <0.95 and >=0.95, the easiest now > is to use nCOMMANDS. > Since you are writing a milter, you control the filenames, its easy to > make sure they don't contain \n > (if they did, it wouldn't have worked until now anyway). Yes, it's a milter, which supports ClamAV since a very long time ago. I pass to clamd the path to the entire message (mail format). I don't worry with file decoding. Clamd already know how to do that, and do it very well. No need to reinvent the wheel. On the other hand, I indeed do that for spam check purposes, but this is a different history. > if you want to use the new features, such as IDSESSION and INSTREAM, you > can send these commands to clamd, > and if it replies UNKNOWN COMMAND, you can fallback to something else. > For example: > nIDSESSION\nnVERSION\nnEND\n > > Will reply UNKNOWN COMMAND for old clamd, and will reply with the > VERSION for new clamd. Thanks, I'll take a look to see how my filter can benefit from this new features. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
