- dovecot - dovecot.org

[Dovecot] Related 2.0.alpha2 issue
by Mike Abbott 03 Nov '09

03 Nov '09

Just saw this new twist to an issue I reported last week with dovecot-2.0.alpha2. I logged into an IMAP account using telnet to port 143. After 30 seconds dovecot closed the connection. Mon Nov 2 16:00:07 server dovecot[52355]: imap: dup2(-1, 5) failed: Bad file descriptor Mon Nov 2 16:00:07 server dovecot[52355]: imap: service(imap): dup2s failed Mon Nov 2 16:00:07 server dovecot[52355]: imap-login: Login: user=<userV>, method=PLAIN, rip=192.168.1.10, lip=192.168.1.7, pid=59521 Mon Nov 2 16:00:37 server dovecot[52353]: master: service(imap): Initial status notification not received in 30 seconds, killing the process Mon Nov 2 16:00:37 server dovecot[52353]: master: service(imap): child 59521 killed with signal 9 Mon Nov 2 16:00:37 server dovecot[52353]: master: service(imap): command startup failed, throttling

1 0

[Dovecot] Unable to create imap nested dirs.
by Leo 02 Nov '09

02 Nov '09

Hi all, I'm trying to config a dovecot server on a debian-lenny box but I'm experiencing a problem that serveral users have on the net, but I haven't found any solution. I'm trying to create nested dirs with my thunderbird 2.0.0.23 client but without any luck :( I can create dir in the root, but not subdirs. have you any ideas? here you can you see the small config and attached my full config dovecot -n # 1.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.12.6-arm1 armv5tejl Debian 5.0.3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mbox_write_locks: fcntl dotlock auth default: passdb: driver: pam userdb: driver: passwd # dovecot -a # 1.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.12.6-arm1 armv5tejl Debian 5.0.3 base_dir: /var/run/dovecot log_path: info_log_path: log_timestamp: %Y-%m-%d %H:%M:%S syslog_facility: mail protocols: imaps listen: * ssl_listen: ssl: yes ssl_ca_file: ssl_cert_file: /etc/ssl/certs/dovecot.pem ssl_key_file: /etc/ssl/private/dovecot.pem ssl_key_password: ssl_parameters_regenerate: 168 ssl_cipher_list: ssl_cert_username_field: commonName ssl_verify_client_cert: no disable_plaintext_auth: yes verbose_ssl: no shutdown_clients: yes nfs_check: yes version_ignore: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_user: dovecot login_greeting: Dovecot ready. login_log_format_elements: user=<%u> method=%m rip=%r lip=%l %c login_log_format: %$: %s login_process_per_connection: yes login_chroot: yes login_trusted_networks: login_process_size: 64 login_processes_count: 3 login_max_processes_count: 128 login_max_connections: 256 valid_chroot_dirs: mail_chroot: max_mail_processes: 512 mail_max_userip_connections: 10 verbose_proctitle: no first_valid_uid: 500 last_valid_uid: 0 first_valid_gid: 1 last_valid_gid: 0 mail_access_groups: mail_privileged_group: mail mail_uid: mail_gid: mail_location: mail_cache_fields: mail_never_cache_fields: imap.envelope mail_cache_min_mail_count: 0 mailbox_idle_check_interval: 30 mail_debug: no mail_full_filesystem_access: no mail_max_keyword_length: 50 mail_save_crlf: no mmap_disable: no dotlock_use_excl: yes fsync_disable: no mail_nfs_storage: no mail_nfs_index: no mailbox_list_index_disable: yes lock_method: fcntl maildir_stat_dirs: no maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: no maildir_very_dirty_syncs: no mbox_read_locks: fcntl mbox_write_locks: fcntl dotlock mbox_lock_timeout: 300 mbox_dotlock_change_timeout: 120 mbox_min_index_size: 0 mbox_dirty_syncs: yes mbox_very_dirty_syncs: no mbox_lazy_writes: yes dbox_rotate_size: 2048 dbox_rotate_min_size: 16 dbox_rotate_days: 1 mail_drop_priv_before_exec: no mail_executable: /usr/lib/dovecot/imap mail_process_size: 256 mail_plugins: mail_plugin_dir: /usr/lib/dovecot/modules/imap mail_log_prefix: %Us(%u): mail_log_max_lines_per_sec: 10 imap_max_line_length: 65536 imap_capability: imap_client_workarounds: imap_logout_format: bytes=%i/%o imap_id_send: imap_id_log: imap_idle_notify_interval: 120 pop3_no_flag_updates: no pop3_enable_last: no pop3_reuse_xuidl: no pop3_lock_session: no pop3_uidl_format: %08Xu%08Xv pop3_client_workarounds: pop3_logout_format: top=%t/%p, retr=%r/%b, del=%d/%m, size=%s dict_db_config: dict_process_count: 1 managesieve_max_line_length: 65536 managesieve_logout_format: bytes=%i/%o managesieve_implementation_string: dovecot auth default: mechanisms: plain realms: default_realm: cache_size: 0 cache_ttl: 3600 cache_negative_ttl: 3600 executable: /usr/lib/dovecot/dovecot-auth user: root chroot: username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ username_translation: username_format: master_user_separator: anonymous_username: anonymous krb5_keytab: gssapi_hostname: winbind_helper_path: /usr/bin/ntlm_auth failure_delay: 2 verbose: no debug: no debug_passwords: no ssl_require_client_cert: no ssl_username_from_cert: no use_winbind: no count: 1 worker_max_count: 30 process_size: 256 passdb: driver: pam args: deny: no pass: no master: no userdb: driver: passwd args:

3 3

[Dovecot] Another 2.0.alpha2 panic
by Mike Abbott 02 Nov '09

02 Nov '09

This time using maildir instead of mdbox. Fri Oct 30 21:08:16 server dovecot[27407]: lda(pid 27407 user userW): Panic: file istream.c: line 104 (i_stream_read): assertion failed: ((size_t)ret+old_size == _stream->pos - _stream->skip) 0 libSystem.B.dylib 0x00007fff875f4eba __kill + 10 1 libSystem.B.dylib 0x00007fff875f4eac kill + 14 2 libSystem.B.dylib 0x00007fff87683519 raise + 25 3 libSystem.B.dylib 0x00007fff876a4e12 abort + 90 4 libdovecot.0.dylib 0x00000001000d1027 i_set_failure_file + 275 5 libdovecot.0.dylib 0x00000001000d03ec i_syslog_error_handler + 0 6 libdovecot.0.dylib 0x00000001000d06d2 i_debug + 0 7 libdovecot.0.dylib 0x00000001000d9c00 i_stream_read + 392 8 libdovecot.0.dylib 0x00000001000d8104 i_stream_create_limit + 436 9 libdovecot.0.dylib 0x00000001000d9ab7 i_stream_read + 63 10 libdovecot.0.dylib 0x00000001000d9cf1 i_stream_read_data + 103 11 libdovecot.0.dylib 0x00000001000c4bef message_parse_header_next + 145 12 libdovecot.0.dylib 0x00000001000c646f message_parser_init_from_parts + 287 13 libdovecot.0.dylib 0x00000001000c5a4b message_parser_parse_next_block + 133 14 libdovecot.0.dylib 0x00000001000c5bc8 message_parser_parse_header + 64 15 libdovecot-storage.0.dylib 0x0000000100043883 index_mail_parse_headers + 189 16 libdovecot-storage.0.dylib 0x0000000100043b53 index_mail_get_header_stream + 597 17 libdovecot-storage.0.dylib 0x0000000100043f89 index_mail_get_first_header + 49 18 libdovecot-storage.0.dylib 0x0000000100011d1d mail_get_first_header + 15 19 dovecot-lda 0x0000000100002eda mail_deliver_get_address + 24 20 dovecot-lda 0x00000001000020f0 main + 2484 21 dovecot-lda 0x0000000100001734 start + 52

2 2

[Dovecot] How to create nested dirs
by SKAL 01 Nov '09

01 Nov '09

Hi all, I'm experiencing a problem that several users had, but I could not find a solution. I cannot create any subfolders with my thunderbird 2.0.0.23 client, but I can creat other folders. Any ideas? tnx leo # dovecot -n # 1.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.12.6-arm1 armv5tejl Debian 5.0.3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mbox_write_locks: fcntl dotlock auth default: passdb: driver: pam userdb: driver: passwd # dovecot -a # 1.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.12.6-arm1 armv5tejl Debian 5.0.3 base_dir: /var/run/dovecot log_path: info_log_path: log_timestamp: %Y-%m-%d %H:%M:%S syslog_facility: mail protocols: imaps listen: * ssl_listen: ssl: yes ssl_ca_file: ssl_cert_file: /etc/ssl/certs/dovecot.pem ssl_key_file: /etc/ssl/private/dovecot.pem ssl_key_password: ssl_parameters_regenerate: 168 ssl_cipher_list: ssl_cert_username_field: commonName ssl_verify_client_cert: no disable_plaintext_auth: yes verbose_ssl: no shutdown_clients: yes nfs_check: yes version_ignore: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_user: dovecot login_greeting: Dovecot ready. login_log_format_elements: user=<%u> method=%m rip=%r lip=%l %c login_log_format: %$: %s login_process_per_connection: yes login_chroot: yes login_trusted_networks: login_process_size: 64 login_processes_count: 3 login_max_processes_count: 128 login_max_connections: 256 valid_chroot_dirs: mail_chroot: max_mail_processes: 512 mail_max_userip_connections: 10 verbose_proctitle: no first_valid_uid: 500 last_valid_uid: 0 first_valid_gid: 1 last_valid_gid: 0 mail_access_groups: mail_privileged_group: mail mail_uid: mail_gid: mail_location: mail_cache_fields: mail_never_cache_fields: imap.envelope mail_cache_min_mail_count: 0 mailbox_idle_check_interval: 30 mail_debug: no mail_full_filesystem_access: no mail_max_keyword_length: 50 mail_save_crlf: no mmap_disable: no dotlock_use_excl: yes fsync_disable: no mail_nfs_storage: no mail_nfs_index: no mailbox_list_index_disable: yes lock_method: fcntl maildir_stat_dirs: no maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: no maildir_very_dirty_syncs: no mbox_read_locks: fcntl mbox_write_locks: fcntl dotlock mbox_lock_timeout: 300 mbox_dotlock_change_timeout: 120 mbox_min_index_size: 0 mbox_dirty_syncs: yes mbox_very_dirty_syncs: no mbox_lazy_writes: yes dbox_rotate_size: 2048 dbox_rotate_min_size: 16 dbox_rotate_days: 1 mail_drop_priv_before_exec: no mail_executable: /usr/lib/dovecot/imap mail_process_size: 256 mail_plugins: mail_plugin_dir: /usr/lib/dovecot/modules/imap mail_log_prefix: %Us(%u): mail_log_max_lines_per_sec: 10 imap_max_line_length: 65536 imap_capability: imap_client_workarounds: imap_logout_format: bytes=%i/%o imap_id_send: imap_id_log: imap_idle_notify_interval: 120 pop3_no_flag_updates: no pop3_enable_last: no pop3_reuse_xuidl: no pop3_lock_session: no pop3_uidl_format: %08Xu%08Xv pop3_client_workarounds: pop3_logout_format: top=%t/%p, retr=%r/%b, del=%d/%m, size=%s dict_db_config: dict_process_count: 1 managesieve_max_line_length: 65536 managesieve_logout_format: bytes=%i/%o managesieve_implementation_string: dovecot auth default: mechanisms: plain realms: default_realm: cache_size: 0 cache_ttl: 3600 cache_negative_ttl: 3600 executable: /usr/lib/dovecot/dovecot-auth user: root chroot: username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ username_translation: username_format: master_user_separator: anonymous_username: anonymous krb5_keytab: gssapi_hostname: winbind_helper_path: /usr/bin/ntlm_auth failure_delay: 2 verbose: no debug: no debug_passwords: no ssl_require_client_cert: no ssl_username_from_cert: no use_winbind: no count: 1 worker_max_count: 30 process_size: 256 passdb: driver: pam args: deny: no pass: no master: no userdb: driver: passwd args:

2 2

[Dovecot] Author wanted for Dovecot article in Linux Magazine (Germany)
by Markus Feilner 31 Oct '09

31 Oct '09

Hi list, I am an editor at the German Linux Magazine and I am searching for an author or input on Dovecot, its advantages and especially the recent features. I had organized some authors, but unfortunately they don't have time right now. :-) Nevertheless I heard many positive comments on Dovecot. I can write or help writing the article, but I would love to have some input from an experienced dovecot admin - perhaps with some stunning, unusual setup that might interest our readers (most of them are skilled admins and programmers...) Something that can't be easily done with other mail servers would be great, something spectacular that is suitable to convince an mail admin why he should migrate to Dovecot. It won't be long, just about 2-3 pages (a maximum of 15000 characters) including screen shots and/or listings, code, > 10 Links and an author's biography with photo. Anybody interested? That would be great, feel free to send me a mail to: mfeilner(a)linuxnewmedia.de Unfortunately, we don't have much time, there's only two weeks left, but I will help and do a lot of work for the article. And don't worry about language! :-) Thanks a lot! -- Best Regards - Mit freundlichen Gruessen Markus Feilner ------------------------- Feilner IT Linux & GIS Linux Solutions, Training, Seminare und Workshops - auch Inhouse Koetztingerstr 6c 93057 Regensburg Telefon: +49 941 8 10 79 89 Mobil: +49 170 3 02 70 92 WWW: www.feilner-it.net mail: mfeilner(a)feilner-it.net Bei Xing: http://www.xing.com/profile/Markus_Feilner -------------------------------------- My OpenVPN book - OPENVPN : Building and Integrating Virtual Private Networks http://www.packtpub.com/openvpn/book My new book - Out now: SCALIX Linux Administrator's Guide http://www.packtpub.com/scalix/book

2 1

[Dovecot] Dovecot in-house benchmarking
by Joseba Torre 30 Oct '09

30 Oct '09

Hi, Before some major changes in our infrastructure, I was interested in the performance impact of moving indexes to our NAS (Emc Celerra v5.5). So I downloaded both dovecot-1.1.19 and dovecot-1.2.6, compiled them and wrote 2 confs for each of them, one with local indexes and another with indexes in the NAS. Then I created 19 pam users, and tested system performance this way: - uninstall current installed version - install a new version - start dovecot - for each user run: imaptest user=user pass=pass host=localhost port=143 mbox=${MBOX} seed=123 secs=300 | tail -1 > file - stop dovecot I'm not sure if these tests are real, but our results are: * In our conf, 1.1.19 and 1.2.6 performance are roughly the same * Moving the indexes to our NAS makes the system 3 times slower As we currently only have 1 system accessing mails or indexes, I tried later with nfs_* = no, and mmap_disable = no. This makes performance 10% better in any situation. Our testing setup (very close to the real one) - Dell PowerEdge 2850, 2 P4 Xeon 3GHz, 3GB RAM - RHEL 4.7 (not sure about this, the last RHEL4) 32 bits - mailboxes are always in a nfs filesystem - for testing mbox file I've used dovecot-cvs.mbox I've attached a couple of graphs to show this results (I've a lot of them, but result are pretty close from one to another). Also, dovecot -n output for 1.2.6 with indexes in the NAS. Only needed changes have been applied from one conf to another. If you feel that the benchmark can be more "real" with some changes, just tell me. Also, if you are interested in the rest of graphs or date, tell me. Next week I'll be quite busy, but as soon as possible I'll test with an iSCSI disk for indexes. Aaaaaaaaaaagur. -- Joseba Torre. Vicegerencia de TICs, área de Explotación

