SpamAssassin auto-delete does not work

[Saeven]

To simply have the server DELETE and NOT deliver emails that are tagged as spam by SpamAssassin, click here now.

In vain I click, and the emails are still delivered to the email addresses instead of being deleted as exacted. How can I make SpamAssassin delete spam?

SpamAssassin: enabled
SpamBox: disabled

Thanks!
Alex

[Zaf]

Create an email filter from Manage Email submenu in cPanel. Select SPAM ASSASSIN SPAM HEADER in the drop down list; select 'begins with'; 'Yes'; type "Discard" in destination. That should do it for you

[godyn]

Hi,

I tried the discard filter literly and several times.
I checked many times, but didn't work for the spam box.

I disabled the SPAM box also (because every spam came into it and I needed to check that box constantly to free webspace)
But now it comes in my inbox...
So only option is enabeling.

I also tried these setting:
Filter Destination
$h_X-Spam-Status: begins "Yes" Discard
$h_X-Spam-Status: contains "[SPAM]" Discard
$header_subject: contains "SPAM" Discard
$header_subject: contains "[SPAM]" Discard

But non gave result.
I guess discard doesn't work.
How can I setup so Spam is not delivered and just deleted?

[screege]

Has anyone found a solution I have the same problem for some domains for some others the filter works fine.

[Bdzzld]

Try the following Filter :

[Any Header] that [contains] [X-Spam-Status: Yes] Destination [:fail:]

shown as :

$message_headers contains "X-Spam-Status: Yes" :fail:

That should work for you...

Regards.

[godyn]

Thanks so much !
I've installed it.
Hope it works.

Where can I lookup all the options for the filters? I did not find a :fail: command.

[Bdzzld]

:fail: = The sender receives a message that the mailbox does not exist. This functionality is documented in the catch-all section. Dunno where other options are documented. Instead of :fail: you can still use Discard.

Regards.

[godyn]

than I rather have fail, so the spammer get their junk back ;-)
THX !

[screege]

Nope filters aren´t working for me here is one message I got today:

Spam detection software, running on the system "server1.la-nets.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details.

Content preview: KOKO PETROLEUM (KKPT) - THIS STOCK IS UNDISCOVERED S T O
C K GEM Current Price: 1.50 Symbol - KKPT [...]

Content analysis details: (18.9 points, 7.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
2.9 FROM_LOCAL_NOVOWEL From: localpart has series of non-vowel letters
3.5 BAYES_99 BODY: Bayesian spam probability is 99 to 100%
[score: 1.0000]
2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address
[68.35.62.27 listed in dnsbl.sorbs.net]
3.9 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL
[68.35.62.27 listed in sbl-xbl.spamhaus.org]
1.9 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP
[68.35.62.27 listed in combined.njabl.org]
1.9 RATWARE_MS_HASH Bulk email fingerprint (msgid ms hash) found
2.8 RATWARE_OUTLOOK_NONAME Bulk email fingerprint (Outlook no name)
found

If anyone knows why the filters aren´t working I would appreciate it alot.

Thank you

PD

Also so far I have putted this filters, but they don´t seem to work:

$h_X-Spam-Status: begins "Yes" Discard
$header_subject: contains "***SPAM***" Discard
$message_headers contains "X-Spam-Status: Yes" Discard

[Bdzzld]

Hi,

Is it possible your e-mail filter is called before SpamAssassin? In that case, it's perfectly explainable...

For some reason one of my domains does no longer work with the set e-mail filter too...

Testing the e-mail with the set filter says it will be "tagged"... I think cPanel made a mistake and configured the e-mail filter to be run before SpamAssassin... can anyone please confirm this??

Thanks.

[Wallaby]

There is definitely a problem with filters not working that has started in the last few days. We too are finding that some, but not all, spam that is correctly tagged and should be discarded by a filter is not being discarded.

The funny thing is that most stuff is being correctly filtered, only some messages are not being filtered.

Anyone got any ideas?

PS: I'm on the Release version, and I tried restarting Exim. This is affecting 2 servers so far.

[HollyRidge]

Having the same problem that started a couple of days ago, even though settings have been active and working for months! Also now some of my legit mail isnt geting through.

[HollyRidge]

Ok I got it where my mail isnt deleted by disabling spamassassin and reenabling it, then deleting out all of my mail filters. I tried putting mail filters back in but mail stops getting to my mail boxes when I do this.

[fcsnc]

There is definitely a problem with filters not working that has started in the last few days. We too are finding that some, but not all, spam that is correctly tagged and should be discarded by a filter is not being discarded.

The funny thing is that most stuff is being correctly filtered, only some messages are not being filtered.

Anyone got any ideas?

PS: I'm on the Release version, and I tried restarting Exim. This is affecting 2 servers so far.

I'm on STABLE, and this has been going on for me, too, for about a week. I'm probably going to post a sample with full headers a little later when I get time. The thing that seems to be common among the strange new messages that are getting around the Exim filter is that they all contain a line like the following:

X-Spam-Exim: u4TZITDwFB6uz5Zx7o4QsT92

Which is meaningless to me, but apparently messes with the Exim transport code somehow when Spamassassin is integrated.

[tuux1598g]

We have been experiencing a similar problem over the past few days...

The thing that seems to be common among the strange new messages that are getting around the Exim filter is that they all contain a line like the following:

X-Spam-Exim: u4TZITDwFB6uz5Zx7o4QsT92

I notice that this is correct, the majority of messages marked of spam are being discarded by exim fiters as expected, however the ones that have started getting through all contain this header (X-Spam-Exim).

I just thought I'd share this idea with you as a possible temporary solution (I know it isn't a suitable long-term solution and I haven't had chance to test if it actually works yet). I've added the following line to SpamAssassins local.cf file (I attempted a per-user setting but a change to SpamAssassin settings by the user via cPanel messes this up):

remove_header spam Exim

(and then restart exim so that the SpamAssassin settings are reloaded)

This causes SpamAssassin to remove the potentially problematic X-Spam-Exim header from all email messages marked as spam. As I said, this may not work - I've not had chance to test yet but its an idea for a 'quick-fix' - any potential problems/views on this would be appreciated.


Regards,
Shaun Smith