- dovecot - dovecot.org

[Dovecot] Index maintenance
by Anders 24 Apr '08

24 Apr '08

Hi. I am unable to find information about what happens to the index file if I use something like the cron script at the bottom of http://wiki.dovecot.org/Plugins/Expire There must be some information in the index that is no longer needed. When and how will Dovecot clean this up? Thanks, Anders.

2 5

[Dovecot] sieve header :matches for multiline header
by Anton Yuzhaninov 24 Apr '08

24 Apr '08

RFC3028 say: Folding of long header lines (as described in [IMAIL] 3.4.8) is removed prior to interpretation of the data. The folding syntax (the CRLF that ends a line plus any leading whitespace at the beginning of the next line that indicates folding) are interpreted as if they were a single space. But it seems to be not true for dovecot-sieve-1.0.2 for header Received: from example.ru (example.ru [192.168.105.14]) by myserver (Postfix) with ESMTP id D4DA5D85927 This sieve test work: header :matches "Received" "from *by myserver (Postfix) with ESMTP id *" But this test not work, while should also work according to RFC: header :matches "Received" "from * by myserver (Postfix) with ESMTP id *" -- WBR, Anton Yuzhaninov

4 3

[Dovecot] ACLs generating plugin problems.
by "Fábio M. Catunda" 24 Apr '08

24 Apr '08

Hi! I'm trying to use an ACL to avoid deletion of messages that are inside .Trash folder, the ACL is already working very well, the problem that I'm facing is that even if the message is not deleted, mail_log logs that it has been deleted. Also, in some cases part of the lazy_expunge code is executed too, but sometimes I just dont know where the message is, thats weird. I erased deleted and expunged folders, then I deleted a message, It hasn't been deleted, but "deleted" and "expunged" folders has been created. Anyway, I would like to know if there is a way to stop plugin execution when an ACL matches. Thanks a lot.

2 3

[Dovecot] alert function, V2
by Stewart Dean 24 Apr '08

24 Apr '08

I guess the alert function is not part of the spec, because it appears to be unimplemented in Dovecot, even though most clients implement it. Timo, I would hope this would be easy to implement, and it's functionality that will be valuable to every installation. Here's why. America recently had the tragedy of a shooting rampage on a large university campus (yes, America should do something about the violence and free access to guns in our culture/society). What was worse was that, due to the lack of an emergency notification process, some 20+ people died needlessly. Now all college and university administration are scrambling to set up emergency notification processes. Our first take on this is a massive all-hands mailing list, but a) best case, it would take 15 minutes (and as much as an hour) to get to everybody's mailbox. b) users would have to read through their mail and stumble on the message What's needed is an "in-your-face" unavoidable alert, and the UWIMAP alert functionality provides this. As I recall, you touch just about anything in your IMAP client and there's a popup message in the middle of the client IMAP window...and it happens repeatedly. We tried it back 3-4 years ago and found it too annoying to use. For this purpose, it's perfect. The wy UWIMAP did it, the presence of the file /etc/imapd.alert triggers it, and the text in that file is transmitted to the client. The message has to be short, a one-liner for a small popup window, but this could be a pointer to a shared system message folder. Of course, DC could sense the activation of the alert in some other fashion that the presence of a file. Ideally, whatever activates the alert function should be able to be turned on remotely; I had in mind to do it using a mail aliases that is a pipe to a executable... What say you? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

6 9

[Dovecot] dovecot-1.1.rc3 assertion failure in index-sync.c
by richs＠whidbey.net 24 Apr '08

24 Apr '08

