WordPress doesn't send emails

Hi,

I also installed WordPress on Ubuntu/nginx and emails are not being sent out. The answer given above does not seem to help/indicates that it should be working out of the box. Are there special settings that are needed for emails to work?

Estou com o mesmo problema. Entrei em contato com o suporte e me responderam aqui…

Hey there!

Thank you for getting in touch with us! I would be more than happy to help.

I can certainly help with this. While our droplets are self-managed, I am happy to offer advice and brainstorm with you on this. There are a lot of reasons for this. To get a quick opinion on it, you can visit the link below and send an e-mail to the address that it generates you. This will give you a full report on how your e-mail appears to recipient servers.

http://www.mail-tester.com

These are the most common reasons why e-mails are filtered to spam folders:

1. Inconsistent headers
2. PTR lookup failure / no DNS record matching PTR
3. SPF Failure
4. Content

Inconsistent headers could be something like you sending from your server but in the ‘From’ field it shows that it was sent from somewhere else, like Yahoo, Hotmail, etc. The ‘From’ field should show an address that your server should be sending as (typically your domain).

You should make sure that your server’s hostname is a fully qualified domain name (example: server.mydomain.com) and that the droplet is named to match, so that the PTR record is set. Additionally, your DNS should have that hostname (example: server.mydomain.com) pointing to your droplet IP address so that reverse lookups are consistent.

Your SPF record is a DNS record of the type ‘TXT’ which includes either a reference to a DNS record that points to your droplet IP address or the droplet IP address itself. For example, if I want to send mail as mydomain.com and I want to send from my website, as well as a droplet with the IP of 1.2.3.4, my SPF record might look like this:

‘v=spf1 +a +ip4:1.2.3.4 ~all’

The ‘~all’ tells the receiving mail server to basically do what it thinks is best if the mail does not match the ‘+a’ (domain’s primary A record) or the ‘+ip4:1.2.3.4’ (the droplet’s IP address). You can also use ‘-all’ instead which suggests to the recipient mail server that any e-mail not originating from these points should be discarded.

Finally, content. Your content can be read as spam whether you intend for it to be or not. Try sending e-mails without long signatures, images, brand names, or website names to rule out the content of your e-mails. However, keep in mind that past content can impact your future e-mails as well.

Now, it is important to note that the most common belief is that blacklists cause filtering to spam folders. In most cases, blacklisting will actually cause e-mail rejection, not filtering to spam folders. However, it is certainly a possibility, even if not a probability, that blacklistings can impact what folder your e-mails land in. You can look up blacklistings for your IP address here:

http://mxtoolbox.com/blacklists.aspx

Do note that not every blacklist is relevant. Recipient servers have to actually use them for them to matter. Many are not widely used, and therefore do not matter. If you question whether this is the case with a particular blacklist, feel free to ask us, we generally know which ones are important.

If you have any other questions, please let us know, we are always here to help :)

Thank you,

Nick Platform Support Specialist DigitalOcean

ref:_00Do0IjOV._5001NV5lJD:ref

I have the similar problem and I wish DO looks into this and makes it work out of the box.