Damn all the spammers in the world.

pucky

Verified User
Joined
Sep 9, 2006
Messages
758
Dam all the spammers in the world.

Some bastard spammer is using a legit domain on one of our servers as the reply to email address for thousands and thousands of stock spam they are sending.

The result is thousands and thousands of bounced spam returning to server by the minute. Its so bad i can hardly read exim/mainlog while tailing the file.

I have already asked the site owner to terminate the site after we backed it up but that hasnt helped because the domain is still pointing to our nameservers.

The bounces are being rejected but its not stopping the delivery attempt. I already reduced the number of possible connnections to port 25 to only 20 connections but now legit users are complaining that they are getting "refused: too many connections" messages.

So the question is, why is delivery still being seen as going to our server if there are no more DNS records in place?

May every spammer in exhistance be so fortunate to choke to death on their own vomit, while they sleep. :rolleyes:
 
Unfortunately the DNS does not stop existing on the internet until the TTL (time to live) has expired and sometime longer than that. The TTL is typically set to 4 hours, just so you know :(

Regards,
 
resolveit said:
Unfortunately the DNS does not stop existing on the internet until the TTL (time to live) has expired and sometime longer than that. The TTL is typically set to 4 hours, just so you know :(

Regards,

I know that but there is no TTL anymore. The domain was terminate along with all the records more than 12hrs ago. This has been going on for 4days now, nonstop. This domain no longer appears in /etc/virtual/domainowners, domains and there are no DNS records on any of the other servers including this one.

If i visit the site, the default apache logo comes up. If a site is terminated in DA why isnt the site returning a page not found? Seems that sites terminated in DA always resolve back to the Apache screen instead of returning a page not found like it should.

Anyone know.
 
If this hasn't been resolved yet, try tracing the dns:

$ dig +trace example.com

To see why example.com still sees your DNS.

Jeff
 
Back
Top