- dovecot - dovecot.org

[Dovecot] 1.2 problem 'dovecot -n' vs dovecot.conf
by Walt Shekrota 30 Mar '11

30 Mar '11

To elaborate, if there is a database associated with this setup it is really fubar. note: tail of dovecot -n lda: postmaster_address: postmaster mail_plugins: sieve quota_full_tempfail: yes deliver_log_format: msgid=%m: %$ rejection_reason: Your message to <%t> was automatically rejected:%n%r auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 504 socket: type: listen client: path: /var/spool/postfix/private/dovecot-auth mode: 432 user: postfix group: postfix plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve This in no way represents the settings in my dovecot.conf. It seems to have rembered old .conf settings and mixed them. At no time was mode 504 set or even 432. What am I doing wrong? Thanks. -Walt I'm also toying with the idea of loading 2.x if I can figure out the PPA stuff.

2 1

[Dovecot] doveadm
by Walt Shekrota 30 Mar '11

30 Mar '11

Hi Where does this utility reside for installation. I use Ubuntu and installed dovecot-imapd and dovecot-pop3d so far. Does it now ship in the regular dovecot installation packages? Thanks. -Walt

4 3

[Dovecot] Dovecot-2.0.11 searches in all LDAP directory
by Басов Евгений 29 Mar '11

29 Mar '11

Hello. I have some users IDs in different OUs with different passwords. Base OU for mail server is 'ou=Mail, dc=ph, dc=com' Trying manual search: # ldapsearch -b 'ou=Mail, dc=ph, dc=com' -D 'cn=bind, ou=Users, dc=ph, dc=com' -w XXX -s sub -h mainserv.ph.com '(&(objectClass=qmailUser)(uid=someuser))' uid mailMessageStore … # extended LDIF … uid: someuser mailMessageStore: /var/mail/someuser/Maildir/ # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 It works fine. My dovecot configuration: # 2.0.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.36-gentoo-r5 x86_64 Gentoo Base System release 2.0.1 base_dir = /var/run/dovecot/ listen = * login_trusted_networks = 192.168.1.0/24 mail_location = maildir:~/.maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date passdb { args = * driver = pam } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin/sieve = ~/.dovecot.sieve plugin/sieve_dir = ~/sieve protocols = imap ssl_cert = </etc/ssl/dovecot/server.pem ssl_key = </etc/ssl/dovecot/server.key userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } verbose_proctitle = yes protocol lda { mail_plugins = sieve } My /etc/dovecot/dovecot-ldap.conf.ext: hosts = mainserv.ph.com dn = cn=bind, ou=Users, dc=ph, dc=com dnpass = XXX debug_level = 255 auth_bind = yes ldap_version = 3 base = ou=Mail, dc=ph, dc=com scope = subtree user_attrs = mailMessageStore=home user_filter = (&(objectClass=qmailUser)(uid=%u)) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=qmailUser)(uid=%u)) I tested IMAP over telnet: $ telnet mainserv.ph.com 143 Trying 192.168.1.252... Connected to mainserv.ph.com. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN] Dovecot ready. a001 LOGIN someuser password1 Two passwords are tested: for uid from ou=Mail and ou=Users. LDAP logs of searches: slapd[1917]: filter: (&(objectClass=posixAccount)(uid=someuser)) slapd[1917]: attrs: slapd[1917]: uid slapd[1917]: userPassword slapd[1917]: uidNumber slapd[1917]: gidNumber… and etc after this: slapd[1917]: => access_allowed: search access to "cn=John Smith,ou=Mail,dc=ph,dc=com" "objectClass" requested slapd[1917]: => dn: [2] ou=mail,dc=ph,dc=com slapd[1917]: => acl_get: [2] matched slapd[1917]: => acl_get: [2] attr objectClass… and etc I have some questions: 1. Why is it searches in another LDAP places, not only ou=Mail, dc=ph, dc=com? 2. It not put mailMessageStore from ou=Mail, dc=ph, dc=com. Why? 3. How disable lookup in another LDAP places exept ou=Mail, dc=ph, dc=com? Thanks for answers.

2 3

[Dovecot] Upgrade to v2.0 conf file fails
by Nikolaos Milas 29 Mar '11

29 Mar '11

