Re: projecthoneypot blocking access to bug reporting form

On Wed, Feb 25, 2009 at 4:20 PM, Jo Schulze <jo@feuersee.de> wrote: > Hi, > > I was just about to assign a feature request to HTML Template_Flexy but > I can't because > > We can not allow you to continue since your IP has been marked > suspicious by the http://projecthoneypot.org/, if that was done > in > error then please contact pear-dev@lists.php.net as well as the > projecthoneypot people to resolve the issue. > > When looking up my current IP (88.66.235.40) at > http://projecthoneypot.org it says > > This IP has not seen any suspicious activity within the last 3 months. > This IP is most likely clean and trustworthy now. (This record will > remain public for historical purposes, however.) > > To be more precise, the last (and AFAICS only) report is more than 7 > months old. In fact the IP is part of the dynamic IP pool of Arcor AG, > Germany (a german ISP), assigned to DSL dial-up connections. > > I don't think it is a good idea to include dynamic IP pools to blocking > lists at all, especially if they are that old. Chances are high that > the whole IP pool will get blocked because of one SPAM idiot who > reconnects (thus gets a randomly new IP) after every SPAM attempt. > > Either do a better checking against the blacklist or rm the whole thing > from bugs.php.net > Easy on the assumptions. ;-) If IPs from those pools were not included we would all drown in spam. In general, it would make sense for Arcor to block ports or shape traffic on their IP pool if it's known to be a host of abusers. I think Arcor can also contact ProjectHoneyPot and work with them on whitelisting and what not -- but they haven't. So far ProjectHoneyPot has helped us a lot to cut down on spam, but of course we can look into your issue and see if we can handle older reports in a more relaxed way. TIll