January 2011 - dovecot

[Dovecot] permissions on auth-userdb
by spamvoll＠googlemail.com 28 Jun '12

28 Jun '12

Hi.. im still trying to upgrade to 2.0. Im getting: dovecot: lda: Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Permission denied (euid=10000(vmail) egid=10000(vmail) missing +r perm: /var/run/dovecot/auth-userdb, euid is not dir owner) the error is correct caus its owned by root. My Questions is who should own it ? Im not sure how that works, what process/user calls the auth-userdb ? The auth-userdb returns the args generated in master.conf, right ? i think comment out the user and group setting in master.conf will fix it but im not sure if that is the securest way. the mails come from postfix via dovecot-lda Hans master.conf service auth { # auth_socket_path points to this userdb socket by default. It's typically # used by dovecot-lda, doveadm, possibly imap process, etc. Its default # permissions make it readable only by root, but you may need to relax these # permissions. Users that have access to this socket are able to get a list # of all usernames and get results of everyone's userdb lookups. unix_listener auth-userdb { mode = 0600 #user = vmail #group = vmail } auth-ldap.conf.ext passdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf.ext } userdb { driver = static args = uid=vmail gid=vmail home=/home/MAILBOXES/%u/ mail=/home/MAILBOXES/%u/mail }

5 8

[Dovecot] gnutls support
by Daniel L. Miller 12 Jun '12

12 Jun '12

Other than license issues, is there an advantage to using gnutls vs openssl? Or is openssl superior - at least in the current implementations? -- Daniel

2 3

[Dovecot] Folder Aliases - Revisited Yet Again
by Daniel L. Miller 11 Apr '12

11 Apr '12

I just did a search through my archives - seems this topic has been requested a few times since my posting two years ago. I asked about a specific implementation - which Mr. Sirainen never commented on. He was probably focused on something more important at the time - like a paying job. So I'll ask again... Calling Timo! If we can't get clients to agree on a "standard" set of folders (probably reasonably safe assumption) and if protocol implementations of variations of "*LIST*" are too far in the future...what about having alternative folder names presented based on login name - maybe by an extension? So where my usual login might be "user(a)domain.com", and that would continue to be supported as the default login, I could now have "user(a)domain.com+thunderbird", "user(a)domain.com+mobile", etc.? And each of those extensions would then have a system-wide map defining folder name relationships, like "Sent=Sent Items". Does this seem doable? -- Daniel

2 4

[Dovecot] Some Dovecot LDA version sends MDN rather than DSN for overquota.
by Mark Sapiro 12 Feb '12

12 Feb '12

It appears that there is some version of the Dovecot LDA that is sending an RFC 3798 MDN rather than an RFC 3464 DSN to report non-delivery to a user who is over quota. See <https://bugs.launchpad.net/mailman/+bug/693134> for a discussion of this and <https://bugs.launchpad.net/mailman/+bug/693134/+attachment/1773018/+files/A…> for the actual MDN message. The issue is that apparently a user was over quota and Dovecot returned an MDN with a disposition of deleted. This is intended to mean the the mail was delivered to the user but the user deleted it without reading it. If the message was actually not delivered, this should be reported to the MTA so it can return an appropriate SMTP status, or the LDA should send an RFC 3464 DSN with an action of failed. Note that I do not actually use the Dovecot LDA nor do I have any access to the system where the notice in the bug report was received, so I may have incomplete information and this may not be relevant to current versions of Dovecot, but I think it is wrong for Dovecot to report over quota non-delivery via an MDN. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 3

[Dovecot] Quota Calculation seems to be wrong when using dsync
by Thomas Leuxner 12 Feb '12

12 Feb '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Recently I encountered odd quota increases when using 'dsync' with the latest and greatest: 2.0.8 (89936539e3b8). Say you got something in place like this: plugin { quota = dict:user::file:%h/mdbox/dovecot-quota quota_rule = *:storage=1GB quota_rule2 = Trash:storage=+10%% } Kick off a manual backup: $ dsync -u user(a)domain.tld backup mdbox:/<path to backup>/mdbox This results in doubling the quota for the backed up user. It doesn't seem to matter whether 'mirror' or 'backup' mode is used, both increase the "source" quota. Doesn't sound right to me. You can only get to the "real" usage by running a recalc manually: $ doveadm quota recalc -u user(a)domain.tld Anyone else seen this? Regards Thomas P.S. Merry Christmas -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) iEYEARECAAYFAk0VtH8ACgkQ+meF/S97aXjUkwCfdZFpUPCOY9UiukT+G68jCHHr mmMAnRHz56BXMzpC84CIYvUn4KHpl8OA =M0AZ -----END PGP SIGNATURE-----

2 9

[Dovecot] dovecot evaluation on a 30 gb mailbox
by Rajesh M 04 Nov '11

04 Nov '11

hi all i use qmail toaster. i recently changed over to dovecot. posting below my evaluation on the same my machine dual core dual xeon 5140 processor, with 4 gb ram, centos linux with qmailtoaster i had setup a qmail tap account which backups up data for a client of mine mailbox size over 30 gb setup dovecot with squirrelmail and logged in it had over one hundred and thirty nine thousand emails 139019 emails in the 30 gb mailbox Reports 1) first login : took 7 minutes to parse 139019 mails but never timed out. this was simply impossible with courier 2) the next login it took 5 seconds by which time the mail numbers increased to 139045 3) next i changed squirrelmail display preference to list 500 mails per page and then clicked on inbox ... expecting dovecot to take atleast around 1-2 mins to show the mails ... the mails were displayed in just 8 seconds .. awesome performance qmailtoaster is simply waiting for a dovecot integration i am evaluating the stability of dovecot now in the next 2-3 weeks i post stability report rajesh

