In the last few years, we actually coded quite a lot of tools or changes to some of the features DirectAdmin offers. One of them being SpamAssassin of course.
I can't remember why we needed to count the number of disabled SpamAssassin users, but I think it had something to do with capacity planning.
It works quite easy - and doesn't require much coding - but why reinvent the wheel.
http://servecontent.sensson.net/files/sa-enabled.phps
Usage: php -q sa-enabled.php
Sample output will look like:
If you have any questions let me know.
I can't remember why we needed to count the number of disabled SpamAssassin users, but I think it had something to do with capacity planning.
It works quite easy - and doesn't require much coding - but why reinvent the wheel.
http://servecontent.sensson.net/files/sa-enabled.phps
Usage: php -q sa-enabled.php
Sample output will look like:
Code:
[root@xeon-1 ~]# php -q sa-enabled.php
user1 has its spamfilter disabled
user2 has its spamfilter disabled
user3 has its spamfilter disabled
user4 has its spamfilter disabled
---------------------------
Disabled: 4
Enabled: 0
---------------------------If you have any questions let me know.