November 2009 - dovecot

[Dovecot] Dovecot+Sieve Please Help!...
by Andrey Garkin 16 Nov '09

16 Nov '09

Dovecot Sieve Plugin... 1. ./configure --with-dovecot=/usr/lib/dovecot make make install protocol lda { postmaster_address = postmaster(a)kipalex.ru mail_plugins = sieve } plugin { sieve = /home/vmail/kipalex.ru/andrey(a)kipalex.ru/dovecot.sieve } 2. dovecot.sieve file in /home/vmail/kipalex.ru/andrey(a)kipalex.ru require "fileinto"; if header :contains "Subject" "***SPAM***" { fileinto "/home/vmail/kipalex.ru/andrey(a)kipalex.ru/.Spam/new"; } And in the dovecot.log I see: 2009-11-16 13:45:55 deliver(andrey(a)kipalex.ru): Error: sieve: msgid=<351009bd0911160227r6ef9f39fja32c2893cb7fc54e(a)mail.gmail.com>: failed to store into mailbox '/home/vmail/kipalex.ru/andrey(a)kipalex.ru/.Spam/new': Invalid mailbox name 2009-11-16 13:45:55 deliver(andrey(a)kipalex.ru): Error: sieve: execution of script /home/vmail/kipalex.ru/andrey(a)kipalex.ru/dovecot.sieve failed, but implicit keep was successful Mail system is already up and working... Please Help... Why Dovecot plugin is not working???

3 3

[Dovecot] More dovecot-2.0.alpha2 problems
by Mike Abbott 16 Nov '09

16 Nov '09

1. My earlier patch to fix a typo in array.h was not good enough. Here's one that not only compiles, but also doesn't crash: --- dovecot-2.0.alpha2/src/lib/array.h 2009-10-08 10:04:35.000000000 -0500 +++ dovecot/src/lib/array.h 2009-10-29 20:47:47.000000000 -0500 @@ -72,8 +72,7 @@ (elem)++) # define array_foreach_modifiable(array, elem) \ for (elem = ARRAY_TYPE_CAST_MODIFIABLE(array) \ - buffer_get_modifiable_data((array)->arr.buffer, NULL)) + \ - (array)->arr.buffer->used; \ + buffer_get_modifiable_data((array)->arr.buffer, NULL); \ elem != CONST_PTR_OFFSET(*(array)->v, (array)->arr.buffer- >used); \ (elem)++) #endif 2. Sometimes I see a flood of these errors in the log: [...] Fri Oct 30 14:45:23 server dovecot[9585]: imap: service(imap): dup2s failed Fri Oct 30 14:45:23 server dovecot[9585]: imap-login: Login: user=<userX>, method=PLAIN, rip=192.168.1.8, lip=192.168.1.7, pid=11362 Fri Oct 30 14:45:23 server dovecot[9585]: imap(pid 11362 user userX): Connection closed bytes=118/934 Fri Oct 30 14:45:23 server dovecot[9585]: imap: dup2(-1, 5) failed: Bad file descriptor Fri Oct 30 14:45:23 server dovecot[9585]: imap: service(imap): dup2s failed Fri Oct 30 14:45:23 server dovecot[9585]: imap-login: Login: user=<userY>, method=PLAIN, rip=192.168.1.8, lip=192.168.1.7, pid=11363 Fri Oct 30 14:45:23 server dovecot[9585]: imap(pid 11363 user userY): Connection closed bytes=118/972 Fri Oct 30 14:45:23 server dovecot[9585]: imap: dup2(-1, 5) failed: Bad file descriptor Fri Oct 30 14:45:23 server dovecot[9585]: imap: service(imap): dup2s failed [...] 3. imap crashed when using mdbox: Fri Oct 30 14:54:49 server dovecot[11491]: imap(pid 11938 user userZ): dbox /Volumes/Mail/userZ/mailboxes/INBOX/Sent/dbox-Mails: map uidvalidity mismatch (1256918863 vs 1256919073) Fri Oct 30 14:54:49 server dovecot[11491]: imap(pid 11938 user userZ): Disconnected: Internal error occurred. Refer to server log for more information. [2009-10-30 14:54:49] bytes=553447/2146313 Fri Oct 30 14:54:49 server dovecot[11491]: imap(pid 11938 user userZ): dbox /Volumes/Mail/userZ/storage: rebuilding indexes Fri Oct 30 14:54:49 server dovecot[11491]: imap(pid 11938 user user): Panic: file dbox-file.c: line 308 (dbox_file_get_mail_stream): assertion failed: (file->input != NULL) 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 0x00000001000e8027 i_set_failure_file + 275 5 libdovecot.0.dylib 0x00000001000e6eef i_set_failure_internal + 103 6 libdovecot.0.dylib 0x00000001000e76d2 i_debug + 0 7 libdovecot-storage.0.dylib 0x000000010005768a dbox_file_seek_next + 0 8 libdovecot-storage.0.dylib 0x000000010005772a dbox_file_seek_next + 160 9 libdovecot-storage.0.dylib 0x0000000100084266 mdbox_storage_rebuild + 1406 10 libdovecot-storage.0.dylib 0x0000000100085617 mdbox_mailbox_alloc + 1271 11 libdovecot-storage.0.dylib 0x00000001000271e1 mail_storage_unref + 93 12 libdovecot-storage.0.dylib 0x0000000100023386 mail_namespace_get_storage_name + 162 13 libdovecot-storage.0.dylib 0x0000000100023429 mail_namespaces_deinit + 35 14 libdovecot-storage.0.dylib 0x0000000100028c39 mail_user_alloc + 311 15 libdovecot-storage.0.dylib 0x000000010002889a mail_user_unref + 40 16 imap 0x0000000100007fa4 client_destroy + 404 17 imap 0x0000000100006eb3 client_input + 87 18 libdovecot.0.dylib 0x00000001000eca50 io_loop_handler_run + 224 19 libdovecot.0.dylib 0x00000001000ed55a io_loop_run + 56 20 libdovecot.0.dylib 0x00000001000e393d master_service_run + 27 21 imap 0x000000010000fb45 main + 557 22 imap 0x0000000100000dd0 start + 52 Hope this helps.

