December 2009 - dovecot

[Dovecot] sieve vs deliver -m
by Frank Cusack 29 Dec '09

29 Dec '09

I'm invoking deliver through postfix with a dovecot transport in master.cf, using the -m ${extension} argument. If I have no sieve script, or a sieve script with an implicit keep, the mail gets correctly filed into the -m mailbox. However if the sieve script has an explicit discard, this gets honored if it doesn't match another sieve action. Shouldn't -m take precedence? I would say that if an extension is present any other sieve action should be ignored, perhaps just sieve_before should be run then the message filed per the extension. -frank

2 7

[Dovecot] Fwd: Dovecot-deliver sometimes fails when message set to discard via sieve
by Tobias Lang 28 Dec '09

28 Dec '09

Anfang der weitergeleiteten E-Mail: > Von: Steve Wagner <lanwin(a)lanwin.de> > Datum: 28. Dezember 2009 21:51:39 MEZ > An: Tobias Lang <tobias.lang(a)evoscout.de> > Betreff: Re: [Dovecot] Dovecot-deliver sometimes fails when message set to discard via sieve > > Sorry it took some time to get in to this failing situation. > > Procmail log--> > > procmail: [29952] Mon Dec 28 21:36:33 2009 > procmail: Match on "< 256000" > procmail: Locking "spamassassin.lock" > procmail: Executing "/usr/bin/spamc,-U,/var/run/spamd.sock" > procmail: [29952] Mon Dec 28 21:36:35 2009 > procmail: Unlocking "spamassassin.lock" > procmail: No match on "^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*" > procmail: No match on "^X-Spam-Status: YES" > procmail: No match on "^List-Id: .*debian-arm.lists.debian.org" > procmail: No match on "^^rom[ ]" > procmail: Executing "/opt/dovecot/libexec/dovecot/deliver" > procmail: Error while writing to "/opt/dovecot/libexec/dovecot/deliver" > procmail: Assigning "LASTFOLDER=/opt/dovecot/libexec/dovecot/deliver" > procmail: Assigning > "LASTFOLDER=/home/lanwin/Maildir/new/1262032593.29952_2.vs5923" > procmail: Notified comsat: > "lanwin@0:/home/lanwin/Maildir/new/1262032593.29952_2.vs5923" > From KeineAntwortAdresse(a)web.de Mon Dec 28 21:36:33 2009 > Subject: discoTEL > =?ISO-8859-1?Q?Tarif=3A_F=FCr_7=2C5_Cent=2FMin=2E_telefonier > Folder: /home/lanwin/Maildir/new/1262032593.29952_2.vs5923 > 41096 > procmail: Unlocking "/home/lanwin/Maildir/.lockmail" > > Dovecot Deliver Log--> > > 2009-12-28 21:36:35 deliver(lanwin): Info: sieve: > msgid=<E1NPMKF-00014k-00(a)mxnl04.web.de>: marked message to be discarded > if not explicitly delivered (discard action) > > Dose not look better to me. > > Steve > > Am 28.12.2009 18:06, schrieb Tobias Lang: >> >> Am 28.12.2009 um 15:09 schrieb Steve Wagner: >> >>> [snip] >>> >>> :0 w >>> | /opt/dovecot/libexec/dovecot/deliver >> >> Looks uncritical to me. Although there is no default rule at the end of >> .procmailrc, Dovecot deliver and Sieve should reroute everything not >> catched by a rule to INBOX. >> >> Did Procmails "VERBOSE=on" reveal something? >> >> Tobi >>

1 0

[Dovecot] managesieve error
by Lampa 26 Dec '09

26 Dec '09

Hello, when using sieve-php and using LOGIN auth, getting: 2009-11-21T15:13:48+0100 managesieve-login: Panic: file client.c: line 449 (client_set_auth_waiting): assertion failed: (client->to_auth_waiting == NULL) 2009-11-21T15:13:48+0100 dovecot: Error: child 8474 (login) killed with signal 6 (core dumps disabled) (latest ip=127.0.0.1) I'm using dovecot 1.2.6 from package debian testing (1:1.2.6-1) -- Lampa

2 1

[Dovecot] basic understanding of imap in dovecot
by dovecot＠paz.bz 24 Dec '09

24 Dec '09

I have always used a pop3 daemon, and switching to dovecot has been my introduction to imap. Imap is foreign to me. I am wondering if I am a little off-track here, and would like some clarification. My MTA (exim) delivers email to: /mail/user dovecot, sucks that mail from /mail/user TO /home/user/mail/<filenamesoffolders> dovecot IMAP further uses /home/user/mail/.imap/folders/{.index / .index.cache / .index.log} the mail folder which exim uses doesn't seem to get emptied by dovecot when it sucks the email into /home/user/mail/<filenamesoffolders> when using IMAP. If POP3 is used via dovecot, then it appears that the interaction is directly to the original exim folder and that it does indeed empty (or at least it has the "FOLDER INTERNAL DATA" entry). I suppose my question is, is there a way to have dovecot empty/parse the original exim mailbox so that the customer email isn't sitting in two spots, taking up double the space. This would be in the IMAP environment only, as POP3 seems to be fine. Any online references available to help a newbee understand IMAP? Thanks!

3 2

[Dovecot] 2.0.beta1/07e688afe81b imap crash
by Pascal Volk 24 Dec '09

24 Dec '09

