Notes on new IPBlock code, 4.25-11

Raymond Dijkxhoorn raymond at PROLOCATION.NET
Mon Dec 1 19:58:16 GMT 2003


> connections blocked out.  But, the rogue machine had flooded my
> with several thousand messages in those 13 minutes, and it took nearly
> two hours for this flood to be processed by my server.  A lot of these
> messages were subsequently deleted as high-spam by Spamassassin and MS,
> or doublebounced, or were blocked by AOL (the target site).  Some got
> delivered.  The tsunami of spam was already on my mail server by the
> time MS shut the door, since IPBlock is run last in the MS process.

Another thing you could do is use the simple script i have running. It
can clean out your in and your out queue, i made it for bot h sendmail
and exim. If you have a IP in your accesslist with DENY it will lookup
the files of that sender and delete the according q* and d* files
automaticly. That will clean your queue for the offending IPs amazingly
fast. :) If you proceess the queue most likely you will end up in AOLs
spamblock in a few days.

If people are interested i can mail it.


More information about the MailScanner mailing list