Daniel L. Miller wrote: > Daniel L. Miller wrote: >> Daniel L. Miller wrote: >> >>>>> I may have perhaps found the answer. My exportExtremeFileAppend was >>>>> checked, and the exportextreme file was ... a trifle large. A "sort -u" >>>>> shrunk it to a manageable size, and ASSP is blocking connections again. >>>>> >>>>> May I recommend a warning message in the GUI, and possibly an overflow >>>>> error should be reported for larger files for when a idiot like me tries >>>>> to shoot himself in the foot? >>>>> >>>>> >>>>> >>>> Could you be more specific as to the size. >>>> >>>> >>> Of course I already deleted the file without taking note of the size - >>> but it think it was over 10M. Took a while to load ASSP each time too! >>> >>> >> I'm still blocking lots of others - but this particular site is still >> able to get past the IP blocks. Mail analyzer states that the IP is in >> both the exportextreme and the denysmtp. >> >> How are they getting through?!? > I see the message DOES have a valid SPF - does a valid SPF bypass the > penalty box blocks? Abbreviated headers follow:
But what does the maillog say? SPF comes AFTER the denysmtp, there is no way it could bypass it. Only these bypass(ignore) the denysmtp - ispip - accept all - nodelay - noprocessing IP - whitelisted IP - Penalty White Box Kevin ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
