It took me a while to close the loop with the client on this.
We are running
SurgeMail Version 7.2a-1, Built Jun 1 2016 09:35:50, Platform OSX_intel (OS X 10.7.5)
on the server in the branch office, which is retrieving all email for a domain via popfetch.
Here are sample headers:
From: Waldeburg Konstantin <michelinaHIDDEN@comune.baronissi.sa.it>
Reply-To: Waldeburg Konstantin <michelinaHIDDEN@comune.baronissi.sa.it>
Subject: =?iso-8859-1?Q?M=C3=B6chtest_du_eine_Sch=C3=B6nheit_beim_ersten_Date_fick?=
=?iso-8859-1?Q?en=3F?=
Message-ID: HIDDEN@4bd1d69a4352663e23a097d7ee@www.harmoniecroissance.com>
X-Mailer: PHPMailer 5.2.14 (https://github.com/PHPMailer/PHPMailer)
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="b1_9c378c4bd1d69a4352663e23a097d7ee"
Content-Transfer-Encoding: 8bit
Return-Path: michelinaHIDDEN@comune.baronissi.sa.it
X-OriginalArrivalTime: 13 Dec 2016 00:52:55.0195 (UTC) FILETIME=[3D67CEB0:01D254DB]
X-X-Originating-IP: 37.186.217.132
X-Rcpt-To: <xxxxx>
X-SPAM-FLAG: Yes
X-X-SpamDetect: ********: 8.0 sd=8.0 0.87((!X-Verify-Helo:+OK),(X-myrbl:unknown)) [nnot=0,ng=0,nsum=0,nb=0,nw=0,4.82]
X-NotAscii: charset=iso-8859-1
X-LangGuess: German
X-X-MyRbl: Color=Unknown ip=37.186.217.132
X-IP-stats: No info recorded yet ip=37.186.217.132
Status: U
X-Originating-IP:
X-Rcpt-To: <xxxxx>
X-Rcpt-Original: <xxxxx>
X-SpamContent: IsSpam
X-LangGuess: German
X-Probe: +OK skipped, known ip address
X-Phrase: IsSpam score=1.00
On the server in the branch office, the affected user has the following in his friend.rul:
move:Spam-Mail:X-X-Spam-Detect:********
move:Spam-Mail:X-Spam-Detect:********
These rules do not fire.
If I put in a rule such as
move:Spam-Mail:FromHIDDEN@r@example.com
it fires as expected.
Best,
Chris
> Am 30.11.2016 um 07:25 schrieb surgemail-support <surgemailHIDDEN@t@netwinsite.com>:
>
> 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
>>>
>>
>
>
|