2 2

[Dovecot] file_dotlock_create(~/.dovecot.lda-dupes) failed: No such file or directory
by Rene Bakkum 16 Nov '09

16 Nov '09

Hi, I am having some problems with my vacation messages using dovecot. The mail is send without problems, and the auto-respond is working as well. But its always auto-responding, because the lda-dupes file can't be created. See mail log below: Nov 16 13:43:03 mail003 postfix/smtpd[6501]: connect from mail-bw0-f211.google.com[209.85.218.211] Nov 16 13:43:03 mail003 postfix/smtpd[6501]: D6FE6F64F: client=mail-bw0-f211.google.com[209.85.218.211] Nov 16 13:43:03 mail003 postfix/cleanup[6505]: D6FE6F64F: message-id=<4B014929.1000008(a)gmail.com> Nov 16 13:43:03 mail003 postfix/qmgr[27330]: D6FE6F64F: from=<[my.gmail.account]>, size=1946, nrcpt=1 (queue active) Nov 16 13:43:03 mail003 deliver([my.test.account]): file_dotlock_create(~/.dovecot.lda-dupes) failed: No such file or directory Nov 16 13:43:03 mail003 postfix/pickup[5934]: F202DF690: uid=5000 from=<> Nov 16 13:43:03 mail003 deliver([my.test.account]): msgid=<4B014929.1000008(a)gmail.com>: sent vacation response to <[my.gmail.account]> Nov 16 13:43:03 mail003 postfix/cleanup[6505]: F202DF690: message-id=<dovecot-1258375383-947629-0@mail003> Nov 16 13:43:04 mail003 postfix/qmgr[27330]: F202DF690: from=<>, size=570, nrcpt=1 (queue active) Nov 16 13:43:04 mail003 deliver([my.test.account]): msgid=<4B014929.1000008(a)gmail.com>: saved mail to INBOX Nov 16 13:43:04 mail003 postfix/pipe[6506]: D6FE6F64F: to=<[my.test.account]>, relay=dovecot, delay=0.21, delays=0.08/0.01/0/0.12, dsn=2.0.0, status=sent (delivered via dovecot service) Nov 16 13:43:04 mail003 postfix/qmgr[27330]: D6FE6F64F: removed Nov 16 13:43:05 mail003 postfix/smtp[6510]: F202DF690: to=<[my.gmail.account]>, relay=gmail-smtp-in.l.google.com[74.125.93.114]:25, delay=1.6, delays=0.07/0.01/0.32/1.2, dsn=2.0.0, status=sent (250 2.0.0 OK 1258375453 7si18156568qwb.35) Nov 16 13:43:05 mail003 postfix/qmgr[27330]: F202DF690: removed I manually created the file, but its keeping getting the message: root@mail003:/home/vmail/mydomain.com/info/.Maildir# ls -la drwx------ 6 vmail vmail 4096 2009-11-16 14:04 . drwx------ 3 vmail vmail 4096 2009-11-16 12:37 .. drwx------ 2 vmail vmail 4096 2009-11-16 14:04 cur -rw------- 1 vmail vmail 340 2009-11-16 13:49 dovecot.index -rw------- 1 vmail vmail 22528 2009-11-16 14:04 dovecot.index.cache -rw------- 1 vmail vmail 7000 2009-11-16 14:04 dovecot.index.log -rwx------ 1 vmail vmail 0 2009-11-16 14:03 .dovecot.lda-dupes -rwx------ 1 vmail vmail 485 2009-11-16 12:33 .dovecot.sieve -rw------- 1 vmail vmail 208 2009-11-16 12:56 .dovecot.sievec -rw------- 1 vmail vmail 522 2009-11-16 14:04 dovecot-uidlist -rw------- 1 vmail vmail 8 2009-11-11 14:31 dovecot-uidvalidity -rw------- 1 vmail vmail 0 2009-11-11 14:31 dovecot-uidvalidity.4afabcaa drwx------ 2 vmail vmail 4096 2009-11-16 14:04 new -rw------- 1 vmail vmail 6 2009-11-11 14:45 subscriptions drwx------ 2 vmail vmail 4096 2009-11-16 14:04 tmp drwx------ 5 vmail vmail 4096 2009-11-11 14:45 .Trash Is the ~/.dovecot.lda-dupes linking to another path, and how can I adjust this so it searches for /home/vmail/%d/%n/.Maildir/ ? Thanks, - Rene

