Rated 2 out of 5 stars

Seems like a great idea, but isn't currently working for me. I tried applying mango's fix, but the Spam Rating column is still coming up empty. My x-spam-status headers look like this:

Yes, score=7.4

Also, I noticed that the option dialog has an Advanced tab that seems to anticipate the lower case issue:

function toLowerCase() { [native code]}

But trying to save options gives an error:

"The header you entered contains an invalid character, such as ':', a non-printable character, a non-ascii character, or an eight bit ascii character."

Presumably related to the brackets in the default value - but there's no indication how to correctly implement lowercasing.

Also, trying to use the add-on on an IMAP mailbox results in the following lines being added to your prefs.js:

user_pref("mailnews.customDBHeaders", "function toLowerCase() {\n [native code]\n} function toLowerCase() {\n [native code]\n} function toLowerCase() {\n [native code]\n}");
user_pref("mailnews.customHeaders", "X-Spam-Status: X-Spambayes-Classification: Bcc: X-PHP-Script: X-Spam-Score: Return-path: functiontoLowerCase(){[nativecode]}: functiontoLowerCase(){[nativecode]}: function toLowerCase() {\n [native code]\n}");

which *breaks* IMAP access! (And doesn't go away when you uninstall the add-on.) Beware of this - you'll need to revert those lines by hand to regain access to the IMAP box(es) it broke.

Finally, there are a couple options related to showing the score and rules (!) in the message that seem to have no effect for me. The latter sounds really cool. Too bad none of this is working. Here's hoping for an updated version soon.

Great, but requires tweaking Rated 3 out of 5 stars

I tried using this on Thunderbird 24.0.1 with a server running SpamAssassin 3.3.2 and couldn't get it to show up. The email has a line that looks like:
X-Spam-Status: No, score=-1.1, hits=-1.1, required=5.0, autolearn=ham, shortcircuit=no
It looks like there's a problem with how the string is parsed to determine the score.

Update: I made the changes recommended by Mango and now it works perfectly! Someone should make these changes to the version available here. While the changes are easy to make for us software developers, it's not so easy for someone not as tech savvy.
If it didn't require tweaking I'd give this add-on 5 stars.

Interesting but not working for me Rated 3 out of 5 stars

It seems a very interesting plugin but it's not working for me. With the following header:
X-Spam-Status: Yes, score=8.6
X-Spam-Score: 86
X-Spam-Bar: ++++++++
X-Spam-Report: Yes, score=8.6, required=-1.0
pts rule name description
---- ---------------------- -----------------------------------------

Nothing appears in the Spamness column... I have setup the mail header to "X-Spam-Report" and clicked a thousand of times on the repair folder... I"m not sure what I'm doing wrong.

Solid performer Rated 4 out of 5 stars

I had to alter this extension slightly to allow it to work with the default X-Spam-Status header used by my cPanel server. I changed Spamness.parseHeader to:

Spamness.parseHeader = function(headerStr) {
var score = (score = headerStr.match(/(score|hits) ?= ?([-\d\.]+)/)) ? parseFloat(score[2]) : 0;
var required = (required = headerStr.match(/(required) ?= ?([-\d\.]+)/)) ? parseFloat(required[2]) : 0;
var tests = (tests = headerStr.match(/tests ?= ?(.*?[^, ])( |$)/)) ? tests[1].split(/,\s*/) : [];
return new Spamness.Header(score, required, tests);
};

Also, I changed the last line of Spamness.getHeaderName to:

return header.toLowerCase();

This allows Score Header to be case-insensitive. Before, it had to be in lower case.

Thanks to Ryan for this excellent extension. I have been testing new SpamAssassin configuration and it is very useful to be able to sort messages by spam score.

Spam Ingredients Rated 5 out of 5 stars

I was just sitting at my desk thinking how useful it would be; hoping, dreaming and wishing that I had a way to sort emails in a folder by their spam rating. A quick Google later and I found that some genius had already done all the work and made me this add on.

I installed the Spamness 0.6.2 add on to Thunderbird 15.0.1
And it "just works" perfectly with my existing Debian / Postfix / Spamassassin set up.

I can now clearly see an overview of how the server responsible for delivering my emails is identifying messages as spam where previously I had to dig through the headers on an individual per mail basis.

I liked how after the initial install there is a prompt screen that gives your a brief but sufficient overview on how to use the software rather than expecting you to wade through the entire internet trying to locate a text file of documentation. It's clear to me that some thought has gone into this add on.

I don't usually write reviews but I felt the average rating for this add on didn't reflect it's performance as people had scored it (in my opinion) too low possibly because they didn't understand how it should be used or due to their own unique (weird) configuration requirements.

This review is for a previous version of the add-on (0.6.2). 

Rated 3 out of 5 stars

It's cool. I test in thunderbird 10.0

This review is for a previous version of the add-on (0.6.2). 

Kill vs Required Rated 1 out of 5 stars

Just got the 0.6 version, still no joy. My SA uses "kill" instead of "required" and thus the regex dont get it. It seems that the regex is on the jar file and I cannot adjust it.

This review is for a previous version of the add-on (0.6).  This user has a previous review of this add-on.

Rated 2 out of 5 stars

Just so you know...

WHM/cPanel servers are configured with Exim and Spamassasin. On these servers, the default is such that HAM (non spam) does not report the following attributes in the X-Spam-Status header.

required=_REQD_ tests=_TESTSSCORES(,)_ autolearn=_AUTOLEARN_

All you get in the headers is the following:
X-Spam-Status: No, score=-2.6
X-Spam-Score: -25
X-Spam-Bar: --
X-Spam-Flag: NO

So any mail that is hosted on a WHM/cPanel server, will not have the details for Spamness to see anything and thus won't work.

I have configured my server to show the information in X-Spam-Report just to see if Spamness would work, but unfortunately, I cannot get Spamness to see any header other than x-spam-status. (and yes, I'm clicking Index folders button).

Every time I go back into the add-on preferences, it is set back to x-spam-status instead of x-spam-report.

I would like to use this add-on, but unfortunately, it doesn't work....and I would be that a majority of mail users out there that are using Thunderbird are using WHM/cPanel hosted mail.

This review is for a previous version of the add-on (0.3).  This user has a previous review of this add-on.

Thanks for the report.

"I have configured my server to show the information in X-Spam-Report just to see if Spamness would work, but unfortunately, I cannot get Spamness to see any header other than x-spam-status. (and yes, I'm clicking Index folders button)."

That's a known bug, but it's partly because of the way Thunderbird deals with custom headers. It's a global preference, but any extension can absolutely set the value. I've tried to adjust for that, but it was with a buggy implementation in 0.3. It's been fixed in an unreleased version I keep meaning to push out. Hopefully you'll see it soon, and then you can evaluate whether it fits your needs.

Spamtastic :-) Rated 5 out of 5 stars

Tested on v3.1.2. Works perfectly.

I find the best use of this plugin is on my Junk folder, using spamness to sort the contents. Then any ham floats to the top.

This review is for a previous version of the add-on (0.3). 

Good idea but hardly effective or of any use Rated 2 out of 5 stars

I've always used Thunderbird's native spam filter because, after a month of "training", it is practically unbeatable, specially for people like me who get a lot of spam, even in comparison to SpamAssassin's filter. If I were to depend on SpamAssassin, a lot more spam would find its way into my Inbox.

Proof of this is Spamness. Using Spamness on my Trash folder, with about 2800 messages in it, including at least 2000 actual spam messages, it only tagged about 10 messages or so. Thunderbird detected all that spam for me, whereas Spamness or SpamAssassin didn't have much clue.

I'm thinking the obvious way to work this out would be to add Thunderbird's spam training information to the equation, but I don't know if that's possible or within the scope of this extension (I'm not a programmer myself).

Finally, I really found this extension to be a great idea. I sure hope it gets to improves over these flaws and wish I could help more with this improvement.

This review is for a previous version of the add-on (0.3). 

Not Equivalent to SpamAssassin

Hi, add-on author here. This sounds like a review and rating of SpamAssassin, which is why I've flagged it. SpamAssassin is a server-side piece of software. Spamness merely reads SA's data. It does no active detection or tagging on its own inside Thunderbird as TB's junk mail component does, it just displays SA's analysis.

Thanks for going through the trouble of trying it out. It does sound like you might want your server admin to check out your SpamAssassin installation. Mine works so well in concert with TB's junk detection that I barely pay attention to spam anymore. I wrote about it recently: http://ryanlee.org/journal/view/6390/

Please fix Rated 4 out of 5 stars

I think this extension is a nice idea but as others have commented it needs to have a configurable area to customise the X Header and to show just spam score if user prefers.

Please fix :)

This review is for a previous version of the add-on (0.1). 

Rated 5 out of 5 stars

Worked out of the box.

This review is for a previous version of the add-on (0.1). 

compatible spamassassin config Rated 4 out of 5 stars

I like this add-on. It works on my Ubuntu Hardy Thunderbird client and debian etch spamassassin server. I later played with my spamassassin headers config and it stopped working. This is the line from my /etc/spamassassin/local.cf that got it working again:

add_header all Status _YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTSSCORES(,)_ autolearn=_AUTOLEARN_

the above is all one line. I issue clear_headers before this line.

This review is for a previous version of the add-on (0.1). 

Rated 3 out of 5 stars

I initially thought Spamness wasn't working because it wouldn't sort an existing folder but it does a good job of sorting newly received mail.

This review is for a previous version of the add-on (0.1). 

Re-index folders

As noted in the extension description, Spamness can only work on folders that existed before its installation when you re-index them. There should be a better way to indicate that after installation, though, so I'll be looking into how to make that more clear.

Rated 1 out of 5 stars

My Spamassassin generates a tag like this: X-Spam-Status: Yes, score=1.3 required=0.0 tests=HTML_IMAGE_ONLY_32,
HTML_IMAGE_RATIO_06,HTML_MESSAGE autolearn=disabled version=3.2.4-gr0

Spamness couldn't handle this and did no sorting or visuals.

This review is for a previous version of the add-on (0.1). 

Rated 2 out of 5 stars

My own SpamAssassin configuration only presents scores in this header:
X-Spam-Status: Yes, score=10.7 required=5.0 tests=...

Therefore, this add-on is currently useless to me, but if that can be fixed I'd find it very useful.

It's nice enough just having a column showing the spam score and being able to sort by it; a simple number would be much more useful to me than a graphic.

This review is for a previous version of the add-on (0.1). 

Rated 1 out of 5 stars

It'd have a higher rating if it offered a configuration option for the header name it should be looking at -- not every SpamAssassin install calls the header 'X-Spam-Status'. Nifty idea, though.

This review is for a previous version of the add-on (0.1).