We just came across a mailbox today that, when accessed via POP3 or IMAP, crashes Dovecot. It seems to be another index-related corruption issue (as removing "dovecot.index" for INBOX fixed it); Using POP3: dovecot: Apr 09 10:28:14 Warning: POP3(USERNAME): Maildir /mail/USERNAME/Maildir: UIDVALIDITY changed (1145576765 -> 1207677483) dovecot: Apr 09 10:28:14 Panic: POP3(USERNAME): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) dovecot: Apr 09 10:28:14 Error: POP3(USERNAME): Raw backtrace: pop3 [0x80c04e4] -> pop3 [0x80c013c] -> pop3 [0x808eb9a] -> pop3(index_mailbox_set_recent_seq+0x3e) [0x808ebde] -> pop3(maildir_sync_index+0x923) [0x8064173] -> pop3 [0x8062e22] -> pop3(maildir_storage_sync_init+0x58) [0x8062f98] -> pop3(mailbox_sync+0x1f) [0x80912af] -> pop3(client_create+0x1de) [0x805968e] -> pop3(main+0x403) [0x805b503] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x707dec] -> pop3 [0x8058e71] dovecot: Apr 09 10:28:14 Error: child 28169 (pop3) killed with signal 6 Using IMAP (after "SELECT INBOX"): dovecot: Apr 09 10:56:31 Warning: IMAP(USERNAME): Maildir /mail/USERNAME/Maildir: UIDVALIDITY changed (1145576765 -> 1207677483) dovecot: Apr 09 10:56:31 Panic: IMAP(USERNAME): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) dovecot: Apr 09 10:56:31 Error: IMAP(USERNAME): Raw backtrace: imap [0x80cd564] -> imap [0x80cd1bc] -> imap [0x809b32a] -> imap(index_mailbox_set_recent_seq+0x3e) [0x809b36e] -> imap(maildir_sync_index+0x923) [0x8070903] -> imap [0x806f5b2] -> imap(maildir_storage_sync_init+0x58) [0x806f728] -> imap(mailbox_sync+0x1f) [0x809da3f] -> imap(cmd_select_full+0xd5) [0x805dec5] -> imap(cmd_select+0x19) [0x805e069] -> imap [0x805f799] -> imap [0x805f827] -> imap [0x805ffb5] -> imap(client_input+0x5e) [0x80601ce] -> imap(io_loop_handler_run+0x100) [0x80d4d50] -> imap(io_loop_run+0x28) [0x80d42e8] -> imap(main+0x4ac) [0x8067bdc] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x125dec] -> imap [0x8059d61] dovecot: Apr 09 10:56:31 Error: child 7057 (imap) killed with signal 6 We made a copy of the mailbox and index in case any further testing would be helpful, -Rich

2 1

[Dovecot] Rare problem with Indexes?
by richs＠whidbey.net 24 Apr '08

24 Apr '08

We've been running 1.1 rc3 now for about a month, and overall it's been very fast and stable. There is however an Index-related problem that keeps cropping up which prevents a user from accessing their mailbox until their Indexes are manually removed. Somehow, an Index becomes problematic, and Dovecot hangs forever when the mailbox is accessed. It manifests when a user logs in and issues a "SELECT INBOX", or "GETQUOTAROOT" when "maildirsize" needs rebuilding. When Dovecot hangs, no data is returned and no further commands are accepted, and the daemon must be killed. We see no errors in the logs, but have yet to catch the problem with "mail_debug" enabled. We're using NFS with Maildir's and these related options: mail_location = maildir:/mail/%Lu/Maildir:INDEX=/mail/%Lu/Cache mmap_disable = yes mail_nfs_storage = yes mail_nfs_index = yes mail_drop_priv_before_exec = yes mail_cache_min_mail_count = 128 mailbox_idle_check_interval = 5 maildir_stat_dirs = yes maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = no Has anyone else run across the need to purge Indexes manually? Could this be unrecoverable Index corruption, or a locking issue? We've made a copy of the mailbox when the problem occurs. However, when we test it later, Dovecot re-builds the "dovecot.index" file itself just fine, and functions normally. We plan to "mail_debug" when this happens next to see if we can get more information. Thanks! -Rich

2 1

[Dovecot] Dovecot features
by Phan Thanh Diện 24 Apr '08

24 Apr '08

Hi, We would like to switch from courier-imap to dovecot. I have installed dovecot on a machine running FreeBSD 6.3 and now testing it. My questions are below: 1. Can I configure dovecot to delete all files that are older, say 10 days, from defined mail boxes (for example Trash or Spam). 2. After I access mail box (using web mail squirrel imap) all emails moved from 'new' directory to 'cur'. Then messages are not accessible for pop3. Such behavor doesn't occur with courier-imap. Can I force dovecot to behave like courier-imap? Many thanks for help. Dien Phan