Hi Timo, I've replaced a mdbox, as long Thunderbird was connected. The result is attached. Regards, Pascal -- The trapper recommends today: face1e55.0935803(a)localdomain.org #0 0x00007f0caa42ea18 in mail_namespace_get_vname (ns=0x0, dest=0x145d460, name=0x14bf1f9 "INBOX") at mail-namespace.c:418 No locals. #1 0x00007f0caa48eec0 in index_storage_mailbox_alloc (ibox=0x14b7890, name=0x14bf1f9 "INBOX", input=0x0, flags=265, index_prefix=0x7f0caa4e67b2 "dovecot.index") at index-storage.c:461 box = 0x14b7890 path = 0x14b7890 "x{K\001" dir_gid = 0 origin = 0x14b7828 "" dir_origin = 0x2d8 <Address 0x2d8 out of bounds> vname = 0x145d460 __PRETTY_FUNCTION__ = "index_storage_mailbox_alloc" #2 0x00007f0caa4cdd89 in mdbox_mailbox_alloc (storage=0x1462a20, list=0x0, name=0x14bf1f9 "INBOX", input=0x0, flags=265) at mdbox-storage.c:126 mbox = 0x14b7890 pool = 0x14b7828 #3 0x00007f0caa4cc84d in rebuild_restore_msg (ctx=0x14c4cf0, msg=0x151a098) at mdbox-storage-rebuild.c:545 storage = 0x1462a20 file = 0x0 hdr = 0x7fffc4a037c0 dbox_rec = {map_uid = 0, save_date = 0} mailbox = 0x14bf1f9 "INBOX" box = 0x0 mbox = 0x100000009 error = MAIL_ERROR_NONE deleted = false created = false size = 834 ret = 1 seq = 0 __PRETTY_FUNCTION__ = "rebuild_restore_msg" #4 0x00007f0caa4ccb73 in rebuild_handle_zero_refs (ctx=0x14c4cf0) at mdbox-storage-rebuild.c:632 msgs = 0x14ed000 i = 0 count = 1 #5 0x00007f0caa4ccdbe in rebuild_finish (ctx=0x14c4cf0) at mdbox-storage-rebuild.c:685 No locals. #6 0x00007f0caa4cd13e in mdbox_storage_rebuild_scan (ctx=0x14c4cf0) at mdbox-storage-rebuild.c:762 hdr = 0x14a3910 dir = 0x1475f70 d = 0x0 path = 0x145d298 dir_len = 24 uid_validity = 1261521073 ret = 0 __PRETTY_FUNCTION__ = "mdbox_storage_rebuild_scan" #7 0x00007f0caa4cd226 in mdbox_storage_rebuild (storage=0x1462a20) at mdbox-storage-rebuild.c:788 ctx = 0x14c4cf0 st = {st_dev = 2305, st_ino = 4562950, st_nlink = 2, st_mode = 16832, st_uid = 1000, st_gid = 1000, __pad0 = 0, st_rdev = 0, st_size = 4096, st_blksize = 4096, st_blocks = 8, st_atim = { tv_sec = 1261522332, tv_nsec = 0}, st_mtim = {tv_sec = 1261522325, tv_nsec = 0}, st_ctim = {tv_sec = 1261522325, tv_nsec = 0}, __unused = {0, 0, 0}} ret = 32524 #8 0x00007f0caa4cdc42 in mdbox_storage_destroy (_storage=0x1462a20) at mdbox-storage.c:93 storage = 0x1462a20 #9 0x00007f0caa43416f in mail_storage_unref (_storage=0x14a4ec0) at mail-storage.c:327 storage = 0x1462a20 __PRETTY_FUNCTION__ = "mail_storage_unref" #10 0x00007f0caa42db3a in mail_namespace_free (ns=0x14a4e70) at mail-namespace.c:50 No locals. #11 0x00007f0caa42e7df in mail_namespaces_deinit (_namespaces=0x14c0100) at mail-namespace.c:349 ns = 0x14a4e70 namespaces = 0x0 #12 0x00007f0caa436c9c in mail_user_deinit_base (user=0x14c0090) at mail-user.c:28 No locals. #13 0x00007f0ca91a22e8 in quota_user_deinit (user=0x14c0090) at quota-storage.c:463 quser = 0x14c0e10 #14 0x00007f0caa437257 in mail_user_unref (_user=0x14c8ef8) at mail-user.c:128 user = 0x14c0090 __PRETTY_FUNCTION__ = "mail_user_unref" #15 0x00000000004121e1 in client_destroy (client=0x14c8ea0, reason=0x0) at imap-client.c:197 cmd = 0x7fffc4a03ac8 __PRETTY_FUNCTION__ = "client_destroy" #16 0x0000000000413991 in client_input (client=0x14c8ea0) at imap-client.c:802 cmd = 0xc4a03b0c output = 0x0 bytes = 170 __PRETTY_FUNCTION__ = "client_input" #17 0x00007f0caa1ca9d6 in io_loop_handler_run (ioloop=0x1465f60) at ioloop-epoll.c:208 ctx = 0x1469fc0 events = 0x146a800 event = 0x146a800 list = 0x1466e80 io = 0x1467980 tv = {tv_sec = 4, tv_usec = 997221} events_count = 4 t_id = 2 msecs = 4998 ret = 1 i = 0 j = 0 call = true #18 0x00007f0caa1c9681 in io_loop_run (ioloop=0x1465f60) at ioloop.c:350 No locals. #19 0x00007f0caa1b3aef in master_service_run (service=0x1464ee0, callback=0x41f55f <client_connected>) at master-service.c:473 No locals. #20 0x000000000041f76a in main (argc=1, argv=0x146d010) at main.c:307 set_roots = {0x4234a0, 0x0} service_flags = MASTER_SERVICE_FLAG_KEEP_CONFIG_OPEN storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT postlogin_socket_path = 0x0

1 0

[Dovecot] Permissions errors while reading messages via IMAP
by Geoff Sweet 24 Dec '09

24 Dec '09

