#5 Problem with aliases.

[SpammyKnocker]

I think there is a basic problem with the current
domain aliases system.

- Since targetted websites often change their IP, they
often end up in an alias list and are then locked there
and never polled again.

- Since only the original domain for an IP with aliases
is ever polled, if this site is taken down, none of the
others that might still be active is ever polled again.

- Only the oldest domain of an aliases list is ever
polled, and if it fails, it "protects" all other aliases.

- If the original domain for an IP with aliases is
moved to another IP, spamdot seems to takes all of it's
aliases with it.

- Sometimes domains hosted with the same IP belong to a
single individual, but it might not be the case. If
that happens, others on the same IP get a free ride.

- All the aliases share the same AddTime value and will
get wrongfully erased once this expires

For these reasons, I think that aliases might not be
that good, and each target could be thought as a fully
independant entity with moving IP that sometimes happen
to share the same IP as others.

To prevent a single IP with many diferent domains from
getting all the attention (thus depriving all others
...) a count of domains that share the same IP shall be
maintained and polling frequency can be adjusted to be
something like the square root of the domain count (IE,
if 10 domains share an IP, the interval between polling
would be sqrt(10)=3.33 x what it would have been normally)

BTW, it's nice to see the project evolving again ...
(did you get my reply to your mail ?)