2 2

[Dovecot] Panic: Message unexpectedly expunged from index
by Cliff Hayes 16 Nov '09

16 Nov '09

Hello, I just installed Fedora 11 with Dovecot 1.2.6 and am now seeing a steady stream of these in maillog: Nov 15 15:52:03 sendmail dovecot: POP3(<username>): Panic: Message unexpectedly expunged from index Nov 15 15:52:03 sendmail dovecot: POP3(<username>): Raw backtrace: pop3 [0x4930ab] -> pop3 [0x493123] -> pop3 [0x4927b6] -> pop3 [0x43ddd4] -> pop3 [0x43de84] -> pop3(index_mail_set_seq+0x146) [0x449c16] -> pop3 [0x43e129] -> pop3(index_storage_search_next_nonblock+0x141) [0x44d5c1] -> pop3(mailbox_search_next_nonblock+0x20) [0x45b580] -> pop3(mailbox_search_next+0x26) [0x45b5d6] -> pop3 [0x419ef9] -> pop3(client_command_execute+0x666) [0x41abd6] -> pop3(client_handle_input+0x80) [0x418f80] -> pop3(io_loop_handler_run+0xbd) [0x49b02d] -> pop3(io_loop_run+0x18) [0x49a498] -> pop3(main+0x526) [0x41b286] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x3a9b61ea2d] -> pop3 [0x418809] Nov 15 15:52:03 sendmail dovecot: dovecot: child 26792 (pop3) killed with signal 6 (core dumps disabled) I see nothing about this in the mail archives or on the internet! What could be happening and how do I fix? I'm also seeing lots of these: Nov 15 11:26:24 sendmail dovecot: POP3(<username>): Log synchronization error at seq=12646,offset=172 for /var/spool/mail/.imap/INBOX/dovecot.index: Extension introduction for unknown id 1 Nov 15 11:26:24 sendmail dovecot: POP3(<username>): fscking index file /var/spool/mail/.imap/INBOX/dovecot.index Here are the only things I messed with in dovecot.conf: protocols = pop3 mail_location = mbox:/var/spool/mail:INBOX=/var/spool/mail/%u mbox_very_dirty_syncs = yes Thanks in advance, Cliff

1 0

[Dovecot] IMAP folders' codepages problem ?
by michael＠euroinfissi.eu 14 Nov '09

14 Nov '09