Greetings all, I have been trying to setup a new system using Postfix and Dovecot to manage email for a bunch of virtual domains. So far everything is great, and I am now at the point where I am trying to build a webmail interface for the system. I'm using RoundCube for now. The tutorial I have been working from is here: http://workaround.org/articles/ispmail-etch/ Which seems to be a decent enough read. At this point I can login without issue but I can't see any mail messages. When I login, dovecot throws errors like this: Dec 23 12:08:49 mail1 dovecot: auth(default): client out: OK 1 user=geoff.sweet(a)test.com Dec 23 12:08:49 mail1 dovecot: auth(default): master in: REQUEST 1 4312 1 Dec 23 12:08:49 mail1 dovecot: auth(default): master out: USER 1 geoff.sweet(a)test.com uid=5000 gid=5000 home=/home/vmail/test.com/geoff.sweet Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): Effective uid=5000, gid=5000, home=/home/vmail/test.com/geoff.sweet Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): maildir: data=/home/vmail/test.com/geoff.sweet/Maildir Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): maildir++: root=/home/vmail/test.com/geoff.sweet/Maildir, index=, control=, inbox=/home/vmail/test.com/geoff.sweet/Maildir Dec 23 12:08:49 mail1 dovecot: imap-login: Login: user=<geoff.sweet(a)test.com>, method=PLAIN, rip=192.168.20.11, lip=192.168.20.12 Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): Disconnected: Logged out bytes=39/431 Dec 23 12:08:49 mail1 dovecot: auth(default): new auth connection: pid=4315 Dec 23 12:08:49 mail1 dovecot: auth-worker(default): sql(geoff.sweet(a)test.com,192.168.20.11): query: SELECT email as user, password FROM view_mailboxes WHERE email='geoff.sweet(a)test.com'; Dec 23 12:08:49 mail1 dovecot: auth(default): client in: AUTH 1 PLAIN service=imap lip=192.168.20.12 rip=192.168.20.11 lport=143 rport=43878 resp=AGdlb2ZmLnN3ZWV0QHdob290aXMuY29tAGJvYjEyMzQ1 Dec 23 12:08:49 mail1 dovecot: auth(default): client out: OK 1 user=geoff.sweet(a)test.com Dec 23 12:08:49 mail1 dovecot: auth(default): master in: REQUEST 2 4311 1 Dec 23 12:08:49 mail1 dovecot: auth(default): master out: USER 2 geoff.sweet(a)test.com uid=5000 gid=5000 home=/home/vmail/test.com/geoff.sweet Dec 23 12:08:49 mail1 dovecot: imap-login: Login: user=<geoff.sweet(a)test.com>, method=PLAIN, rip=192.168.20.11, lip=192.168.20.12 Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): Effective uid=5000, gid=5000, home=/home/vmail/test.com/geoff.sweet Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): maildir: data=/home/vmail/test.com/geoff.sweet/Maildir Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): maildir++: root=/home/vmail/test.com/geoff.sweet/Maildir, index=, control=, inbox=/home/vmail/test.com/geoff.sweet/Maildir Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): Namespace : Using permissions from /home/vmail/test.com/geoff.sweet/Maildir: mode=0700 gid=-1 Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): open(/home/vmail/test.com/geoff.sweet/Maildir/dovecot.index.log) failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +r perm: /home/vmail/test.com/geoff.sweet/Maildir/dovecot.index.log) Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): open(/home/vmail/test.com/geoff.sweet/Maildir/dovecot-uidlist) failed: Permission denied Dec 23 12:08:49 mail1 last message repeated 2 times There is some permission issue that allows dovecot to deliver email to the /home/vmail location (I dislike this location and want to change it) via the dovecot LDA process, but then not be able to read it when accessed via IMAP. I'm very confused lol. Dovecot version 1.2.9 dovecot -n: # 1.2.9: /etc/dovecot.conf # OS: Linux 2.6.18-164.6.1.el5 i686 CentOS release 5.4 (Final) ext3 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_greeting: Dovecot ready. mail_location: maildir:/home/vmail/%d/%n/Maildir mail_debug: 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 lda: log_path: /home/vmail/dovecot-deliver.log auth_socket_path: /var/run/dovecot/auth-master postmaster_address: postmaster(a)test.com mail_plugins: global_script_path: /home/vmail/globalsieverc auth default: mechanisms: plain login debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail

2 4

[Dovecot] virtual plugin: Broken mailbox list
by e-frog 23 Dec '09

23 Dec '09

Hello Timo, I'm testing the latest hg version from the 1.2 series and get the following in dovecot's error log as soon as I try to access the virtual mailbox Dec 11 18:23:07 ubuntu-test dovecot: IMAP(xxxxx): virtual index /etc/dovecot/virtual/unseen: Broken mailbox list $ cat dovecot-virtual * unseen $ dovecot -n # 1.2.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31-16-generic-pae i686 Ubuntu 9.10 protocols: imap imaps managesieve disable_plaintext_auth: no 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 verbose_proctitle: yes mail_location: maildir:~/.maildir mail_debug: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/lib/dovecot/rawlog /usr/lib/dovecot/wrapper.sh mail_executable(imap): /usr/lib/dovecot/rawlog /usr/lib/dovecot/wrapper.sh mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): expire fts fts_squat virtual quota imap_quota mail_log acl mail_plugins(imap): expire fts fts_squat virtual quota imap_quota mail_log acl mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve mail_log_max_lines_per_sec: 0 namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: virtual/ location: virtual:/etc/dovecot/virtual:INDEX=~/.maildir/control:CONTROL=~/.maildir/control list: children lda: postmaster_address: postmaster@ubuntu hostname: ubuntu mail_plugins: sieve virtual expire quota acl mail_plugin_dir: /usr/lib/dovecot/modules/lda deliver_log_format: msgid=%m: from=%f: %$ log_path: /var/log/deliver.log info_log_path: /var/log/deliver.log sendmail_path: /usr/lib/sendmail rejection_subject: Rejected: %s rejection_reason: Your message to <%t> was automatically rejected:%n%r auth_socket_path: /var/run/dovecot/auth-master auth default: 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: 438 plugin: quota: dict:user::proxy::dictionary expire: Trash 1 "INBOX/log check" 1 expire_dict: proxy::dictionary mail_log_events: delete undelete expunge copy mailbox_delete mailbox_rename flag_change mail_log_fields: uid box msgid size flags sieve: ~/.dovecot.sieve sieve_dir: ~/sieve deliver_log_format: msgid=%m: from=%f: %$ fts: squat fts_squat: partial=4 full=10 dict: dictionary: mysql:/etc/dovecot/dovecot-dict-sql.conf