Hi, I am trying to use the command: doveconf -n -c dovecot-1.conf > dovecot-2.conf to upgrade my dovecot.conf file, but it fails (see below). Judging from the message that vsz_limit is the new setting for login_process_size, I have retried using login_process_size=256 rather than login_process_size=64 (which was the initial value), but the error persists. Please advise. Thanks, Nick Output of "doveconf -n -c" command: =========================================================================================================================== doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in dovecot.conf:1: protocols=imaps is no longer necessary, remove it doveconf: Warning: Obsolete setting in dovecot.conf:1: protocols=pop3s is no longer necessary, remove it doveconf: Warning: Obsolete setting in dovecot.conf:6: ssl_cert_file has been replaced by ssl_cert = <file doveconf: Warning: Obsolete setting in dovecot.conf:7: ssl_key_file has been replaced by ssl_key = <file doveconf: Warning: Obsolete setting in dovecot.conf:8: ssl_ca_file has been replaced by ssl_ca = <file doveconf: Warning: Obsolete setting in dovecot.conf:12: login_process_size has been replaced by service { vsz_limit } doveconf: Warning: Obsolete setting in dovecot.conf:13: login_process_per_connection has been replaced by service { service_count } doveconf: Warning: Obsolete setting in dovecot.conf:25: imap_client_workarounds=outlook-idle is no longer necessary doveconf: Warning: Obsolete setting in dovecot.conf:25: imap_client_workarounds=netscape-eoh is no longer supported doveconf: Warning: Obsolete setting in dovecot.conf:59: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf: Warning: Obsolete setting in dovecot.conf:62: passdb ldap {} has been replaced by passdb { driver=ldap } doveconf: Warning: Obsolete setting in dovecot.conf:66: userdb ldap {} has been replaced by userdb { driver=ldap } doveconf: Warning: Obsolete setting in dovecot.conf:70: auth_user has been replaced by service auth { user } doveconf: Error: service(pop3-login): vsz_limit is too low doveconf: Fatal: Error in configuration file dovecot.conf: service(pop3-login): vsz_limit is too low ===========================================================================================================================

1 1

[Dovecot] global sieve not working
by Barry Kwok 29 Mar '11

29 Mar '11

