https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6224
--- Comment #4 from Adam Katz <[email protected]> 2009-10-22 07:35:41 UTC --- (In reply to comment #3) > > # example (couldn't figure out how to skip the /s) > > header BUG_IN_HEADER Received =~ /(by.*by)/s > > Identical headers like Received are internally represented by a single > multi-line string. This is documented somewhere, I hope -- at least has been > mentioned a couple times on list. What's the recommended way to ensure you're only parsing one at a time? > The /s modifier makes a dot match any char, *including* a newline, which it > usually doesn't. That's why it is necessary for this example rule. > > Works as expected. Resolved, INVALID. As I stated, I couldn't distill the bug into a simple test case, so I included a real-world example, which LACKS the /s modifier but still fires. With NO modifiers, [^\[]* apparently matches newlines. If you look at the debug output (line 2), you can see the newline (delimiting two Received headers) that it matched. Maybe this is a perl regexp issue? -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