2 2

[Dovecot] imap-login crashes after upgrade to Dovecot 1.2.8 Linux 64-bit
by Chris Wakelin 23 Dec '09

23 Dec '09

Hi all, We moved our Dovecot installation first of all to have all folders and inboxes on NetApps via NFS (with indexes local) then from a physical Solaris 8 4-way UltraSparc server running Dovecot 1.2.5 (32-bit) to a virtualised Ubuntu 8.04 64-bit server with a single virtual processor (in VMWare ESX 3.5) running Dovecot 1.2.8 (64-bit). Since the change, many of our users have experienced random disconnections when proxied in imap-login (either using the internal SSL proxy, or to an external IMAP server) and the error logs contain things like: > Dec 18 00:27:58 imap-login: Info: Disconnected: Connection queue full (auth failed, 1 attempts): user=<user0>, method=PLAIN, rip=<ip0>, lip=134.225.32.156, TLS > Dec 18 00:27:58 imap-login: Panic: file ioloop.c: line 39 (io_add): assertion failed: (fd >= 0) > Dec 18 00:27:58 IMAP 9486 <user1> <ip1> : Info: Connection closed bytes=224/1753 > Dec 18 00:27:58 IMAP 10116 <user2> <ip2> : Info: Connection closed bytes=82/707 ... > Dec 18 00:27:58 IMAP 10296 <user3> <ip3> : Info: Disconnected in IDLE bytes=44/435 > Dec 18 00:27:58 IMAP 10298 <user3> <ip3> : Info: Disconnected in IDLE bytes=263/1662 > Dec 18 00:27:58 dovecot: Error: child 5124 (login) killed with signal 6 (core dumped) (latest ip=<ip0>) > Dec 18 00:27:58 imap-login: Info: Aborted login (no auth attempts): rip=<ip0>, lip=134.225.32.156, TLS: Disconnected and a backtrace gives: > (gdb) bt > #0 0x00007ff1030ad095 in raise () from /lib/libc.so.6 > #1 0x00007ff1030aeaf0 in abort () from /lib/libc.so.6 > #2 0x00000000004112d5 in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:160 > #3 0x0000000000411333 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=<value optimized out>, args=<value optimized out>) at failures.c:443 > #4 0x0000000000410996 in i_panic (format=0x6 <Address 0x6 out of bounds>) at failures.c:207 > #5 0x000000000041420e in io_add (fd=-1, condition=IO_READ, callback=0x404db0 <client_input>, context=0x6af000) at ioloop.c:39 > #6 0x00000000004059db in client_auth_failed (client=0x6af000, nodelay=true) at client-authenticate.c:103 > #7 0x0000000000405e07 in client_handle_args (client=0x6af000, args=<value optimized out>, success=true, nodelay_r=0x7fff571009af) > at client-authenticate.c:198 > #8 0x0000000000406214 in sasl_callback (_client=0x6af000, reply=SASL_SERVER_REPLY_SUCCESS, data=0x0, args=0x6361d0) at client-authenticate.c:277 > #9 0x000000000040eb13 in auth_client_input_ok (conn=0x75b6c8, args=<value optimized out>) at auth-server-request.c:196 > #10 0x000000000040dbf3 in auth_client_input (conn=0x75b6c8) at auth-server-connection.c:136 > #11 0x0000000000414aa8 in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:208 > #12 0x0000000000413b9d in io_loop_run (ioloop=0x6552b0) at ioloop.c:335 > #13 0x0000000000408e81 in main (argc=2, argv=0x7fff57100c58, envp=0x7fff57100c70) at main.c:494 Up until this afternoon we had "login_process_per_connection = yes", and login_max_connections at the default (256). This evening I tried with "login_process_per_connection = no" with no problems, except more CPU load and needing to increase login_max_processes_count (and strictly speaking the max fds set with ulimit -n would need to be increased, though I didn't do that as it would have involved killing and restarting the master process - come back Solaris plimit!) Just after midnight, I switched back to "login_process_per_connection = no" and set "login_max_connections = 32" and managed to get core dumps enabled, hence the above! Apart from this problem, the virtual machine has been doing extremely well, so it's not CPU or I/O load related. I'm not sure whether the problem is caused by the switch from Dovecot 1.2.5 to 1.2.8, Solaris to Linux, physical to virtual, or 32-bit to 64-bit! Perhaps we changed too much at once, but it did mean we kept the service going while power was turned off in our main machine room last weekend ... Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 6

[Dovecot] expire db(s)?
by ben＠electricembers.net 23 Dec '09

23 Dec '09

with two separate dovecot/backend servers accessing one central mysql server, will it be ok to have them both use the same expires table? Or will that confuse the actual dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool.sh cronjob since some of the entries mailboxes won't exist locally? Ben

2 3

[Dovecot] qpopper to dovecot migration
by Jernej Porenta 23 Dec '09

23 Dec '09

