https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6649
--- Comment #9 from Darxus <[email protected]> 2011-08-15 22:18:36 UTC --- Created attachment 4955 --> https://issues.apache.org/SpamAssassin/attachment.cgi?id=4955 Sample email that hits __SEEK_4CZTNZ. I can delete my compiled rules and verify this attached email hits __SEEK_4CZTNZ (the rule with the linefeed problem) via JM_SOUGHT_3. Then I run sa-compile, and it *still* hits. Which shouldn't be possible, due to 0x01 in the pre-compiled rule being converted to 0x0A in the input to re2c. How do I verify it's the compiled form of a rule that I'm hitting? I'm pretty sure there's something fantastically broken in here. $ spamassassin -D -t < SEEK_4CZTNZ.mbox 2>&1 | grep 4CZTNZ Aug 15 18:11:40.458 [6210] dbg: rules: ran body rule __SEEK_4CZTNZ ======> got hit: "[binary gunk]" BTW, I created that .mbox file by just copying and pasting the regex (stuff between the //s) into a perl print statement and outputting it to a file. Then just adding a From header and blank line before it. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
