As many spam filtering providers are continually upping their defenses against spam, DKIM and DMARC support is going to be an increasing need-to-have for authenticating client's email servers as non-spammers.
Rackspace is even updating their systems to support DKIM signing on outgoing email and will be implementing DMARC as well which is going to make spam filtering even more troublesome with them when our client's systems don't support either.
And Office 365 supports DKIM as well...it seems rather odd that Reflexion is lagging behind so much in bringing these features to the table.
Anyone hear any update on this? We are getting pressure from a few of our clients to implement DKIM / DMARC support for their domains. I really don't want to have to change spam providers again. :/
It seems as though they aren't enhancing the Reflexion product anymore and concentrating development on the Sophos Cloud Email Security https://www.sophos.com/en-us/products/sophos-email.aspx
I'd love to see this as well.
DKIM is based on the domain of the sender and can be implemented by our partners to sign their mail with no additional work on reflexion side. They would not strip this signature or modify the DKIM header.DMARC is similar except it can use SPF or a DKIM signature, again it is implemented on the partner side.
No plans on updating the platform yet but with the plans of enhancing it in the future, it may be supported.
So you're saying that even though the mail is being sent via an outbound connector to Reflexion, the DMARC and DKIMM DNS changes can happen on the client side? My understanding after some quick research is that any time a filter is acting as a 'middle man' to deliver mail, as in the case of Reflexion, said records need to be maintained on that end.
Are you saying that when using Office 365 and Reflexion, then these instructions are still 100% accurate?
Bumping the thread.
Would like to see an update or clarification from Reflexion support please.
Is it enough to enable DKIM and DMARC on our end, or does Reflexion need to support this?
We're looking at disabling EOP for Office 365 as recommended by Reflexion and need to know the answer to this first.
+1 el mejor biombo japones
With phishing being the primary vector of attacks for all bad actors, why is Sophos not making this a priority????Get with the program!!!