Verification of signatures is done through amavisd-new/SpamAssassin. On the other hand, Apple is now including an updated version of amavisd-new with its Server OS, so why rely on extra components when all we need is already available. dkimproxy is still a valid solution, but it hasn’t been maintained much in the past couple of years. Unlike previous versions of this tutorial which were based on dkimproxy and amavisd, this tutorial relies only on amavisd. Second, it allows you to sign outgoing messages with a digital signature for recipients to verify your mail server. First, it is used to verify if a sender domain is using DomainKeys/DKIM signatures and if the incoming mail was correctly signed. There are plenty of discussions about this available on the internet.ĭomainKeys/DKIM functionality has two sides to it. This is a decision you must make for yourself.
Neither will I discuss whether DomainKeys/DKIM are useful or not. You will not find many explanations as to why something is done one way or the other. The purpose of this document is to provide instructions on how to implement DomainKeys/DKIM on OS X 10.10.x Yosemite and OS X 10.11.x El Capitan With Server 5.x. Please make sure you have a backup before applying modifications to your server. Caveats – READ this chapter!ĭISCLAIMER: The author(s) claim(s) no responsibility for any damage that may occur from the use of any information found here or found on links followed from this document.
Using amavisd-net to sign outgoing messages 5. Using Mail::DKIM to verify incoming messages 4.
0 kommentar(er)
