> Well, once again, the users managed to get their pc infected > with various s**t from the web.
Heh... same old story <g>... but I don't think it's something related to ASSP, otherwise this list may turn into some kind of "how to fight malware and fix PEBKAC" one :D > As a result at a clients' office (branch office actually, not the main > offices), there's a bot on a pc and is adding crap addresses on its > own ! Well.... first of all, add the IP of that PC to the "redlist" or, if you can't use a regexp and add it to redre; next, enable the ASSP rate limiter by properly setting the "LocalFrequency..." parameters (and since you're at it also set the appropriate regexp in "logging" to ensure you'll be alerted in case a sender goes over those limits; then (btw after killing that network admin, possibly using the Vlad method [1]) proceed setting up the branch office firewall so that people there will NOT be able to contact external hosts on port 25/tcp but will only be able to send mail through the "main" mailserver OR using some alternate port (for example, SMTP submit over SSL) [1] http://en.wikipedia.org/wiki/Vlad_III_the_Impaler ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