19 43

[Dovecot] doveadm "-S <socket_path>" option enabled in 2.0.8?
by David Warden 03 Jun '11

03 Jun '11

I apologize if this is a stupid question but I just compiled 2.0.8 and am trying to use doveadm to get the quota for a user using the -S <socket_path> option because I have different options for the various local IPs that dovecot listens on. For example, my default quota is filesystem (NFS rquota) and I can get that by doing: doveadm quota get -u warden which tells me: Quota name Type Value Limit % User quota STORAGE 1313476 1766400 74 But when I try to get my quota on a different local IP using the -S flag to doveadm: doveadm quota get -u warden -S 137.238.2.244:143 I am told: get: invalid option -- S The strange thing is doveadm's usage says that the -S option is valid for quite a few commands and in the man pages for those commands it looks like they should work for the way I'm calling doveadm. In the 2.0.8 source I also see code that looks like it should be parsing the -S flag. I can telnet to 127.0.0.1:143 and do ". getquotaroot inbox" which gives me the same information as "doveadm quota get -u warden" and I can telnet to 137.238.2.244:143 and ". getquotaroot inbox" also tells me my quota, but I'm hoping to use doveadm to periodically recalc my Maildir++ quota and update the squat FTS indexes and for that to happen doveadm needs to be able to be told what local IP address/port to connect to (I think). Here's my doveconf -n: # 2.0.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-194.26.1.0.1.el5 x86_64 Red Hat Enterprise Linux Server release 5.5 (Tikanga) nfs auth_cache_size = 10 M auth_master_user_separator = * auth_mechanisms = plain login auth_username_format = %Ln deliver_log_format = msgid="%m" subject="%s" from="%f" size=%p result="%$" first_valid_uid = 0 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_log_format_elements = user=%u method=%m rip=%r lip=%l lport=%a mpid=%e encryption=%c mail_location = maildir:/home/%Lu/Maildir:CONTROL=/Mail/mailhome/%Lu/.dovecot:INDEX=/Mail/mailhome/%Lu/.dovecot mail_log_prefix = "service=%s user=%u rip=%r lip=%l " mail_nfs_storage = yes mail_plugins = zlib quota mail_log notify fts fts_squat 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 namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes } passdb { args = cache_key=%u dovecot driver = pam } plugin { autocreate = Trash autocreate2 = Drafts autocreate3 = Sent autosubscribe = Trash autosubscribe2 = Drafts autosubscribe3 = Sent fts = squat mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append mail_log_fields = uid box msgid size from subject flags mail_log_group_events = yes quota = fs:User quota quota_exceeded_message = Quota exceeded (mailbox for user is full). Please see http://go.geneseo.edu/emailoverquota for help deleting messages while over quota. sieve = /Mail/mailhome/%Lu/.filter.sieve sieve_dir = /Mail/mailhome/%Lu/.sievedir } postmaster_address = postmaster(a)geneseo.edu protocols = imap pop3 sieve quota_full_tempfail = yes service managesieve-login { inet_listener sieve { port = 4190 } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { mail_plugins = zlib quota mail_log notify fts fts_squat sieve } protocol lda { mail_plugins = zlib quota mail_log notify fts fts_squat sieve zlib } protocol imap { imap_logout_format = bytes(in/out)=%i/%o mail_max_userip_connections = 50 mail_plugins = zlib quota mail_log notify fts fts_squat quota imap_quota autocreate imap_zlib fts fts_squat } protocol sieve { managesieve_logout_format = bytes(in/out)=%i/%o } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = bytes(in/out)=%i/%o, top=%t/%p, retr=%r/%b, del=%d/%m, mailbox-size=%s pop3_uidl_format = UID%u-%v } local 137.238.2.244 { mail_location = maildir:/Mail/mailhome/$Lu/mailtest/Maildir:CONTROL=/Mail/mailhome/%Lu/mailtest/.dovecot2-control:INDEX=/Mail/mailhome/%Lu/mailtest/.dovecot2-index namespace { location = prefix = } plugin { quota = maildir:User quota quota_rule = *:storage=200M quota_rule2 = Trash:storage=+50M zlib_save = gz zlib_save_level = 6 } } local 137.238.1.1 { protocol imap { ssl_cert = </etc/pki/tls/certs/imaps.geneseo.edu.crt ssl_key = </etc/pki/tls/private/imaps.geneseo.edu.key } } local 137.238.2.244 { protocol imap { ssl_cert = </etc/pki/tls/certs/mailtest.geneseo.edu.crt ssl_key = </etc/pki/tls/private/mailtest.geneseo.edu.key } } local 137.238.1.1 { protocol pop3 { ssl_cert = </etc/pki/tls/certs/imaps.geneseo.edu.crt ssl_key = </etc/pki/tls/private/imaps.geneseo.edu.key } } local 137.238.2.244 { protocol pop3 { ssl_cert = </etc/pki/tls/certs/mailtest.geneseo.edu.crt ssl_key = </etc/pki/tls/private/mailtest.geneseo.edu.key } }