7 10

[Dovecot] 1.1 a major improvement
by Cor Bosman 24 Apr '08

24 Apr '08

I recently switched one of our 30 imap servers to 1.1RC4 from 1.0.x, and the difference is huge. The load on the server dropped from 5+ to 0.3 or so. This means there is no more io waiting going on. Thats on FreeBSD 6.2. Great work Timo! Cor

2 1

[Dovecot] dovecot: Fatal: IMAP(user2): write(event_pipe) failed: Bad file descriptor
by Mart Pirita 24 Apr '08

24 Apr '08

Hello. Since I upgraded few months ago from version 1.0 to 1.1 (right now using v1.1.rc4) in logs for some users only (but in different servers) I noticed errors: dovecot: Fatal: IMAP(user2): write(event_pipe) failed: Bad file descriptor dovecot: Fatal: IMAP(user3): write(event_pipe) failed: Bad file descriptor So only for some imap users. And in different servers. And this error happens suddenly, I already tried to delete delete cache and index files. However the users themselves haven't noticed any problems. Shall I just ignore these errors on what? Configuration is quite simple: dovecot -n # 1.1.rc4: /etc/dovecot.conf protocols: imaps pop3 pop3s ssl_parameters_regenerate: 0 disable_plaintext_auth: 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 login_log_format_elements: %u [%r] %m %c mail_max_userip_connections(default): 90 mail_max_userip_connections(imap): 90 mail_max_userip_connections(pop3): 9 maildir_copy_preserve_filename: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/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 imap_client_workarounds(default): outlook-idle netscape-eoh tb-extra-mailbox-sep delay-newmail imap_client_workarounds(imap): outlook-idle netscape-eoh tb-extra-mailbox-sep delay-newmail imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_logout_format(default): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_logout_format(imap): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_logout_format(pop3): bytes=%i/%o, del=%d/%m, size=%s auth default: cache_size: 1024 failure_delay: 3 passdb: driver: pam args: cache_key=%u%r%s * userdb: driver: passwd -- Mart

2 1

[Dovecot] Dbox + imap_quota still crashing on 1.1rc4
by Eric T 24 Apr '08

24 Apr '08

