Re: using existing score value in new rule's score

2019-02-22 Thread David Jones
On 2/22/19 4:37 PM, David B Funk wrote: > Is there a rule "score" syntax that allows you to use the score assigned > to an existing rule to calculate the value assigned to another rule? > > Specifically what I'm trying to do is to negate the "damage" a > particular rule does for messages that

Re: using existing score value in new rule's score

2019-02-22 Thread David B Funk
On Sat, 23 Feb 2019, RW wrote: On Fri, 22 Feb 2019 16:37:30 -0600 (CST) David B Funk wrote: Is there a rule "score" syntax that allows you to use the score assigned to an existing rule to calculate the value assigned to another rule? ... What I want to do is to create a local rule: meta

Re: using existing score value in new rule's score

2019-02-22 Thread RW
On Fri, 22 Feb 2019 16:37:30 -0600 (CST) David B Funk wrote: > Is there a rule "score" syntax that allows you to use the score > assigned to an existing rule to calculate the value assigned to > another rule? ... > What I want to do is to create a local rule: > > meta L_HTML_IMAGE_ONLY_28_FIX (

using existing score value in new rule's score

2019-02-22 Thread David B Funk
Is there a rule "score" syntax that allows you to use the score assigned to an existing rule to calculate the value assigned to another rule? Specifically what I'm trying to do is to negate the "damage" a particular rule does for messages that meet particular local criteria. For example:

Re: Semi Off-topic: VFEMail destroyed

2019-02-22 Thread Antony Stone
On Friday 22 February 2019 at 21:44:07, Alex Woick wrote: > In the end, it comes back to trust. Don't employ people you don't trust. How do you know you don't trust them until you find out you can't? Antony. -- The truth is rarely pure, and never simple. - Oscar Wilde

Re: Semi Off-topic: VFEMail destroyed

2019-02-22 Thread Alex Woick
Kevin A. McGrail schrieb am 16.02.2019 um 17:59: Insider threat detection is a whole different ball of wax from backup and disaster recovery.  However, there are numerous protocols to help for that threat. Specifically Principle of Least Privilege (POLP) and Separation of Duties.  I consider

Re: Problem with spamassassin update at /usr/bin/sa-update line 1603

2019-02-22 Thread Kevin A. McGrail
On 2/22/2019 5:36 AM, mbaldov wrote: > So I ask you if it's possible to intervene on the mirror's list with > some option so that to exclude the bad mirrors. Escalating that issue to our sysadmins list.  Thanks for reporting the problem. -- Kevin A. McGrail Member, Apache Software Foundation

Re: Problem with spamassassin update at /usr/bin/sa-update line 1603

2019-02-22 Thread RW
On Fri, 22 Feb 2019 11:36:38 +0100 mbaldov wrote: > Hello, > I have a mailserver with postfix installed (v.2.11.0) on Ubuntu 14.04 > LTS with Amavis, ClamAV and Spamassasins (v. 3.004002) > Since the last upgrade that I have done next week, the upgrade of new > signatures fails The SA rules are

Problem with spamassassin update at /usr/bin/sa-update line 1603

2019-02-22 Thread mbaldov
Hello, I have a mailserver with postfix installed (v.2.11.0) on Ubuntu 14.04 LTS with Amavis, ClamAV and Spamassasins (v. 3.004002) Since the last upgrade that I have done next week, the upgrade of new signatures fails with this messages: "/etc/cron.daily/spamassassin:Cannot open file