3 3

[Dovecot] dovecot-lda 2.0.8 Panic: stream doesn't support seeking backwards
by Jacky Chan 16 May '11

16 May '11

Running 2.0.8 as IMAP server and LDA with quota support. The environment is: os: 64bit Slackware 13.1.0 fs: ext3 smtp: postfix-2.7.2 imap: dovecot-2.0.8 The dovecot setting in postfix master.cf dovecot unix - n n - - pipe user=mailuser:mailuser argv=/usr/dovecot/libexec/dovecot/dovecot-lda -d ${recipient} Everything work fine and mail can be saved to user's home directory without error when the user is not over quota. If over quota occur, the maillog log this error message: Command died with signal 6: "/usr/dovecot/libexec/dovecot/dovecot-lda". Command output: lda: Debug: Loading modules from directory: /usr/dovecot/lib64/dovecot lda: Debug: Module loaded: /usr/dovecot/lib64/dovecot/lib10_quota_plugin.so lda: Debug: auth input: xxx(a)xxx.com home=/home/mail_data/xxx.com/xxx quota_rule=*:storage=1024 uid=9203 gid=9203 lda: Debug: Added userdb setting: plugin/quota_rule=*:storage=1024 lda(xxx(a)xxx.com): Debug: Effective uid=9203, gid=9203, home=/home/mail_data/xxx.com/xxx lda(xxx(a)xxx.com): Debug: Quota root: name= backend=maildir args= lda(xxx(a)xxx.com): Debug: Quota rule: root= mailbox=* bytes=1048576 messages=0 lda(xxx(a)xxx.com): Debug: Quota rule: root= mailbox=Trash bytes=+104857600 messages=0 lda(xxx(a)xxx.com): Debug: maildir++: root=/home/mail_data/xxx.com/xxx, index=, control=, inbox=/home/mail_data/xxx.com/xxx lda(xxx(a)xxx.com): Debug: Quota root: name= backend=maildir args= lda(xxx(a)xxx.com): Debug: none: root=, index=, control=, inbox= lda(xxx(a)xxx.com): Panic: stream doesn't support seeking backwards lda(xxx(a)xxx.com): Error: Raw backtrace: /usr/dovecot-2.0.8/lib64/dovecot/libdovecot.so.0(+0x3ca6a) [0x7ffc860a1a6a] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x32) [0x7ffc860a1b52] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7ffc8607c031] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot.so.0(+0x45834) [0x7ffc860aa834] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot.so.0(i_stream_seek+0x86) [0x7ffc860a81f6] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot.so.0(+0x45d87) [0x7ffc860aad87] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot.so.0(i_stream_read+0x64) [0x7ffc860a8284] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7ffc860a894d] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot.so.0(message_parse_header_next+0x73) [0x7ffc8608e973] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot.so.0(+0x2b1a7) [0x7ffc860901a7] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x29) [0x7ffc860908f9] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot.so.0(message_parser_parse_header+0x41) [0x7ffc86090a91] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot-storage.so.0(index_mail_parse_headers+0xc2) [0x7ffc86535fd2] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot-storage.so.0(+0x462ea) [0x7ffc865362ea] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot-storage.so.0(index_mail_get_first_header+0x5e) [0x7ffc8653689e] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot-lda.so.0(mail_deliver_get_log_var_expand_table+0x48) [0x7ffc862eb848] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot-lda.so.0(+0x593a) [0x7ffc862eb93a] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot-lda.so.0(mail_deliver_log+0x118) [0x7ffc862ebb28] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x2e2) [0x7ffc862ec012] -> /usr/dovecot-2.0.8/lib64/dovecot/libdovecot-lda.so.0(mail_deliver+0xe3) [0x7ffc862ec2c3] -> /usr/dovecot/libexec/dovecot/dovecot-lda(main+0x67c) [0x402dec] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x7ffc858f4c7d] -> /usr/dovecot/libexec/dovecot/dovecot-lda() [0x402549] I tried run the dovecot-lda at command line: /usr/dovecot/libexec/dovecot/dovecot-lda -d xxx(a)xxx.com < some_saved_mail The result is dovecot quota plugin reject the mail and send an over quota message back to the sender without any error. It seems that the error is only occur with postfix pipe command. Any hints?

