index aacfe236849c054b29c866bf73c3a1c7804bcd35..fac7b505394b9c3f2c849ce17159f68fdadfde69 100644 (file)
For every plugin, you can provide at least four additional hooks:
.I postcreate,
-.I postdelete,
+.I postremove,
.I postmodify
and
.I check.
The
.I logging
statement enables event logging on GOsa side. Setting it to
-.I syslog,
-GOsa will log every action a user performs via syslog. Setting it to
-.I mysql,
-GOsa will log every action to a mysql server, defined in the
-GOsa systems plugin. Both values can be combined as a comma seperated
-list.
+.I true,
+GOsa will log every action a user performs via syslog. If you use
+rsyslog and configure it to mysql logging, you can browse all events
+within GOsa.
-GOsa will not log anything, if the logging value is empty.
+GOsa will not log anything, if the logging value is empty or set to
+false.
.PP
.B loginAttribute
statement determines if GOsa should remove the mailbox from your IMAP
server or keep it after the account is deleted in LDAP.
+.B cyrusAutocreateFolders
+.I string
+.PP
+The
+.I cyrusAutocreateFolders
+statement contains a comma seperated list of personal IMAP folders that
+should be created along initial account creation.
+
.B postfixRestrictionFilters
.I path
.PP
If you have only one release, or want to define a default release to be shown
by GOsa, define the
-.I defaultFaiRelease
+.I defaultFaiRelease="ou=sarge,ou=fai,ou=configs,ou=syst..."
within the
.I faiManagement
class definition