Currently SmarterMail doesn't allow you to specify a Hash Algorithm for "Domain Keys Signing" and default it's to SHA1 - You should allow us to choose SHA256
DKIM supports multiple digital signature algorithms. Two algorithms
are defined by this specification at this time: rsa-sha1 and rsa-
sha256. Signers MUST implement and SHOULD sign using rsa-sha256.
Verifiers MUST implement both rsa-sha1 and rsa-sha256.
In addition, DomainKeys gives us the option to set a single canonicalization method "Simple" or "nofws".
"nofws" was in the old standard and has been removed. We should be able to set both the Body and Header Separately as we do for DKIM Signing.
c= Message canonicalization (plain-text; OPTIONAL, default is
"simple/simple"). This tag informs the Verifier of the type of
canonicalization used to prepare the message for signing. It
consists of two names separated by a "slash" (%d47) character,
corresponding to the header and body canonicalization algorithms,
respectively. These algorithms are described in Section 3.4. If
only one algorithm is named, that algorithm is used for the header
and "simple" is used for the body. For example, "c=relaxed" is
treated the same as "c=relaxed/simple".
I also thing you should give us the ability to set the "Headers" that get signed, just as you do for DKIM and it shouldn't be pre-setted.
I seen a few instances where people test out Smartermail, because I use Smartermail, then when they notice these issues, they switch to a different mail server. It will be nice if we can get this changed, I want as many people using Smartermail as possible.