- dovecot - dovecot.org

[Dovecot] mbox sync failure
by Alnis Morics 03 Jul '09

03 Jul '09

Hi, Yesterday I had to reboot my server machine and I think there was an email client connected from the LAN during the reboot which I did not notice then. Now that mailbox is no longer accessible: as soon as I try to connect, it lets me wait forever while openin the folder, and cycles endlessly this message in the logs: Jul 2 19:40:37 myhostname dovecot: imap-login: Login: user=<username>, method=PLAIN, rip=#.#.#.#, lip=#.#.#.#, TLS Jul 2 19:40:37 myhostname dovecot: IMAP(username): unlink(/var/mail/username.lock) failed: Permission denied Jul 2 19:40:48 myhostname dovecot: IMAP(username): file mbox-sync.c: line 1372 (mbox_sync_handle_eof_updates): assertion failed: (trailer_size <= 2) Jul 2 19:40:48 myhostname dovecot: IMAP(username): Raw backtrace: imap [0x80b2081] -> imap [0x80b1f99] -> imap [0x807a536] -> imap [0x807ae71] -> imap(mbox_sync+0x422) [0x807d3c2] -> imap(mbox_storage_sync_init+0x3e) [0x807d8de] -> imap(imap_sync_nonselected+0x1c) [0x806446c] -> imap(_cmd_select_full+0xc3) [0x805be83] -> imap(cmd_select+0x19) [0x805c059] -> imap [0x805d5ef] -> imap [0x805d690] -> imap(_client_input +0x74) [0x805dd64] -> imap(io_loop_handler_run+0xf0) [0x80b7e20] -> imap(io_loop_run+0x18) [0x80b7338] -> imap(main+0x478) [0x8066388] -> /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7e36455] -> imap [0x8058561] Jul 2 19:40:48 myhostname dovecot: child 2459 (imap) killed with signal 6 (I have Debian Lenny with dovecot 1.0.15.) I tried to add the user dovecot to the group mail and give the group mail write permission to the mailbox. The permission errors stopped appearing but everything else is still there, including .lock file and 3 imap-login processes that resume as soon as I try to kill them. There are also 2 unimportant mailboxes that still work. I can view the beginning of the "username" mailbox with mc inner viewer, but it hangs as I go to the end of file. Tried to copy the file so I could freely experiment with it but the copying hung up when it reached 87 % (the file is 1.1 GB). The copied part was unreadable. Tried to formail -ds < /var/mail/username >> /backup/usernameJul3 but with the same result. Is there a way to repair the synchronization of the mbox? Or at least a way to recover its content?

1 0

[Dovecot] 64 bit vs 32 Bit
by Mario Antonio Garcia 03 Jul '09

03 Jul '09

Do you think that there is a substantial performance gain by running Dovecot in a 64 bit Architecture? Regards, Mario Antonio

3 2

[Dovecot] Dovecot Support Added to OSSEC
by Michael Starks 03 Jul '09

03 Jul '09

I have added (beta) Dovecot support for the OSSEC HIDs. It will detect certain attacks and error conditions, and optionally block the attacker (similar to fail2ban). Rather than re-hash the details here, I refer you to the OSSEC mailing list for details on how to install. I would appreciate any feedback either here, there, or privately. The idea is to get a few people trying it so I thought a post here would be good, too.

1 0

[Dovecot] Problem no update maildirsize
by Jose Luis Marin Perez 02 Jul '09

02 Jul '09

Dears Sirs, I've noticed that since the Courier to Dovecot migration have had few problems with the %usage of email accounts as they do not reflect the real use, to fix this I have to manually delete the file maildirsize and run the command vuserinfo user(a)domain.com, depending on your experience may be the cause of this problem? thanks Jose Luis _________________________________________________________________ Discover the new Windows Vista http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE

1 1

[Dovecot] about Update Road and no IDLE in CAPABILITY
by kfx 02 Jul '09

02 Jul '09

Hi list, I'm in the path of moving from courier-imap to dovecot and testing it since 1.2-rc3. So far it is very promising. Thank you for your amazing work. So my first question is: what is the recommended update road ? For now, I first "managesieve patch"/compile the source, go on to the old source folder and do a "make uninstall", switch back to the new source folder and do the "make install". As I am using dovecot-sieve and managesieve, the update is a little bit tricky. My second question is how to have the IDLE mode to appear in the server's CAPABILITY announce (without touching imap_capability in the conf ?) I think the IDLE mode is working because when I send me a mail from the server directly in command line like: " echo test | mail -s test my(a)address.com" The mail immediately pop-up in my thunderbird from my workstation. # !tel telnet 127.0.0.1 143 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] My Message ------- No IDLE. Details: - Centos 5.3 x86_64 (Selinux in permissive mode) - /proc/sys/fs/inotify/ exist - # rpm -qa | grep gamin gamin-0.1.7-8.el5 gamin-0.1.7-8.el5 gamin-devel-0.1.7-8.el5 gamin-devel-0.1.7-8.el5 - Dovecote 1.2.0 Compilation: $ ./configure --with-ldap=yes --with-notify=inotify Install prefix . : /usr/local File offsets ... : 64bit I/O polling .... : epoll I/O notifys .... : inotify SSL ............ : yes (OpenSSL) GSSAPI ......... : no passdbs ........ : passwd passwd-file shadow checkpassword ldap : -pam -bsdauth -sia -sql -vpopmail userdbs ........ : static prefetch passwd passwd-file checkpassword ldap nss : -sql -vpopmail SQL drivers .... : : -pgsql -mysql -sqlite - # dovecot --version 1.2.0 - # dovecot -n # 1.2.0: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-128.1.10.el5 x86_64 CentOS release 5.3 (Final) ext3 log_path: /var/log/dovecot-error.log info_log_path: /var/log/dovecot-debug.log protocols: imap imaps pop3 pop3s managesieve ssl_ca_file: /etc/pki/CA/chaine.crt ssl_cert_file: /etc/pki/dovecot/certs/server.pem ssl_key_file: /etc/pki/dovecot/private/server.key login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_greeting: My Message verbose_proctitle: yes mail_uid: vmail mail_gid: vmail mail_location: maildir:/var/vmail/%n mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota expire mail_plugins(imap): quota imap_quota expire mail_plugins(pop3): quota expire mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): imap_client_workarounds(managesieve): auth default: username_format: %Ln verbose: yes debug: yes passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot-ldap-userdb.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: maildir:User quota quota_rule: *:storage=10GB quota_rule2: Trash:storage=10%% expire: Trash 1 Trash/* 1 expire_dict: proxy::expire sieve_dir: /var/sieve-upload/ sieve: /var/sieve-scripts/%u.sieve dict: expire: db:/var/lib/dovecot/expire.db Thank you, kfx

2 2

[Dovecot] dovecot start up messages
by Xueron Nee 02 Jul '09

02 Jul '09

Hi, Why dovecot prints these messages when start up? And how to suppress it? # /home/mail/init/dovecot.init restart Stopping Dovecot: [ OK ] ILoading modules from directory: /home/mail/lib/dovecot/imap IModule loaded: /home/mail/lib/dovecot/imap/lib01_acl_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib02_imap_acl_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib10_quota_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib11_imap_quota_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_autocreate_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_convert_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_expire_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_fts_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_mail_log_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib20_virtual_plugin.so IModule loaded: /home/mail/lib/dovecot/imap/lib21_fts_squat_plugin.so IEffective uid=99, gid=99, home=/tmp IQuota root: name=user backend=dict args=:proxy::quota_dict Startting Dovecot: [ OK ] Thanks :) -- Xueron Nee http://www.xueron.com

2 1

[Dovecot] Directory Layout Performance
by Mario Antonio Garcia 02 Jul '09

02 Jul '09

From a performance perspective: Which Directory layout is better: 1. All mailboxes are stored in a single directory and prefixed with a dot or 2. Maildirs using physical directories, such as: Maildir/folder/subfolder/ It looks like the second option -- File Sytem Layout (LAYOUT=fs) -- could spread the load in a better way ...... I do not expect a user reaching maximum number of subfolders in linux , but what about those heavy users with a lot of sub-folders: Is there a significant performance gain by choosing a specific Directory Layout ... Any Comments? Regards, Mario Antonio

4 8

[Dovecot] keeping 2 dovcots in sync?
by joakim＠verona.se 02 Jul '09

02 Jul '09

I would like to have one master dovecot instance that gets email, and a slave dovecot on my laptop. I use maildir, and I was thinking of doing this with unison, but I suppose dovecots indexes would go out of sync whenever I used unison. There seems to be a number of imap folder synchronizers, but I have heard they are troublesome. Any hints? -- Joakim Verona

2 1

[Dovecot] dovecot lda and postfix
by Mauricio Tavares 02 Jul '09

02 Jul '09

