Dear Kevin, many thanks for your quick response. Unfortunately, there is no output generated except for a warning message that I have no description defined for my custom rule:
# spamassassin -tD < ./test\:2\,Sdj 2>&1 | grep -i FR_Spam2
Jan 1 20:08:56.590 [60105] dbg: config: warning: no description set for
FR_Spam2
Any other thoughts? Ideas?
Many thanks.
Best regards
Sebastian
> Am 01.01.2016 um 19:52 schrieb Kevin A. McGrail <kmcgr...@pccc.com>:
>
> On 1/1/2016 1:37 PM, Sebastian Wolfgarten wrote:
>> Dear all,
>>
>> I wish you and your families a happy, prosperous and healthy year 2016!
>>
>> As for me, I am spending the first day of the new year battling with some
>> custom SA rule that seems to be ignored:
>>
>> header FR_Spam2 Received =~ /e\d{1,2}+\.(.*)\.fr/i
>> score FR_Spam2 3.5
>>
>> Is this rule correct from a syntactical perspective? I would say yes as
>> pcregrep is fine with it.
>>
>> Anyway, here is the scenario that I am trying to handle: I am getting *lots*
>> of spam messages in French with random text with each of them contains a
>> line like "Received from e(1 or 2 digit number).(some random hostname
>> sometimes with dashes and sometimes without).fr“ - here is an example:
> I suggest you run it through spamassassin on the command line with -D and
> check the output. spamassassin -tD < sample-spam.txt 2>&1 | grep -i FR_Spam2
>
> My off the cuff guess is perhaps you are using a glue that tests the spam
> before that received line is added to the email.
>
> Regards,
> KAM
signature.asc
Description: Message signed with OpenPGP using GPGMail