Heya, We are in the process of migrating from qpopper to dovecot as POP3 server (and IMAP as well) and we hit the UIDL issue with dovecot. Qpopper uses its own algorithm to create UIDL values and if you set it up to write them down in the mbox file as X-UIDL, then dovecot can use them (pop_uidl_reuse = yes). But if you don't use that feature from qpopper, than X-UIDLs are missing and there is no way to create the same UIDL values. So, I was wondering if anyone else hit that issue and maybe knows how to address it (writing an extension or something)? Thanks in advance, regards, Jernej

2 1

[Dovecot] Dovecot Deliver CPU usage
by Aravind Divakaran 23 Dec '09

23 Dec '09

Hi All, We have upgraded the dovecot from 1.0 to 1.2.8. After upgradation we have noticed that dovecot deliver process is utilizing a lot of CPU. As a result the mailsystem will stop working. When we limit the no of procs in postfix for dovecot deliver the CPU usage will come down. But we are not facing this problem with the previous version. Below is the log files for dovecot when the error occurs write_full(/home/vmail/dhanbank.co.in/vinukumarvm/temp.server.be3e5a849a909847) failed: No space left on device dovecot: deliver(user(a)example.com): stat(/tmp/Dovecot Delivery Mail) failed: No space left on device But my system has 54gb of free space for root filesystem where tmp residing. Can anyone help me to solve this issue. Rgds, Aravind

5 17

[Dovecot] Panic: file maildir-uidlist.c: line 1242 (maildir_uidlist_records_drop_expunges): assertion failed
by Anton Dollmaier 23 Dec '09

23 Dec '09

Hi all, after inserting another sieve-rule, I get the following backtrace on deliver. The mail gets delivered into the Mailbox, but as deliver does not exit with 0, postfix bounces the mail. The additional rule is the same as all others in my .dovecot-sieve: > require ["fileinto", "include"]; > > if header :contains ["From"] ["@terra.a1a-server.de"] { > fileinto "Server.ADITSystems.terra"; > (...) > } elsif header :contains ["From"] ["@neon.a1a-server.de"] { > fileinto "Server.ADITSystems.neon"; > } else { > include :global "shared.sieve"; > fileinto "Server.Serveradmin"; > } > Dec 23 11:23:37 deliver(serveradmin(a)aditsystems.de): Panic: file > maildir-uidlist.c: line 1242 (maildir_uidlist_records_drop_expunges): > assertion failed: (recs[i]->uid < rec->uid) > Dec 23 11:23:37 deliver(serveradmin(a)aditsystems.de): Error: Raw backtrace: > /usr/lib/dovecot/deliver [0x80e52a1] -> > /usr/lib/dovecot/deliver(default_fatal_handler+0x3a) [0x80e53ca] -> > /usr/lib/dovecot/deliver [0x80e4c79] -> /usr/lib/dovecot/deliver > [0x807e097] -> > /usr/lib/dovecot/deliver(maildir_uidlist_sync_finish+0x29f) > [0x807f10f] -> > /usr/lib/dovecot/deliver(maildir_uidlist_sync_deinit+0xa8) > [0x807f458] -> > /usr/lib/dovecot/deliver(maildir_transaction_save_commit_pre+0x399) > [0x80820c9] -> /usr/lib/dovecot/deliver [0x807bbb2] -> > /usr/lib/dovecot/deliver(index_transaction_commit+0x4e) [0x80a472e] > -> /usr/lib/dovecot/deliver(mailbox_transaction_commit+0x26) > [0x80a9716] -> /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so > [0xb7d30b84] -> > /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so(sieve_result_execute+0x244) > [0xb7d2a024] -> > /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so(sieve_execute+0x87) > [0xb7d37fa7] -> /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so > [0xb7d1bcde] -> /usr/lib/dovecot/deliver(main+0x1108) [0x8061618] -> > /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7d8a455] -> > /usr/lib/dovecot/deliver [0x805f3c1] Following output of "dovecot -n": > # 1.2.8: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.26-2-686-bigmem i686 Debian 5.0.3 > protocols: imap imaps managesieve pop3 pop3s > listen: [::], * > ssl_cert_file: /etc/dovecot/dovecot.pem > ssl_key_file: /etc/dovecot/dovecot.pem > disable_plaintext_auth: no > login_dir: /var/run/dovecot/login > login_executable(default): /usr/lib/dovecot/imap-login > login_executable(imap): /usr/lib/dovecot/imap-login > login_executable(pop3): /usr/lib/dovecot/pop3-login > login_executable(managesieve): /usr/lib/dovecot/managesieve-login > login_process_per_connection: no > login_processes_count: 5 > mail_privileged_group: vmail > mail_location: maildir:~/Maildir > mail_executable(default): /usr/lib/dovecot/imap > mail_executable(imap): /usr/lib/dovecot/imap > mail_executable(pop3): /usr/lib/dovecot/pop3 > mail_executable(managesieve): /usr/lib/dovecot/managesieve > mail_plugins(default): autocreate expire quota imap_quota > mail_plugins(imap): autocreate expire quota imap_quota > mail_plugins(pop3): > mail_plugins(managesieve): > mail_plugin_dir(default): /usr/lib/dovecot/modules/imap > mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap > mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 > mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve > imap_client_workarounds(default): delay-newmail tb-extra-mailbox-sep > imap_client_workarounds(imap): delay-newmail tb-extra-mailbox-sep > imap_client_workarounds(pop3): > imap_client_workarounds(managesieve): > pop3_save_uidl(default): no > pop3_save_uidl(imap): no > pop3_save_uidl(pop3): yes > pop3_save_uidl(managesieve): no > pop3_uidl_format(default): %08Xu%08Xv > pop3_uidl_format(imap): %08Xu%08Xv > pop3_uidl_format(pop3): UID%u-%v > pop3_uidl_format(managesieve): %08Xu%08Xv > pop3_client_workarounds(default): > pop3_client_workarounds(imap): > pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh > pop3_client_workarounds(managesieve): > managesieve_implementation_string(default): dovecot > managesieve_implementation_string(imap): dovecot > managesieve_implementation_string(pop3): dovecot > managesieve_implementation_string(managesieve): Cyrus timsieved v2.2.13 > namespace: > type: private > separator: . > prefix: INBOX. > inbox: yes > list: yes > subscriptions: yes > namespace: > type: public > separator: . > prefix: Server. > location: maildir:/var/mail/vmail/%d/shared/Server:INDEX=~/indexes/Server > list: yes > subscriptions: yes > lda: > postmaster_address: postmaster(a)terra.a1a-server.de > mail_plugins: quota sieve autocreate > deliver_log_format: %m:%$:%f:%s > log_path: /var/log/dovecot-deliver.log > info_log_path: /var/log/dovecot-deliver.log > auth default: > mechanisms: plain login > passdb: > driver: sql > args: /etc/dovecot/dovecot-sql.conf > passdb: > driver: sql > args: /etc/dovecot/dovecot-sql-master.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: 438 > plugin: > sieve: ~/.dovecot.sieve > sieve_global_dir: /etc/dovecot/sieve/ > sieve_dir: %h/sieve > autocreate: INBOX.Trash > autocreate2: INBOX.Spam > autocreate3: INBOX.Sent > autosubscribe: INBOX.Trash > autosubscribe2: INBOX.Spam > autosubscribe3: INBOX.Sent Best regards & merry christmas! Anton Dollmaier

