Re: FORGED_MUA_MOZILLA & FORGED_YAHOO_RCVD

2017-05-29 Thread John Hardin
On Fri, 26 May 2017, RW wrote: On Thu, 25 May 2017 17:29:00 -0700 (PDT) John Hardin wrote: On Thu, 25 May 2017, RW wrote: Message-ID: <74e85e8d-2495-665b-372f-0144bcb2c...@mcgrail.com> header __MOZILLA_MSGID MESSAGEID =~ /^<[A-F\d]{8}\.[A-F1-9][A-F\d]{0,7}\@\S+>$/m Message-ID: S

Re: FORGED_MUA_MOZILLA & FORGED_YAHOO_RCVD

2017-05-26 Thread RW
On Thu, 25 May 2017 17:29:00 -0700 (PDT) John Hardin wrote: > On Thu, 25 May 2017, RW wrote: > > > Actually it does look like there is another problem. This is another > > Thunderbird header from this list with the same format: > > > > Message-ID: <74e85e8d-2495-665b-372f-0144bcb2c...@mcgrail.com

Re: FORGED_MUA_MOZILLA & FORGED_YAHOO_RCVD

2017-05-25 Thread Kevin A. McGrail
And Dave had things working for rule publishing as well. I need to qa some output and turn on Dns so if you get this into svn, we are almost ready. We are fighting a lot of fronts at once but they are all moving forward. Regards, KAM On May 25, 2017 8:29:00 PM EDT, John Hardin wrote: >On Thu,

Re: FORGED_MUA_MOZILLA & FORGED_YAHOO_RCVD

2017-05-25 Thread John Hardin
On Thu, 25 May 2017, RW wrote: Actually it does look like there is another problem. This is another Thunderbird header from this list with the same format: Message-ID: <74e85e8d-2495-665b-372f-0144bcb2c...@mcgrail.com> header __MOZILLA_MSGID MESSAGEID =~ /^<[A-F\d]{8}\.[A-F1-9][A-F\d]

Re: FORGED_MUA_MOZILLA & FORGED_YAHOO_RCVD

2017-05-25 Thread RW
On Thu, 25 May 2017 21:50:08 +0100 RW wrote: > On Thu, 25 May 2017 16:29:06 -0400 > Alex wrote: > > > > I have an email that hit __MOZILLA_MUA, but failed > > FORGED_MUA_MOZILLA because it didn't match __MOZILLA_MSGID. > > The rule is > > meta FORGED_MUA_MOZILLA (__MOZILLA_MUA && !__UNUSA

Re: FORGED_MUA_MOZILLA & FORGED_YAHOO_RCVD

2017-05-25 Thread RW
On Thu, 25 May 2017 16:29:06 -0400 Alex wrote: > I have an email that hit __MOZILLA_MUA, but failed FORGED_MUA_MOZILLA > because it didn't match __MOZILLA_MSGID. The rule is meta FORGED_MUA_MOZILLA (__MOZILLA_MUA && !__UNUSABLE_MSGID && !__MOZILLA_MSGID) so the rule requires __MOZILLA_MSG

Re: FORGED_MUA_MOZILLA & FORGED_YAHOO_RCVD

2017-05-25 Thread John Hardin
On Thu, 25 May 2017, Alex wrote: You can add the fix to your local SA config file: header __MOZILLA_MUAUser-Agent =~ /^mozilla\b/i I have an email that hit __MOZILLA_MUA, The current published __MOZILLA_MUA, or the fixed version above? but failed FORGED_MUA_MOZILLA because it didn

Re: FORGED_MUA_MOZILLA & FORGED_YAHOO_RCVD

2017-05-25 Thread Alex
Hi, On Thu, May 25, 2017 at 3:29 PM, John Hardin wrote: > On Thu, 25 May 2017, Abhishek Tiwari wrote: > >> Hello, >> >> I have no backgroud about . >> I am working on product which is mailserver >> >> I see a complaint online about a false positive, >> >> 1.FORGED_MUA_MOZILLA: 2.309, FORGED_YAHOO

Re: FORGED_MUA_MOZILLA & FORGED_YAHOO_RCVD

2017-05-25 Thread John Hardin
On Thu, 25 May 2017, Abhishek Tiwari wrote: Hello, I have no backgroud about . I am working on product which is mailserver I see a complaint online about a false positive, 1.FORGED_MUA_MOZILLA: 2.309, FORGED_YAHOO_RCVD: 1.63, HTML_MESSAGE: 0.001, NO_RDNS_DOTCOM_HELO: 0.823, TOTAL_SCORE: 8.702

Re: FORGED_MUA_MOZILLA & FORGED_YAHOO_RCVD

2017-05-25 Thread Antony Stone
On Thursday 25 May 2017 at 18:35:34, Abhishek Tiwari wrote: > Hello, > > I have no backgroud about . About what? > I am working on product which is mailserver What sort of mailserver (or, which product)? > I see a complaint online about a false positive, > > 1.FORGED_MUA_MOZILLA: 2.309, FORG

FORGED_MUA_MOZILLA & FORGED_YAHOO_RCVD

2017-05-25 Thread Abhishek Tiwari
Hello, I have no backgroud about . I am working on product which is mailserver I see a complaint online about a false positive, 1.FORGED_MUA_MOZILLA: 2.309, FORGED_YAHOO_RCVD: 1.63, HTML_MESSAGE: 0.001, NO_RDNS_DOTCOM_HELO: 0.823, TOTAL_SCORE: 8.702,autolearn=no 2. -0.000, BAYES_50: 1.567, FOR