October 2007 - dovecot

[Dovecot] Duplicate message
by Timothy Murphy 27 Oct '07

27 Oct '07

I'm running dovecot on my desktop and using kmail as a client on my laptop. I am very happy with this - I was previously running kmail under NFS, and this is infinitely better. There is one small issue, which is not very important. I get a small number of messages apparently duplicated. This doesn't really matter, as there is a facility Folder=>Remove Duplicate Messages under kmail, and this deals with the issue easily enough. I just wondered though why I get the duplicate messages, and if there is some simple way to avoid them?

2 1

[Dovecot] 1.1b4: Disconnected: EOF while appending
by Luigi Rosa 27 Oct '07

27 Oct '07

I am moving some messages from an IMAP account to another. During the process I got this message: dovecot: IMAP(mailstore): Disconnected: EOF while appending bytes=263276/427306 (no core dump) I deleted dovecot.index.cache and dovecot.index.log and the error disappeared Ciao, luigi -- / +--[Luigi Rosa]-- \ Committee: a life form with six or more legs and no brain.

2 4

[Dovecot] virtual hosting
by gaoqiang.qian＠nokia.com 27 Oct '07

27 Oct '07

I am a newee in Dovecot, Now my dovecot is working fine to be connected to receive email sent to one domain. Could anyone tell me how can I configure it to be connected to receive email sent to another domain. I really heading the wall. thanks. Gao

3 3

[Dovecot] dovecot-auth: Too many open files
by Joe Allesi -X (joallesi - Coyote Creek Consulting at Cisco) 27 Oct '07

27 Oct '07

All, [version: dovecot-0.99.11-4.EL4.src.rpm] We recently experienced an issue that prevented all new IMAP logins from occurring. Although it appears that it was due to running out of available system file descriptors, I'm still not sure what the true root cause was as I can't replicate the same error in our test environment. The system file descriptor max was set at (per `cat /proc/sys/fs/file-nr`) 380081 , and we're averaging around 7,000 in use. It appears that the main issue was dovecot-auth, so does this appear to fall in line with the known PAM bug in this version? Auth config: auth_userdb = passwd auth_passdb = pam Checked maillogs (cleansed): Oct 16 11:48:05 host dovecot-auth: PAM: pipe() failed: Too many open files Oct 16 04:48:06 host imap-login: Disconnected [::ffff:<internal_IP>] Oct 16 11:48:11 host dovecot-auth: PAM: pipe() failed: Too many open files Oct 16 04:48:11 host imap-login: Aborted login [::ffff:<internal_IP>] Oct 16 04:48:11 host dovecot-auth: PAM unable to dlopen(/lib/security/pam_nologin.so) Oct 16 04:48:11 host dovecot-auth: PAM [dlerror: /lib/security/pam_nologin.so: cannot open shared object file: Too many open files] Oct 16 04:48:11 host dovecot-auth: PAM adding faulty module: /lib/security/pam_nologin.so Oct 16 04:48:11 host dovecot-auth: PAM unable to dlopen(/lib/security/pam_stack.so) Oct 16 04:48:11 host dovecot-auth: PAM [dlerror: /lib/security/pam_stack.so: cannot open shared object file: Too many open files] So, during the event I performed an strace against the dovecot-auth process and noticed the following error as well: accept(3, 0xbfe05a50, [2]) = -1 EMFILE (Too many open files) gettimeofday({1192538310, 41972}, NULL) = 0 poll([{fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL, revents=POLLIN}, {fd=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=18, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=7, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=23, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=8, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=11, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=12, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=13, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=14, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=19, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=16, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=17, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=6, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=15, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=20, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=21, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=9, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=22, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=24, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=25, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=26, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=27, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=28, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=34, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=33, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=29, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=37, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=30, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=31, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=41, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, ...], 1020, 1585) = 1 gettimeofday({1192538310, 99354}, {480, 0}) = 0 Then I checked for the current network connections: netstat | grep imap | wc -l 42 Then used lsof to check for open files: while true ; do lsof | awk '{ print $3 }' | wc -l ; sleep 4 ; done 21728 21668 (restarted dovecot) 1838 1953 1864 2066 2018 2020 2036 2189 2661 2558 2490 (cont @2,000) Thanks! Joe Allesi

5 6

[Dovecot] Problem in mbox-sync.c
by Hal Pomeranz 27 Oct '07