2 1

[Dovecot] Openbsd Postfix-Dovecot-SASL
by thekat 22 Dec '09

22 Dec '09

Greetings all, I have a OpenBSD /Dovecot server at home running and sending / receiving email "internally" without issue.. Recently, I set up the same at our Parish, but one of our users wants to get their email externally. The user can read their email but has to "send" via the local ISP server.. The problem After much searching I have not found an answer to my question. I would like the user to authenticate to be able to "send" email "through" the server.. OpenBSD uses bsdauth by default in Dovecot. After reading the Postfix http://www.postfix.org/SASL_README.html and the Dovecot Wiki http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL I have tried multiple configurations but I can't seem to get this to work.. It may be something very simple that I am missing.. All users on the Server have accounts in /etc/passwd (just no shell) Postfix - main.cf mailbox_command = /usr/local/libexec/dovecot/deliver mynetworks = 127.0.0.0/8 smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination dovecot --version 1.1.16 dovecot -n # OS: OpenBSD 4.6 i386 base_dir: /var/dovecot/ protocols: imaps listen: *, [::] ssl_cert_file: /etc/ssl/dovecotcert.pem disable_plaintext_auth: no login_dir: /var/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: _dovecot login_max_processes_count: 256 max_mail_processes: 32 mail_location: maildir:~/Maildir mbox_write_locks: fcntl imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep auth default: cache_size: 1024 passdb: driver: bsdauth args: cache_key=%u userdb: driver: passwd socket: type: listen client: path: /var/run/auth-client mode: 432 user: _postfix master: path: /var/run/auth-master mode: 384 user: _postfix Error using bsdauth Dec 21 15:07:09 aml000t3 dovecot: dovecot v1.1.16 starting up Dec 21 15:07:09 aml000t3 dovecot: Panic: auth(default): file passdb.c: line 190 (passdb_init): assertion failed: (passdb->passdb->default_pass_scheme != NULL || passdb->passdb->cache_key == NULL) Dec 21 15:07:09 aml000t3 dovecot: child 18954 (auth) killed with signal 6 (core not dumped) Dec 21 15:07:09 aml000t3 dovecot: Fatal: Auth process died too early - shutting down It looks like bsdauth has a bug and even though this thread "lists" a patch, I haven't been able to find it.. http://old.nabble.com/bsdauth-with-cache_key-failed-ts25800484.html#a258004… so I guess I am looking for an alternative to be able to allow users to "send through the server" Thx for any pointers tk -- View this message in context: http://old.nabble.com/Openbsd-Postfix-Dovecot-SASL-tp26890148p26890148.html Sent from the Dovecot mailing list archive at Nabble.com.

2 4

[Dovecot] Remove From Server When Deleted From Deleted Items
by Matt 21 Dec '09

21 Dec '09

In Windows Live Mail I have this setting enabled: "Remove From Server When Deleted From Deleted Items". It does not seem to remove them even when the trash is emptied though. Am using POP3 access. Anyone else see this? Matt

1 0

[Dovecot] Dovecot v2.0 wiki
by Timo Sirainen 21 Dec '09

21 Dec '09

I forked the wiki to http://wiki1.dovecot.org/ is the old docs for v1.x http://wiki2.dovecot.org/ is the new docs for v2.0 For now wiki.dovecot.org points to wiki1, but once v2.0 is released I'll change it to point to wiki2. I symlinked the user directory, so users should stay synced between the wikis. The main reason for wiki2 is to be able to describe Dovecot v2.0's actual behavior everywhere and get rid of all the old v1.x specific settings. The wiki1 is already annoyingly bloated and confusing with information about v1.0 and then v1.1 and maybe even how it's still different in v1.2.. Now would be a good time to do any other larger changes, if anyone has suggestions. :) (Oh, and I haven't yet done any actual changes to wiki2..)

3 5

Re: [Dovecot] [exim] Exim + Dovecot deliver overquota problems
by Nikita Koshikov 21 Dec '09

21 Dec '09

