ALL messages going to SPAM folder!

Spam Sieve has been working great forever… suddenly, in Apple Mail, all my messages are going to the spam folder. Some of them (the ones I don’t consider Spam) are being left colored white. But they are still moved.

I re-trained the corpus after clearing it, and that did not change anything.

Running on imac osx 10.4.10, Apple Mail…

Any help would be appreciated!
Michael

Normally this means that Mail is no longer asking SpamSieve to examine the messages, so it just moves them all to the Spam mailbox. Thus, the SpamSieve corpus is probably irrelevant.

Do you still see the SpamSieve training commands in the Message menu? If not, try choosing “Install Apple Mail Plug-In” from the SpamSieve menu. Also make sure that the name of the SpamSieve rule in Mail is “SpamSieve”.

Michael,

Thanks for the quick post!

I do have the plug-in menu items… train as good, etc…

And it does seem from the log (i just checked) that spam sieve is evaluating the messages, for example…from the log, the first one was in the spam folder, and it was white. (RE: A long one), the message below it (MegaDik Penis Enlargement), was in the spam folder and colored something… and the one below that (Pre-Owned Exhibits) was also colored normal white… which is correct, but all the ones below marked good were moved to the spam folder, and the other rules were not evaluated.

thanks
Michael

Predicted: Good (1)
Subject: Re: a long one
From: harkins@codetel.net.do
Identifier: SmIpBOxSp/l2TeuXAEBK8w==
Reason: (“harkins@codetel.net.do”) matched rule <From (address) Is Equal to “harkins@codetel.net.do”> in SpamSieve whitelist
Date: 2007-08-22 11:35:40 -0700

Trained: Good (Auto)
Subject: Re: a long one
Identifier: SmIpBOxSp/l2TeuXAEBK8w==
Actions: added to Good corpus (228)
Date: 2007-08-22 11:35:40 -0700

Predicted: Spam (95)
Subject: You need our new improved MegaDik Penis Enlargement Pills, Please read on…
From: fhc@linuslerner.com
Identifier: gi5A3M2X0wrX2O7FuGgaTw==
Reason: P(spam)=1.000[0.999], bias=0.000, S:^long-subject(1.000), R:^88(1.000), R:^88(1.000), S:our(0.999), S:improved(0.005), XM:MicrosoftOutlookExpress6.00.2800.1409(0.995), S:Pills(0.995), x-mimeole:ProducedByMicrosoftMimeOLEV6.00.2800.1409(0.995), discreet?(0.995), R:^red^bezeqint^net(0.995), R:^bezeqint^net(0.995), S:Please(0.844), R:^userid(0.831), H:X-Priority(0.810), ^small(0.792)
Date: 2007-08-22 11:35:40 -0700

Predicted: Good (27)
Subject: Pre-Owned Exhibits - August '07
From: EXHIBITTRADER.COM@mail.vresp.com
Identifier: qvfEJQQSxfTrg16v7MZzAQ==
Reason: P(spam)=0.000[0.500], bias=0.000, pop(0.000), 600(0.999), 600(0.999), fraction(0.999), info@(0.001), A:info@(0.001), stories(0.001), useful(0.999), ^a-width-150(0.002), islands(0.002), purchase!(0.998), director(0.002), custom(0.002), custom(0.002), A:Press(0.002)
Date: 2007-08-22 11:35:42 -0700

Trained: Good (Auto)
Subject: Pre-Owned Exhibits - August '07
Identifier: qvfEJQQSxfTrg16v7MZzAQ==
Actions: added rule <From (address) Is Equal to "EXHIBITTRADER.COM@mail.vresp.com"> to SpamSieve whitelist, added rule <From (address) Is Equal to "reply-21548c0a2d-98d0a2c58e@u.cts.vresp.com"> to SpamSieve whitelist, added rule <List-Unsubscribe Is Equal to “<mailto:reply-21548c0a2d-98d0a2c58e@u.cts.vresp.com?subject=unsubscribe>”> to SpamSieve whitelist, added to Good corpus (229)
Date: 2007-08-22 11:35:42 -0700

And I just saw these errors in the log…

=====================================================================
Error: Couldn’t commit because database disk image is malformed
Date: 2007-08-22 12:14:17 -0700

Predicted: Good (1)
Subject: test
From: mary@ashlandsky.com
Identifier: cKM1ie1x+fbIOUqmh+EMVg==
Reason: (“Mary Danca”) matched rule <From (name) Is Equal to “Mary Danca”> in SpamSieve whitelist
Date: 2007-08-22 12:17:17 -0700

Trained: Good (Auto)
Subject: test
Identifier: cKM1ie1x+fbIOUqmh+EMVg==
Actions: added to Good corpus (230)
Date: 2007-08-22 12:17:17 -0700

Error: Couldn’t commit because cannot start a transaction within a transaction
Date: 2007-08-22 12:17:22 -0700

It looks like SpamSieve is examining these messages and finding them not to be spam. So my guess is that you have another rule below the SpamSieve rule that’s moving them to the Spam mailbox.

How do you know that the other rules were not evaluated?

This means that SpamSieve’s statistics database is damaged. You can reset it by quitting SpamSieve and renaming the file:

/Users/<username>/Library/Application Support/SpamSieve/History.db

to “History Old.db”. This will not affect the accuracy, only the statistics.