Is there any reason why many emails from senders that previously sailed through as good are now being caught as junk?  This is after updating to 9.9 build 6397.  I am running community edition

Anthony,

The latest version of Xeams checks for DMARC alignment before assigning a score for a whitelisted address. DMARC will be aligned if either SPF or DKIM is aligned. In our opinion, more than 95% of the emails you receive should have either SPF or DKIM aligned. 

In the rare cases where you receive an email from a domain that does not adhere to either SPF or DKIM, but you still want their messages, you can make those exceptions by checking "Skip DMARC alignment" by modifying the sender filter. 

Note that many email providers, including Microsoft and Google, don't even accept the message if both SPF and DKIM are missing, forcing almost everyone to create these records. 

That appears to be the case, but it's happening to many, many inbound emails so I have to be on top of this every day.  It's not helpful that the Sender Filter has no way to search, so finding the filters takes a long time.  This is happening with mail from big companies - Here's an analysis example from Schwab.  Even though their domain is whitelisted, still everything goes to junk.  Is there an easier way to find the sender filter that is being used (e.g. from the analysis)?

Anthony,

Your screenshot is very helpful. It suggests that you're routing your messages from DynDNS. Therefore, almost every message will appear to be forged since SPF will never pass. Emails with a DKIM signature should pass, provided DynDNS does not modify the content in a way that causes the DKIM signature to fail. Your screenshot also shows that the DKIM signature failed, indicating the message was modified before it reached Xeams, causing the signature not to match.

In short, every filtering rule in Xeams that relies on the sender's IP address will not work because emails are being routed through another server.

I assume you're using DynDNS to route emails because you don't have a static IP address. One way to avoid these problems is to rent a small virtual machine somewhere on the Internet. A small machine typically costs less than $7/month. This will give you a static IP, and you won't have to use DynDNS.

Workaround to your current problem

• Visit https://www.xeams.com/manuallypatching.htm and ensure you're using build 6399
• Then, add the following line to the server.properties file
• ignore.dmarc.alignment.in.sender.filter=true
• Save the file and restart Xeams

Once done, Xeams will process whitelisted filters blindly, even if DMARC fails.