DKIM not available in Plesk, marking all emails as spam

[Xavier12]

Hey guys,

Hope you're well and happy holidays!

So, I have been searching everywhere online and have not come to a fully working conclusion with the issue regarding outgoing emails going to spam via gmail, hotmail, etc.

Domain keys are activated, but it seems that domain keys is deprecated, making it useless when it comes to spam detection for email servers such as google, aol, etc.

The only alternative found was here: http://blog.matoski.com/articles/spf-dk-dkim-plesk-debian/

But that means that every customers DKIM will have to be created manually via command line. This would be a mission when having over 500+ ongoing customers signing up.

What is the true automated alternative for this issue? Will you guys be implementing DKIM automation for Plesk? I am pretty much against trying to use c(p)anel + Centos and just love Plesk. So I prefer Plesk any day..

Please advise, thnx!

 

[UFHH01]

...
Domain keys are activated, but it seems that domain keys is deprecated, making it useless when it comes to spam detection for email servers such as google, aol, etc.
...

It doesn't matter what sort of verification is used, either DomainKeys and/or DKIM, but does indead matter IF the setup is correct. To prove your configurations, please use a tool like "http://www.port25.com/support/authentication-center/email-verification/"

Your setup for SPF for example is incorrect and you will always be declared as spam on eMail - servers verifying the SPF entry. The definition "+all" tell other server, that they should use "PASS", with a hard fail, if one other SPF defintion fails.... and it sure will fail, because you define "hosting.example.com" as reference with no valid SPF entry at all... not even correct DNS - entries for this subdomain.

 

[Xavier12]

Hi,

Thanks for the response. SPF seems to have been set for the server hostname as mentioned, but I am still getting a spam situation happening. Also, what would hosted domains SPF be required to be?

 

[UFHH01]

Hi Xavier12,

please use a much better TXT and/or SPF entry, like:

v=spf1 +a +mx +a:<hostname> +ip4:<ip.mail> ?all​

and if you use IPv6 as well, then please use:

v=spf1 +a +mx +a:<hostname> +ip4:<ip.mail> +ip6:<ipv6.mail> ?all
​

( These definitions can be used in your global DNS - template, Plesk will add the assigned IPv4 and/or IPv6 adresses as defined for the domain and the "hostname" from your server configuration.
Please only use the +ip6 - part, if you have IPv6 adresses defined, otherwise the domain specific DNS - entry will have a false "+ip6:<ipv6.mail>" entry, which you have to delete )


As well, don't forget to define SPF - entries at your providers nameservers ( domain provider / registrar ) as well, because they are mostly the initial nameservers and not the ones on your rented server.

 

[Xavier12]

Hey there,

Thanks for this! The set up we've used is the ipv4 option since that is only what we use at this moment..

As far as the SPF regarding our domain provider, we have created custom nameservers that are pointing to the ip that plesk is using which are labeled as ns1.domain.com and ns2.domain.com. Therefore plesk is our dns controller and not our domain provider

From there we control our dns for all domains in plesk, including the hostname for our plesk control panel. With that being said, for some reason after modifying the settings provided, our emails are still being displayed as spam. Right now the focus is customer domains because we ended up creating a dkim for our main domain, which works fine. One of the customer domains that we are troubleshooting this issue with has dns hosted on cloudflare and the settings that you provided were used accordingly. Even after displaying pass for domain keys, its still marked as spam in gmail

Please advise, thnx!

 

[UFHH01]

Hi Xavier12,

after changing entries on a nameserver it can take up to 48 hours untill they are syncron with all the other nameservers on the world. You don't know, which nameserver yahoo or google use to verify the records.

The answer is mostly located in the header section of each eMail being declared as spam. Especially Google and Yahoo include failures and issues regarding SPF, DomainKeys and/or DKIM, which is the most possible reason, why eMails are declared as spam. Have a closer at them, please or post the whole header section here to investigate issues - there are too much reasons and I don't want to guess. ^^