- dovecot - dovecot.org

[Dovecot] Dovecot Sieve
by J4 18 Jan '11

18 Jan '11

Hi, I am looking for the Dovecot Sieve mailing list. Is there one? Regards, j

2 5

[Dovecot] Sieve 0.2.2 how to use sievec
by Nikita Koshikov 18 Jan '11

18 Jan '11

Hello list, How can I compile sieve script under new 0.2.2 version from comandline? Under root: #sievec default-before.sieve sievec(root): Error: user root: Initialization failed: Namespace '': mkdir(/root/data) failed: Permission denied (euid=8(mail) egid=12(mail) missing +w perm: /root, euid is not dir owner) sievec(root): Fatal: Invalid user settings. Refer to server log for more information.

4 6

[Dovecot] Question about indexes and maildir/sdbox/mdbox
by Javier de Miguel Rodríguez 17 Jan '11

17 Jan '11

Hello We are now running dovecot 2.0.9 with indexes in a ram disk and maildir storage in a test system. We have the following questions: - If there is a power outage / kernel crash, we will lose the content of ramdisk. We have tested that indexes are regenerated when a user logs in via imap, so e-mail access will be "slower" after a power outage / kernel crash, but everything should work as expected (TM). Are we missing something? - We are evaluating migrating from maildir to dbox. There are two alternatives: sdbox and mdbox. Reading about dbox in the wiki (http://wiki2.dovecot.org/MailboxFormat/dbox) we see that using a ram disk for indexes for mdbox is a really bad idea: /"Note that with dbox the Index files actually contain significant data which is held nowhere else. Index files for both *single-dbox* and *multi-dbox* contain message flags and keywords. For *multi-dbox*, the index file also contains the map_uids which link (via the "map index") to the actual message data. This data cannot be automatically recreated, so it is important that Index files are treated with the same care as message data files."/ So in mdbox we should not use a ramdisk for indexes. But what about sdbox? sdbox indexes work as maildir indexes? Are sdbox indexes bigger than maildir indexes? Thank you very much for your support Regards Javier

3 2

[Dovecot] OT: Trojita v0.2.9 Released
by Michael Orlitzky 17 Jan '11

17 Jan '11

There was some interest in Trojita (an IMAP client) on this list at one point. It looks like it's been seeing steady development again: http://jkt.flaska.net/blog/Trojita_v0_2_9__a_Qt_IMAP_e_mail_client.html

2 1

[Dovecot] UW-IMAP .imaprc - does dovecot use this file in any way
by Paul Griffith 17 Jan '11

17 Jan '11

Hi, We are in the process of settings up a test server to help us test moving from UW-IMAP to Dovecot. I didn't see any reference to the UW-IMAP .imaprc file, does Dovecot just ignore this file. cat .imaprc I accept the risk set mail-subdirectory mail Paul

2 2

[Dovecot] Imap V4 rev.1 support
by Antonio Manogué 17 Jan '11

17 Jan '11

Hi. I'm running dovecot 1.0.rc7 in a RHEL. I need to know if this version supports IMAPV4 rev1 and IDLE for a new project. Thanks. -- Antonio Manogué Saiz Técnico de Sistemas Dpt. Sistemas y Comunicaciones email: amanogue(a)sabeco.es Tlf: 976 188 184

4 3

[Dovecot] Running two different versions of Dovecot (was: making folders unmovable)
by Dave 17 Jan '11

17 Jan '11

OK, so I decided to go ahead and just upgrade to the latest 1 series Dovecot and see if that solves my ACL/config issues I've been having. (I tried compiling 2.0.9, but it errored out and I assume that's because it's a pretty old machine/compiler.) Anyway, 1.2.16 compiled fine, and I installed it in another location from the currently running 1.1 series install. I have this new install running (IMAP) on a non-standard port while I test it out, and it starts fine and all seems well. However, I'm wondering, is it OK to run it and have it look at the same Maildir mailboxes as the currently running 1.1 series install? Does that have the potential to mess with indexes or change anything in a bad way? (FWIW, I tried it briefly, and after changing the port number in and restarting my mail client [Thunderbird], it had trouble pulling up the mailbox I was trying to access.) David

2 2

[Dovecot] dsync crash
by Pavel Volkovitskiy 17 Jan '11

17 Jan '11

Hello! I'm converting mailboxes from maildirs to mdbox and dsync crashes on two of them /var/mail-nfs-1 - nfs mount /var/mail-nfs-indexes - local fs /usr/bin/dsync -f -u user(a)site.ru mirror mdbox:/var/mail-nfs-1/mail/site.ru/user/mail:INDEX=/var/mail-nfs-indexes/site.ru/user dsync(user(a)site.ru): Panic: file istream-limit.c: line 79 (i_stream_limit_seek): assertion failed: (v_offset <= lstream->v_size) gdb bt: #0 0xb7fe1424 in ?? () #1 0xb7d66e42 in abort () from /lib/libc.so.6 #2 0xb7ee6f55 in default_fatal_finish (type=<value optimized out>, status=<value optimized out>) at failures.c:187 #3 0xb7ee7057 in default_fatal_handler (ctx=0xbfffef84, format=0xb7f08c78 "file %s: line %d (%s): assertion failed: (%s)", args=0xbfffefa4 "\312\361\360\267O") at failures.c:201 #4 0xb7ebd79a in i_panic (format=0xb7f08c78 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:259 #5 0xb7ef1159 in i_stream_limit_seek (stream=0x82277e8, v_offset=25769827482, mark=false) at istream-limit.c:79 #6 0xb7eede77 in i_stream_skip (stream=0x8227818, count=197) at istream.c:202 #7 0xb7eedf07 in i_stream_seek (stream=0x8227818, v_offset=5630) at istream.c:224 #8 0xb7f93c1f in dbox_attachment_file_get_stream_from (file=0x81ef248, stream=0xbffff10c) at dbox-attachment.c:168 #9 dbox_attachment_file_get_stream (file=0x81ef248, stream=0xbffff10c) at dbox-attachment.c:223 #10 0xb7f96a79 in get_mail_stream (_mail=0x81993a8, hdr_size=0x0, body_size=0x0, stream_r=0xbffff17c) at dbox-mail.c:234 #11 dbox_mail_get_stream (_mail=0x81993a8, hdr_size=0x0, body_size=0x0, stream_r=0xbffff17c) at dbox-mail.c:253 #12 0xb7f3d4f7 in mail_get_stream (mail=0x0, hdr_size=0x0, body_size=0x0, stream_r=0xbffff17c) at mail.c:179 #13 0xb7d1a66a in zlib_mail_save_finish (ctx=0x81d3ee8) at zlib-plugin.c:253 #14 0xb7f43438 in mailbox_save_finish (_ctx=0x808edf0) at mail-storage.c:1410 #15 0x08056898 in local_worker_save_msg_continue (worker=0x808ed08) at dsync-worker-local.c:1670 #16 0x08056a37 in local_worker_msg_save (_worker=0x808ed08, msg=0x80ee6c8, data=0xbffff350, callback=0x8050b80 <msg_save_callback>, context=0x80b2c60) at dsync-worker-local.c:1729 #17 0x08055dea in dsync_worker_msg_save (worker=0x808ed08, msg=0x80ee6c8, data=0xbffff350, callback=0x8050b80 <msg_save_callback>, context=0x80b2c60) at dsync-worker.c:234 #18 0x08050c69 in msg_get_callback (result=DSYNC_MSG_GET_RESULT_SUCCESS, data=0xbffff350, context=0x80b2c60) at dsync-brain-msgs-new.c:78 #19 0x080563a1 in local_worker_msg_get_next (worker=0x80832d0, get=0xbffff394) at dsync-worker-local.c:1825 #20 0x080565ed in local_worker_msg_get (_worker=0x0, mailbox=0x80d6ba1, uid=15, callback=0x8050bd0 <msg_get_callback>, context=0x5c9a) at dsync-worker-local.c:1846 #21 0x08055a09 in dsync_worker_msg_get (worker=0x80832d0, mailbox=0x80d6ba1, uid=15, callback=0x8050bd0 <msg_get_callback>, context=0x80b2c60) at dsync-worker.c:261 #22 0x08050a31 in dsync_brain_msg_sync_add_new_msg (iter=0x80d6ce0) at dsync-brain-msgs-new.c:180 #23 dsync_brain_mailbox_add_new_msgs (iter=0x80d6ce0) at dsync-brain-msgs-new.c:210 #24 dsync_brain_msg_sync_add_new_msgs (iter=0x80d6ce0) at dsync-brain-msgs-new.c:309 #25 0x0805023f in dsync_brain_msg_sync_more (sync=0x80d6a48) at dsync-brain-msgs.c:430 #26 0x0804eb60 in dsync_brain_sync_msgs (brain=0x8092140) at dsync-brain.c:726 #27 dsync_brain_sync (brain=0x8092140) at dsync-brain.c:847 #28 0x0804f970 in dsync_brain_subs_list_finished (context=0x80c62b8) at dsync-brain.c:170 #29 dsync_worker_subs_input (context=0x80c62b8) at dsync-brain.c:223 #30 0x0804ee97 in dsync_brain_sync (brain=0x8092140) at dsync-brain.c:832 #31 0x0804f7f8 in dsync_brain_mailbox_list_finished (context=0x8098d20) at dsync-brain.c:99 #32 dsync_worker_mailbox_input (context=0x8098d20) at dsync-brain.c:126 #33 0x0804ecf5 in dsync_brain_sync (brain=0x8092140) at dsync-brain.c:823 #34 0x0804f698 in dsync_brain_sync_all (brain=0x8092140) at dsync-brain.c:887 #35 0x0804db76 in main (argc=6, argv=0x80651c0) at dsync.c:303 doveconf -n: # 2.0.9 (d8179b523116): /etc/dovecot/dovecot.conf # OS: Linux 2.6.35-24-generic-pae i686 Ubuntu 10.10 auth_default_realm = mtx.ru auth_mechanisms = plain login digest-md5 cram-md5 apop ntlm auth_realms = mtx.ru disable_plaintext_auth = no first_valid_uid = 1 info_log_path = /var/log/dovecot/dovecot-main.log lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /var/log/dovecot/dovecot-main-errors.log log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = Server ready. mail_attachment_dir = /var/mail-nfs-1/mail/attachments mail_attachment_min_size = 16 k mail_fsync = never mail_location = maildir:%Lh:INDEX=/var/mail-indexes/%Ld/%Ln mail_plugins = " lazy_expunge zlib" 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 mdbox_rotate_size = 32 M mmap_disable = yes namespace { inbox = yes location = prefix = separator = / type = private } namespace { hidden = yes list = no location = mdbox:/var/mail-nfs-1/mail-backup/%Ld/%Ln prefix = .EXPUNGED/ separator = / type = private } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { lazy_expunge = .EXPUNGED/ lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes quota = maildir quota_rule = *:storage=0 sieve = ~/dovecot.sieve sieve_global_path = /etc/dovecot/scripts/dovecot.sieve sieve_storage = /var/mail/%d/%n/sieve } protocols = imap pop3 sieve service anvil { unix_listener anvil { group = mail mode = 0660 user = root } } service auth { unix_listener auth-client { mode = 0666 } unix_listener auth-master { group = mail mode = 0660 user = Debian-exim } unix_listener auth-userdb { group = mail mode = 0660 user = root } user = root } service imap-login { process_limit = 256 process_min_avail = 5 } service imap { executable = /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap process_limit = 1024 } service managesieve-login { process_limit = 256 process_min_avail = 5 } service managesieve { process_limit = 1024 } service pop3-login { process_limit = 256 process_min_avail = 5 } service pop3 { process_limit = 1024 } ssl_cert = </etc/ssl/certs/mail.mtx.ru.crt ssl_key = </etc/ssl/private/mail.mtx.ru.key userdb { args = username_format=%n /var/mail/userdb/userdb-%Ld driver = passwd-file } userdb { args = uid=8 gid=8 home=/var/mail/%d/%n driver = static } verbose_proctitle = yes protocol lda { debug_log_path = /var/log/dovecot/dovecot-lda-debug.log info_log_path = /var/log/dovecot/dovecot-lda.log log_path = /var/log/dovecot/dovecot-lda-errors.log mail_debug = no mail_plugins = " lazy_expunge zlib sieve" } protocol imap { imap_capability = +NAMESPACE } -- Pavel

1 0

[Dovecot] IMAP V4 Rev.1 supported in dovecot 1.0.rc7
by Antonio Manogué 17 Jan '11

17 Jan '11

Hi. I'm running dovecot 1.0.rc7 in a RHEL. I need to know if this version supports IMAPV4 rev1 and IDLE for a new project. Thanks. [root@pony mail]# uname -a Linux pony.sabeco.es 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686 i686 i386 GNU/Linux [root@pony mail]# dovecot --version 1.0.rc7 [root@pony mail]# dovecot -n # /etc/dovecot.conf 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 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 auth default: passdb: driver: pam userdb: driver: passwd -- Antonio Manogué Saiz Técnico de Sistemas Dpt. Sistemas y Comunicaciones email: amanogue(a)sabeco.es Tlf: 976 188 184

2 2

Re: [Dovecot] SSD drives are really fast running Dovecot
by Joseph Tam 17 Jan '11

17 Jan '11

On Sat, 15 Jan 2011, Charles Marcus wrote > Doing this will also help train users in proper email management - > treating their INBOX just like they would a physical INBOX tray on their > desk. They wouldn't just let paper pile up there, why do so in their > INBOX (because they 'can')? Ie, it should be something they should > always strive to keep totally EMPTY. Of course this practically never > happens, but the point is, they need to learn to make a decision once > they are finished with it, and most importantly, take said action - > either delete it, or file it. This is pretty much what I do with the mail domain I administer. I've set the INBOX with a modest quota, and a personal mail folder with a generous quota. I encourage users to keep their INBOX as a "working set", and archive the rest using any method they prefer. It forces users to process their Email (or at least their INBOX). and keeps packratting in check. Super-big INBOX quotas seem to encourage wasteful habits. I've helped some users clean out their mailboxes and was surpised at the amount of junk being kept for years and years. Apart from a few users moaning about their meager INBOX, this policy works out fairly well. Joseph Tam <jtam.home(a)gmail.com>

2 1