On Mon, 21 Dec 2009 13:44:42 +0100 Joan <aseques(a)gmail.com> wrote: > > > > You need to check user's quota on routing stage, not transport. > > > It'd be much better, because I would allow me to mix overquota and > no-overquota recipients. > But the problem in my case is that I am using some hashing to > distribute the users' mailboxes, dovecot can handle this easily > because it supports some interesting stuff > (http://wiki.dovecot.org/Variables) Exim have much more variables and functions http://exim.org/exim-html-4.69/doc/html/spec_html/ch11.html#SECTexpvar, so if you don't use any special dovecot variable data, than it shouldn't be a problem. > With a perl script I could also do that, I would like only if it's the > last resort (too much overhead I would think) > > Parsing file and counting quota value - is trivial stuff. The main disadvantage of this way is executing external aplication on every RCPT TO command. If you'll decide to use perl consider using option perl_at_start to minimize aplication starting time.

1 0

[Dovecot] Released Pigeonhole Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.9
by Stephan Bosch 21 Dec '09

21 Dec '09

Hello Dovecot users, Due to personal matters I haven't had time to do anything in the last few weeks. Before that I provided some pre-releases and since nobody indicated problems with those, I release them definitively now. I hope the shit storm has blown over, so that I can dedicate more of my time towards Pigeonhole development. The Sieve release involves a large architectural change, but also fixes quite a few small problems. The ManageSieve release is necessary to match Sieve API changes. Changelog Sieve v0.1.14: * Made the imposed limits on the number of redirects and the number of actions configurable. The settings are called sieve_max_actions and sieve_max_redirects. * Did a major rework of extension handling, making sure that no global state is maintained. This change was triggered by problems that global state info would cause for Dovecot v2.0, but it is also important for v1.2 as it significantly cleans up the library implementation. + Made LDA Sieve plugin recognize the deliver_log_format setting. + Message headers produced from user-supplied data are now RFC2047-encoded if necessary for outgoing messages. This is for example important for the :subject argument of the vacation action. + Added support for the $text$ substitution in the deprecated notify extension. + The subaddress extension now also accepts recipient_delimiter setting as an alias for sieve_subaddress_sep setting. This anticipates the recipient_delimiter setting in v2.0. - Fixed logging of mailbox names. It logged the converted mUTF7 version in stead of the original UTF8 version supplied by the user. - Fixed a minor memory leak in the multiscript support. - Fixed a bug in the recompilation of Sieve scripts. Made sure that scripts are only recompiled when the script file - or the symlink pointing to it - is strictly newer. Changelog ManageSieve v0.11.10: * This release contains adjustments to match changes in the Sieve API. This means that this release will only compile against Pigeonhole Sieve v0.1.14. - Fixed compilation of ManageSieve against CMUSieve. The releases are available as follows: Sieve: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14.tar.gz.sig ManageSieve (package + patch): http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10.tar.gz.… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.9-managesieve-0.11.10.diff.… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.9-managesieve-0.11.10.diff.… Refer to http://pigeonhole.dovecot.org for more information. Have fun testing the new releases and don't hesitate to notify me when there are problems. Releases for Dovecot v2.0 are still under development... Regards, -- Stephan Bosch stephan(a)rename-it.nl

2 4

[Dovecot] Dovecot vs Exim file locking
by Daniel Campos 21 Dec '09

21 Dec '09

Hi all: We're planning to deploy a large e-mail system storing maildirs in a NAS system through NFS. One of the options we're thinking on is using Dovecot+EXIM. As far as I've read in both project's documentation, both services implement locking allowing multiple servers to access the same maildirs in order to distribute the service load. However, I can't find any information explaining whether both locking mechanisms are compatible, whether any additional configuration is needed both in Dovecot and/or EXIM, or even whether any locking synchronization between both services is needed/recommendable at all. The only remote clue I've found is that, according to Dovecot docs: "Because Dovecot uses its own non-standard locking (dovecot-uidlist.lock dotlock file), other MUAs accessing the maildir don't support it." (but EXIM is not a MUA, anyway) Anyhow theoretically MailDir could even be considered free of locking problems, but I'm not sure of the real implications of putting together several Exim and Dovecot installations pointing to the same NFS filesystem. Any knowledge/experience/link/clue on this would be greatly appreciated. Thanks in advance, Daniel Campos

4 4

[Dovecot] deliver panics when handling mails bigger than some kByte
by Leon Meßner 19 Dec '09

19 Dec '09

Hi, i've just upgraded to dovecot-1.2.8 (from 1.2.4) and do now get the following errors when deliver gets hands on mails with some attachments. # tail -n 1 /var/log/messages Dec 14 19:00:36 mail3 dovecot: deliver(user): Panic: file istream.c: line 96 (i_stream_read): assertion failed: (stream->eof) The MTA is postfix running inside a FreeBSD 7.2-STABLE jail. The homes where deliver should put mails are mounted via NFS. As it works with small attachments perhaps this is related to the message size. However i don't get the "stale NFS file handle" error any more which i did under 1.2.4 (See thread that begins with: Message-ID: <20091016122519.GC6309(a)emmi.physik-pool.tu-berlin.de> ) Greetings, Leon

2 2

[Dovecot] "Filename keeps changing" issue
by Paul Ezvan 19 Dec '09

19 Dec '09

