# # Rate Limited by Google Bulk Email Senders Guidelines
APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

Rate Limited by Google Bulk Email Senders Guidelines

I've removed advertising from most of this site and will eventually clean up the few pages where it remains.

While not terribly expensive to maintain, this does cost me something. If I don't get enough donations to cover that expense, I will be shutting the site down in early 2020.

If you found something useful today, please consider a small donation.

Some material is very old and may be incorrect today

© May 2019 Anthony Lawrence


You might see a message like this in your Mail logs:

421-4.7.0 unsolicited mail originating from your IP address. To protect our users from spam, mail sent from your IP address has been temporarily rate limited. Please visit http://www.google.com/mail/help/bulk_mail.html to review our Bulk Email Senders Guidelines.

The message means what it says: Gmail will eventually accept the email, but it will be delayed.

I forward emails to my gmail account so that I have important messages in two places, and I recently noticed that this was causing these messages in my logs. As I am only forwarding to myself, I'm certainly not complaining to Google about spam, but of course I may be forwarding spam that I get myself. Was that why I got those messages?

At the page referenced above, Google makes several recommendations:

To ensure that Gmail can identify you:

  • Use a consistent IP address to send bulk mail.
  • Keep valid reverse DNS records for the IP address(es) from which you send mail, pointing to your domain.
  • Use the same address in the 'From:' header on every bulk mail you send.

We also recommend the following:

  • Sign messages with DKIM. We do not authenticate messages signed with keys using fewer than 1024 bits.
  • Publish an SPF record.
  • Publish a DMARC policy.

I felt I was meeting all of those recommendations except DMARC, so I added that. Still, the messages kept cluttering my INBOX. What was going on?

I was astounded when I found what may be the answer: a while back I had moved my mailserver to a new host and IP address. Amazingly, I forgot to have a PTR (reverse DNS) record created!

Of course I corrected that immediately. I don't know yet if that was the last piece Google needed, but it may well have been. It would certainly have helped if they were more specific in their responses!

If you found something useful today, please consider a small donation.

Got something to add? Send me email.

(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

-> Rate Limited by Google Bulk Email Senders Guidelines

Inexpensive and informative Apple related e-books:

Take Control of Pages

Take Control of OS X Server

Take Control of Automating Your Mac

Take Control of Upgrading to El Capitan

Digital Sharing Crash Course

More Articles by © Anthony Lawrence

Printer Friendly Version

Have you tried Searching this site?

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us

Printer Friendly Version

The people I distrust most are those who want to improve our lives but have only one course of action in mind. (Frank Herbert)

Linux posts

Troubleshooting posts

This post tagged:

Kerio Connect


Kerio Info

Kerio Pricing

Kerio RSS Feed


Unix/Linux Consultants

Skills Tests

Unix/Linux Book Reviews

My Unix/Linux Troubleshooting Book

This site runs on Linode