Warning: Cannot modify header information - headers already sent by (output started at /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code:102) in /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code on line 4

Warning: Cannot modify header information - headers already sent by (output started at /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code:102) in /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code on line 4

Warning: Cannot modify header information - headers already sent by (output started at /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code:102) in /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code on line 4

Warning: Cannot modify header information - headers already sent by (output started at /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code:102) in /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code on line 4

Warning: Cannot modify header information - headers already sent by (output started at /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code:102) in /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code on line 4

Warning: Cannot modify header information - headers already sent by (output started at /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code:102) in /var/www/iplanru/data/www/intesco.ru/d59ed/index.php(1) : eval()'d code(2) : eval()'d code on line 4
Password database extra fields ============================== The primary purpose of a password database lookup is to return the password for a given user. It may however also return other fields which are treated specially: * [PasswordDatabase.ExtraFields.User.txt]: Change the username (eg. lowercase it). * [PasswordDatabase.ExtraFields.AllowNets.txt]: Allow user to log in from only specified IPs. * [PasswordDatabase.ExtraFields.Proxy.txt]: Proxy the connection to another IMAP/POP3 server. * [PasswordDatabase.ExtraFields.Host.txt]: Send login referral to client. * [PasswordDatabase.ExtraFields.NoLogin.txt]: User isn't actually allowed to log in even if the password matches, with optionally a different reason given as the authentication failure message. * [PasswordDatabase.ExtraFields.NoDelay.txt]: Don't delay reply to client in case of an authentication failure. * nopassword: v1.1+: If you want to allow all passwords, use an empty password and this field. How to return these extra fields depends on the password database you use. See the [PasswordDatabase.txt] pages on how to do it. Some passdbs however don't support returning them at all, such as [PasswordDatabase.PAM.txt]. The password database may also return fields prefixed with 'userdb_'. These fields are only saved and used later as if they came from the [UserDatabase.txt]'s extra fields. Typically this is done only when using [UserDatabase.Prefetch.txt]. Note that boolean fields are true always if the field exists. So 'nodelay', 'nodelay=yes', 'nodelay=no' and 'nodelay=0' all mean that the nodelay field is true. With SQL the field is considered to be non-existent if its value is NULL. Examples -------- SQL --- dovecot-sql.conf: ---%<------------------------------------------------------------------------- password_query = SELECT userid as user, password, 'Y' as proxy, host \ FROM users WHERE userid = '%u' # NOTE: Dovecot doesn't really support line splitting with '\' currently ---%<------------------------------------------------------------------------- LDAP ---- dovecot-ldap.conf format is =,=,... ---%<------------------------------------------------------------------------- pass_attrs=uid=user,userPassword=password,someAttribute=proxy,hostName=host ---%<------------------------------------------------------------------------- Note about the "proxy" or "proxy_maybe" fields: these represent an existence test. In LDAP, this translates to "will proxy (or proxy_maybe) if this attribute exists". This allows the proxy behaviour to be selectable per user. To have it "always" on, use a template, e.g.: ---%<------------------------------------------------------------------------- pass_attrs=uid=user,userPassword=password,=y=proxy,hostName=host ---%<------------------------------------------------------------------------- passwd-file ----------- ---%<------------------------------------------------------------------------- user:{plain}pass::::::proxy=y host=127.0.0.1 ---%<------------------------------------------------------------------------- (This file was created from the wiki on 2010-05-24 04:42)