Robert - elists-2 wrote:
>
>
>>
>> I have *always* run SA through MailScanner. This configuration is not
>> new,
>> I
>> have run it this way for *years*. The only thing that's new is the
>> version
>> of SA. As soon as I upgraded to v3.2.3, the problems started.
>>
>> If you can't be helpful, I can certainly understand. But I don't need an
>> argument, nor your attitude.
>
> Marablue,
>
> You haven't helped yourself or tried any suggestions to check your own
> stuff
> out moron...
>
> You are like the only person I have ever seen on this list that really
> needs
> to check this out...
>
> http://www.catb.org/~esr/faqs/smart-questions.html
>
> it is probably the most polite clue stick out there...
>
> - rh
>
>
Read it, probably years before you were born.
My initial post gave every detail needed, except for the output of --lint
-D, which I provided when Daryl kindly asked.
You seem to have missed my first post, I'll past it here again:
--begin copy&paste--
I've used custom rules in /etc/mail/spamassassin/local.cf since v3.1.7 with
never a problem. Since upgrading to v3.2.3, it's as if SpamAssassin isn't
seeing/registering the same rules that have always worked.
I'm running SpamAssassin on CentOS 4.5, with cPanel and through a
MailScanner package, so spamd is disabled through cPanel.
Any time I've added a custom rule I make sure it passes lint, then reload
MailScanner. I've never had a problem with SA not "acknowledging" the rules
in local.cf until v3.2.3. This version isn't seeing rules that have been
there several versions back.
I've run --lint -D, and SA is reading local.cf (I can post the log if
needed). The only other thing I changed a few days before this started was
switching from using openprotect.com's SARE channels to dostech.net. I can't
imagine that change would have caused this, though, and the rules pass lint.
SA is just...chosing to ignore them.
I'm completely perplexed on what to do, aside from downgrading to a
previously known working (for me) version. Any ideas on what to check/change
would be appreciated.
-- end copy&paste --
The only other information I could have possibly include would have been my
version of Perl. I didn't say "v3.2.3 is broken! OMG it's not working!" I
simply and politely asking for suggestions as to what I might have missed,
because SINCE UPGRADING TO SA 3.2.3, not only has spam dramatically
increased, but changing custom rules in local.cf doesn't seem to change
anything on the spam that comes through, when this has worked perfectly well
in previous versions of SA.
I've read this list for a long time. I've seen some really, truly STUPID
questions come through...and seen them be answered, civilly, helpfully. The
only difference is I don't have a masculine username. I truly hate coming
off as a cranky feminist who complains I am being treated unfairly because
of my gender.
But when it quacks like a duck...it's a duck.
--
View this message in context:
http://www.nabble.com/v3.2.3-isn%27t-recognizing-local.cf-custom-rules-tf4289420.html#a12218144
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
