On 14.08.2012 19:32, Cristian wrote:
[....]
[....]
Y run daily:
dspam_merge user1 user2 user3 -o globaluser
The globaluser is the merged group. With this command the data of the
users is put into the globaluser really?
It should. That's at least what the command dspam_merge is supposed to do.
So when delete the data of the users the dspam read the data from the
globalgroup?
Yes. The data is (should be) in the globalgroup. And it is read from
there. But look at this (as an example).
globalgroup has 1'000'000 tokens and 100'000 processed messages
user data has 1'000 tokens and 100 processed messages
Now assume a inbound message has 100 tokens and those 100 tokens fully
get a hit in globalgroup then you have 100 tokens out of 1 Million. Now
assume you get 100 tokens fully hit the user data then you have 100
tokens out of 1'000 tokens. I think you don't need much mathematical
knowledge to understand that the user hit has more weight than the same
hit on the globalgroup.
This is ok?
Yes. It is okay.
This is bad?
No. It is not bad. IMHO it is unusual to do that daily merge but why not?
How train the global merged group?
With dspam_train maybe?
This not is really a user,
This does not matter for DSPAM.
and the accouts run in mdbox format. The idea is train the globalgroup
from the trained users.
Then maybe using a managed group would be better?
Cristian.
--
Kind Regards from Switzerland,
Stevan Bajić
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dspam-user mailing list
Dspam-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-user
