AppGini Community Forums

I am wondering if anyone else has this problem.

When a user signs up a welcome email is sent from Appgini. Unfortunately it seems that if the user has a Gmail account, the message is blocked and we receive this message.

Final-Recipient: rfc822; *****@gmail.com (I removed the user email for privacy)
Action: delayed
Status: 4.7.0 (This message does not have authentication information or fails to pass authentication checks. To best protect our users from spam, the message has been blocked. Please visit https://support.google.com/mail/answer/ ... entication for more information. a14si5653688ook.68 - gsmtp)

bruceholt wrote: ↑

2020-05-30 21:49

I am wondering if anyone else has this problem.

When a user signs up a welcome email is sent from Appgini. Unfortunately it seems that if the user has a Gmail account, the message is blocked and we receive this message.

Final-Recipient: rfc822; *****@gmail.com (I removed the user email for privacy)
Action: delayed
Status: 4.7.0 (This message does not have authentication information or fails to pass authentication checks. To best protect our users from spam, the message has been blocked. Please visit https://support.google.com/mail/answer/ ... entication for more information. a14si5653688ook.68 - gsmtp)

using phpmail or smtp? check admin settings page

I was using php but after having the issue changed it to smtp, SSL on port 465 but same issue.

Hi,

may this can help you.

To minimize the chance that your messages are marked as spam, set up these authentication methods:

Publish an SPF record https://support.google.com/a/answer/33786 for your domain. SPF prevents spammers from sending unauthorized messages that appear to be from your domain.
Turn on DKIM signing https://support.google.com/a/topic/2752442 for your messages. Receiving servers use DKIM to verify that the domain owner actually sent the message. Important: Gmail requires a DKIM key of 1024 bits or longer.
Publish a DMARC record https://support.google.com/a/topic/2759254 for your domain. DMARC helps senders protect their domain against email spoofing.
For SPF and DKIM to authenticate a message, the message From: header must match the sending domain. Messages must pass either the SPF or the DKIM check to be authenticated.

Thank you for the info. I will check if we have those and see how we go.