Hello, I have been experiencing a issue for a while with dovecot 1.2.8 : Dec 4 12:54:00 gen1 dovecot: IMAP(paul): maildir_file_do(/home/paul/Maildir/.Travail.Linux.Arch Linux/cur/1224250603.M73770P8724.gen0:2,): Filename keeps changing Dec 4 12:54:01 gen1 dovecot: IMAP(paul): Disconnected: Internal error occurred. Refer to server log for more information. [2009-12-04 12:53:59] bytes=4445/26986 So I can't get the messages in this directory neither with Evolution neither with Horde neither with Squirrelmail, but it works with roundcubemail. How can I debug this ? dovecot -n # 1.2.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31-ARCH i686 protocols: imap imaps pop3 pop3s managesieve ssl_cert_file: /etc/ssl/certs/ezvan.fr.pem ssl_key_file: /etc/ssl/private/ezvan.fr.key login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login login_process_per_connection: no mail_location: maildir:~/Maildir mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_process_size: 0 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): imap_client_workarounds(managesieve): lda: postmaster_address: postmaster(a)ezvan.fr mail_plugins: sieve sieve_global_path: /var/sieve/global auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 plugin: sieve: ~/.dovecot.sieve sieve_storage: ~/sieve Thanks for help ! Paul Ezvan

6 11

[Dovecot] dovecot: pipe() failed: Too many open files
by JW 19 Dec '09

19 Dec '09

In the past few months we've been having increasing problems with dovecot timing out pop3 logins. As best I can tell it gets to the point where it won't accept any new pop3 logins. The error in the mail log is: dovecot: pipe() failed: Too many open files I've researched this problem a number of times, usually I see suggestions to increase ulimit. I've done this a number of times, all the way up to: ulimit -n 8192 I've put that in the init script right above the daemon start line. So far it hasn't helped. In addition, when looking at lsof, it doesn't seem like we're anywhere near the actual limit. for example, last time dovecot only had 1032 files open. Does anyone have any idea what could be causing the error? Or what else I can try to figure this out? Thank you, JW -- ---------------------- System Administrator - Cedar Creek Software http://www.cedarcreeksoftware.com

5 7

[Dovecot] Release candidates for Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.8
by Stephan Bosch 19 Dec '09

19 Dec '09

Hello Dovecot users, I am getting closer to new releases for Sieve and ManageSieve for Dovecot v1.2.8. However, the release for Sieve includes a large restructuring of the sources to improve extension handling and to remove global state. That is why I first provide a few pre-releases for you to check first: Sieve http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14pre.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14pre.tar.gz.sig ManageSieve http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10pre.tar.… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10pre.tar.… Check the NEWS files in the respective repositories for other changes included in these releases: http://hg.rename-it.nl/dovecot-1.2-sieve/file/216f58aae5c1/NEWS http://hg.rename-it.nl/dovecot-1.2-managesieve/file/a44ca0d89875/NEWS Feel free to test these release candidates and please notify me when you incur any problems. The real releases will follow this weekend. Regards, -- Stephan Bosch stephan(a)rename-it.nl

3 5

[Dovecot] Maildir on NFS - attribute caching question
by Brandon Davidson 18 Dec '09

18 Dec '09

Hi Timo, We've been running Dovecot with Maildir on NFS for quite a while - since back in the 1.0 days I believe. I'm somewhat new here. Anyway... The Wiki article on NFS states that 1.1 and newer will flush attribute caches if necessary with mail_nfs_storage=yes. We're running 1.2.8 with that set, as well as mail_nfs_index=yes, mmap_disable=yes and fsync_disable=no. We have a pool of POP/IMAP and SMTP machines that are accessing the maildirs, and can't guarantee any sort of user session affinity to a particular host. We also mount our NFS shares with 'noac', which is what I'm writing to ask about. I'd like to stop doing that for performance reasons. Do you see any issues with taking that out of the mount options, given our environment? Thanks, -Brad

2 1

[Dovecot] lot's of timeouts
by Götz Reinicke - IT-Koordinator 18 Dec '09

18 Dec '09

Hi, since some time ago we do have a lot of "timeouts" connecting to our imap/po3 server. This week I switched the whole system to a new dual quadcore xeon, 24GB RAM, SAS2 RAID-10. (SUN Fire 4170) But the mailclients (mostly thunderbird and apple mail) still reporte the timeouts by accessing the mailboxes. The server is doing smtp, imap/pop3, webmailsystem and spam/antivirus-checking all together. (RH EL 5, sendmail, horde, mysql, mailscanner, spamassassin) We use the original RH dovecot-1.0.7, mbox-format and mailboxes up to 4 GB ... (historicaly grown ...) So where to start debugging the imap/pop3 timeouts? What information may I provide, which doc may I read? Thanks for helping me to find and fix the problem. Best regards Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 420 Fax +49 7141 969 55 420 E-Mail goetz.reinicke(a)filmakademie.de Filmakademie Baden-Württemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzende des Aufsichtsrats: Prof. Dr. Claudia Hübner Staatsrätin für Demographischen Wandel und für Senioren im Staatsministerium Geschäftsführer: Prof. Thomas Schadt

2 4

[Dovecot] v2.0.beta1 released
by Timo Sirainen 18 Dec '09

18 Dec '09

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig Now that v2.0 is in beta stage I don't expect anything big to change anymore. The configuration and the APIs shouldn't change in non-backwards compatible ways. There are still bugs left to be fixed and some small features to be implemented, but I'd like to have people start testing it more. The biggest unimplemented "feature" is how to convert v1.x configuration easily/automatically to v2.0. Either the old config file should be translated to new one, or Dovecot should be able to read the old config file as-is. I think I like the translation better, so that people won't still be using v1.x configuration when v2.1 arrives and drops v1.x support. Largest changes since alpha3: - if some IP address is failing authentications, all auth attempts from the IP are delayed increasingly. a successful auth drops the delay. max delay is 15 seconds. this is enforced by auth process, so it works across different connections/processes/protocols. - lib-storage plugin API changed. processes handling multiple users now support different plugins for different users. - expire plugin's settings work a bit differently now: http://hg.dovecot.org/dovecot-2.0/rev/46691becc45e - post-login scripting works again, see http://dovecot.org/list/dovecot/2009-December/045139.html - Tons of fixes

7 20