Hi! I probably have a problem with the imap folders codepages. I use polish email clients such as MS Outlook and Windows Mail. The clients try to create folders like Wiadomości-Śmieci but Dovecot creates Wiadomo&AVs-ci-&AVs-mieci This happens on two different dovecot installations 1: Installation A # 1.2.6: /etc/dovecot.conf # OS: Linux 2.6.30.9-96.fc11.x86_64 x86_64 Fedora release 11 (Leonidas) info_log_path: /var/log/maillog protocols: imaps ssl_listen: * ssl: required ssl_cert_file: /etc/pki/certs/dovecot/dovecot.pem ssl_key_file: /etc/pki/certs/dovecot/dovecot_key.pem ssl_cipher_list: ALL:!ADH!LOW:!SSLv2:!EXP:+HIGH:+MEDIUM disable_plaintext_auth: yes verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_privileged_group: dovecot_mail mail_debug: yes mail_plugins: autocreate quota imap_quota expire lda: postmaster_address: root@localhost auth default: passdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot-sql.conf plugin: autocreate: Trash autosubscribe: Trash quota: dict:user::proxy::quota quota_rule: *:storage=1048576 quota_warning: storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/bin/quota-warning.sh 80 expire: Trash 7 INBOX 365 expire_dict: proxy::expire dict: quota: mysql:/etc/dovecot-dict-quota.conf expire: mysql:/etc/dovecot-dict-expire.conf 2: Installation B # 1.1.19: /usr/local/dovecot/etc/dovecot.conf # OS: Linux 2.6.22.14-72.fc6 x86_64 Fedora Core release 6 (Zod) base_dir: /usr/local/dovecot/var/run/dovecot/ log_path: /usr/local/dovecot/var/log/dovecot_log info_log_path: /usr/local/dovecot/var/log/dovecot_log protocols: imaps ssl_cert_file: /usr/local/ssl/certs/dovecot/certificate_04102009.crt ssl_key_file: /usr/local/ssl/certs/dovecot/privateKey_04102009.key ssl_cipher_list: ALL:!ADH!LOW:!SSLv2:!EXP:+HIGH:+MEDIUM verbose_ssl: yes login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login login_user: dovecot_login mail_privileged_group: dovecot_mail mail_plugins: expire quota imap_quota trash lda: postmaster_address: root@localhost hostname: filemon mail_plugins: expire quota mail_plugin_dir: /usr/local/dovecot/lib/dovecot/lda sendmail_path: /usr/sbin/sendmail auth_socket_path: /usr/local/dovecot/var/run/dovecot/auth-master auth default: mechanisms: plain login debug: yes passdb: driver: passwd-file args: /usr/local/dovecot/etc/passwd.dovecot userdb: driver: passwd-file args: /usr/local/dovecot/etc/passwd.dovecot socket: type: listen master: path: /usr/local/dovecot/var/run/dovecot/auth-master mode: 384 user: mail plugin: quota: dict:user::proxy::quotadict quota_rule: *:storage=5G:messages=2000 quota_rule2: Trash:storage=1G:messages=1000 quota_warning: storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/bin/quota-warning.sh 80 trash: /usr/local/dovecot/etc/dovecot-trash.conf expire: Trash 7 Spam 7 INBOX 180 Sent 180 auth_socket_path: /usr/local/dovecot/var/run/dovecot/auth-master expire_dict: proxy::expire dict: quotadict: mysql:/usr/local/dovecot/etc/dovecot-dict-quota.conf expire: mysql:/usr/local/dovecot/etc/dovecot-dict-expire.conf Please help :-) What should I do to have the right codes for the folder names? Best regards Michael Lattari

2 1

[Dovecot] v1.2.7 released
by Timo Sirainen 14 Nov '09

14 Nov '09

http://dovecot.org/releases/1.2/dovecot-1.2.7.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.7.tar.gz.sig * IMAP: IDLE now sends "Still here" notifications to same user's connections at the same time. This hopefully reduces power usage of some mobile clients that use multiple IDLEing connections. * IMAP: If imap_capability is set, show it in the login banner. + IMAP: Implemented SORT=DISPLAY extension. - Login process creation could have sometimes failed with epoll_ctl() errors or without epoll probably some other strange things could have happened. - Maildir: Fixed some performance issues - Maildir: Fixed crash when using a lot of keywords. - Several fixes to QRESYNC extension and modseq handling - mbox: Make sure failed saves get rolled back with NFS. - dbox: Several fixes.