4 5

[Dovecot] linking problems of dovecot 2.0.3
by Funda Wang 30 Apr '11

30 Apr '11

Hello, I'm currently packaging dovecot 2.0.3 under Mandriva Linux. It has been using LDFLAGS="-Wl,--as-needed -Wl,--no-undefined" for shared libraries for over two years[1]. And I've found there are lots of linking problems with dovecot 2.0.3. After some investigation, I've made small patch regarding dovecot 2.0.3, posted here: http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/dovecot/branches… Even after applying mentioned patch, it still produce following errors: make[3]: Entering directory `/tmp/dovecot/BUILD/dovecot-2.0.3/src/login-common' /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -O2 -g -pipe -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fstack-protector-all -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -export-dynamic -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-O1 -Wl,--build-id -o libdovecot-login.la -rpath /usr/lib64/dovecot liblogin.la ../lib-dict/libdict.la ../lib-dovecot/libdovecot.la -lrt libtool: link: gcc -shared -Wl,--as-needed -Wl,--whole-archive ./.libs/liblogin.a ../lib-dict/.libs/libdict.a -Wl,--no-whole-archive -Wl,--as-needed -Wl,--no-undefined -Wl,-z -Wl,relro -Wl,-O1 -Wl,--build-id -Wl,-rpath -Wl,/tmp/dovecot/BUILD/dovecot-2.0.3/src/lib-dovecot/.libs -Wl,-rpath -Wl,/usr/lib64/dovecot -L/usr/lib64/ -lssl -lcrypto -ldl -lpthread ../lib-dovecot/.libs/libdovecot.so -lrt -Wl,-soname -Wl,libdovecot-login.so.0 -o .libs/libdovecot-login.so.0.0.0 ./.libs/liblogin.a(client-common.o): In function `get_var_expand_table': /tmp/dovecot/BUILD/dovecot-2.0.3/src/login-common/client-common.c:372: undefined reference to `login_binary' ./.libs/liblogin.a(client-common.o): In function `client_create': /tmp/dovecot/BUILD/dovecot-2.0.3/src/login-common/client-common.c:50: undefined reference to `client_vfuncs' ./.libs/liblogin.a(client-common-auth.o): In function `client_auth_parse_args': /tmp/dovecot/BUILD/dovecot-2.0.3/src/login-common/client-common-auth.c:111: undefined reference to `login_binary' /tmp/dovecot/BUILD/dovecot-2.0.3/src/login-common/client-common-auth.c:99: undefined reference to `login_binary' ./.libs/liblogin.a(client-common-auth.o): In function `client_auth_begin': /tmp/dovecot/BUILD/dovecot-2.0.3/src/login-common/client-common-auth.c:491: undefined reference to `login_binary' ./.libs/liblogin.a(login-settings.o): In function `login_settings_read': /tmp/dovecot/BUILD/dovecot-2.0.3/src/login-common/login-settings.c:195: undefined reference to `login_binary' ./.libs/liblogin.a(main.o): In function `login_access_lookup_next': /tmp/dovecot/BUILD/dovecot-2.0.3/src/login-common/main.c:185: undefined reference to `login_binary' ./.libs/liblogin.a(main.o):/tmp/dovecot/BUILD/dovecot-2.0.3/src/login-common/main.c:338: more undefined references to `login_binary' follow ./.libs/liblogin.a(main.o): In function `main': /tmp/dovecot/BUILD/dovecot-2.0.3/src/login-common/main.c:358: undefined reference to `login_process_preinit' ./.libs/liblogin.a(main.o): In function `main_init': /tmp/dovecot/BUILD/dovecot-2.0.3/src/login-common/main.c:308: undefined reference to `clients_init' ./.libs/liblogin.a(main.o): In function `main_deinit': /tmp/dovecot/BUILD/dovecot-2.0.3/src/login-common/main.c:317: undefined reference to `clients_deinit' ./.libs/liblogin.a(sasl-server.o): In function `anvil_check_too_many_connections': /tmp/dovecot/BUILD/dovecot-2.0.3/src/login-common/sasl-server.c:187: undefined reference to `login_binary' collect2: ld returned 1 exit status Could somebody take a look? Thanks. [1]: http://wiki.mandriva.com/en/Underlinking

2 6

[Dovecot] restarting director
by Cor Bosman 08 Apr '11

08 Apr '11

Hi all, anyone having any problems with restarting the director? Every time I bring down 1 of the director servers, reboot it, or just restart it for whatever reason, im seeing all kinds of problems. Dovecot generally always gives me this error: Jan 20 22:49:55 imapdirector3 dovecot: director: Error: Director 194.109.26.173:444/right disconnected before handshake finished It seems the directors cant agree on forming a ring anymore, and this may be leading to problems with clients. I mostly have to resort to bringing down all directors, and restarting them all at once. Not really a workable solution. As an example, last night for a few hours we were getting complaints from customers about being disconnected, and the only obvious error in the log was the one above, after one of my colleagues had to restart a director because of some changes in the syslog daemon. After I restarted all directors withing a few seconds of each other, all complaints disappeared. Timo, i know ive asked similar questions before, but the answer just eludes me. If I have 3 director servers, and need to take one down and restart it, what is the proper method to reconnect the ring? In practice, I cant seem to work it out and I mostly end up with the above error until I just restart them all. Not fun with 20.000 clients connected. Cor

3 4