On 22 Apr 2016 at 19:27, xxxxxx@shadowgard.com wrote:

> On 22 Apr 2016 at 18:35, Bruce  Johnson wrote:
>
> > There are separate issues here:
>
> > 1) threading is being broken by one or more email clients/servers
> > out there. Not a lot that can be done here about that.
>
> > 2) Email being delivered to spam, even when the address is
> > whitelisted. That is strictly a server side issue. Yahoo, for
> > example, does not publish a `spam score´ per se, like Spam Assassin
> > or Barracuda does. Oh no! They have to have their own system which
> > injects about 750 bytes of 'random characters that look like base64
> > encoding but arenTMtTM into the headers. I cannot determine from that
> > why they would consider one message spam and another from the same
> > person on the same mai?ing list t? be  ham.
>
> > Unfortunately neither issue can be solved by either me or
> > simplelists.
>
> > DMARC/DKIM *may* be broken on some email *recipient´s* side but
> > Simplelists does pass properly configured testing for that. I know
> > that because we control our own email servers and I can check that
> > directly. (and again, that should break every message from a
> > particular sender/domain not just some of them, because it does not
> > rely at all on message content)
>
> > If the recipient´s servers are misconfigured, all bets are off.
> > DMARC/DKIM depends on both sides working correctly.
>
> Well, here goes the first test. Let's see what it looks like on gmail
> & yahoo.

Ok, the above did wind up in spam on my gmail account, and the
headers make clear that I was right:

Received-SPF: pass (google.com: domain of
owner-tml+shadow97218=xxxxxx@simplelists.com designates
89.16.184.173 as permitted sender) client-ip=89.16.184.173;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@simplelists.com;
       dkim=neutral (body hash did not verify)
header.i=@shadowgard.com;
       spf=pass (google.com: domain of
owner-tml+shadow97218=xxxxxx@simplelists.com designates
89.16.184.173 as permitted sender)
smtp.mailfrom=owner-tml+shadow97218=xxxxxx@simplelists.com;
       dmarc=fail (p=QUARANTINE dis=NONE) header.from=shadowgard.com

See that last bit? Because shadowgard.com *does* have a dmarc policy,
and the message indicates it's *from* a shadowgard.com address, it
gets handled according the shadowgard.com's published DMARC rukes,
namely it gets quarantined. Which on google means it gets pushed into
the spam folder.

Now to check yahoo...

Yep, wound up in the spam folder on Yahoo as well. Headers are a
mess. I'll forward both messages to Bruce for further analysis.

Note that on both systems, *only* my post from shadowgard.com wound
up in the spam folder.

--
Leonard Erickson (aka shadow)
shadow at shadowgard dot com