Skip to main content
We are aware of an issue with a recent Apache update that causes proxied sites to return a "421 Misdirected Request" error. Please see the following article for more information and updates:
Websites show 421 Misdirected Request error while using EA Nginx

gmail rejecting emails from one of my domains

mmaciel
hello everyone so, gmail is rejecting emails from one domain, it returns an error message saying dkim and spf is not properly configured
Delivery to the following recipients failed permanently: * person='nathalia.basegio@gmail.com'>@gmail.com Reason: There was an error while attempting to deliver your message with [Subject: "asdfasdf"> to person='nathalia.basegio@gmail.com'>@gmail.com. MTA godaddyrelayserver.secureserver.net received this response from the destination host IP - 142.250.101.26 - 550, 550-5.7.26 This mail is unauthenticated, which poses a security risk to the 550-5.7.26 sender and Gmail users, and has been blocked. The sender must 550-5.7.26 authenticate with at least one of SPF or DKIM. For this message, 550-5.7.26 DKIM checks did not pass and SPF check for [mydomain.com] did 550-5.7.26 not pass with ip: [208.109.80.52 (godaddy relay server)]. The sender should visit 550-5.7.26

Comments

8 comments

Date Votes
  • cPRex Jurassic Moderator
    Hey there! If the issue is with the relay server IP, you'll likely need to add that to your SPF record like this: yourdomain.com. 14400 IN TXT "v=spf1 ip4:1.2.3.4 +ip4:4.3.2.1 ~all"
    as that would let you authenticate your messages from multiple IPs. If that doesn't help, reaching out to the relay provider would be the best option as they have likely run into this issue before.
    0
  • mmaciel
    Hey there! If the issue is with the relay server IP, you'll likely need to add that to your SPF record like this: yourdomain.com. 14400 IN TXT "v=spf1 ip4:1.2.3.4 +ip4:4.3.2.1 ~all"
    as that would let you authenticate your messages from multiple IPs. If that doesn't help, reaching out to the relay provider would be the best option as they have likely run into this issue before.

    hey Rex, thanks for the reply i did that, unfortunately it didn't work, but the error message now changed This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: user@gmail.com host dedrelay.secureserver.net [208.109.80.210] SMTP error from remote mail server after end of data: 550 5.2.0 589Gqijq3Q2SS589GqTTQm :DED: message not accepted due to spam ruleset Reporting-MTA: dns; myipsecureserver.net Action: failed Final-Recipient: rfc822;user@gmail.com Status: 5.0.0 Remote-MTA: dns; dedrelay.secureserver.net Diagnostic-Code: smtp; 550 5.2.0 589Gqijq3Q2SS589GqTTQm :DED: message not accepted due to spam ruleset
    before it would take a minute or two to receive the error message, now this one immediatly appears in my inbox as soon as i press send
    0
  • cPRex Jurassic Moderator
    Well, unfortunately it looks like they are just blocking you as spam now and not even checking anything in the headers. It would be best to reach out to that provider and see if they have any ideas.
    0
  • mmaciel
    Well, unfortunately it looks like they are just blocking you as spam now and not even checking anything in the headers. It would be best to reach out to that provider and see if they have any ideas.

    hey, so i added +include:secureserver.net at the spf record and now apparently it works, gonna do a few more tests, but already received a message from this domain to my gmail thanks Rex
    0
  • cPRex Jurassic Moderator
    Interesting - let us know how it works out!
    0
  • mmaciel
    Interesting - let us know how it works out!

    apparently it's fine now, sent a bunch of emails from different accounts under this domain to a bunch of different gmail accounts and all arrived thanks again Rex, i was so fixated on the godaddy ip, thinking the problem surely was with the relay server that i didn't even think of changing the spf myself hehe
    0
  • cPRex Jurassic Moderator
    I'm glad the more generic SPF record for GoDaddy worked well!
    0
  • sparek-3
    In my experience Gmail also requires a DMARC record, even if that DMARC record is something utterly stupid: [font="courier new">_dmarc 900 IN TXT "v=DMARC1; p=none" I've never been a huge fan of DMARC, because it's basically telling recipient mail servers how to react to failed SPF and DKIM authentications... which begs the question, why does SPF and DKIM need oversight? Where does the oversight end? Is there eventually going to be another record to tell recipient servers how to react to DMARC records?
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post