Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/26/2024 in all areas

  1. root@control [~]# dig +short TXT @ns1.heliohost.org stichtingdecitadel.nl "v=spf1 ip4:64.62.151.106 ip6:2001:470:1:1ee::2009 include:smtp.spf.ziggo.nl ~all" root@control [~]# dig +short TXT @ns2.heliohost.org stichtingdecitadel.nl "v=spf1 ip4:64.62.151.106 ip6:2001:470:1:1ee::2009 include:smtp.spf.ziggo.nl ~all"
    1 point
  2. DKIM, SPF, and DMARC have been set up for the domain stichtingdecitadel.nl. We recommend sending a test email to https://www.mail-tester.com/ to make sure that everything is set up correctly. If you get less than a 10/10 score please post a link to the full report so we can help you fix any other issues that there may be. Plesk frequently produces DKIM values that are too long to fit on a single TXT record. In those cases you must break the TXT record into 2 pieces. You can take a look at the DNS zone now if you want to see how it's done.
    1 point
  3. Plesk does not have the ability to talk to our DNS, so these will never set up on their own. Also, several IPs in that SPF (notably the .77 and .67 IPs) are obsolete or irrelevent (.66 and ::3 don't host any user accounts and would never send user emails). You only need the .106 and :2009 IPs for Johnny. I'll let Krydos add the DKIM value as I cannot figure out why that record causes the zone file to become invalid (named-checkzone comes back invalid with a syntax error on the line with the key if I add it, so I removed the DKIM line for now). SPF and DMARC are added.
    1 point
  4. I just checked and they were set up already but SPF was configured for the wrong IP address. I've corrected that issue and email deliverability should improve in the next few hours. If you continue to have issues after a few hours, please use mail-tester.com and post the report here so we can see if there's anything else we can do to assist with email that isn't delivering.
    1 point
  5. 1 point
×
×
  • Create New...