27 Oct '07

We've just cut over to a new mail server running Dovecot 1.0.5. The underlying OS is RHEL 5. User mailboxes are stored in Unix mbox format on a local ext3 file system. The MTA on the system is the default RedHat version of Sendmail 8.13.8 with procmail for local delivery. We're using a combination of dotlock and fcntl style locking. The output of "dovecot -n" for this system appears below my signature. Periodically we see errors like the following in our logs: Oct 21 19:36:01 postoffice1 dovecot: POP3(someuser): file mbox-sync.c: line 1433 (mbox_sync_handle_eof_updates): assertion failed: (file_size >= sync_ctx->expunged_space + trailer_size) Oct 21 19:36:01 postoffice1 dovecot: POP3(someuser): Raw backtrace: pop3 [0x809eda1] -> pop3 [0x809ecbc] -> pop3(mbox_sync+0x1088) [0x806c4e8] -> pop3(mbox_storage_sync_init+0x3e) [0x806cb6e] -> pop3(client_create+0x1a4) [0x80552a4] -> pop3(main+0x556) [0x8057236] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x304dec] -> pop3 [0x8054a11] Oct 21 19:36:01 postoffice1 dovecot: child 24409 (pop3) killed with signal 6 Note that while the above log is for a POP3 user, we also see similar behavior when some users access mail folders via IMAP as well. The real problem with this behavior is that sometimes, but not in all cases, the process will leave behind a dotlock when it exits. If the abandoned dotlock is on the user's inbox, then procmail won't deliver new mail to the user until the lock is cleared. This is a big problem. Anybody seen this behavior before and/or know what's causing it? Can anybody suggest ideas for further debugging this issue? We'd appreciate any help that you all can provide. Thanks! -- Hal Pomeranz, Founder/CEO Deer Run Associates hal(a)deer-run.com Network Connectivity and Security, Systems Management, Training -- # /hpsw/mail/dovecot/sbin/dovecot -n # 1.0.5: /hpsw/mail/dovecot/etc/dovecot.conf syslog_facility: local3 protocols: imap imaps pop3 pop3s ssl_cert_file: /hpsw/mail/configs/dovecot/pki/certs/dovecot.pem ssl_key_file: /hpsw/mail/configs/dovecot/pki/private/dovecot.pem disable_plaintext_auth: no login_dir: /hpsw/mail/dovecot/var/run/dovecot/login login_executable(default): /hpsw/mail/dovecot/libexec/dovecot/imap-login login_executable(imap): /hpsw/mail/dovecot/libexec/dovecot/imap-login login_executable(pop3): /hpsw/mail/dovecot/libexec/dovecot/pop3-login mail_location: mbox:/hpsw/mail/users/%u/dovecot:INBOX=/hpsw/mail/users/%u/MBOX mbox_read_locks: dotlock fcntl mail_executable(default): /hpsw/mail/dovecot/libexec/dovecot/imap mail_executable(imap): /hpsw/mail/dovecot/libexec/dovecot/imap mail_executable(pop3): /hpsw/mail/dovecot/libexec/dovecot/pop3 mail_plugin_dir(default): /hpsw/mail/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /hpsw/mail/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /hpsw/mail/dovecot/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: passdb: driver: pam userdb: driver: passwd

3 7

[Dovecot] master user can not login with digest-md5 password
by Daniel 27 Oct '07

27 Oct '07

Hi! I'm trying to use a master user, here is what I'm doing: dovecot.conf: auth default { [...] passdb passwd-file { args = /etc/dovecot.passdb_master pass = yes master = yes } passdb passwd-file { args = /etc/dovecot.passdb } [...] } (Dovecot said that one can not place the passdb containing "master = yes" last, why?) This only works if the master user (in the master passwd file) has PLAIN password scheme. It doesn't work with DIGEST-MD5. Here is the log when it's in DIGEST-MD5: auth(default): passdb(master,84.x.x.x,master): Master user logging in as leva auth(default): digest-md5(leva,84.x.x.x): password mismatch imap-login: Disconnected: user=<leva>, method=DIGEST-MD5, rip=84.x.x.x, lip=212.x.x.x, TLS When the master password is in PLAIN scheme, I can login as anyone. I'm using dovecot-1.1beta4. Daniel

2 1

