There is an unwanted side effect of the change to the behaviour of ForcePBExtreme in build 0.1.11 of ASSP 1.60. If a sending MTA sends exceeds the extreme penalty threshold in a single session, it is allowed to keep sending in that session. Witness the following log extract (where PenaltyExtreme is set to 150):
Oct-15-09 18:26:33 id-27593-00009 [InvalidAddress] 83.237.113.114 <rash3...@recalor.com> user unknown agx...@ourdomain.com Oct-15-09 18:26:33 id-27593-00009 83.237.113.114 <rash3...@recalor.com> added 25 (user unknown agx...@ourdomain.com), total score for this message is now 25 Oct-15-09 18:26:33 id-27593-00009 [InvalidAddress] 83.237.113.114 <rash3...@recalor.com> user unknown agy...@ourdomain.com Oct-15-09 18:26:33 id-27593-00009 83.237.113.114 <rash3...@recalor.com> added 25 (user unknown agy...@ourdomain.com), total score for this message is now 50 Oct-15-09 18:26:33 id-27593-00009 [InvalidAddress] 83.237.113.114 <rash3...@recalor.com> user unknown agz...@ourdomain.com Oct-15-09 18:26:33 id-27593-00009 83.237.113.114 <rash3...@recalor.com> added 25 (user unknown agz...@ourdomain.com), total score for this message is now 75 Oct-15-09 18:26:33 id-27593-00009 [InvalidAddress] 83.237.113.114 <rash3...@recalor.com> user unknown agv...@ourdomain.com Oct-15-09 18:26:33 id-27593-00009 83.237.113.114 <rash3...@recalor.com> added 25 (user unknown agv...@ourdomain.com), total score for this message is now 100 Oct-15-09 18:26:34 id-27593-00009 [InvalidAddress] 83.237.113.114 <rash3...@recalor.com> user unknown agt...@ourdomain.com Oct-15-09 18:26:34 id-27593-00009 83.237.113.114 <rash3...@recalor.com> added 25 (user unknown agt...@ourdomain.com), total score for this message is now 125 Oct-15-09 18:26:34 id-27593-00009 [InvalidAddress] 83.237.113.114 <rash3...@recalor.com> user unknown agy...@ourdomain.com Oct-15-09 18:26:34 id-27593-00009 83.237.113.114 <rash3...@recalor.com> added 25 (user unknown agy...@ourdomain.com), total score for this message is now 150 Oct-15-09 18:26:34 id-27593-00009 [InvalidAddress] 83.237.113.114 <rash3...@recalor.com> user unknown agp...@ourdomain.com Oct-15-09 18:26:34 id-27593-00009 83.237.113.114 <rash3...@recalor.com> added 25 (user unknown agp...@ourdomain.com), total score for this message is now 175 Oct-15-09 18:26:34 id-27593-00009 [InvalidAddress] 83.237.113.114 <rash3...@recalor.com> user unknown ah...@ourdomain.com Oct-15-09 18:26:34 id-27593-00009 83.237.113.114 <rash3...@recalor.com> added 25 (user unknown ah...@ourdomain.com), total score for this message is now 200 Oct-15-09 18:26:34 id-27593-00009 [InvalidAddress] 83.237.113.114 <rash3...@recalor.com> user unknown agp...@ourdomain.com Oct-15-09 18:26:34 id-27593-00009 83.237.113.114 <rash3...@recalor.com> added 25 (user unknown agp...@ourdomain.com), total score for this message is now 225 Oct-15-09 18:26:34 id-27593-00009 [InvalidAddress] 83.237.113.114 <rash3...@recalor.com> user unknown agz...@ourdomain.com Oct-15-09 18:26:34 id-27593-00009 83.237.113.114 <rash3...@recalor.com> added 25 (user unknown agz...@ourdomain.com), total score for this message is now 250 Oct-15-09 18:26:34 id-27594-06283 [InvalidAddress] 89.230.134.67 <ballar...@rothe1.com> user unknown agz...@ourdomain.com I think ForcePBExtreme should be enforced at connection time *and* (as before) per message thereafter. -----Original Message----- From: Fritz Borgstedt [mailto:f...@iworld.de] Sent: Thursday, October 15, 2009 1:23 PM To: ASSP development mailing list Subject: Re: [Assp-test] Feature Request re IP Penalty Blocking ASSP development mailing list <assp-test@lists.sourceforge.net> schreibt: >Unlikely they >will send you legitimate mail in the future anyway, more likely they >will send spam after they expire from PB. Just my opinion... However in the newest version of V1 (1.6.0) the meaning of ForcePBExtreme has changed: Enforce Early PenaltyBox Extreme Blocking (ForcePBExtreme) If set and DoPenaltyExtreme is enabled, ASSP will do DoPenaltyExtreme immediately after connection. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
