[Kroupware] ClamAV in kolab

[Ian Reinhart Geiser]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings
	I have some additions to add ClamAV for antivirus checking on kolab.  What=
 is=20
the policy about adding packages or provideing packages for kolab?  Have we=
=20
talked about this.  I have also have a question on adding users on the scal=
e=20
of about 2k at a time.  Currently I have a script that takes a csv file and=
=20
creates a compatable ldif file that i then upload.

	Lastly have we thought about adding the following feilds we enable systems=
 to=20
use kolab's central ldap database for pam authentication:
	objectClass: posixAccount
	objectClass: account
	 loginShell: /bin/bash
	uidNumber: xxxx
	gidNumber: xxxx
	homeDirectory: /home/xxxx
	gecos: User Name,,,,KDE Developer

	Where would I add this so that we can maintain that information from the w=
eb=20
interface, and better yet, does anyone even want this feature?  Central log=
in=20
is a real love it or hate it thing, but I can tell you when we roll out kol=
ab=20
to a company with more than 100 users, maintaining more than one passwd db=
=20
can become annoying. (i use to maintain my universities network, we had 500=
0=20
users and 4 servers all with different password systems, we just moved=20
everything the year that i left to ldap auth off of the NDS server, it was=
=20
VERY cool.)

Cheers=09
	-ian reinhart geiser
=2D --=20
=2D --:Ian Reinhart Geiser <geiseri@yahoo.com>
=2D --:Public Key: http://geiseri.myip.org:8080/publickey.txt
=2D --:Jabber: geiseri@geiseri.myip.org
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+IFAgPy62TRm8dvgRAnE1AKCzMWGKSfPStBU/oIYz3CfwZ8gN3ACgpBTC
UBfOIm3ARo2DlDCIhyjseM4=3D
=3DRmj3
=2D----END PGP SIGNATURE-----