- dovecot - dovecot.org

[Dovecot] pam_authenticate() failed: authentication error
by Zbigniew Szalbot 14 Mar '09

14 Mar '09

Hello, I would like to ask for your help. I have noticed some error messages issued by dovecot. Mar 13 20:00:57 relay dovecot: auth-worker(default): pam(example(a)example.com): pam_authenticate() failed: authentication error (/etc/pam.d/dovecot missing?) Not surprisingly $ l /etc/pam.d/dovecot ls: /etc/pam.d/dovecot: No such file or directory The funny thing is that authentication does work but I guess I have something misconfigured. I'd appreciate if you could help me. I am on a FreeBSD system (7.0) if that matters. Thank you! -- Zbigniew Szalbot

5 8

[Dovecot] How can i override mail_location?
by Zhang Huangbin 14 Mar '09

14 Mar '09

Hi, all. I use dovecot-1.1.11 with OpenLDAP backend. but i found the mail_location is not correct. How can i override mail_location setting in dovecot.conf? LDAP user data and dovecot config are attached below. in dovecot config, mail_location is: ---- mail_location = maildir:/%Lh/%Ld/%Ln/:INDEX=/%Lh/%Ld/%Ln/ ---- but the correct maildir should be 'homeDirectory' + 'mailMessageStore': ---- maildir:/home/vmail/a.cn/w/ww/www/ ---- LDAP user: ---- dn: mail=www(a)a.cn,ou=Users,domainName=a.cn,o=domains,dc=iredmail,dc=org objectClass: inetOrgPerson objectClass: mailUser objectClass: top cn: www sn: www uid: www mail: www(a)a.cn accountStatus: active homeDirectory: /home/vmail mailQuota: 104857600 userPassword: {SSHA}crkYO5tg8KRkOY7W3bRgjtLQ+79U4NgG enabledService: mail enabledService: smtp enabledService: pop3 enabledService: imap enabledService: deliver mailMessageStore: a.cn/w/ww/www/ ---- Dovecot ldap config file: ---- user_attrs = homeDirectory=home,=sieve_dir=/home/vmail/sieve/%Ld/%Ln/,mailMessageStore=maildir:mail,mailQuota=quota_rule=*:bytes=%$ ---- Dovecot main config file: ---- # dovecot -n # 1.1.11: /etc/dovecot.conf # OS: Linux 2.6.18-128.el5 x86_64 Red Hat Enterprise Linux Server release 5.3 (Tikanga) log_path: /var/log/dovecot.log protocols: pop3 pop3s imap imaps listen: * ssl_cert_file: /etc/pki/iRedMail/SSL_Cert.pem ssl_key_file: /etc/pki/iRedMail/SSL_Key.pem login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_uid: 500 mail_gid: 500 mail_location: maildir:/%Lh/%Ld/%Ln/:INDEX=/%Lh/%Ld/%Ln/ mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota zlib mail_plugins(imap): quota imap_quota zlib mail_plugins(pop3): quota zlib mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login default_realm: a.cn user: vmail passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot-ldap.conf socket: type: listen client: path: /var/spool/postfix/dovecot-auth mode: 438 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 438 user: vmail group: vmail plugin: quota: maildir quota_rule: *:storage=10M expire: Trash 7 Trash/* 7 Junk 30 expire_dict: proxy::expire auth_socket_path: /var/run/dovecot/auth-master sieve: /home/vmail/sieve/%Ld/%Ln/.dovecot.sieve dict: expire: db:/var/lib/dovecot/expire/expire.db ---- -- Best regards. Zhang Huangbin - Open Source Mail Server Solution for RHEL/CentOS 5.x: http://code.google.com/p/iredmail/

3 5

Re: [Dovecot] using passwd userdb with sql passdb
by Timo Sirainen 14 Mar '09

14 Mar '09