My global sieve rule is not working and do not compile. But per-user sieve is working. Here is my dovecot -n: log_path: /var/log/dovecot.log protocols: imap pop3 ssl: no 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: 501 mail_gid: 501 mail_location: maildir:/var/vmail/%u/Maildir/:INDEX=/var/vmail/%u/Maildir/ 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 acl imap_acl mail_plugins(imap): quota imap_quota acl imap_acl mail_plugins(pop3): mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: shared separator: / prefix: shared/%%u/ location: maildir:%%Lh/Maildir:INDEX=%Lh/Maildir/shared/%%Lu list: children lda: postmaster_address: root mail_plugins: sieve quota autocreate expire auth_socket_path: /var/run/dovecot/auth-master sieve_global_path: /var/vmail/sieve/dovecot.sieve log_path: /var/log/sieve.log auth default: mechanisms: plain login default_realm: mydomain.net user: vmail username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_+@ passdb: driver: pam passdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot-mysql.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: dict:user::proxy::quota quota: maildir quota_rule: *:storage=0 acl: vfile acl_shared_dict: file:/var/spool/dovecot/shared-mailboxes.db expire: Trash 7 Trash/* 7 Junk 30 expire_dict: proxy::expire sieve: /var/vmail/sieve/%Ld/%Ln/dovecot.sieve dict: quota: mysql:/etc/dovecot-dict-quota.conf expire: db:/var/lib/dovecot/expire.db By reading sieve.log, it simple ignore sieve_global_path: /var/vmail/sieve/dovecot.sieve but the per user sieve /var/vmail/sieve/%Ld/%Ln/dovecot.sieve is working --barry

4 6

[Dovecot] file permissions
by Walt Shekrota 29 Mar '11

29 Mar '11

Dovecot 1.2.12 maildir format using :LAYOUT=fs (my Mail dir came from KDE) I can't remember the permissions of the /Mail/ directory because I haven't been concerned with it too much until now. I think they were user:user or user:mail. Now a new mail ends up 600 root:mail. (in alternate directories) When I start my mutt client to the imap server it gets an error for any folder containing a root:mail new mail file. I think the root ownership is a procmail side effect? If I chmod 760 Mail/folder/* (then the new emails show in dovecot without the access error) It appears mail comes to the INBOX fine just not individual folders On the initial access, dovecot gets a "missing +r perm" or "+x" in the log. 1: What permission structure should permeate my Mail dir? 2: What might affect the incoming mail file getting wrong permissions/ownership? I'm thinking the later may be a procmail issue unless it is related to initial incorrect permissions? Thanks for any insight. -Walt

3 4

[Dovecot] Trouble with password scheme module
by Ian R. Justman 29 Mar '11

29 Mar '11

Hi, all. About two and a half years ago, I wrote a hack to add an additional MD5-based password scheme to Dovecot, but I wrote it as a hack to src/auth/password_scheme.c since it was relatively easy to do, and I needed to get a machine running since the machine I was replacing, a Sun Ultra 5 running Post.Office, had dying hard drives. Now, I'm actually sitting down and adapting it as a module and am having trouble getting it to work. The code tarball itself can be picked up here: http://www.ian-justman.com/code/dovecot/password_scheme_po_smd5.tar.gz Before I continued, I made sure that a system-level account worked: # telnet <server IP> 110 Trying <server IP>... Connected to <server IP>. Escape character is '^]'. +OK Dovecot ready. user <username> +OK pass <password> +OK Logged in. quit +OK Logging out. Connection closed by foreign host. I then enabled the module, which introduces the password scheme "PO-SMD5". I have Dovecot's default scheme set to SMD5. If I get a password hash whose value has a {PO-SMD5} tag on it, the session looks like the following: # telnet <server IP> 110 Trying <server IP>... Connected to <server IP>. Escape character is '^]'. +OK Dovecot ready. user <user with PO-SMD5 password> +OK pass <user's password> -ERR Authentication failed. quit +OK Logging out Connection closed by foreign host. The following entry is deposited into the system log: Mar 28 17:44:51 <hostname> dovecot: auth: Error: sql(<username>,<server IP>): Unknown scheme PO-SMD5 However, when I try using an account covered by the system (which does work when the plugin isn't loaded in dovecot.conf), the session looks like the following: mikuru# telnet <server IP> 110 Trying <server IP>... Connected to <server IP>. Escape character is '^]'. +OK Dovecot ready. user <user with system password> +OK pass <user's password> Connection closed by foreign host. The following entry is deposited into the system log: Mar 28 17:45:13 <hostname> dovecot: pop3: Error: dlopen(/usr/local/lib/dovecot/lib_password_scheme_po_smd5.so) failed: /usr/local/lib/dovecot/lib_password_scheme_po_smd5.so: Undefined symbol "password_scheme_unregister" Otherwise, the patch I developed under 1.x applies cleanly to 2.0.x's password_scheme.c and works perfectly as a builtin. This work was done under FreeBSD 8.1-RELEASE amd64. Any ideas? --Ian. -- Ian R. Justman UNIX hacker. Anime fan. Any questions? ianj (at) ian-justman.com

1 2

[Dovecot] xi.rename-it.nl problems
by Robert Schetterer 28 Mar '11

28 Mar '11

Hi , i know there were errors reported before with autobuild packs from xi.rename-it.nl , hint was purge and remove old dovecot packs, but at reinstall i ever get such ucfr: Attempt from package dovecot-pop3d to take /etc/dovecot/conf.d/20-pop3.conf away from package dovecot-common ucfr: Aborting. on a few packs ,any idea? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 2

[Dovecot] dovecot auth password mismatch
by david＠davidwbrown.name 28 Mar '11

28 Mar '11

Hello dovecot gods, after using Postfix with webmail for 8 years the new gen of email smartphones forces me to consider using IMAP. Actually, for several months I was successfully using IMAP. I believe the reason why IMAP worked previously (before migrating to the Cloud) the hosting server and the client machines were considered local by the system. Now, I have moved everything to a Cloud service. And, now attempts to use my Ubuntu Evolution or iPhone generates the following error condition in my logs: dovecot: auth(default): client in: AUTH 1 PLAIN service=imap lip=xxx.yyy.www.zzz rip=75.214.160.72 lport=143 rport=59107 resp=AGRhdmlkAGx1dGVmaXNr dovecot: auth(default): passwd(kilroy,75.214.160.72): lookup dovecot: auth(default): passwd(kilroy,75.214.160.72): Password mismatch dovecot: auth(default): passwd(kilroy,75.214.160.72): CRYPT(mypass) != 'x' dovecot: auth(default): new auth connection: pid=15522 dovecot: auth(default): client out: FAIL 1 user=kilroy ******************* dovecot -n ******************* 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.34.1-rscloud x86_64 Ubuntu 10.04.2 LTS log_timestamp: %Y-%m-%d %H:%M:%S disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mail_location: maildir:~/Maildir mbox_write_locks: fcntl dotlock auth default: realms: myname.name, hisname.name, hername.name default_realm: myrealm.com username_format: %n verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd userdb: driver: passwd

1 0

[Dovecot] Support not compiled in for passdb driver ldap
by Stéphane Wartel 28 Mar '11

28 Mar '11

Hello, From repo, the lastest release 2.0.11-0~auto+32 does not have ldap support :/ auth: Fatal: Support not compiled in for passdb driver 'ldap' Regards, Stephane

1 1