How do I send 200 emails (not a newsletter) without running the risk of going to spam list?

Asked

Viewed 443 times

7

Every month we send 200/300 handwritten emails with variable text to the month’s customers (not a newsletter). Via PHP I can make the text dynamic, and send automatically, but the problem is sending 200 emails without the domain ending up in a spam list... Any idea how to do this?

  • 4

    Use your own service for this. The Mandrill, for example, allows up to 12k free emails per month.

1 answer

8


Send the authenticated emails you won’t have a problem with. In a small service I manage, more than 80,000 emails a day have been sent for more than 10 years and have never been spammed. Eventually you may have a problem regarding reverse dns, email headers and dns settings. But these are relatively simple things to solve. And also, avoid sending to those who do not authorize the receipt, because when you do this the person who receives usually denounces and so gets dirty the domain until it falls into the public databases of spammers. Then at that point you will have a certain difficulty in asking for the removal.

Care should also be taken that it is not enough just to send authenticated. You also need to make sure of the limits and standards of the environment, the server where the script will be run. Usually shared hosting detects long runs and blocks them. Others allow continuous executions, but detect email sending and impose a limit of 100 to 400 daily or monthly emails. Finally, you should consult the rules of your hosting provider.

Another observation is the email server that will be used to authenticate the submissions. One should also observe the limits of this mail server. gmail, for example, has a limit of 400 emails per day, but this limit varies with the type of account used.

In short:

1. Verifique as normas e limites do servidor de hospedagem
2. Verifique as normas e limites do servidor do email usado para autenticar
3. Verifique configurações de DNS reverso tanto para IPV4 quanto para IPV6
4. Não camufle o domínio do email que está enviando. seja o mais transparente possível

The bad point of authenticated sending is the delay in sending. Because each sending requires an authentication. It is possible to send legitimate emails without falling into spamlists, using the native function mail(), no authentication. But for this the server must be well configured. The important thing is that the sending server can be recognized and "audited" remotely in relation to its identity. In this case, the checks are done by the DNS settings. Therefore, avoid sending from a server that does not have a DNS domain. A subdomain can be used, for example.

However, the volume you want to send is small. It is possible to execute everything in less than 1 second even when authenticated. For this you will need asynchronous execution techniques.

  • Do you have any idea how I can authenticate emails ? I usually use php to send emails

  • 1

    With PHP itself you can send authenticated. Popular libraries like Phpmailer, Swiftmailer, among others are recommended. I particularly prefer Swiftmailer. There are also other means using the mail() native function itself, without using third-party libraries, but it’s a little more complicated when running on a shared hosting server without access to advanced administrative settings.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.