1 0

[Dovecot] How to see if sieve is active ?
by Koenraad Lelong 30 Oct '09

30 Oct '09

Hi, I think I activated sieve, but it's doing nothing. I know manage-sieve works so I made some rules. But they do nothing. I ran sieve-test, which seems to work, but does not move the mail I test. Is this how it works ? I thought the -e parameter just "tested" the rules and did nothing and my command was supposed to do the "real thing". I read there should be a log. I don't find this, how should I enable this ? I just found that lda can have a separate log. I'll enable this and see. I read the wiki-page different times, but I don't see what I'm doing wrong. I attached some files. Sieve-test.txt is the command and output from sieve-test. Phpscript.sieve is the file .dovecot.sieve points to, and dovecot-config is my dovecot config ;-). Thanks for any pointers. Regards, Koenraad Lelong. # 1.2.5: /etc/dovecot/dovecot.conf # OS: Linux 2.6.22.19-0.4-default x86_64 openSUSE 10.3 (X86-64) base_dir: /var/run/dovecot/ log_path: /var/log/dovecot log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps managesieve listen(default): *:143 listen(imap): *:143 listen(managesieve): * ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(managesieve): ssl_ca_file: /etc/postfix/certificate/cacert.org.pem ssl_cert_file: /etc/postfix/certificate/mailbox.pem ssl_key_file: /etc/postfix/certificate/mailboxkey.pem disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot//login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login first_valid_uid: 499 last_valid_uid: 499 mail_location: maildir:/var/vmail/%d/%u mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugin_dir(default): /usr/lib64/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib64/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib64/dovecot/modules/managesieve managesieve_logout_format(default): bytes=%i/%o managesieve_logout_format(imap): bytes=%i/%o managesieve_logout_format(managesieve): bytes ( in=%i : out=%o ) lda: postmaster_address: postmaster(a)ace-electronics.be sendmail_path: /usr/lib/sendmail auth_socket_path: /var/run/dovecot/auth-master mail_plugins: sieve auth default: mechanisms: plain login user: nobody passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: vmail plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve sieve-test .dovecot.sieve new/1256755771.V6806I4ec63M549667.lace3 Performed actions: * store message in folder: Opensuse Implicit keep: (none) Info: final result: success # This script has been automatically generated by avelsieve # (Sieve Mail Filters Plugin for Squirrelmail) # Warning: If you edit this manually, then the changes will not # be reflected in the users' front-end! #AVELSIEVE_VERSIONYTo0OntzOjU6Im1ham9yIjtpOjE7czo1OiJtaW5vciI7aTo5O3M6NzoicmVsZWFzZSI7aTo5O3M6Njoic3RyaW5nIjtzOjU6IjEuOS45Ijt9 #AVELSIEVE_CREATED1256640979 #AVELSIEVE_MODIFIED1256715146 require ["fileinto","envelope","reject","vacation","imap4flags","relational","comparator-i;ascii-numeric","regex","body","date"]; #START_SIEVE_RULEYTo2OntzOjQ6ImNvbmQiO2E6MTp7aTowO2E6NTp7czo0OiJraW5kIjtzOjc6Im1lc3NhZ2UiO3M6NDoidHlwZSI7czo2OiJoZWFkZXIiO3M6NjoiaGVhZGVyIjtzOjc6IlN1YmplY3QiO3M6OToibWF0Y2h0eXBlIjtzOjg6ImNvbnRhaW5zIjtzOjExOiJoZWFkZXJtYXRjaCI7czoxMDoiW29wZW5zdXNlXSI7fX1zOjQ6InR5cGUiO3M6MToiMSI7czo5OiJjb25kaXRpb24iO3M6MzoiYW5kIjtzOjY6ImFjdGlvbiI7czoxOiI1IjtzOjY6ImZvbGRlciI7czo4OiJPcGVuc3VzZSI7czo0OiJzdG9wIjtzOjI6Im9uIjt9END_SIEVE_RULE if header :contains "Subject" "[opensuse]" { fileinto "Opensuse"; stop; } #START_SIEVE_RULEYTo2OntzOjQ6ImNvbmQiO2E6MTp7aTowO2E6NTp7czo0OiJraW5kIjtzOjc6Im1lc3NhZ2UiO3M6NDoidHlwZSI7czo2OiJoZWFkZXIiO3M6NjoiaGVhZGVyIjtzOjc6IlN1YmplY3QiO3M6OToibWF0Y2h0eXBlIjtzOjg6ImNvbnRhaW5zIjtzOjExOiJoZWFkZXJtYXRjaCI7czo5OiJbRG92ZWNvdF0iO319czo0OiJ0eXBlIjtzOjE6IjEiO3M6OToiY29uZGl0aW9uIjtzOjM6ImFuZCI7czo2OiJhY3Rpb24iO3M6MToiNSI7czo2OiJmb2xkZXIiO3M6NzoiZG92ZWNvdCI7czo0OiJzdG9wIjtzOjI6Im9uIjt9END_SIEVE_RULE if header :contains "Subject" "[Dovecot]" { fileinto "dovecot"; stop; } #START_SIEVE_RULEYTo2OntzOjQ6ImNvbmQiO2E6MTp7aTowO2E6NTp7czo0OiJraW5kIjtzOjc6Im1lc3NhZ2UiO3M6NDoidHlwZSI7czo2OiJoZWFkZXIiO3M6NjoiaGVhZGVyIjtzOjc6IlN1YmplY3QiO3M6OToibWF0Y2h0eXBlIjtzOjg6ImNvbnRhaW5zIjtzOjExOiJoZWFkZXJtYXRjaCI7czoxNDoiW0JhY3VsYS11c2Vyc10iO319czo0OiJ0eXBlIjtzOjE6IjEiO3M6OToiY29uZGl0aW9uIjtzOjM6ImFuZCI7czo2OiJhY3Rpb24iO3M6MToiNSI7czo2OiJmb2xkZXIiO3M6NjoiQmFjdWxhIjtzOjQ6InN0b3AiO3M6Mjoib24iO30%3DEND_SIEVE_RULE if header :contains "Subject" "[Bacula-users]" { fileinto "Bacula"; stop; } #START_SIEVE_RULEYTo2OntzOjQ6ImNvbmQiO2E6MTp7aTowO2E6NTp7czo0OiJraW5kIjtzOjc6Im1lc3NhZ2UiO3M6NDoidHlwZSI7czo2OiJoZWFkZXIiO3M6NjoiaGVhZGVyIjtzOjc6IlN1YmplY3QiO3M6OToibWF0Y2h0eXBlIjtzOjg6ImNvbnRhaW5zIjtzOjExOiJoZWFkZXJtYXRjaCI7czoxMjoiW01haWEtdXNlcnNdIjt9fXM6NDoidHlwZSI7czoxOiIxIjtzOjk6ImNvbmRpdGlvbiI7czozOiJhbmQiO3M6NjoiYWN0aW9uIjtzOjE6IjUiO3M6NjoiZm9sZGVyIjtzOjQ6Ik1haWEiO3M6NDoic3RvcCI7czoyOiJvbiI7fQ%3D%3DEND_SIEVE_RULE if header :contains "Subject" "[Maia-users]" { fileinto "Maia"; stop; } #START_SIEVE_RULEYTo2OntzOjQ6ImNvbmQiO2E6MTp7aTowO2E6NTp7czo0OiJraW5kIjtzOjc6Im1lc3NhZ2UiO3M6NDoidHlwZSI7czo2OiJoZWFkZXIiO3M6NjoiaGVhZGVyIjtzOjc6IlN1YmplY3QiO3M6OToibWF0Y2h0eXBlIjtzOjg6ImNvbnRhaW5zIjtzOjExOiJoZWFkZXJtYXRjaCI7czo2OiJbdGVzdF0iO319czo0OiJ0eXBlIjtzOjE6IjEiO3M6OToiY29uZGl0aW9uIjtzOjM6ImFuZCI7czo2OiJhY3Rpb24iO3M6MToiNSI7czo2OiJmb2xkZXIiO3M6NzoiZG92ZWNvdCI7czo0OiJzdG9wIjtzOjI6Im9uIjt9END_SIEVE_RULE if header :contains "Subject" "[test]" { fileinto "dovecot"; stop; }

