Displaying 7 results from an estimated 7 matches for "ldapattr".
2012 May 29
2
v2.1.7 released
http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz
http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz.sig
* Session ID is now included by default in auth and login process
log lines. It can be added to mail processes also by adding
%{session} to mail_log_prefix.
+ Added ssl_require_crl setting, which specifies if CRL check must
be successful when verifying client certificates.
+
2012 May 29
2
v2.1.7 released
http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz
http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz.sig
* Session ID is now included by default in auth and login process
log lines. It can be added to mail processes also by adding
%{session} to mail_log_prefix.
+ Added ssl_require_crl setting, which specifies if CRL check must
be successful when verifying client certificates.
+
2014 Aug 25
0
Problem overriding default quota limit for LDAP users
...1mail=maildir:/var/mail/***.ru/testmail@
***.ru#011home=/var/mail/***.ru/testmail@
***.ru/#011quota_rule=*:bytes=2048576
Information from:
http://dovecot.org/list/dovecot/2012-July/084859.html
v2.1.7 2012-05-29 Timo Sirainen
* LDAP: Compatibility fix for v2.0: ldap: If attributes contain
ldapAttr=key=template%$ and ldapAttr *doesn't exist, skip the
key*
instead of using "template" value with empty %$ part for the
key.
OK, if quotaMail not set, shall apply root quota.
Check LDAP:
ldapsearch -x -h ***.***.local -D 'dovecot' -W -b
'OU=XXX,dc=***,dc=local' -...
2012 Jul 26
4
Problem overriding default quota limit
Hi,
We get user's quota limit from LDAP. ?It works fine when user has
quota attribute in LDAP (this is when it's different from default
quota). But when user doesn't have quota limit attribute Dovecot
doesn't take default value defined in quota plugin and assign unlimit
quota to user.
Our configuration is similar to the example from wiki (
2007 Jun 15
8
ANNOUNCE: External node attributes
...Really, I''ve completely rewritten external node support. Here''s the
changelog entry:
Only ONE node source can be used -- you can use LDAP, code, or
an external node program, but not more than one.
LDAP node support has two changes: First, the "ldapattrs"
attribute is
now used for setting the attributes to retrieve from the
server (in
addition to required attriutes), and second, all retrieved
attributes
are set as variables in the top scope. This means you can
set attributes
on your LDAP nodes and...
2012 Aug 23
1
Puppet Agent VS User
.../var/log/puppet/http.log
ignorecache = false
ignoreimport = false
ignoreschedules = false
inventory_port = 8140
inventory_server = puppet
inventory_terminus = facter
keylength = 1024
lastrunfile = /var/lib/puppet/state/last_run_summary.yaml
lastrunreport = /var/lib/puppet/state/last_run_report.yaml
ldapattrs = all
ldapbase = ""
ldapclassattrs = puppetclass
ldapnodes = false
ldapparentattr = parentnode
ldappassword = ""
ldapport = 389
ldapserver = ldap
ldapssl = false
ldapstackedattrs = puppetvar
ldapstring = (&(objectclass=puppetClient)(cn=%s))
ldaptls = false
ldapuser = "...
2011 Nov 04
1
Storeconfigs and nagios and foreman
...attributes to include when querying LDAP for nodes.
All
# returned attributes are set as variables in the top-level scope.
# Multiple values should be comma-separated. The value ''all''
returns
# all attributes.
# The default value is ''all''.
# ldapattrs = all
# The password to use to connect to LDAP.
# The default value is ''''.
# ldappassword =
# Whether to search for node configurations in LDAP. See
# http://projects.puppetlabs.com/projects/puppet/wiki/LDAP_Nodes
for more information.
# ldapnodes = fal...