You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@spamassassin.apache.org on 2019/12/02 12:20:58 UTC

[Bug 7776] New: Machine Learning Online Course

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7776

            Bug ID: 7776
           Summary: Machine Learning Online Course
           Product: Spamassassin
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Building & Packaging
          Assignee: dev@spamassassin.apache.org
          Reporter: jimmyreece2345@gmail.com
  Target Milestone: Undefined

The tester didn't provide any data about the application version and testing
environment. We will talk through these details further in the article. As for
the priority, testers usually assign a priority level, which may change later.
his section raises the most questions. Here, the tester should explain Steps to
Reproduce, Actual Results, and Expected Results. A bug report should give as
much relevant information as possible. If your QA representatives don't
describe how to reproduce a bug thoroughly enough, then developers will waste
time trying to figure out what’s wrong.

After reading the description in our screenshot, web developers will
immediately ask what login credentials were used: admin, test user, or
moderator. Also, they’ll need to know the server (environment) on which the bug
was produced. In other words, did this happen on a testing server, for example,
https://testing-bugs.sprinklebit.com, or a production server, 
The tester should also have provided Expected results. These details help a
developer — who may not be very familiar with the app — understand the issue
faster. Finally, we don’t see any visual documentation of this bug, such as
attached images.
Kindly, see the URL only for machine learning online course,
https://intellipaat.com/machine-learning-certification-training-course/.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7776] Limit Bayes parsed token count

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7776

--- Comment #3 from Henrik Krohns <ap...@hege.li> ---
Just in case 3.4.4 realizes..

Sending        spamassassin-3.4/lib/Mail/SpamAssassin/Plugin/Bayes.pm
Transmitting file data .done
Committing transaction...
Committed revision 1871708.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7776] Limit Bayes parsed token count

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7776

Henrik Krohns <ap...@hege.li> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |apache@hege.li

--- Comment #1 from Henrik Krohns <ap...@hege.li> ---
On Wed, Dec 11, 2019 at 01:58:03PM +0100, Matus UHLAR - fantomas wrote:
>
> My question was, if there's a bug in the bayes code, causing it to eat too
> much of memory.  Both ~750B per token with file-based bayes or ~600B per
> token in redis-based BAYES looks like too much for me.

Not so much a bug, but we should probably add some internal limit to parsed
tokens (10000?) - a normal message would not contain more tokens.  At those
counts the per token memory usage is irrelevant (but we could look at
optimizing it too).  Just need to be careful not to create a loophole for
spammers (filling up few 50k parts with random short tokens, so last part
won't be tokenized at all?)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7776] Limit Bayes parsed token count

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7776

Henrik Krohns <ap...@hege.li> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Henrik Krohns <ap...@hege.li> ---

Quick analyze of corpus shows token counts pretty much never exceed ~2000.
Implemented some hard limits which are way abobe that, 50k tokens for body, 10k
for uris/headers.

Sending        trunk/lib/Mail/SpamAssassin/Plugin/Bayes.pm
Transmitting file data .done
Committing transaction...
Committed revision 1871706.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7776] Machine Learning Online Course

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7776

Henrik Krohns <ap...@hege.li> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
                 CC|                            |apache@hege.li
             Status|NEW                         |RESOLVED

--- Comment #1 from Henrik Krohns <ap...@hege.li> ---
spam

Anyone have permissions to delete the user?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7776] Machine Learning Online Course

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7776

Henrik Krohns <ap...@hege.li> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Building & Packaging        |trash
           Assignee|dev@spamassassin.apache.org |apache@hege.li

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7776] Limit Bayes parsed token count

Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7776

Henrik Krohns <ap...@hege.li> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|Undefined                   |4.0.0

-- 
You are receiving this mail because:
You are the assignee for the bug.