In looking at your failures, I have noticed several problems.
The first is that the originating ip for your emails (208.115.108.162) is listed on Five Ten's blacklist (http://www.five-ten-sg.com). Yahoo, Hotmail, and AOL all use their own internal blacklists, and to my knowledge don't rely on third party blacklists (such as Five Ten). That being said, it's a good indicator that something is afoot. You can delist yourself at five ten here: http://www.five-ten-sg.com/blackhole.php?ip=208.115.108.162&Search=Search. Delistings usually take around 12 to 24 hours. While this won't necessarily FIX your Yahoo, Hotmail, AOL problem... you should delist pronto.
The biggest problem is the lack of MX record for gemini.shiftapp.com. The emails are "FROM" james@gemini.shiftapp.com. It is a very common anti-spam tactic to lookup the MX record of the sending domain on incoming email. When AOL etc lookup the MX record for gemini.shiftapp.com, and they see none... they will likely classify as spam on the spot. At the very least, an MX will allow the recipients of these emails to reply.
Reverse DNS: You have a valid PTR record for that IP. AOL etc just simply look to see that PTR records exist... they don't really care what the PTR record returns so you are "good to go" as they say.
I didn't find any SPF records for gemini.shiftapp.com or shiftapp.com. That's ok because SPF never really caught on. Kinda like 8 track or Laser Discs... they look good on paper, but never gained critical mass.
My bet is the lack of MX records. One other thing to consider: make sure your email server is not an open relay (allowing unauthenticated users to send mail to other users not hosted on your server). Also, might be wise to do an audit of all email going through your system... if one of your users is (knowningly or UNknowingly) sending spam through your server, you'll be skating uphill!
Hope this helps, and best of luck! -Chris
The solution isn't to make spamassassin score these mails correctly, the solution is to not send them to spamassassin in the first place.
You need to add a rule beforehand to explicitly accept mails from your bulkmail host.
accept hosts = 192.168.0.3
Change 192.168.0.3
to be server / network where you want to allow mails to come in from.
Best Answer
You need to modify
received_header_text
as per the documentation.It defaults to:
After modification it'll be: