[quote user="J_Aarni"]

I think you should run spamhaltersetup.exe from \mercury\daemons directory.

[/quote]

That was exactly it J.  I simply had no idea that was there.  I'm quite happy that there's now a solved thread relating to this.

Thanks for your help. 

I've been using Content Control with the original spambust.dat and black/whitelists for some time.  I thought I'd try Spamhalter to try to remove some of the manual work for myself.

As my subject states, I simply can't get any Spamhalter headers to appear on any messages.  I trawled through this forum and believe I'm in the same situation as MrPush as per this thread: http://community.pmail.com/forums/thread/22420.aspx . Unfortunately this thread concluded without a result.

Spamhalter  4.5.0.408 is running on Mercury 4.74 and I fed it this database to begin: http://www.vandenbogaerde.net/files/words4.zip.

Spamhalter is functioning and happily updating white4.db3, log files and the words3.db3 file from messages I send to 'yesspam'.  I can force the X-SPAMHALTER headers into a message if I send one to <user>+spamtest@<domain>, and this proved my filter for X-SPAMHALTER: Spam detected! works.

The only thing I can see in the setup that should effect whether a message is processed or not is the Local IP networks.  By default this was set to 127.0.0.1/8,192.168.0.0/16.  I tested with this field blank but still saw no headers.  I've since put these addresses back in.

Any assistance appreciated. 

Edit:  I mention above that the words3.db3 (should say words4.db3) is updating and clearing out emails in the 'yesspam' user's New Mail box.  Turns out this ONLY happens when I send an email to <user>+spamtest@<domain>.  I've had emails in 'yesspam' all day, and only now that I send another +spamtest email were they removed and words4.db3 updated. 

Hi!

Is there any headers on the message, if you check "Add headers with debug informations"?

AFAIK, current Spamhalter version is  4.5.1.411.

Hello :) 

Without debug headers, the first 3 header lines of a message sent to <user>+spamtest@ start with X-SPAMHALTER. 

Enabling debug headers, the first 24 header lines of a message sent to <user>+spamtest@ start with X-SPAMHALTER. 

Every other message without +spamtest before the @, with or without Spamhalter debug headers on have zero X-SPAMHALTER lines anywhere.

Newer version you say?  I downloaded from here just the other day http://www.ararat.cz/doku.php/en:spamhalter .  If there's something newer than that, I'll be happy to try it.

New version of Spahhalter is included in Mercury 4.7.2. I'm not sure, but I think you should run spamhaltersetup.exe from \mercury\daemons directory.