MailBee.NET (in MailBee.NET.dll) Version: 11.2.0 build 590 for .NET 4.5
public enum DomainKeysVerifyResult
Public Enumeration DomainKeysVerifyResult
The DomainKeys signature of the message is valid and up to date.
The message is not signed with DomainKeys signature.
The DomainKeys signature tag in the message headers is invalid.
The DomainKeys signature is expired.
The DomainKeys signature refers to a non-existent sender domain.
DNS query could not be performed. Perhaps, all DnsServers (supplied in dnsRequestor parameter
of Verify(MailMessage, Smtp) method) are dead. By default, MailBee throws MailBeeDomainKeysException in case of this error.
The DomainKeys DNS record of the sender domain is incorrect.
The DomainKeys signature of the message is invalid.
The public key contained in DomainKeys DNS record of the sender domain has wrong format.
It's not possible to verify the given DKIM signature because it uses SHA256 while the current system does not support SHA256 algorithm
(usually, in case of .NET Framework prior to 4.0 on a FIPS-enabled system). By default, MailBee throws MailBeeDomainKeysException in case of this error.
With MailBee.NET.dll for .NET 4.0+ this error will never occur, regardless whether Windows operates in FIPS mode or not.
Some errors are considered a problem with the system running MailBee
and thus by default MailBee will throw MailBeeDomainKeysException in case of such errors.
To suppress exceptions and get all errors as the method's return values, disable
DomainKeys.ThrowExceptions (or MailMessage.ThrowExceptions
if you using MailMessage.DomainKeysVerify method).
|In case of a FIPS-compliant system, enable FipsMode to make MailBee always use FIPS-compliant methods.
If you don't do that, MailBee will fall back to a FIPS-compliant method only after the default method fails, and this degrades performance a bit.
However, in .NET 2.0/3.5 the SHA256 method (which is used in DKIM) is available only as FIPS-noncompliant implementation. On a FIPS system,
it's recommended to always use MailBee.NET.dll for .NET 4.0+ along with the corresponding .NET Framework.|See Also