Hello, On 08/26/2010 10:34 AM, pete wrote:
A small bugreport again, in http://clapf.acts.hu/wiki/doku.php/howto:ubuntu_clapf_mysql_libclamav the useradd comment specifies 777 as the new user id, but "id" says 778, which is probably not possible. I tried on 10.04 and the id is 777 :)
Though it's not my howto, however I corrected it :-)
Do you have a roadmap for 0.4.5? Will there be an rc3? How far is rc2 from -current, which one should i install for a new system?
Well, no. I wanted to release the final 0.4.5 a week after rc2, however a few LDAP related issues emerged, and I still have some to resolve. After this I will release rc3, and if everything is fine, then the stable 0.4.5 a week later (or so). If you are using ldap with clapf and using the webui, I'd suggest you wait a day or so, until I fix the issues mentioned before, otherwise use the latest nightly build, as it's the closest to the rc3 version. And rc3 is supposed to be the same as 0.4.5 (unless a bug is found). If you are interested in the roadmap of 0.4.6, then I want to add support for white/blacklist to be stored in memcached. Another issue is to create user groups who share the same view of what is spam or ham. Let's say you have a shiny box running clapf, and filter emails for a university with students. Perhaps they consider viagra emails as spam, but what if there's also a chemistry class, who are interested in viagra (not the spam, but the product)? The right solution would be to create a distinct token group for the chemistry class. OK, you can assign a distinct uid for everyone (and it works), but it might be useful if the members of the chemistry class share the same token group (ie. the global tokens and the 'chemistry tokens' with uid=5). I gave a silly idea to Gabor to create the users of the chemistry class with the same clapf user id. However I forgot the uid field was unique, so it couldn't happen. A wierd workaround in the current version could be to create a single user for the chemistry class (eg. uid=5), then assign all the chemistry class emails to this user. This may work, however you can forget the quarantine feature. So In the 0.4.6 series I will add a correct solution to this problem. So these things will be definetely added to 0.4.6, and of course if you have a idea what to include more, I consider adding it. Best regards, Janos
