![spamfighter exchange module spamfighter exchange module](https://techgenix.com/content/mse/img/upl/image0011316633509489.jpg)
Reverse NDR attack is one of the most common method of spamming a mail server by the hackers. DKIM=permerror = The message could not be verified due to some error that is unrecoverable.DKIM=temperror – This is a temproary error where unable to verify the public key for the DKIM verification.This is possibly a configuration error on the sending domain side. DKIM=neutral = The message was signed, but it was not formed correctly.DKIM=Policy – The messages were signed but the signatures were not acceptable.DKIM=None – The messages were not signed.
#Spamfighter exchange module verification
![spamfighter exchange module spamfighter exchange module](https://www.practical365.com/wp-content/uploads/2010/12/sem-configure02-450x435.png)
Because in this case the private key is owned by Microsoft and the public key is maintained in their office365 DNS records. With this office 365 CNAME option we can rotate the keys whenever required. But office 365 requests the customers to publish the CNAME and point them to a public key in DNS which will delegate the corresponding name space to office 365.Later we publish the public key in the DNS record. In on premise we keep the private keys in our outgoing Anti spam gateway or DKIM agent which will be responsible for signing every outbound emails with DKIM stamp.The main difference between enabling DKIM in on premise environment and office 365 is: In this article we will go through the steps to enable DKIM in pure office 365 cloud environment.įor understanding DKIM concepts and Enabling DKIM in on premise environment you can follow my previous blog