Technical Services Archive

Plesk: Update Spamassassin to Fix 2010 Bug

Recently, I’ve been seeing more and more reports of users saying that good email are getting marked as spam. This issue is due to a bug in SpamAssassin that treats dates past 20xx as far future dates. Fortunately, you can easily update your spam assassin rules to fix this issue.

The bug causes emails with a date of 2010 to be hit with a higher spam score by 3.2 points. As a result, these emails could get blocked.

If your SpamAssassin install adds headers, you can see this as a:

FH_DATE_PAST_20XX

rule violation.

To correct this issue, you can run:

sa-update

Which should pull down the latest SpamAssassin rules. This works on SpamAssassin version 3.2 and above.

By default, Plesk does not automatically update SpamAssassin rules. There is a cron job in:

/etc/cron.d/sa-update

But by default it is disabled. On Plesk servers, you may want to modify:

/usr/share/spamassassin/sa-update.cron

To call

/etc/rc.d/init.d/psa-spamassassin restart

Instead of the default SpamAssassin start up script.

Practical Thinking on AI, Code, and Risk

Managing AI Operations

You're Buying AI. Who's Managing It?

Buying tools is easy; operationalizing them is where the risk lives. Why tool adoption stalls without pragmatic governance.

Read article

Code & Automation Risk

What to Ask Before You Ship AI-Generated Code

Why 35,000 lines of unowned prompt-code become an organizational liability, and how architectural guardrails protect you.

Read article

Legacy Modernization

Legacy Software a Problem? AI Can Help.

Full rewrites fail 4 out of 5 times. How targeted, AI-assisted refactoring modernizes core systems without big-bang rebuild risk.

Read article

Let's talk about what you need.

Tell me about your situation. If there's a fit, we'll schedule a call.

Start a Conversation