In the original email I posted, I'm asking two questions.
1. I'm getting two warnings about nonexistent rules. Is this fixable? And
2. why is lint reporting a random set of 13 missing descriptions when I have
actually put those descriptions into local.cf?
As to the descriptions themselves, it's
On Mon, 7 Mar 2016, Charles Sprickman wrote:
I’ve been running with some daily training for a little over a week and I’m
seeing less spam in my inbox. I’ve seen a few things slip through because
bayes tipped them below the default score, these were two phishing emails.
Here’s some rule stats
> On Feb 29, 2016, at 3:18 PM, Reindl Harald wrote:
>
> Am 29.02.2016 um 21:05 schrieb Charles Sprickman:
>>> On Feb 29, 2016, at 4:23 AM, Reindl Harald wrote:
>>>
>>> Am 29.02.2016 um 06:24 schrieb Charles Sprickman:
I’ve not had much luck with Bayes - when I had it enabled recently on a
On Mon, 7 Mar 2016 19:11:12 +0100
Reindl Harald wrote:
> Am 07.03.2016 um 19:05 schrieb RW:
> > If someone gets around to creating descriptions for these rules you
> > wont see them
>
> maybe *you* won't see them, others do
>
> they are part of the report-headers instead something like
I kn
On 3/7/2016 1:05 PM, RW wrote:
On Mon, 7 Mar 2016 15:12:25 +
Robert Chalmers wrote:
I?ve added descriptions, grabbing the actual RULE name with awk, and
creating the list that way.
{
a=$12;
print "describe " a " Spam check applied.";
}
The result is like this.
describe L
Am 07.03.2016 um 19:10 schrieb Ryan Coleman:
Thanks to this header my server automatically filtered your email into my
scanned spam folder.
Seems appropriate enough.
:)
fix your rule to have a "starts with" instead a "contains" :-)
On Mar 7, 2016, at 12:05 PM, Reindl Harald wrote:
Am 0
Thanks to this header my server automatically filtered your email into my
scanned spam folder.
Seems appropriate enough.
:)
> On Mar 7, 2016, at 12:05 PM, Reindl Harald wrote:
>
>
>
> Am 07.03.2016 um 19:01 schrieb Chalmers:
>> I see. Hmmm.
>> I have the system really screwed down tight, a
Am 07.03.2016 um 19:05 schrieb RW:
On Mon, 7 Mar 2016 15:12:25 +
Robert Chalmers wrote:
The result is like this.
describe LONG_TERM_PRICE Spam check applied.
describe MULTIPART_ALT_NON_TEXT Spam check applied.
describe TVD_IP_OCT Spam check applied.
describe HK_NAME_DR Spam check applied.
I see. Hmmm.
I have the system really screwed down tight, and understand how I can use the
mail reading client to run a rule to divert such a message to a specific
mailbox. I thought it may be possible to divert messages that do get marked as
spam to be dumped.
I can't see how some get through
On Mon, 7 Mar 2016 15:12:25 +
Robert Chalmers wrote:
> I?ve added descriptions, grabbing the actual RULE name with awk, and
> creating the list that way.
>
> {
> a=$12;
> print "describe " a " Spam check applied.";
> }
>
>
> The result is like this.
> describe LONG_TERM_PRICE
Am 07.03.2016 um 19:01 schrieb Chalmers:
I see. Hmmm.
I have the system really screwed down tight, and understand how I can use the
mail reading client to run a rule to divert such a message to a specific
mailbox. I thought it may be possible to divert messages that do get marked as
spam to
On Sun, 6 Mar 2016 07:35:37 +
rob...@chalmers.com.au wrote:
> I'm trying to drop such messages, not have them still appear in my
> mailbox, but can't find a way? Any ideas?
Are you sure you really want to do this? IMO it's a really bad idea.
Rejecting or discarding very high-scoring spam is
I’ve added descriptions, grabbing the actual RULE name with awk, and creating
the list that way.
{
a=$12;
print "describe " a " Spam check applied.";
}
The result is like this.
describe LONG_TERM_PRICE Spam check applied.
describe MULTIPART_ALT_NON_TEXT Spam check applied.
descr
On 3/6/2016 1:35 AM, rob...@chalmers.com.au wrote:
I'm trying to drop such messages, not have them still appear in my
mailbox, but can't find a way? Any ideas?
Setup a procmail recipe to move the messages to /dev/null.
https://wiki.apache.org/spamassassin/UsedViaProcmail
--
IBM i on Power Sys
14 matches
Mail list logo
