Sorry If I annoyed somebody about what I said.

Maybe, my language has a prob in expressing to everybody what I thought.

@ Brett : Thanks for your information. I guess some main points you gave me
I haven't known from the ASSP wiki. As I said above, my mail system receives
~300.000 emails a day (my company has nearly 10,000 email users), so I can't
handle everything in the logs file, just using it to trace/check whenever
users reports, it's enough to give me stress.

@ Mr.Fritz : just my 2cent. I admit that my knowledge about ASSP, I'm new
with ASSP so sorry for any incovenient.

@ Daniel: Thank you very much. I have a mistake about mail archive in
spam/ham folders (maybe my assp system marked some ham emails -> spam and
leave it at spam mail folder, anyway my mistake :) )

1 & 2 : *Understood* :)

3: I see that a new db will be created after running rebuildspam process.
But in ASSP 2 (5.0x), when Rebuild spam (and move2num) was built-in ASSP, I
see an option that the new data will be added in the existing DB (am I
wrong, again :( ?) + my misunderstandings about rebuild spam --> annoying
people here.

So Can you explain about that new option in ASSP 2 (5.0x), Mr.Fritz?

4 & 5 : Totally agree :)

On Fri, Aug 22, 2008 at 1:10 AM, Daniel L. Miller <[EMAIL PROTECTED]> wrote:

> Fritz Borgstedt wrote:
> >> after that remove/delete those spam/ham emails and start a new
> >> process from the "beginning", of course, the next rebuild spam DB
> >> will add new data to the existing Bayesian DB was created.
> >>
> >
> > Of course?
> > I give up.
> Among other things - I think Duc has a language problem here.  We'll get
> through it - anyone "punishing" ASSP under this kind of load deserves a
> little more patience so he'll keep stress testing it for the rest of us
> humble mortals.
>
> Duc, let me try to clear up a few misunderstandings.
>
> 1.  The ASSP ham/spam database is only intended for use by ASSP to
> generate the bayesian DB.  It is not, should not, and really can not, be
> used as a mail archive, temporary storage, or end-user garbage bin.
> This is something you MUST understand before proceeding - it is best to
> pretend that while it LOOKS like messages are being stored in the
> spam/ham folders, these files are actually unreadable garbage and should
> be left alone.  It's even possible in a future version these folders and
> partial message copies will go away altogether.
>
> So if you HAVE been using the spam/ham folders for any purpose - stop
> immediately or you're only going to give yourself pain.
>
> 2.  If you want to have an actual mail archive, make use of the
> different cc options.  In particular, use the "sendAllSpam" setting for
> archiving copies of spam.  Explore the "Copy Spam & Ham" settings to
> achieve what you want.
>
> 3.  The rebuild process examines the files in the spam/ham folders and
> generates a database of keywords.  This database is COMPLETELY
> RE-WRITTEN each time the rebuild process is run.
>
> 4.  ASSP's intent is to adapt to current conditions.  So as new junk
> messages and formats appear, ASSP learns and works to block the new
> attacks.  However, it is also good to keep in mind defenses that have
> already worked.  For this reason, ASSP continuously updates its spam/ham
> database - but "scatters" the stored messages so the updates are gradual
> - it's quite possible messages older than 3 months will continue to exit
> in your repository for some time.  But the rebuild generates a snapshot
> picture of the database AT THAT MOMENT.
>
> 5.  Based on this, your idea of running rebuild when the spam/ham
> reaches some number cannot work.  What may be possible, at some time in
> the future, would be to automatically run the rebuild based on message
> traffic.  But at this time, that feature does not exist, and the
> scheduled rebuild process has been sufficient for every installation.
> It is VITAL that you configure the database settings as you have been
> advised already.
>
> --
> Daniel
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Assp-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/assp-user
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to