4 6

Re: [Dovecot] Public Folder Quotas
by Anton Dollmaier 29 Oct '09

29 Oct '09

> OK thanks just one last query, would the quota rule be something like this? > quota_rule2 = Public*:storage=100M =========== namespace public { prefix = shared. separator = . (...) } dict { quotadict = mysql:/etc/dovecot/dovecot-dict-quota.conf expire = mysql:/etc/dovecot/dovecot-dict-expire.conf } quota = dict:INBOX::proxy::quotadict quota2 = dict:shared:%d:ns=shared.:proxy::quotadict quota_rule = *:storage=50M:messages=1000 quota_rule2 = Trash:storage=50M:messages=100 quota2_rule = *:storage=100M:messages=1000 =========== this currently works - you must use the prefix of the namespace as parameter in the quota-definition.

2 1

[Dovecot] dovecot-shared and shared "\Seen" flags
by Dave 29 Oct '09

29 Oct '09

(Running Dovecot 1.1.0) Is it possible to either - (a) Still have shared "\Seen" flags even while using the dovecot-shared file or (b) Indicate to Dovecot in some way other than the dovecot-shared file which permissions to use for any messages created? The problem is, in my shared folder (using symlinks) scenario I am using, I have to use the dovecot-shared file to make sure new messages get written with the correct user and group permissions so that everyone appropriate can access them, but I still would like the functionality of the shared "\Seen" flags in these shared/symlinked folders (which having dovecot-shared seems to knock out). Is it possible to do both somehow? Dave

