... you're usually OK ... debug might tell you why ... might be able to
tell you why ... it probably did.
Haha. Now that we've cleared THAT up ;-)
Kidding aside ... I understand.
Thanks,
JTDeLys
JT DeLys wrote:
One comment that I'll share: After reading the list, wiki, general web,
etc I got the clear message that lint+debug-ing is a wise/necessary step.
It wasn't immediately clear to me that these 'failures' weren't real
problems (that's why I'm asking here, of course). Is there s
This is normal, some regexes can't be optimized. They're still used
though.
> What do I do about these?
Nothing.
That's good. And, thanks.
(Re-enabling loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody now).
One comment that I'll share: After reading the list, wiki, general web, etc
I go
JT DeLys wrote:
I've installed Spamassassin version 3.2.1, and have enabled
loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody
in 'init.pre'.
After downloading the latest rule updates using sa-update, when I
compile the rules using
sa-compile --sudo -D
It finishes "correctly" at
C
After reading a bunch of typical posts on the user list, is THIS issue/topic
(sa-compile related) better reported to the Developer list or the Bug
Reporting tools?
Thanks,
JTDeLys
I've installed Spamassassin version 3.2.1, and have enabled
loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody
in 'init.pre'.
After downloading the latest rule updates using sa-update, when I compile
the rules using
sa-compile --sudo -D
It finishes "correctly" at
COMPILE DONE
Checking