On Fri, 2009-03-13 at 16:18 -0700, Shane W wrote: > The problem may be the shane@ bit. If I delete the sql > entry, the lookup just shows 'shane'. I'm not loging in > with @ but my query does use the username,domain syntax for > instances of virtual users which don't use passwd userdb: > select username,domain,password from users > WHERE username = '%n' AND domain = '%d' Does the domain field contain an empty string instead of NULL? If so, I think the behavior is correct. Maybe change the query to: where username = '%n' and (domain = '%d' or ('%d' = '' and domain is null)) And change all the domain='' to domain=NULL.

1 0

Re: [Dovecot] Problem with sasl auth with postfix...
by Douglas M. Stanley 14 Mar '09

14 Mar '09

----- "Timo Sirainen" <tss(a)iki.fi> wrote: > On Fri, 2009-03-13 at 16:40 -0400, Douglas M. Stanley wrote: > > Yep, postfix is installed: > > > > mailserver:/etc/postfix# postconf -h mail_owner > > postfix > .. > > > Mar 13 19:16:30 mailserver dovecot: auth(default): User doesn't > exist: postfix > > Does your Postfix installation actually work? What user do you see > running the Postfix processes? Yep, works fine. The user running the postfix processes is postfix: root 4219 1 0 19:28 ? 00:00:00 /usr/lib/postfix/master postfix 4302 4219 0 19:48 ? 00:00:00 qmgr -l -t fifo -u postfix 4319 4219 0 19:49 ? 00:00:00 tlsmgr -l -t unix -u -c postfix 4352 4219 0 21:27 ? 00:00:00 pickup -l -t fifo -u -c Thanks, Doug

2 3

[Dovecot] New to list, got a quota question
by Vlad Sedov 14 Mar '09

14 Mar '09

Hello folks - I'm running dovecot on top of qmail/vpopmail/mysql, serving up about 2500 mailboxes. Everything is running very smooth and fast.... I recently upgraded dovecot to 1.1, so I'm trying to implement some extra features like IMAP quotas. I'm using the sql passdb, with the following config: driver = mysql connect = host=/var/lib/mysql/mysql.sock user=username password=password dbname=vpopmail default_pass_scheme = PLAIN password_query = SELECT CONCAT(pw_name, '@', pw_domain) AS user, pw_clear_passwd AS password FROM vpopmail WHERE pw_name = '%n' AND pw_domain = '%d' user_query = SELECT pw_dir as home, 508 AS uid, 503 AS gid FROM vpopmail WHERE pw_name = '%n' AND pw_domain = '%d' My vpopmail installation keeps the quota information in the mysql database (pw_shell field) instead of maildirsize. The quota is in maildir format, e.g. 400M or 50331648S. Unlimited quota is specified as NOQUOTA. The question is... Is it possible to make dovecot understand this format and get it directly from SQL (via user_query, for example) or would it be easier to reconfigure the vpopmail installation somehow to use maildirsize? Thanks! Vlad

2 4

[Dovecot] vpopmail support on 64 bits
by aledr 13 Mar '09

13 Mar '09

Good day! Compiling 1.1.11 with vpopmail flag on a 64bit system drop me these warnings that breaks it portability: passdb-vpopmail.c: In function 'vpopmail_lookup_credentials': passdb-vpopmail.c:71: warning: pointer targets in passing argument 2 of 'callback' differ in signedness passdb-vpopmail.c: In function 'vpopmail_preinit': passdb-vpopmail.c:141: warning: implicit declaration of function 'auth_cache_parse_key' passdb-vpopmail.c:142: warning: assignment makes pointer from integer without a cast Thanks. -- [ ]'s Aledr - Alexandre "OpenSource Solutions for SmallBusiness Problems"

2 1

[Dovecot] how to handle CA CRL updates with client certificate verification context ?
by Raphael PRECIGOUT 13 Mar '09

13 Mar '09

