- dovecot - dovecot.org

[Dovecot] v1.2.12 and debug
by Walt Shekrota 30 Mar '11

30 Mar '11

Is there some kind of extended debug that might show why my maildir is not foundat login? It has worked off and on, once briefly today then no more. I'm going around twiddling knobs guessing at this point which is foolish. I need some real bread crumbs to indicate what is going wrong. I've tried all kinds of .conf file ... example file etc. I figured using the least number of settings should get me somewhere but I still have no luck. I'd love to just give up and load that PPA for 2.x but I have no idea what package to install in debian. (I have the PPA update) Thanks. -Walt

2 1

[Dovecot] dovecot.conf
by Walt Shekrota 30 Mar '11

30 Mar '11

In 1.2.12 or there abouts how do changes in the dovecot.conf happen? After doing the sig HUP I have noted there is generally a delay in the recognition of items in my .conf. An example I had logging set off, turned it on and it was several restarts before I again saw logging? This delay is driving me nuts in trying to figure out what needs to change. Thanks. -Walt

2 2

[Dovecot] dovecot-lda can not find home dir
by Pete 30 Mar '11

30 Mar '11

Hello, Running dovecot 2.0.11 and pigeonhole on Fedora 14 x86_64. The lda can not seem to find the user's home directory, yet other parts of dovecot (pop3, imap, managesieve) can. Grepping "Effective uid" from /var/log/maillog: Mar 29 11:21:34 new-eagle dovecot: pop3(pete): Debug: Effective uid=726, gid=726, home=/home/pete Mar 29 11:23:18 new-eagle dovecot: imap(pete): Debug: Effective uid=726, gid=726, home=/home/pete Mar 29 11:23:52 new-eagle dovecot: managesieve(pete): Debug: Effective uid=726, gid=726, home=/home/pete Mar 29 11:24:53 new-eagle dovecot: managesieve(pete): Debug: Effective uid=726, gid=726, home=/home/pete Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: Effective uid=726, gid=726, home= Although mail does get delivered, the .dovecot.lda-dupes file can not be created because of this: Mar 29 11:26:15 new-eagle dovecot: lda: Debug: Loading modules from directory: /usr/lib64/dovecot Mar 29 11:26:15 new-eagle dovecot: lda: Debug: Module loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: Effective uid=726, gid=726, home= Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: fs: root=/home/pete/mail, index=, control=, inbox=/var/spool/mail/pete Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: userdb lookup skipped, username taken from passwd lookup for process euid Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: none: root=, index=, control=, inbox= Mar 29 11:26:15 new-eagle dovecot: lda(pete): Error: User pete doesn't have home dir set, disabling duplicate database Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: sieve: using sieve path for user's script: /home/pete/.dovecot.sieve Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: sieve: opening script /home/pete/.dovecot.sieve Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: sieve: script /home/pete/.dovecot.sieve successfully compiled Mar 29 11:26:15 new-eagle dovecot: lda(pete): Debug: sieve: executing script from /home/pete/.dovecot.sieve Mar 29 11:26:15 new-eagle dovecot: lda(pete): sieve: msgid=<FF641E3CEA3748B5B7D678ABE85F1A7B@pete1>: stored mail into mailbox 'INBOX' Dovecot seems to be able to determine the user's home directory, but I do not know how to tell dovecot-lda where it is. Running "doveadm user pete" produces: userdb: pete system_groups_user: pete uid : 726 gid : 726 home : /home/pete In /home/pete, the .forward file is: | "/usr/libexec/dovecot/dovecot-lda" Entry from /etc/passwd: pete:x:726:726:Peter:/home/pete:/bin/false Output of dovecot -n: # 2.0.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.35.11-83.fc14.x86_64 x86_64 Fedora release 14 (Laughlin) ext4 auth_cache_size = 10 M auth_debug = yes auth_mechanisms = login plain auth_verbose = yes disable_plaintext_auth = no listen = * mail_debug = yes mail_location = mbox:/home/%u/mail:INBOX=/var/spool/mail/%u:INDEX=MEMORY 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 mbox_write_locks = fcntl passdb { driver = pam } plugin/sieve = /home/%u/.dovecot.sieve plugin/sieve_dir = /home/%u/sieve protocols = pop3 imap sieve rejection_reason = Sorry, your message was automatically rejected:%n%r rejection_subject = failure notice re: %s service managesieve-login { inet_listener sieve { port = 4190 } } ssl = no userdb { driver = passwd } protocol lda { mail_plugins = sieve I did update from dovecot-2.0.9 (which the lda could find the home directory) but I also had to change the mail_location from: mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=MEMORY to: mail_location = mbox:/home/%u/mail:INBOX=/var/spool/mail/%u:INDEX=MEMORY Also had to change: plugin/sieve = ~/.dovecot.sieve plugin/sieve_dir = ~/sieve To: plugin/sieve = /home/%u/.dovecot.sieve plugin/sieve_dir = /home/%u/sieve ... in order for 2.0.11 to function. Any thoughts on how to get the home dir passed correctly to lda ? Thanks, Pete

2 3

[Dovecot] service auth { client_limit=4096 } is lower than required under max. load (5720
by Frank Bonnet 30 Mar '11

30 Mar '11

Hello Since I started up dovecot2 this morning I get this kind of warning message when I start Dovecot Help appreciated thanks doveconf: Warning: service auth { client_limit=4096 } is lower than required under max. load (5720) Stopping dovecot. Waiting for PIDS: 79978, 79978. doveconf: Warning: service auth { client_limit=4096 } is lower than required under max. load (5720) Starting dovecot. doveconf: Warning: service auth { client_limit=4096 } is lower than required under max. load (5720) Warning: service auth { client_limit=4096 } is lower than required under max. load (5720)

2 1

[Dovecot] migrating to dovecot
by Alexandre Chapellon 30 Mar '11

30 Mar '11

Hello, I am trying to setup a migration scenario from an proprietary solution to dovecot IMAP/POP3. Whereas am only at the strating point, things appear quite complicated because of the following reasons: - The proprietary solution uses special/own/proprietary mailbox format (wich is more like maildir but is not maildir) - I don't have direct access to the filesystem where the mails are stored. The best I could do would be a snapshots of the filesystem - I have about 1,5TB of mail data. - Having users to be forced to empty their mailbox before migration or re-download their whole mailbox after migration would be something hard for me to present as a correct option. Am looking for advices that would avoid me loosing time searching in bad directions. Or even point me to a miraculous tool thatdoes all magic while i have a beer :) Best regards. -- horoa: la voie est libre

4 6

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

30 Mar '11

I am curious why these do not seem to match? It especially bothers me that the modes set are different. Am I missing something? Thanks. -Walt

2 1

[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