DDoS attack from *.*.*.*.bc.googleusercontent.com
Problem reported by Douglas Foster - 11/4/2026 at 7:50 PM
Submitted
Just a warning based on our results.

So far today, more than 2000 messages using more than 1000 email domain names and more than 1000 unique HELO names from slightly less than 500  unique IP addresses.   Started about 8am local time, and has varied between 100 and 250 per hour since then, with no evidence of stopping.   Google's poor client control makes them an attractive attack platform, and we suffer!

The domain names are impersonations, so we are containing the attacks by having Declude delete messages that we would normally send to quarantine.

The one consistent feature is that the reverse DNS is accurate (*.*.*.*.bc.googleusercontent.com), but we cannot easily use that to block messages because our gateway is currently SmarterMail, and it does not implement SMTP blocks based on the Reverse DNS name.  The defense is also made difficult because we have a couple of legitimate senders that use googleusercontent.com.
Terry Fairbrother Replied
could you add a routing rule to quarantine 'from address / from domain" googleuserconent.com and add a NOT condition against the real addresses "from address / from address"?

any real one that get through can be then added to the rule and then released
Douglas Foster Replied
.bc.googleusercontent.com is the reverse DNS name.   So the applicable routing rule could be "contains specific words or phrases" in field "email header" which contains ".bc.googleusercontent.com".  Then the action could be delete (or quarantine)

The lack of complex filtering rules are the weakness of most filtering systems.   Routing rules do move us in the right direction.
kevind Replied

You could score Reverse DNS (*.*.*.*.bc.googleusercontent.com) which could block messages at SMTP.  Additional tests might let you lower the score to allow mail from the legitimate senders that use googleusercontent.com.
Douglas Foster Replied
Yes, I logged a feature request to filter on Reverse DNS.   Ticket 288-3173DA79-0011 on April 16, 2026

Reply to Thread

Enter the verification text