Piped emails and spamassassin

[Destructo]

I've given up searching for help online as searching for any term + "kayako" ends up listing every site with Kayako installed instead of relevant results, so I hope someone can help me here.

I have email piping setup and it works great, but emails being piped directly to Kayako don't pass through spamassassin and I can't figure out how to set that up. In two days we've received nearly 200 spam emails and it's gotten to the point of ridiculousness. By the way, spamassassin works great for all normal email addresses that aren't piped into Kayako.

For those of you with similar setups, how are you getting spamassassin to scan all emails? Are you piping emails to spamassassin then to Kayako?

[Jamie Edwards]

Hi Destructo,

I have moved your thread to the Technical Chat forum. Unfortunately, I have no idea how to have Spam Assassin work its magic on forwarded e-mails. I know for certain that Plesk and cPanel do not offer this functionality out of the box.

If you find out how, I would be glad to hear

[Jamie Edwards]

Hi there,

This is interesting:

A Small Orange Forums > Spam Assassin Filtering and Mail Forwarders

I did find out that Spam Assassin does it work before the forwarding.
But Spam Assassin isn't the program or process that does the deleting or filtering of e-mail based on its Spam score. Spam Assassin merely reads the e-mail and adds a Spam score to it (0=not spammy, >0 more spammy). This spam score can be used by other mail handling software to determine how to handle the mail.

Maybe Spam Assassin is attaching the spam score to the e-mail headers of forwarded e-mail?

[Destructo]

Thanks for the quick response, Jamie. I did look at that just to make sure that the problem wasn't just that spamassassin wasn't modifying the subject line, but the headers are completely clear of any mention of spamassassin.

As usual, I come up with a fix minutes after posting for help!

I was already piping all emails to a shell script due to an earlier problem with php errors causing piping to fail. My email forward is setup like this:

|/home/domain.com/support/cli/wrapper.sh

Inside of wrapper.sh, I have these two lines:

#!/bin/sh
/usr/bin/spamassassin -e "$@" | /home/yourdomain.com/support/cli/index.php "$@" > /dev/null 2>&1

That is forcing the email first through spamassassin, which outputs a new version of the email with modified headers that is then injected into Kayako. The final bit sends all unwanted output to /dev/null to avoid piping problems.

So far so good, I tested it by sending normal emails and emails with spam links and they were all handled correctly. Now I'll setup some filters to have all marked spam sent to a folder where it will be reviewed before being deleted.

Hopefully that helps anyone else who might be having that problem.

[Jamie Edwards]

Hi Destructo,

Fantastic, thanks for sharing.

[Matthew]

Here's how I enabled SpamAssassin for piped emails on my Centos 4 server, with qmail:

| /usr/bin/spamassassin | php -q /var/www/vhosts/mysupport.com/httpdocs/cli/index.php

Took me a few minutes to figure out, so maybe someone else can benefit.