• The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

dkim, where?

Sven L.

Regular Pleskian
Hello,

I was looking how to setup DKIM on my 11.5 when I came across a post where parallels promised this would be included in plesk 12...

so I loaded up my test server and spend 30 minutes searching for it.

so, is DKIM properly integrated into plesk 12?

yes = so, where are the options to make it work please?

no = so, when will it be implemented?


thx in advance.
 
Sorry, DKIM is not implemented in Plesk 12. We have corresponding plans but I haven't any ETA when it will be implemented.
 
What about real spf DNS entries? When will that be done?

The current txt record are only a transitional and temporal solution.

In fact, there are starting to be more and more providers who will not recognize the txt records as valid and fail your SPF pass
 
Its interesting to know why did they starts to ignore txt records with spf rules. This decision affects their customers. Could you provide us with examples of such providers?
 
Hello,

I can't tell you specific providers right now. I have received customer complaints from returned/bounced emails this year and after short investigation it was because of this.

SPF is suposed to be used with a type99 DNS entry, the TXT was only a backwards compatible addition.

if you read SPF specifications, it states that you SHOULD use type99 and that keeping a TXT for backwards compatibility is only RECOMMENDED

and it has been like this for quite a while now.

so instead of staying with a "recommended" system that is already giving problems and bounced emails when meeting a server that actually DOES deprecate old stuff in favour of the real specifications, why don't you guys implement the proper way already, as it should have been for a long time already?

please get this done BEFORE someone huge like google or hotmail decide to not accept TXT as valid SPF anymore and we start getting 99% of our mail bounced back because plesk didn't do their homework.
same could be said about DKIM. get it done before the "big guys" decide to block stuff that's not properly signed.

sources:

http://stackoverflow.com/questions/...-spf-txt-spf-type-99-or-just-one-or-the-other
http://www.openspf.org/Community/SPFv3-SPF-RR-exclusive
 
It seems that RFC4408 is obsolete: http://www.rfc-editor.org/rfc/rfc7208.txt

I was testing my SPF today, and here is what I've got as result:
SPF records are published in DNS as TXT records.

The TXT records found for your domain are:
v=spf1 +a +mx -all

DNS Type SPF SPF records found for the domain are:
v=spf3 +a +mx -all

DNS Type SPF use has been removed in the standards track version of SPF, RFC 7208. These records should be removed.
 
Back
Top