I ran a test and had no problem making them work. What version of 
surgemail are you using?  Feel free to email support directly, 
surgemailHIDDEN@t@netwinsite.com

     ChrisP


On 29/11/2016 11:32 a.m., surgemailHIDDEN@etwinsite.com wrote:
> I tried that, but the rule doesn’t appear to fire. I couldn’t get any filter rules to fire, so I was wondering whether they are applied at all to messages retrieved via popfetch. How can I debug that?
>
> Chris
>
>> Am 28.11.2016 um 23:28 schrieb surgemail-support <surgemailHIDDEN@t@netwinsite.com>:
>>
>> I believe you can do this by adding a filter rule in the destination users account, set it to move a message with header
>>
>> X-X-SpamDetect
>>
>> containing
>>
>> ********
>>
>> to the spam folder.
>>
>>     ChrisP.
>>
>> On 28/11/2016 6:25 a.m., Chris Ferebee wrote:
>>> I have a setup with a colocated SurgeMail server that handles email for multiple clients, and one client who runs his own SurgeMail server in his office.
>>>
>>> The secondary server retrieves email for its domain via popfetch.
>>>
>>> On the primary server, I have g_spam_subject set to 10 and mostly rely on zen.spamhaus.org to block spam.
>>>
>>> On the secondary server, the client is complaining about a high level of spam which is originating from systems not easily blocked by any RBL, so we would like to use the Quarantine mechanism on his office server.
>>>
>>> However, when I enable it, while it does quarantine messages containing a Spam:(10-asterisks) subject prefix as inserted by my primary server, I can’t get the Quarantine feature to filter messages with a score of 8 or higher, which is what we would like to achieve.
>>>
>>> The headers of messages on the secondary server have no X-SpamDetect: line, instead I see  X-X-SpamDetect:. I suspect this is rewritten during popfetch?
>>>
>>> How can I get the secondary server to apply its Quarantine rules based on the score listed in the X-X-SpamDetect: header line?
>>>
>>> Thanks,
>>> Chris
>>
>