Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread Nick Edwards
proven wrong my arse, like everything "proven wrong according to reindl" means SFA and does NOT make it wrong just because YOU think it is wrong. I think its right, other members of this list think its right and the SA devies think its right, live with it, you were already told what to do to over

Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread Reindl Harald
Am 25.01.2016 um 23:45 schrieb Nick Edwards: Just look at the energy he's spent whining about it -V- the energy he could have spent to lower/zero the score what happened long ago but a local workaround makes proven wrong behavior not right - see below i run likely the most customized

Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread Reindl Harald
Am 25.01.2016 um 23:45 schrieb Nick Edwards: just ignore reindl, most the world does (on the few lists he's not been booted off - yet), because its his way or the wrong way - in his eyes only of course, and history shows your wasting your time trying to explain to him thats not how the world wo

Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread Nick Edwards
just ignore reindl, most the world does (on the few lists he's not been booted off - yet), because its his way or the wrong way - in his eyes only of course, and history shows your wasting your time trying to explain to him thats not how the world works, no-one is here to make it work according to

Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread Reindl Harald
Am 25.01.2016 um 16:22 schrieb Matus UHLAR - fantomas: On 25.01.16 15:17, Reindl Harald wrote: not worth an argument when it's simply wrong and hits mostly clear ham and is broken by definition looking at *random* headers? cat maillog | grep FSL_HELO_BARE_IP_2 | grep "result: Y" | wc -l 21 ca

Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread Matus UHLAR - fantomas
On 25.01.16 15:17, Reindl Harald wrote: not worth an argument when it's simply wrong and hits mostly clear ham and is broken by definition looking at *random* headers? cat maillog | grep FSL_HELO_BARE_IP_2 | grep "result: Y" | wc -l 21 cat maillog | grep FSL_HELO_BARE_IP_2 | wc -l 130 cat mai

Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread Reindl Harald
Am 25.01.2016 um 15:43 schrieb RW: On Mon, 25 Jan 2016 15:17:38 +0100 Reindl Harald wrote: one time for the PTR Not worth an argument - masschecker set the score based on spam corpus lower the score and have a nice day not worth an argument when it's simply wrong and hits mostly clear ham

Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread RW
On Mon, 25 Jan 2016 15:17:38 +0100 Reindl Harald wrote: one time for the PTR > > > > Not worth an argument - masschecker set the score based on spam > > corpus > > > > lower the score and have a nice day > > not worth an argument when it's simply wrong and hits mostly clear > ham and is broke

Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread Reindl Harald
Am 25.01.2016 um 15:25 schrieb Axb: On 01/25/2016 03:17 PM, Reindl Harald wrote: masschecker is not worth an argument in 2016: 02-Jan-2016 00:22:49: SpamAssassin: No update available 03-Jan-2016 00:32:25: SpamAssassin: No update available 04-Jan-2016 00:03:32: SpamAssassin: No update available

Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread Axb
On 01/25/2016 03:17 PM, Reindl Harald wrote: masschecker is not worth an argument in 2016: 02-Jan-2016 00:22:49: SpamAssassin: No update available 03-Jan-2016 00:32:25: SpamAssassin: No update available 04-Jan-2016 00:03:32: SpamAssassin: No update available 05-Jan-2016 01:45:11: SpamAssassin: No

Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread Reindl Harald
Am 25.01.2016 um 15:07 schrieb Axb: On 01/25/2016 03:01 PM, Reindl Harald wrote: Am 25.01.2016 um 14:41 schrieb RW: On Mon, 25 Jan 2016 14:11:30 +0100 Reindl Harald wrote: there is *no point* on fire a rule on the third Received header when the HELO is pretty clear "mail1.intellij.net" and

Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread RW
On Mon, 25 Jan 2016 15:01:29 +0100 Reindl Harald wrote: > Am 25.01.2016 um 14:41 schrieb RW: > > On Mon, 25 Jan 2016 14:11:30 +0100 > > Reindl Harald wrote: > > > >> there is *no point* on fire a rule on the third Received header > >> when the HELO is pretty clear "mail1.intellij.net" and matche

Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread Axb
On 01/25/2016 03:01 PM, Reindl Harald wrote: Am 25.01.2016 um 14:41 schrieb RW: On Mon, 25 Jan 2016 14:11:30 +0100 Reindl Harald wrote: there is *no point* on fire a rule on the third Received header when the HELO is pretty clear "mail1.intellij.net" and matches PTR/A perfectly too Of cour

Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread Reindl Harald
Am 25.01.2016 um 14:41 schrieb RW: On Mon, 25 Jan 2016 14:11:30 +0100 Reindl Harald wrote: there is *no point* on fire a rule on the third Received header when the HELO is pretty clear "mail1.intellij.net" and matches PTR/A perfectly too Of course there's a point. It's intended to detect sp

Re: FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread RW
On Mon, 25 Jan 2016 14:11:30 +0100 Reindl Harald wrote: > there is *no point* on fire a rule on the third Received header when > the HELO is pretty clear "mail1.intellij.net" and matches PTR/A > perfectly too Of course there's a point. It's intended to detect spam software that's relaying through

FSL_HELO_BARE_IP_2 fires on wrong header

2016-01-25 Thread Reindl Harald
there is *no point* on fire a rule on the third Received header when the HELO is pretty clear "mail1.intellij.net" and matches PTR/A perfectly too at least 1.5 points is unacceptable for (in general questionable) deep header inspection score FSL_HELO_BARE_IP_2 1.998 1.593 1.998 1.593 Receive