[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
GROUP/EXGROUP going nuts ?
- To: hobbit (at) hswn.dk
- Subject: GROUP/EXGROUP going nuts ?
- From: "Jerry Yu" <jjj863 (at) gmail.com>
- Date: Wed, 29 Nov 2006 10:27:04 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=sGipKRijPfa7MYWBEgq9yv0wjzt/S5KAAKr2VfROpDfpN7HjT7a28F7O485+qPD5vJjZjw5UDy2cTN7cOZ3vsd6bfLWg+ZC+KzdARXsaLfaKXDu1vY45zF0LgDqlt8C7bsedHHWWXRAZ7fKpBS3mIQLVJr9yHut0Q6lW4lQ5AEU=
if I have a alert rule as below in hobbit-alerts.cfg, every alerts will
match the GROUP rule, plus EXGROUP doesn't seem to be effective either.
Such behavior was observed from the real email received as well as by the
insightful "bbcmd hobbitd_alert --test".
Only one group is defined.
GROUP=junkgroup
MAIL junkgroup (at) my.domain color=red
HOST=* EXGROUP=junkgroup
MAIL realdeal (at) my.domain color=yellow
It is the same case if the group named in hobbit-alerts.cfg is bogus, aka,
not defined in hobbit-clients.cfg.
Only one group is defined in hobbit-clients.cfg, as listed below:
log /tmp/junkgroup.log %(?-i)USER-ID:|EXCEPTION: IGNORE=kilobyte
group=junkgroup
In case it matters, this is the only Hobbit server running on CentOS 4.3/i386.
Version==4.2RC1-20060712