Dear Charles Marcus > Ummm... if your script changes the way ASSP works (enables it to handle > per domain and per user settings for many of the functions) - then I am > at a loss as to how it 'has NOTHING to do with the assp project'... > There is nothing to change on assp . ASSP already(!) permits to use all filters per domain (yes per domain) with spamlover. It's enough a script which list user domain name , and an enable/disable button. Enable remove the domain from the spamlover flat file filter (for example file:helo_spamlover ), disable add the @domain to a spamlover flat file. Then per domain , I added a log button near each domain , which simply execute a tail maillog (for that domain) . My scripts are only a way to manage the spamlover flat files for each filter ! So they are really independent from assp , I didn't touch a single line of assp . The most difficult thing was instead to create a script to extract all email from a cpanel server and put them on local file . I was able to create it and it executes about 1000/email each 0.5 sec. It's so fast that I can execute it every 30 minutes , so the local email list is always updated . I decided to not share these scripts also because these will work only on a server managed by Cpanel . (also if the idea could be used with any other linux or windows hosting control panel)
There are only , I repeat only, 2 things that assp cannot do "per domain" . 1) whitelist per domain and 2) Bayesian Confidence Level per domain Also if 1) and 2) could be solved , but I cannot give you code suggestions because I write in php , I could give you only suggestions to do that... (but Frits on a post already replied that is not interested to point 1 , while no reply to point 2 as I can remember) , to solve the problem with 1) and 2) I leave the Bayesian Confidence Level fairly high . And as of now no problem with whitelist also if it's shared . So the key to use assp per domain is to create spamlover flatfiles . I am currently using my scripts on several Cpanel servers ; most clients are appreciating them a lot - A small percentage find the bayesian filters fairly complicated , so they simply disable them on their control panel (adding their domain name to the spamlover bayesian filter). Also if assp was not born to work per domain , spamlover flat files , permits to do that in a really easy way !! Graziano ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
