>     There is no need to tell their ISP.  Their ISP may
> not be responding.  Blocking the word "HTTrack"
> everywhere would be easier.

It would also harm the vast marojory of its users, who are respecting the
default settings, and who rely on offline browsers such as httrack to get
Internet access.

(see also <http://www.httrack.com/html/abuse.html#WEBMASTERS>)

> You are creating a tool for one end to get the
> benifit and the other end to pay for it.  It's like
> providing guns to the teenagers and telling them not to
> abuse it.

Humm. 

You were probably hit by high-speed and/or numerous multiple connections,
which is impossible to acheive using reasonnable settings.

I think the main problem is that bypassing hard limits should not be feasible
by regular users (that is, not webmasters or programmers themself). I will
enforce in the next release protections to prevent users from setting up more
than what is "reasonnable" (maybe a hard limit to 4 connections, and a hard
bandwidth limit)

I perfectly understand how serious the problem is, and I will setup the
necessary protections that should get rid of these problems in the future. But
you also have to understand that as a free software developper, I have no
reason to allow such abuses (i.e. I will not earn any money, like certain
commercial products). But I will never be able to stop all of them. Using
wget, you can setup multiple sessions in parallel, by starting, say, ten
mirrors, and you will end up with exactly identical problems (wget is not
throttling the bandwidth by default, for example - you can easily clobber a
fast DSL line, evey using one connection)

I hope that these future limits will solve the problem. But you will still be
vulnerable if someone uses another similar software, and setup unreasonnable
limits.