3 2

[Dovecot] v1.1.20 released
by Timo Sirainen 14 Nov '09

14 Nov '09

http://dovecot.org/releases/1.1/dovecot-1.1.20.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.20.tar.gz.sig Hopefully one of the last v1.1 releases. * Upgraded to Unicode 5.2.0 - Maildir: Fixed crash when using a lot of keywords. - file_set_size() was broken with OSes that didn't support posix_fallocate() (almost everyone except Linux), causing all kinds of index file errors.

2 1

[Dovecot] Ownership and permissions for the index directory/filesystem
by Stewart Dean 14 Nov '09

14 Nov '09

I recently upgraded from DC 1.1.15 to 1.2.6. The /var/dcindx index root directory is: drwxrwsrwt 3962 root sys 192512 Nov 13 11:56 ./ thus 3777. It appears that the user index directories created under DC1.1 look like this (here for /var/dcindx/cep): drwx--S--- 5 cep sys 256 Nov 13 14:26 cep/ while those created under V1.2 look like: drwx------ 3 lrenart sys 256 Nov 12 14:59 lrenart/ It seems that the first time that DC goes to do indexing, I now see this error msg: Nov 12 11:45:15 mercury mail:err|error dovecot: IMAP(bpyi): open(/var/spool/mail/bpyi) failed: Permission denied (euid=2586(bpyi) egid=2000(bard2) missing +w perm: /var/spool/mail) ...but never again... Questions: 1) Are the ownership and permissions on the /var/dcindx index root directory ideal or should they be something else? 2) Ideally what should the ownership and permissions be for individual user subdirs? I create the user mail directories when creating a new account, so it would be little extra trouble to create and set the ownership and permissions. I am currently using mbox mailbox format but will be migrating to maildir over the next some months. Dovecot -n > # 1.2.6: /usr/local/etc/dovecot.conf > # OS: AIX 3 0001378F4C00 > listen: *:143 > ssl_listen: *:993 > disable_plaintext_auth: no > verbose_ssl: yes > login_dir: /var/run/dovecot/login > login_executable: /usr/local/libexec/dovecot/imap-login > login_processes_count: 12 > login_max_processes_count: 774 > max_mail_processes: 1280 > mail_max_userip_connections: 12 > verbose_proctitle: yes > first_valid_uid: 200 > mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u > mbox_write_locks: fcntl > mbox_dirty_syncs: no > lda: > postmaster_address: postmaster(a)example.com > auth default: > passdb: > driver: pam > userdb: > driver: passwd -- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

[Dovecot] Index file (date timestamp) issue on OS X 10.6.2 Server
by Darren Latter 14 Nov '09

14 Nov '09

