On Fri, 16 Jul 2010 17:12:22 +0200
Norman Uittenbogaart <norm...@gmail.com> 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
Dspam-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-user
