So, if you have noticed that sometimes Trusting a Sender does not put that sender's email in the inbox, the reason is below. There is nothing in SM to let you know this is happening. 

\\Proposed Solution\\ I believe this is overprotection. If the end user takes the action to "Trust" the sender's email address, it should override the NO Dmarc response. I also believe SM should not override if Dmarc is in place and it fails, but many legitimate domains do not use Dmarc.

 

\\Reason\\Thank you for reaching out. In newer builds of SmarterMail, we evaluate the DMARC result of an incoming email in order to determine if the From Address can be verified as a trusted sender. If DMARC does not pass, I'm afraid the From Address cannot be used to verify the trusted sender status, and the full spam weight of the email will be applied. 

 

This change was made because DMARC is the only check available that can confirm that the From Address listed in the email is associated to the SPF record available. This check ensures that the From Address cannot be spoofed, then automatically trusted just because the From Address is listed as a trusted sender. 

 

In the example you provided, this email had the full spam weight applied because there is no DMARC record available. To correct this issue with the email not being verified as a trusted sender, DMARC must be added by the sender.