Hi, I've run into a bit of a problem and exhausted my knowledge and research. I'm hoping that I've overlooked something very obvious! I moved from a single Apple OS X 10.6.2 server Dovecot environment to a NFS clustered environment, currently with two servers. Both servers are identical hardware, software. Currently both the Dovecot index and data files are on the NFS RAID array. Both servers are configured to work with NFS per the Dovecot guides. The index and data files are accessed via a target link to the NFS mount via /var/spool/imap/dovecot. Email can be sent and received via either server and there are no errors being reported (both platforms are in debug mode). In essence everything appears to be working fine. The issue is that after the index is initially built (all email timestamps are correct) however any new incoming email is timestamped: 8 July 2037 23:53 I checked the index files: drwx------ 5 XXXX mail 4096 Nov 12 20:41 .UND -rw------- 1 XXXX staff 1472 Nov 13 12:30 .nfs.2005105c.0583 -rw------- 2 XXXX mail 56668 Nov 13 15:44 .nfs.200514ff.0583 -rw------- 2 XXXX mail 1364 Nov 13 15:44 .nfs.20051500.0583 drwx------ 2 XXXX mail 12288 Nov 13 15:44 cur -rw------- 1 XXXX mail 118 Nov 13 10:04 dovecot-keywords -rw------- 1 XXXX staff 5359 Nov 13 15:44 dovecot-uidlist -rw------- 1 XXXX staff 8 Nov 12 21:12 dovecot-uidvalidity -rw------- 1 XXXX mail 0 Jul 8 2037 dovecot-uidvalidity.4afc7a3a -rw------- 1 XXXX staff 1472 Nov 13 15:44 dovecot.index -rw------- 2 XXXX mail 56668 Nov 13 15:44 dovecot.index.cache -rw------- 2 XXXX mail 1364 Nov 13 15:44 dovecot.index.log -rw------- 1 XXXX mail 3859 Nov 13 15:47 maildirsize drwx------ 2 XXXX mail 4096 Nov 13 15:44 new -rw------- 1 XXXX mail 902 Nov 1 14:07 subscriptions drwx------ 2 XXXX mail 4096 Nov 13 15:44 tmp When checking the "stand alone" old data - the files are all correctly dated. This issue is the same for all users. Any ideas? Many thanks, Darren sh-3.2# /usr/sbin/dovecotd -n # 1.1.17apple0.5: /private/etc/dovecot/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 456). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: Darwin 10.0.0 i386 nfs base_dir: /var/run/dovecot syslog_facility: local6 protocols: managesieve imaps listen(default): * listen(imap): * listen(managesieve): *:2000 ssl_cert_file: /etc/certificates/X.X.org.X.cert.pem ssl_key_file: /etc/certificates/X.X.org.X.key.pem ssl_cipher_list: ALL:!LOW:!SSLv2:!aNULL:!ADH:!eNULL login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login login_user: _dovecot login_process_per_connection: no max_mail_processes: 200 mail_max_userip_connections(default): 20 mail_max_userip_connections(imap): 20 mail_max_userip_connections(managesieve): 10 verbose_proctitle: yes first_valid_uid: 6 first_valid_gid: 6 mail_access_groups: mail mail_location: maildir:/var/spool/imap/dovecot/mail/%u mail_debug: yes mmap_disable: yes dotlock_use_excl: no mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock mbox_read_locks: fcntl dotlock mbox_write_locks: fcntl dotlock mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_process_sharing(default): full mail_process_sharing(imap): full mail_process_sharing(managesieve): none mail_max_connections(default): 5 mail_max_connections(imap): 5 mail_max_connections(managesieve): 20 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/managesieve sieve_storage(default): sieve_storage(imap): sieve_storage(managesieve): /var/spool/imap/dovecot/sieve-scripts/%u sieve(default): sieve(imap): sieve(managesieve): /var/spool/imap/dovecot/sieve-scripts/%u/dovecot.sieve auth default: mechanisms: gssapi cram-md5 verbose: yes debug: yes debug_passwords: yes passdb: driver: od userdb: driver: od args: partition=/etc/dovecot/partition_map.conf enforce_quotas=no socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: _dovecot group: mail plugin: quota_warning: storage=100%% /usr/libexec/dovecot/quota-exceeded.sh quota: maildir:User quota sieve: /var/spool/imap/dovecot/sieve-scripts/%u/dovecot.sieve

4 6

Re: [Dovecot] Index file (date timestamp) issue on OS X 10.6.2 Server
by Darren Latter 13 Nov '09

13 Nov '09

Squirrelmail operates fine no date/time issues - it's the only bit that works without a problem :) On 13 Nov 2009, at 21:00, Bruce Bodger wrote: > Right... I wasn't thinking of either Postfix or Dovecot, I was thinking that the program that was used to create the actual message may be squirrelmail or some other phpmailer-like affair. > > Good luck, > Bruce > > On Nov 13, 2009, at 2:49 PM, Darren Latter wrote: > >> Hi Bruce, >> >> OS X 10.6 Server uses Postfix and Dovecot so no PHP that I'm aware of - but thanks for the thought! >> I'm wondering if Apple have "enhanced" Dovecot for XSAN clustering/integration? I know that there are several parameters in the dovecot.conf file (mail file locations, index status) that are overridden by other Apple files. >> >> >> >> On 13 Nov 2009, at 20:23, Bruce Bodger wrote: >> >>> >>> On Nov 13, 2009, at 2:15 PM, Darren Latter wrote: >>> >>>> Volumes of emails arriving - hits either server, some will be correctly received with date/time, others time stamped with 8 July 2037, 23:53 >>>> Same server could give either the correct or the 2037 timestamp. >>> >>> It's a long shot, but are the emails that contain the errant date/time stamp being created by any php mail routine? We ask because we've seen similar issues with dates from a PEAR/Date library that's not php v5.3 compliant. >>> >>> B. Bodger >>> >> >> >

1 0