Email limit received from the same domain

Question

Email limit received from the same domain

Navigation

#1 by (1 votes)
#2 by (0 votes)

7

There are SPAM source verification policies that are based on the amount of emails that a particular domain is sending per hour.

These policies can be internal such as those applied by Google, or general as is the example of lists of SPAM.

When we talk about optimizing the sending of newsletters from our own solution the first concerns are not to lower the reputation of the sending IP nor to have the same IP present in the most common SPAM lists.

Looking at this, a question arose:

Nowadays, what is the limit that companies such as Google , Microsoft , Yahoo and others apply to discern whether sending is a reliable newsletter or a source of SPAM?

Of course, there are hundreds of methods in use to find out what SPAM is and what it is not, but what you want to deal with in this topic is the limit of emails, per minute, hour or day, which we can not exceed in order to ensure that for example Google will not consider a certain source address of SPAM when it is only sending reliable newsletters!

Then comes the need to know:

┌─────────────────┬─────────────────────┬───────────────┬──────────────┐
│  Controlado em  │  Tipo               │  Limite por?  │  Limite de?  │
├─────────────────┼─────────────────────┼───────────────┼──────────────┤
│  Google         |  Provedor de Email  │  Hora         │  100         │
├─────────────────┼─────────────────────┼───────────────┼──────────────┤
|  Microsoft      |  Provedor de Email  │  Dia          │  100000      │
├─────────────────┼─────────────────────┼───────────────┼──────────────┤
|  Spamhaus       │  Lista de SPAM      │  Dia          │  1000000000  │
└─────────────────┴─────────────────────┴───────────────┴──────────────┘

Following on trying to get these values or a reference line to plan the application efficiently came up this information:

Google Apps - Receiving limits (English)

...
If an account is the limit, a user can not receive any new email ...

┌─────────────┬──────────┐
│ Per minute  │  180     │
├─────────────┼──────────┤
│ Per hour    │  3600    │ 
├─────────────┼──────────┤
│ Per day     │  86,400  │ 
└─────────────┴──────────┘

But is this limit for Apps accounts, and for Gmail? And in the others? Is a storm being raised in a glass of water?

php spam phpmailer

asked by anonymous 29.10.2014 / 23:06

2 answers

How to change background with javascript? Dynamic Grouping of JSON Data

score 1 · Answer 1

The limits mentioned are for google apps, but they probably apply also to gmail.

However, these are inbound and outbound limits , which you are not interested in, unless you are intending to completely populate the user's inbox with your newsletter, which for me is spam .

What would interest you are IP upload limits , how many similar emails to different accounts gmail would accept before marking your IP as a spammer.

This information is not public and in reality gmail (and no ESP that you pay) should not use such a technique because all that a spammer would have to do to avoid the filter would be to limit the number of spam sent to a certain domain by day.

What you need to do to ensure that your email is not considered spam is to take care of the reputation of your IP, which is a complicated process ... Some tips to get you in the right direction:

Make sure your IP and other IPs in the vicinity have not been previously used by spammers. Starting now with a bad reputation is horrible. Check on list sites such as spamhaus and sorbs. Use mxtoolbox to see if your IP is not currently listed, and do so periodically. Ah, obviously your IP must be fixed .
Make sure your newsletters include a 'one click unsubscribe' link. And users who click on it do not need to sign in to remove themselves from their list and will no longer receive their newsletters.
Use a double opt-in process, the registration is only confirmed when the user clicks the link in the confirmation email.
Make sure the hostname of your MTA has an A record and that the reverse resolution is valid. Hostname - > A - > Hostname
Make sure your MTA can not be used as an 'open relay'.
Use the MXtoolbox tools to see if there are other things to fix in your DNS.
Ask your users to add it to your address book.

When these things are working properly, investigate:

DKIM
SPF
Feedback Loops
List-Unsubscribe header

The most important thing is to make sure that whoever is receiving your newsletter wants to receive it, you can remove yourself from the list at any time and your content is relevant.

score 0 · Answer 2

I think assuming that Google offers a free email to the end user as well as hotmail, there is no way to reach these users' mailboxes in these services efficiently, without a financial agreement, starting from a single IP. My tip would be that in case of mail marketing, you set up a large range of MX, and preferably in multiple domains. Thanks for metric blades already available!