2 3

Re: [Dovecot] 1.1 Quota Question
by Marty Anstey 29 Oct '09

29 Oct '09

>>> We are currently running Dovecot 1.1.16 & Postfix; maildir++. >>> >>> When a message arrives for a mailbox which is over quota, it is bounced. >>> Obviously, this isn't very desirable; the primary downside to this is >>> that when junk mail hits a full mailbox it's bounced to that recipient >>> of the message. On a busy mail system, that could potentially get us >>> blacklisted pretty quickly. Ideally we would like to reject the messages >>> inline. Is there an easy way to set this up? >>> >> >> a) Use deliver -e parameter and configure your MTA to wait on replying >> to DATA command until deliver has finished. I don't know how to make >> Postfix do this (or perhaps it does it by default? dunno). >> >> b) Use quota_warning scripts on 100% quota usage to update user's "quota >> full" bit in a database (or wherever) and have Postfix reject RCPT TO >> command based on that information. I don't know how to do that on >> Postfix's side either. Thanks for the feedback. Option (a) sounds like the cleanest solution, but a bit of testing showed that Postfix doesn't wait on deliver before replying to DATA so this seems to always result in a bounce. I've perused the postfix documentation but so far no luck; if anyone reading this has any insight on how we might configure postfix to behave this way, could you please let me know (maybe offlist would be best, as this may be considered somewhat off-topic). We are using something similar to option (b) currently, but it's not really an elegant approach and we would really like to move away from it. Option (a) sounds great, if we can somehow get it to work. TIA, Marty

1 0