Server blocked by Google for sending too many emails too fast - slow sending ?

[Silver_2000]

The entire server has been blocked as a sender for the past 3 days
Google error says

Diagnostic-Code: smtp; 450-4.2.1 The user you are trying to contact is receiving mail at a rate that
450-4.2.1 prevents additional messages from being delivered. Please resend your
450-4.2.1 message at a later time. If the user is able to receive mail at that
450-4.2.1 time, your message will be delivered. For more information, please
450-4.2.1 visit
450 4.2.1  'The Gmail user you are trying to contact...' - Gmail Help

My entire server only sends and receives about 2000 messages a day

One account does tend to send BIG dumps of email at once, but BIG is relative 100 or so

What I was hoping for is a way to slow the exim service to sending 20 messages per minute max for example
That way it doesnt hit Googles limits and the mail is processed pretty quickly

Any ideas ?

 

[mtindor]

Are those 100-email dumps all to a single Gmail address? If they aren't, then this isn't going to be an issue with your server. The message that Google provides suggests that the recipient Gmail user is receiving emails at too quick a rate, not that your server is necessarily sending too many emails in a short period of time. Of course, it could be that your server is sending too many emails to that user at once. Do you have a particular user who has a lot of mail coming into your server and then being forwarded out to Google?

I ask all of this because I have rarely if ever saw Google deferring emails because of the number of emails my server sends, even if my server is sending a lot of emails in a short time to the Gmail recipient.

It makes me wonder if that particular Gmail user has their email address forced in a bunch of spam somewhere and thus would be getting a lot of bounce emails back to the forged [Gmail] sender from poorly configured mail systems.

If you were to send an email to a different Gmail user around the time that you see those messages in your log, do your emails to that different Gmail user get delivered immediately?

I just don't think it is an issue with your server unless that particular Gmail user has an email account on your server and is forwarding that mail or he/she has some script on the server that is sending him a ton of emails from a forum or something.

Do your accounts on your server have SPF/DKIM enabled? Do you have SRS enabled in Exim?

M

 

[Silver_2000]

Its ANY email from my server to ANY google email
gmail
google apps
doesnt matter
I just tested it from an account that I just setup sending to a new google apps account
Its rejected
same reason
to summarize
google has NEVER received ANY email to the brand new account and the error is that that accouunt is recieving too many emails

Dont know what SRS is

 

[mtindor]

I'd recommend that:

1. you check your server's primary IP address against any blacklists.
- SenderBase
- Multi-RBL Check | The Anti-Abuse Project
- MultiRBL.valli.org - Blacklist, Whitelist and FCrDNS check tool

2. make sure your primary server IP address has proper rDNS in place.
3. make sure that you have DKIM / SPF set up for your domains.
4. make sure you don't have any infected websites sending out spam / or hijacked email accounts sending spam

Google doesn't ordinarily just defer mail from other servers, especially for multiple days, unless they sense bad behavior from your sending IP address.

M

 

[Silver_2000]

We are not in a black list
We dont have any other known issues
we have rdns
this has worked for years and something changed on friday
The server runs Clamav and other security -
Im not seeing any load that would suggest a spammer is using an account on the server
Exim is not seeing any additional load or more emails than normal
Its possible an infected site has installed its own mail relay - but that would impact the server load

I dont see that

 

[cPanelMichael]

Hello,

If you are sending mail in accordance with Gmail's guidelines, and your messages are still blocked, Google offers a troubleshooter you can use at:

Troubleshooting for bulk email senders - Gmail Help

Thank you.