On Sat, 17 Jul 2010 09:01:00 +0200
Norman Uittenbogaart <[email protected]> wrote:
> Hello Stevan,
>
Hello Norman,
> What I am trying todo is the following,
>
> The norman@ user is a longer time user which database is reasonably trained..
> The sander@ user and its domain is a new user.
>
> I was hoping to get the sander@ user and its domain to use the
> training of norman@ until they reached the minimal training of 2500
> emails.
>
aha. Now I see. The problem is that as soon as a user is member of a shared or
shared,managed group he/she can not be part of another group.
If you would look into the documentation of DSPAM then you should see that what
you want is not possible:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
RESTRICTIONS!
A user can simultaneously be a member of multiple classification / global
group(s) and multiple inoculation group(s), but a user cannot be a member
of both a classification / global group(s) or inoculation group(s) and a
shared or shared,managed group.
A user can not be member of:
* both a classification group and a global group
* multiple merged groups
* multiple shared or shared,managed groups
* both a shared group or shared,managed group and a merged group
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
What you could do is to use dspam_merge and merge norman@<domain1>.nl into
sander@<domain2>.nl and completely drop that classification group?
> With kind regards,
--
Kind Regards from Switzerland,
> Norman
>
Stevan Bajić
> On Fri, Jul 16, 2010 at 9:28 PM, Stevan Bajić <[email protected]> wrote:
> > On Fri, 16 Jul 2010 17:12:22 +0200
> > Norman Uittenbogaart <[email protected]> wrote:
> >
> >> Hello I have the following problem.
> >> I have two shared,managed groups, but for only one group this is indeed
> >> working.
> >> For the other group it still has a separate quarantine etc ...
> >> The group beginning with norman@ works.
> >>
> >> What am I doing wrong here ?
> >> Group files looks like the below and I restarted dspam,
> >>
> >> groupname:classification:*norman@<domain1>.nl
> >> sander@<domain2>.nl:shared,managed:*@<domain2>.nl
> >> norman@<domain1>.nl:shared,managed:*@<domain1>.nl,*@<domain3>.nl,*@<domain4>.nl
> >>
> > This is not going to work. A user who is member of a shared group CAN NOT
> > be part of a CLASSIFICATION or INOCULATION or MERGED group.
> >
> > The format for the classification group is as well wrong. If you read the
> > README you will see this here:
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> > The format for a classification group is:
> >
> > group1:classification:user1,user2,userN
> > group2:classification:user3,user4,userN
> >
> > The group name (in the example above 'group1', 'group2') can be anything
> > you
> > like. It is not used by DSPAM and does even not have to be unique.
> >
> > The user/member list for inoculation group allows the following syntax:
> > user1 : Exact match of user with the name "user1"
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> >
> > So no wildchar support for the classification group.
> >
> >
> > The format for the shared,managed group however is correct.
> >
> >
> > Could you write what you want to accomplish with your setup? Your config
> > does not tell me enough to guess what your really want. However.... that
> > "norman@<domain1>.nl" group is anyway shared so there is no need to use a
> > classification group "groupname" for that shared group. Trainings and
> > classifications for the "norman@<domain1>.nl" for the domains <domain1>.nl
> > and <domain3>.nl and <domain4>.nl are anyway already doing what the
> > classification group is supposed to do (the shared group model does way
> > more then classification group has to offer). So this only leaves the
> > "sander@<domain2>.nl" shared group. I guess you wanted the
> > "sander@<domain2>.nl" to profit from the tokens of the
> > "norman@<domain1>.nl" group so therefore you have set up that
> > classification group. Right?
> >
> > Can you try to write in plain words what kind of goal you are trying to
> > reach with groups?
> >
> >
> >>
> >> dspam is the latest version (3.9.0+git20100615-4)
> >>
> > Older version would not work at all with CLASSIFICATION groups. I fixed
> > that bug in the new DSPAM and now groups are doing exactly what they are
> > supposed to do.
> >
> > --
> > Kind Regards from Switzerland,
> >
> > Stevan Bajić
> >
> > ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Sprint
> > What will you do first with EVO, the first 4G phone?
> > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> > _______________________________________________
> > Dspam-user mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/dspam-user
> >
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Dspam-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspam-user
