>> 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
> Nop ! NO knowledge on regex, no knowledge on redlist. > I will avoid using both. > > Also, no time for _that_ learning curve. At least, not now. > Thanks anyway ! Ok, so give up using ASSP and move on, sorry to say this but either you want to solve an issue and have it *solved* or you're just trying to "band-aid" a screwed setup and in this latter case, given that you don't WANT to get a grip on the tool(s) you're using, I don't think I or anyone else here will be able to help you; all in all we're dealing with ASSP here and people using it is supposed to *know* or at least be WILLING to know how it works; if that isn't the case, then, I think that everyone here has better stuff to do and in any case doesn't get paid to help others not even willing to help theirselves > I can do this. It's very high (VERY high) maintenance though and > I thought that _at least_ for that client I wouldn't have to do it No, it's not "high manteinance" it's the rule of thumb, if you run a corporate network which has its own mail system you MUST close port 25 from clients and only allow that from the mail servers; then, by the way, the business is yours so you are free to choose how to screw things up, not my problem at all ------------------------------------------------------------------------------ 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