Emailed about this with 1.1rc3 and didn't get a reply. Tried upgrading to 1.1rc4 and got the same crashing: Centos 5 (in openvz container) 2.6.18-53.1.4.el5.028stab053.4 #1 SMP Fri Jan 18 12:29:44 MSK 2008 x86_64 x86_64 x86_64 GNU/Linux /usr/local/dovecot/sbin/dovecot -n # 1.1.rc4: /usr/local/dovecot/etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imap imaps pop3 pop3s listen(default): *:10143 listen(imap): *:10143 listen(pop3): *:10110 ssl_listen(default): *:10943 ssl_listen(imap): *:10943 ssl_listen(pop3): *:10993 ssl_cert_file: /usr/local/dovecot/etc/ssl/certs/dovecot.pem ssl_key_file: /usr/local/dovecot/etc/ssl/private/dovecot.pem ssl_cipher_list: ALL:!LOW:!SSLv2 disable_plaintext_auth: no login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_user: dovecot-auth first_valid_uid: 2000 last_valid_uid: 2000 first_valid_gid: 2000 last_valid_gid: 2000 mail_uid: 2000 mail_gid: 2000 mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins(default): fts fts_squat quota imap_quota mail_plugins(imap): fts fts_squat quota imap_quota mail_plugins(pop3): expire quota mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 auth default: default_realm: flerd.com verbose: yes debug: yes passdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf userdb: driver: prefetch userdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf socket: type: listen client: path: /usr/local/dovecot/var/run/dovecot/auth-client mode: 438 master: path: /usr/local/dovecot//var/run/dovecot/auth-master mode: 438 user: dovecot-auth plugin: fts: squat quota: dict:user::proxy::quotadict quota_rule: *:storage=1G quota_rule2: Trash:storage=100M expire: Trash 7 Trash/* 7 Spam 3 expire_altmove: * 30 expire_dict: proxy::expire dict: quotadict: mysql:/usr/local/dovecot/etc/dovecot-dict-quota.conf expire: db:/usr/local/dovecot/var/lib/dovecot/expire.db -------------------------- Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. #0 0x00000000004640f9 in mail_index_get_header_ext (view=0x0, ext_id=2, data_r=0x7fffdbbcff90, data_size_r=0x7fffdbbcff88) at mail-index-view.c:550 550 view->v.get_header_ext(view, NULL, ext_id, data_r, data_size_r); (gdb) bt full #0 0x00000000004640f9 in mail_index_get_header_ext (view=0x0, ext_id=2, data_r=0x7fffdbbcff90, data_size_r=0x7fffdbbcff88) at mail-index-view.c:550 No locals. #1 0x000000000044631c in dbox_sync_want_flush_dirty (mbox=0xdd47598, close_flush_dirty_flags=true) at dbox-sync.c:262 hdr = <value optimized out> data = <value optimized out> data_size = <value optimized out> #2 0x00000000004463d1 in dbox_sync_begin (mbox=0x0, ctx_r=0x7fffdbbd00c8, close_flush_dirty_flags=144, force=144) at dbox-sync.c:297 storage = (struct mail_storage *) 0xdd3dc98 ctx = <value optimized out> sync_flags = <value optimized out> ret = <value optimized out> rebuild = <value optimized out> #3 0x0000000000446b98 in dbox_sync (mbox=0x0, close_flush_dirty_flags=144) at dbox-sync.c:396 sync_ctx = (struct dbox_sync_context *) 0xdd47598 #4 0x000000000043f3f4 in dbox_storage_mailbox_close (box=0x0) at dbox-storage.c:311 mbox = <value optimized out> ret = <value optimized out> #5 0x00002aaaab62df50 in fts_mailbox_close (box=0xdd47598) at fts-storage.c:65 fbox = (struct fts_mailbox *) 0xdd48fb0 ret = <value optimized out> #6 0x00002aaaab42a5ed in cmd_getquotaroot (cmd=0xdd3e758) at imap-quota-plugin.c:98 storage = <value optimized out> box = (struct mailbox *) 0x0 iter = (struct quota_root_iter *) 0x0 root = <value optimized out> orig_mailbox = 0xdd42938 "INBOX" mailbox = 0x49ab6a "INBOX" str = (string_t *) 0xdd311c0 #7 0x000000000041abfc in client_command_input (cmd=0xdd3e758) at client.c:553 client = (struct client *) 0xdd3e370 command = <value optimized out> __PRETTY_FUNCTION__ = "client_command_input" #8 0x000000000041acb2 in client_command_input (cmd=0xdd3e758) at client.c:602 client = (struct client *) 0xdd3e370 command = (struct command *) 0x7fffdbbcff90 __PRETTY_FUNCTION__ = "client_command_input" #9 0x000000000041b46f in client_handle_input (client=0xdd3e370) at client.c:643 _data_stack_cur_id = 3 ret = <value optimized out> remove_io = <value optimized out> handled_commands = false #10 0x000000000041b693 in client_input (client=0xdd3e370) at client.c:698 cmd = <value optimized out> output = (struct ostream *) 0xdd3e608 bytes = 27 __PRETTY_FUNCTION__ = "client_input" #11 0x0000000000486de8 in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:201 ctx = <value optimized out> event = (const struct epoll_event *) 0xdd39dc0 list = (struct io_list *) 0xdd3a780 io = (struct io_file *) 0xdd3e6a0 tv = {tv_sec = 1799, tv_usec = 999607} events_count = <value optimized out> t_id = 2 msecs = <value optimized out> ret = 1 i = 0 call = <value optimized out> #12 0x00000000004860cd in io_loop_run (ioloop=0xdd39b60) at ioloop.c:301 No locals. #13 0x0000000000422b01 in main (argc=<value optimized out>, argv=0x0, envp=0x7fffdbbd03c8) at main.c:293 No locals.

2 1