balloons Posted July 7, 2021 Share Posted July 7, 2021 I was looking at some posts related to Gmail so I investigated them. I found the cause. example.heliohost.org. 14400 IN TXT v=spf1 +a +mx +ip4:65.19.143.6 ~all This is the Tommy server SPF record. There is no +a setting. The host name is added after +a. example: +a:example.hellohost.org From this, Gmail refused delivery due to indefinite SPF settings. However, some mail servers still deliver. I removed +a from this record. After that, emails sent from Gmail came to HelioHost. If you see this, please check this first with an email address that does not affect the sending and receiving of emails, and add a comment. With this confirmation, the administrator will be able to modify the name server. Quote Link to comment Share on other sites More sharing options...
wolstech Posted July 7, 2021 Share Posted July 7, 2021 (edited) That's gmail being gmail. The "a" by itself is in fact valid syntax. https://dmarcian.com/spf-syntax-table/ Without the domain after it, it means "look at the A record for this zone". That said, I'm sure we could modify the default zone tables to omit it or make it "+a:tommy.heliohost.org" or the like instead if it really does fix the issue. Gmail is by far the largest email provider we see. Do you have the rejection messages from Google by chance? I'd love to see what Google is saying. Edited July 7, 2021 by wolstech Ask for logs Quote Link to comment Share on other sites More sharing options...
balloons Posted July 7, 2021 Author Share Posted July 7, 2021 Perhaps the SPF record specs have changed several times. The old specifications are maintained. Google only specifies a:example.host.name for this SPF record. https://support.google.com/a/answer/10683907 I've seen other information as well, but most of them just mention a:example.host.name as well. Since ip4 and mx already exist on the same server, removing +a is sufficient. Quote Link to comment Share on other sites More sharing options...
Krydos Posted July 8, 2021 Share Posted July 8, 2021 Gmail receives emails from my Tommy account just fine. The most recent gmail issues were actually our firewall blocking gmail for opening too many connections. The gmail ips are whitelisted now. Quote Link to comment Share on other sites More sharing options...
balloons Posted July 8, 2021 Author Share Posted July 8, 2021 Yes, I think there is that too. There are many reasons why you may not be able to communicate with Gmail. (Recently, there has been abuse of spam) I was able to receive an email from Gmail after changing the SPF record, so I reported this. However, when you test this, the situation may have changed due to other factors. Quote Link to comment Share on other sites More sharing options...
balloons Posted July 17, 2021 Author Share Posted July 17, 2021 This post was information on cPanel. HelioHost lost cPanel and chose Plesk instead. The name server record may have changed due to this effect. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.