Hello!

What is the subject to trigger that content control rule?

I think what you want to find is a line like
Subject: [SPAM] Buy this!
i.e., a "Subject:"-line your ISP has added the "[SPAM]"-tag to.

If this is what your content control is to find, then I suggest the following content control rule:
IF SUBJECT MATCHES "[[]spam]*" WEIGHT 51 TAG "Flagged by NTL"
Note that the leading bracket in "[SPAM]" has to be masked. When used in a regular expression, "[" is considered a metacharacter; if you want to use it as a normal character, "[" has to be masked, e.g. placed within "[ ... ]".

Perhaps, you also need a leading blank space before the Spam-tag. Then, the rule could look like this:
IF SUBJECT MATCHES "[[]spam]*"
OR SUBJECT MATCHES " +[[]spam]*"
WEIGHT 51
TAG "Flagged by NTL"

Hi,

Did a straightforward install of Mercury/32 v4.52.  I'm using the POP Client to retrieve mail from my ISP, and that works.  I've enabled the default Content Control tests, and added one test

if subject matches "[SPAM*" weight 51 tag "Flagged by NTL"

Syntax check says it is OK.

In the actions tab, I've configured it to add a header

JM-SPAM: Yes

and ticked all 3 header boxes.

However, when I receive mail, there are none of the headers I expect to find in the mail (acceptable mail or otherwise).

I've re-started Mercury/32 after changes, but that made no difference.

I have no white list in operation.

Is there anything I've missed ?

Thanks

Jovan 

I believe that mail collected by MercuryD for some reason always is considered local. So you need to make sure you

have your Content Control definition set to apply to all mail, not just messages originating from the Internet.

/Rolf