This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Feature Request - DKIM and DMARC Support

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.

This thread was automatically locked due to age.

Parents

cestlabby_c137 over 5 years ago

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.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

cestlabby_c137 over 5 years ago

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.
Cancel
Vote Up 0 Vote Down

Cancel

Children

Aidan Mirisola-Sullivan over 5 years ago in reply to cestlabby_c137

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?

https://technet.microsoft.com/en-us/library/mt695945(v=exchg.150).aspx#Publish2CNAME
Cancel
Vote Up 0 Vote Down

Cancel
Alex Cher over 5 years ago in reply to Aidan Mirisola-Sullivan

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.

Thanks,
Alex
Cancel
Vote Up 0 Vote Down

Cancel
Monica Sepana Gainina over 5 years ago in reply to Alex Cher

+1 el mejor biombo japones
Cancel
Vote Up 0 Vote Down

Cancel
ChadAnderson over 5 years ago in reply to Alex Cher

+1
Cancel
Vote Up 0 Vote Down

Cancel