Digital Ocean, G Suite, SendGrid, Namecheap

Suporte Instalação
1

Estou tendo muita dificuldade para fazer o e-mail funcionar com meu novo servidor Discourse.

Estou usando a DigitalOcean para hospedagem. Não parece haver nenhum problema por lá. O servidor está em execução e consigo fazer login.

Estou usando o G Suite como e-mail de administrador, mas não para gerenciar os e-mails do site.

Estou usando a Namecheap para DNS e registro de domínio.

Estou usando a SendGrid como provedor SMTP para o site. Já tentei todas as combinações possíveis de verificação que consegui imaginar: usando o domínio de nível superior, usando o subdomínio, removendo as informações de DNS fornecidas pela SendGrid para inserir na Namecheap, adicionando o domínio a uma lista de permissões do G Suite (isso é mesmo necessário?).

Consegui fazer com que os e-mails fossem enviados. Pela SendGrid, vejo que e-mails de teste foram enviados pelo Discourse, mas eles nunca são entregues. A seguinte informação é exibida na mensagem de erro da SendGrid:

Recebido por gmail-smtp-in.l.google.com

Bloqueado

O servidor do Gmail bloqueou a entrega desta mensagem. Embora não tentemos reenviar esta mensagem, tentaremos enviar novas mensagens para este endereço no futuro.

Você pode visualizar todos os endereços em sua [Bloqueios]
Resposta completa do servidor do Gmail:

550 5.7.1 E-mail não autenticado de do.c não é aceito devido à política DMARC 5.7.1 do domínio. Entre em contato com o administrador do domínio do.c se esta for uma correspondência legítima. Visite 5.7.1 para saber mais sobre a iniciativa DMARC. m55-v6si4266550qtc.214 - gsmtp

Isso restringe meu problema estritamente à SendGrid e à verificação de domínio, ou é algo mais? De qualquer forma, a SendGrid nunca quer verificar depois que eu coloco as informações que eles forneceram na seção DNS da minha Namecheap.

2

As it says, Your dmarc record is not correct.
You can find the correct dmarc value in sendgrid and that should be updated into your dns.
Please correct it or contact sendgrid for assistance.

Just by chance, is it a one-click install app from DO?

3

@itsbhanusharma, yes. I did the one-click Discourse setup. Everything went very smoothly up until the SMTP setup. I’ve put in a ticket with SendGrid and am waiting for their response.

4

What is the notification email in your discourse admin? I think that needs to be corrected.

5

It is currently set at noreply@unconfigured.discourse.org.

When going through the setup wizard I chose for the system to handle mail so the one G Suite account I have to accompany the site info@mydomain.com is not flooded with messages, if I’m even understanding it correctly.

6

It can’t be @unconfigured.discourse.org in any case.

Please change it to @(your-discourse-domain) or the domain that’s verified with sparkpost first. I hope that’ll fix it.

Also, you may have to tweak your smtp port as DO may be blocking common SMTP ports on your account.

7

@itsbhanusharma, I made your suggested changes and it worked, although the message did go to my spam folder and is still showing “via SendGrid”. I’m guessing the way to solve that is through domain verification with SendGrid and that will be between me and them.

8

Exactly. They should have provided you some DNS records to create. Those records take care of the whole verification process.

9

Great. Thanks so much for the help. Now I’m wondering if I need to go back and undo some of the things I did like whitelisting my G Suite account with SendGrid and stuff like that.

10

Not immediately, first step that I’d take is to make sure sendgrid is happy with my domain and then I’d test the quality of emails sent using mail-tester.com or similar service.

Once that’s all fixed then only I’d lax any whitelist

11

As it’s set up now, while going through all the various forums trying to troubleshoot my problem I followed one tutorial that had me go into my G Suite settings and whitelist Digital Ocean, not SendGrid like I said. Because that wasn’t related to my actual problem is it necessary anymore or could it cause any problems in the future?

It actually wasn’t even whitelisting. It was SMTP relay service where I added my droplet IP address.

12

While it won’t really cause any problems as long as you retain the IP it can possibly cause spam whitelist if you leave the IP and other owner is a notorious spammer.

So it’s okay to remove it. Also, DO is not sending emails from it’s own IP either. Those are sent from sendgrid.

13

Great. Thanks again for the help.

14

While I’m able to get emails delivered to people who register for the forum now (albeit in their spam folder), I now am having trouble sending admin emails. When I attempt to make a member of the forum and admin, I get the message saying to check my email. My single G suite email address is info@mydomain.com. SendGrid can never seem to send a message from info@mydomain.com to info@mydomain.com. This is quite a problem because I can’t make anyone else an admin because I can never finish the process. There error I get from SendGrid is:

The mydomain.com server blocked this message from being delivered. While we won’t try to send this message again, we will attempt to send new messages to this address in the future.

You can view all addresses in your Blocks suppression group. Learn more.

Full response from the mydomain.com server:

error dialing remote address: dial tcp 167.89.106.64:0->162.255.119.167:25: i/o timeout

15

You should check the mail debugging document. The problem is between sendgrid and your mail server that is refusing connections from sendgrid.

16

I’m using Namecheap, so I had set up all of my SendGrid information CNAME records, but in the “Mail Settings” portion of the Advanced DNS page I didn’t have anything selected. Once I selected Gmail everything began to work. I swear I’d thought I had read something about if you’re setting up SendGrid you don’t need anything the Mail Settings section. Things appear to be working now.