[Dovecot] Messages not marked as read
by Manilal K M 27 Oct '07

27 Oct '07

Hello everybody, Recently I have migrated my IMAP server from Courier-IMAP to dovecot. The migration was successful and all the users are happy due to the speed of the new IMAP server. We are using Horde-3.2+IMP-4.2 as the webmail client. But one of the users is having some unusual issues with his mailbox. Whenever he clicked and open a new email, it's never marked as read. He has to click and open several times to get it marked as "Read". I checked the dovecot version and found that we have a unstable version. So I upgraded to the latest stable version(1.0.5). But still occasionally he has the same issue. Does anyone have experienced similar issue. Please share. regards -- Manilal K M. http://linuxeyes.blogspot.com http://flossvalley.blogspot.com Better to light one candle than to curse the darkness.

2 1

[Dovecot] Keywords (labels) support via virtual folders
by Robert Tomanek 27 Oct '07

27 Oct '07

Hi all, while I am rather a beginner when it comes to IMAP, I was thinking whether it would be possible (and feasible) to implement setting and unsetting of IMAP keywords with the means of virtual folders in Dovecot. The background is that the IMAP keywords seem to be a very useful thing to me: I would often like to be able to 'tag' a message so that it is easy to group with other similar messages and easy to find/ browse later. The problem is that not all IMAP clients support this functionality (as far as I am aware, mine which happens to be The Bat! does not); the only way of achieving similar results is using regular folders for grouping messages but this has several disadvantages, the most prominent one being unable to assign more than one 'tag' to a message this way (without copying a message). What I am thinking of is a server-side 'helper' that intends to achieve functionality similar to native client keywords support by the means of providing 'virtual folders' (as opposed to regular folders that we've known for a long time). The server would expose a list of virtual folders (user defined, either server-side by modifying the configuration, or client-side, by using the existing 'create regular folder' folder functionality but using a special name format that would be recognized by the server to be virtual folder related). These virtual folders would, upon moving a message to them, apply a keyword to the message (but the message would not be moved as it would be the case with regular folders). Upon moving a message from a virtual folder, the keyword would be reset. This means that the messages would not normally be moved from their place in existing hard folder structure but they would additionally be flagged with a keyword (or more of them) and be visible in respective virtual folders. The result is: - keywords support for clients that do not natively support it, - leaving existing message folder structure intact, - support for multiple keywords/ labels per message (one virtual folder = one keyword), - browsing flagged messages via respective virtual folders. What do you think of it? While I've been toying with this and similar ideas for a long time, what I propose above is of course heavily influenced by the recent addition of IMAP access to Gmail ([1]). While I still do not have it enabled for my account, I presume this is how the Gmail labels get translated to IMAP client ([2], [3]). [1] https://mail.google.com/support/bin/topic.py?topic=12760 [2] https://mail.google.com/support/bin/answer.py?answer=77657&topic=12762 [3] https://mail.google.com/support/bin/answer.py?answer=78758&topic=12762 -- Best regards, Robert Tomanek mailto:dovecot@mail.robert.tomanek.org

2 1

[Dovecot] few questions about 1.1*
by Daniel 27 Oct '07

27 Oct '07

Hi! I'm testing 1.1, and have some questions. (How) Can I override the default maildir++ quota setting (I mean quota_rule) in the userdb, so that one won't have quota at all. Right now I'm setting a very high limit in the userdb with quota_rule=*:storage=99G in the extra field. Prior to 1.1 I was using 1.0 and had fs quota. I've had set up dovecot so that the indexes were stored on another partition where there were no fs quotas for the users. Now I'm trying to use maildir++ quota, and wondering if there is still any use of keeping the index files on a separate partition. This will be maybe a bit stupid, but do I still need the quota plugin to be loaded in the protocol {imap,pop3,lda} sections if I'm using the above mentioned new 1.1 maildir++ quota? Furthermore, will deliver be aware of the new quota system? Thanks! Daniel

3 6

[Dovecot] append bug in 1.1beta4?
by Daniel 26 Oct '07

26 Oct '07

Hi! I'm guessing this is the append bug which is still present in dovecot-1.1beta4?: Info: IMAP(leva): Disconnected: EOF while appending bytes=31665/119125 This happens after sending a mail, and trying upload/copy that mail from my local "Sent" folder to my IMAP server's Sent folder. Daniel

2 2