I do not know if this is a help request to solve a problem but to understand what is going on. I am going to start with the problem description as I see it and we will go from there. I have postfix setup to use dovecot for tls/sasl in addition to its normal imap/pop3 functions. Postfix is also setup to do virtual domains, getting its information from the files valias, vmaps, and vhosts which are all located in its /etc/postfix directory: # Virtual domain stuff virtual_mailbox_domains = /etc/postfix/vhosts.txt virtual_mailbox_base = /var/spool/vmail virtual_mailbox_maps = hash:/etc/postfix/vmaps.txt # 1500:1500 is user virtual virtual_uid_maps = static:1500 virtual_gid_maps = static:1500 virtual_alias_maps = hash:/etc/postfix/valias.txt Dovecot uses its own unix passwd-like files to do authentication. In fact, as you can see, I broke them apart so I can make the actual password file readable only by root: mail_location = maildir:~/ auth default { passdb passwd-file { args = /etc/dovecot/passwd } userdb passwd-file { args = /etc/dovecot/users } } I know the norm is to use a database or at least ldap, but I had my reasons. Mailscanner is also installed. So, the whay things have been working so far was, postfix receives an email and checks if it is recipient exists here. If so, it would pass it to mailscanner and then get it back, when it would then drop it at the recipient's mailbox in /var/spool/vmail/domain.com/user. A user would then connect to dovecot to retrieve the email. And when an email was to be sent, postfix would use dovecot to do the user authentication. So far so good. Now I want to add dovecot lda so I can run the cmu sieve plugin (this is dovecot 1.0.1) primarily to move emails mailscanner (and spamassassin) thinks that are spam to each virtual user's Spam maildir directory. So, reading http://wiki.dovecot.org/LDA/Sieve/CMU, I add the following entries to dovecot.conf: protocol lda { mail_plugin_dir = /usr/lib/dovecot/modules/lda sendmail_path = /usr/lib/sendmail auth_socket_path = /var/run/dovecot/auth-master mail_plugins = cmusieve global_script_path = /etc/dovecot/scripts/dovecot.sieve mail_debug = yes log_path = /var/log/dovecot-lda info_log_path = /var/log/dovecot-lda } # I am being rather lazy in my sieve config entry. I did make sure the file # is owned by virtual:virtual plugin { sieve = /etc/dovecot/scripts/dovecot.sieve } socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = virtual # User running Dovecot LDA's deliver } # Postfix is using dovecot for SMTP AUTH (SASL) client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } Then, based on http://wiki.dovecot.org/LDA/Postfix, I edit postfix's master.cf: dovecot unix - n n - - pipe flags=DRhu user=virtual:virtual argv=/usr/lib/dovecot/deliver -f ${sender} -d ${user}@${nexthop} and main.cf: dovecot_destination_recipient_limit = 1 virtual_transport = dovecot # mailbox_virtual_domains was already defined as shown above The dovecot.sieve file looks like this: require ["fileinto", "reject"]; # Spam stuff if header :contains "X-Spam-Level" "********************" { discard; stop; } elsif header :contains "X-Spam-Status" "Yes" { fileinto "Spam"; stop; } So, I restart it and try to send a message to my account, say raub(a)domain.com, in this machine. It bounces back saying the user does not exist. I check th elog files and they seem to agree: dovecot: 2009-06-30 16:31:44 Info: auth(default): passwd-file(raub(a)domain.com): lookup: user=raub(a)domain.com file=/etc/dovecot/users dovecot: 2009-06-30 16:31:44 Info: auth(default): passwd-file(raub(a)domain.com): unknown user Now this is where I am trying to understand what is going on. It seems to me that postfix *or* dovecot went to /etc/dovecot/users looking for raub(a)domain.com. Not finding it there (I had it defined there as raub simply; I have mail_location = maildir:~/ in dovecot.conf, so the username in this file does not need to be related to the user's email address), it decided user does not exist and bounced back. My testing indicated that happened after postfix passed the email to dovecot lda (I guess that virtual_transport = dovecot means it goes to master.cf and looks for the dovecot entry and then passes the message to it). That would mean postfix is not using vmaps to see if the user exists anymore. Instead, it is delegating checking if a user exists to dovecot, which is not what I want to do. I want postfix to worry about getting mail and making sure the recipient exists. Out of the blue, if I replaced the virtual_mailbox entry with local_transport = dovecot, or nothing at all, mail is delivered as it should. My gut feeling is the master.cf dovecot entry is responsible for the problem, but I am not sure because I really do not know everything that is going on there; this is the first time I venture in that file. So, could anyone shed some light on what is causing the problem? Thanks!

4 4

[Dovecot] Dovecot / Sieve
by Joan 02 Jul '09

02 Jul '09

Hi, As the "new Sieve implementation" is using a "gratefully stolen copy of deliver.c from dovecot" (i.e. a dirty code in mail-raw.c), would it be possible for the Sieve piece 1 - to be using files from dovecot directly rather than copying&changing it (which is very bad for maintenance) 2 - to be incorporated in the hg/mercurial tree of dovecot ? Thanks a lot in advance, Joan

3 10