Prized Season software

One of the interesting things on Left hand-side blocking lists (LHSBL, refer to wiki.openrbl.org/wiki/LHSBL) is they are far more effective rejecting ham, than normal / conventional tools used to fight spam.

They are far more restricted.
I got impressed when running SpamAsssassin against a genuine message arrived at my box from LinkedIn.
I thought SpamAssassin would classify it right away as spam, but it didn't. The reason is explained below, after the impressive report by SpamAssassin:

Content analysis details: (-8.3 points, 6.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-4.0 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, medium
trust
[208.111.172.106 listed in list.dnswl.org]
0.0 HTML_MESSAGE BODY: HTML included in message
-4.3 RCVD_IN_BSP_TRUSTED RBL: Sender is in Sender Score Certified (trusted
relay)
[Return Path SenderScore Certified (formerly]
[Bonded Sender) - ]

LinkedIn is white-listed at Sender Score Certified.

The picture shows a brief analysis, from top to bottom, left to right, as follow:

• checking the incoming announced relays at my MTA; this output has email addresses blurred, to avoid harvesting;
• "bondedserver": explained how to use these white-lists; like any other RBL, they are DNS based;
• bottom left, an excerpt of the message;
• bottom right: checking the respective MTA (the arriving IP at my box) is white-listed;
• in this example we have used IP 208.111.172.106 (gnetinfo hostaddr 208.111.172.106 returns mail12-a-ab.linkedin.com, and mail12-a-ab.linkedin.com has address 208.111.172.106).