On Wed, 2014-02-26 at 06:07 -0500, Kevin A. McGrail wrote:
> The logic below just says (if the yes no feature is available). That
> was added in 3.4. So the logic you are writing just says if I am
> running 3.4, x otherwise y.
>
> The goal of the can was to write a different report that used a
>
All that the expression
can(Mail::SpamAssassin::Conf::feature_yesno_takes_args)
does is to check whether the _YESNO_ macro can take arguments.
It is always true in 3.4.0.
I have no idea how it could work before the way you intended.
Mark
The logic below just says (if the yes no feature is available). That was added
in 3.4. So the logic you are writing just says if I am running 3.4, x
otherwise y.
The goal of the can was to write a different report that used a special yes /no
feature.
Regards,
KAM
Noel Butler wrote:
>It w
It worked perfectly with prior versions, only since upgrade to 3.4.0 is
it using the first " its not spam" option, when it is spam (scores
clearly show that), and not using the second *is* spam segment like
previous versions did correctly, no mater I've wiped the test and will
just force it report
Best I read, all that says is, if running 3.4 (which has that feature) is spam.
The logic is the problem.
Regards,
KAM
Noel Butler wrote:
>Hi,
>Did anything change in custom report for 3.4.0 ?
>
>if can(Mail::SpamAssassin::Conf::feature_yesno_takes_args)
>report blah blah blah not spam
>else