Hello, As far as I can read in the Dovecot SSL configuration wiki page, each CA cert must be followed by the related CA CRL in the client certificate verification context ("ssl_ca_file" setting). In my company we do have our own PKI and as soon as Client certificate is compromised we do revoke it and update the related CA's CRL. Does that mean that I have to issue a new "ssl_ca_file" file as soon as our issuing CA CRL is updated ? If yes, does someone has an idea on how to do so ? Is it then necessary to restart dovecot process (to take the "ssl_ca_file" file changes into account) ? Does Dovecot have a way to check the issuing CA CRL automatically ? (the CRL is published in DER format and is accessible though http, the URI is mentionned in the CRL Distribution points of the CA certificate) Thanks in advance for your help. Regards, Raphael

2 1

[Dovecot] Problem with sasl auth with postfix...
by Douglas M. Stanley 13 Mar '09

13 Mar '09

Hello list, I'm running into some problems, and I couldn't find any info about this anywhere on the net. I recently set up a new debian lenny machine, and used my notes from the last debian etch machine I set up, which basically is for postfix + dovecot for sasl auth. On my old etch box, in the dovecot.conf, in the auth default section, I have a socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } However, if I use the same config on my lenny setup, dovecot fails to start, and I see this in my logs: Mar 13 19:16:30 mailserver dovecot: Dovecot v1.0.15 starting up Mar 13 19:16:30 mailserver dovecot: auth(default): User doesn't exist: postfix Mar 13 19:16:30 mailserver dovecot: Auth process died too early - shutting down Mar 13 19:16:30 mailserver dovecot: child 4623 (auth) returned error 89 Now if I comment out the user and group lines, it works fine, but the socket is owned by root, and so I have to change the mode line so that it's world readable in order for postfix to use it. The version of dovecot in etch is: 1.0.rc15-2etch4 and the version in lenny is: 1.0.15-2.3 Any ideas why this might be happening? Did the syntax to do this change between those versions? Any input? I guess I don't mind leaving it world readable, but I wasted an entire morning trying everything to get it to work, so I guess I'm hoping some one atleast has an answer as to why it doesn't work. Thanks, Doug

3 5

[Dovecot] Using LDAP for Dovecot extra/regular fields
by Jack Stewart 13 Mar '09

13 Mar '09

Hi, We're moving to a dovecot proxy / server configuration in order to make sure that a users go to a specific server. If someone has used these LDAP for this, there are a few things that I wish to verify. Dovecot does not verify that type of the LDAP attribute, only that the returned value works. If a boolean is used for a yes/no field, then FALSE sets the field to no and TRUE sets the field to yes. If a multivalue attribute is used for a single value field, the last returned value for the LDAP lookup is used in that field (i.e. host will use the last value). If a string attribute is returned for a yes/no field and has any value, then the associated field is set to true. There is no automatic failover with the host field so if the remote host is down, the IMAP connection no longer works. I'm fairly sure of all of these except for the boolean. Now this is just due diligence. I don't know that turning on/off or switching LDAP attributes is the right way to go to handle failover but it might work for phased rollout. My feeling is the best configuration will be using a secondary IP address that has to be manually turned on for a host after a reboot or shutdown. This creates a poor mans "fencing". The secondary can either be brought up on another host or handled via a load balance with DSR/backup server. As a practical matter, it is probably worth setting sensible attributes for each field (i.e. numeric for host, boolean for proxy/proxy_maybe etc). Any interest in registering an LDAP object class for dovecot? ---Jack

2 2

[Dovecot] Maildir dirty syncs
by Timo Sirainen 13 Mar '09

13 Mar '09

http://dovecot.org/patches/1.1/maildir-dirty-syncs.diff This patch adds a new maildir_very_dirty_syncs setting. If set to "yes", Dovecot assumes it's the only one changing the cur/ directory (so other MDAs can add mails to new/ without problems). This makes it possible to avoid rescanning the cur/ directory all the time looking for filenames. It also looks like (in stress testing) it still scans the cur/ directory unneededly in some situations, but it shouldn't be common. Maybe I'll look into it some day to see why. I'd be interested in hearing how large performance benefits it gives, if any. If they're big I could consider adding it to v1.1.12. If they're pretty much irrelevant I probably won't even bother adding the code to v1.2. I guess you mainly see the performance benefits with large/huge mailboxes.

4 5