- dovecot - dovecot.org

[Dovecot] Monitorize concurrent sessions
by Jordi Espasa Clofent 10 Aug '07

10 Aug '07

Hi all, ¿Is there some way/method to monitorize and see what users are working at same time? Thanks.

1 0

[Dovecot] dovecot: child 1690 (auth-worker) killed with signal 11
by Thomas Zajic 10 Aug '07

10 Aug '07

Hi there, I've been seeing this for quite a while now, but only today finally got off my lazy you-know-what and did a backtrace. Here's the requested info as per http://dovecot.org/bugreport.html: * Dovecot version [root@airframe]:~# dovecot --version 1.0.3 * Operating system or Linux distribution name Slackware 10.2, both kernel 2.6.21.3 and dovecot self-compiled * CPU architecture (x86 or something else?) x86 (AMD Athlon XP 3200+) * Filesystem you used (especially if you use NFS or not) ext3, local (no NFS) * Some kind of description of what you were doing and with what IMAP client. Thunderbird 2.0.0.4 (also happened with earlier versions) mail-notification-4.1 (" " " " " ) * If the problem can be reproduced, it helps a lot if you can tell how. Happens in almost regular intervals, not sure when exactly though. Usually when doing something in TB again (deleting or moving mails) after it has been sitting idling for a while. From the log files going back to July 22nd: [root@airframe]:~# grep "dovecot: child .* (auth-worker) killed with signal 11" /var/log/maillog* | wc -l 258 TB is configured to use TLS and secure authentication, use IDLE, and 5 cached server connections. Mail Notification is configured to use TLS, and to autodetect both the authentication mechanism and IDLE availability. * Dovecot configuration with dovecot -n [root@airframe]:~# dovecot -n # 1.0.3: /usr/local/etc/dovecot.conf login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting_capability: yes verbose_proctitle: yes mail_location: maildir:/home/%u/Maildir:INBOX=/home/%u/Maildir/.INBOX mail_debug: yes fsync_disable: yes maildir_copy_with_hardlinks: yes mail_drop_priv_before_exec: yes auth default: mechanisms: plain digest-md5 cram-md5 debug: yes passdb: driver: shadow args: blocking=yes passdb: driver: passwd-file args: /usr/local/etc/dovecot-passwd userdb: driver: passwd args: blocking=yes * Backtrace [root@airframe]:~# gdb /usr/local/libexec/dovecot/dovecot-auth /usr/local/stow/dovecot-data/var/run/dovecot/core GNU gdb 6.3 [...] Core was generated by `dovecot-auth -w'. Program terminated with signal 11, Segmentation fault. [...] (gdb) bt full #0 0x00000000 in ?? () No symbol table info available. #1 0x08056954 in auth_worker_handle_passl (client=0x8089e18, id=3, args=0x808a082 "user=zlatko-mail\tservice=IMAP\tlip=192.168.1.3\trip=192.168.1.1\tsecured=1") at auth-worker-client.c:242 auth_request = (struct auth_request *) 0x808a3f0 credentials_str = 0x2 <Address 0x2 out of bounds> #2 0x08056c15 in auth_worker_handle_line (client=0x8089e18, line=0x808a078 "PASSL\t1\t2\tuser=zlatko-mail\tservice=IMAP\tlip=192.168.1.3\trip=192.168.1.1\tsecured=1") at auth-worker-client.c:326 id = 3 #3 0x08056ca7 in auth_worker_input (context=0x8085ac8) at auth-worker-client.c:359 client = (struct auth_worker_client *) 0x8089e18 line = 0x808a076 "3\tPASSL\t1\t2\tuser=zlatko-mail\tservice=IMAP\tlip=192.168.1.3\trip=192.168.1.1\tsecured=1" ret = 118 #4 0x0806b841 in io_loop_handler_run (ioloop=0x80851a8) at ioloop-poll.c:199 ctx = (struct ioloop_handler_context *) 0x80851d0 pollfd = (struct pollfd *) 0x80851f0 tv = {tv_sec = 1, tv_usec = 999620} io = (struct io *) 0x8089f88 t_id = 2 msecs = 134765256 ret = 0 call = true #5 0x0806ae89 in io_loop_run (ioloop=0x80851a8) at ioloop.c:329 No locals. #6 0x0805a04b in main (argc=2, argv=0xbfa36e98) at main.c:321 foreground = false (gdb) Please let me know if you need any additional info (log snippets, etc.). Thanks, Thomas -- =-------------------------------------------------------------------------= - Thomas "ZlatkO" Zajic <zlatko(a)gmx.at> Linux-2.6.21 & Thunderbird-2.0 - - "It is not easy to cut through a human head with a hacksaw." (M. C.) - =-------------------------------------------------------------------------=

2 3

[Dovecot] Version 1.1 Alpha 2 Various Stuff
by Jerry Yeager 09 Aug '07

09 Aug '07

Some preamble information… OS X 10.4.10 (all updates) Power Mac Dual G5, 2.0 Postfix with Dovecot SASL, Dovecot LDA, Dovecot imaps (openssl) Mail clients Apple Mail v 2.1 SquirrelMail v 1.4.10a Thunderbird v 2.0.0.6 Mulberry v 4.06 For various versions of Dovecot, from 0.9m up through 1.0.3 things went well, no memorable big problems, with one exception: Mulberry v 4.0.8 would/will not work; i.e. it refuse(d) to connect saying it could not start SSL to begin the connection. Dropped back to version 4.0.6. I switched to version 1.1 alpha 2 (compile and configuration information is attached at the end of this message) 1) Started up Apple mail. Mail boxes disappeared in Apple Mail's list, except for the main Inbox mail box. Fixed by setting mailbox_list_index_disable = yes in the Dovecot.conf file, restarted both Dovecot and Mail, all the mailboxes reappeared and worked correctly. 2) Started up Squirrel Mail using several different browsers. No problems. 3) Started up Thunderbird. No problems. 4) Started up Mulberry. It partially connected, but stopped with the error saying that it had hit the limit for maximum connections. Mail logs show: dovecot: imap-login: Maximum number of connections exceeded: user=<username>, method=PLAIN, rip=192.168.1.1, lip=192.168.1.50, TLS I tried increasing the various limits in the Dovecot.conf file up through a maximum limit of 2048 connections, to no avail. Mulberry will initially connect to several of the mailboxes, but will stop without getting all of them and will throw up the 'over the connection limit' error and will then show you a dialog box that asks you to log-in. Attempting to doing so returns a fatal error 54. I have not tried Mulberry's version 4.0.8. 5) Mail logs had this message suddenly begin appearing: auth-worker(default): pam(username,192.168.1.1): pam_authenticate() failed: Authentication failure Fixed by completely commenting PAM authentication section out; It was: passdb pam { # [blocking=yes] [session=yes] [setcred=yes] # [cache_key=<key>] [<service name>] # ... essentially a placeholder section, since everything inside is commented out # # } now is: #passdb pam { # # ... even the outer block is commented out # #} The error has now disappeared from the logs. Dovecot was build using: CPPFLAGS=-I/usr/local/include/openssl LDFLAGS='-L/usr/local/lib -R/ usr/local/lib' \ ./configure \ --with-ssl=openssl \ --with-libiconv-prefix=/usr/local Dovecot.conf: # 1.1.alpha2: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imaps ssl_listen: *:993 ssl_parameters_regenerate: 24 ssl_cipher_list: ALL:!LOW:!SSLv2 verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: Dovecot login_greeting: Hello, Dovecot is ready. valid_chroot_dirs: /var/mail/vmail/ mail_extra_groups: mail mail_location: maildir:/var/spool/vmail/%d/%n:INDEX=/var/spool/vmail/% d/%n:INBOX=/var/spool/vmail/%d/%n mail_debug: yes mailbox_list_index_disable: yes lock_method: flock imap_client_workarounds: delay-newmail auth default: mechanisms: plain login passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/users socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /usr/local/var/run/dovecot/auth-master mode: 384 user: virtual group: virtual

2 2

[Dovecot] Crash with 1.1alpha2 when lazy_expunge is enabled?
by Rich at Whidbey Telecom 09 Aug '07

09 Aug '07

I'm seeing a crash in 1.1alpha2 when trying to expunge a folder when "lazy_expunge" is enabled: namespace private { separator = . prefix = .EXPUNGED/ location = maildir:/mailstore/%u/Expunged hidden = yes } ... lazy_expunge = .EXPUNGED/ .EXPUNGED/ .EXPUNGED/ Commenting out "lazy_expunge" prevents the crash and mail is expunged. It happens with and without ACL's. Attached is the log output. The messages never actually get moved to the "Expunged" directory, but there is a "temp" file created each time: /mailstore/testuser/Expunged/ drwx------ 6 testuser users 4096 Aug 9 11:39 . drwxr-xr-x 4 testuser users 4096 Aug 9 10:59 .. drwx------ 2 testuser users 4096 Aug 9 10:59 cur -rw------- 1 testuser users 24 Aug 9 11:39 dovecot.list.index.log -rw------- 1 testuser users 28 Aug 9 11:39 dovecot.list.index.uidmap drwx------ 5 testuser users 4096 Aug 9 11:02 .Junk -rw------- 1 testuser users 0 Aug 9 10:59 maildirfolder drwx------ 2 testuser users 4096 Aug 9 10:59 new -rw------- 1 testuser users 0 Aug 9 11:04 temp.mail4.whidbey.net.8596.7b344a891b2c6691 -rw------- 1 testuser users 0 Aug 9 11:32 temp.mail4.whidbey.net.8761.bfe04f5457e4ba7e -rw------- 1 testuser users 0 Aug 9 11:33 temp.mail4.whidbey.net.8765.44e803d87275348a -rw------- 1 testuser users 0 Aug 9 11:37 temp.mail4.whidbey.net.9031.f4a972591af59e05 -rw------- 1 testuser users 0 Aug 9 11:39 temp.mail4.whidbey.net.9125.d67b160254a01631 drwx------ 2 testuser users 4096 Aug 9 10:59 tmp Lazy expunge works on our production 1.0.0 systems. Anyone else seen this? Rich dovecot: Aug 09 11:04:25 Info: imap-login: Login: user=<testuser>, method=PLAIN, rip=209.166.64.35, lip=172.16.125.4 dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Loading modules from directory: /usr/local/lib/dovecot/imap dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Module loaded: /usr/local/lib/dovecot/imap/lib01_acl_plugin.so dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Module loaded: /usr/local/lib/dovecot/imap/lib02_lazy_expunge_plugin.so dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Module loaded: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Module loaded: /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Effective uid=40308, gid=100, home=/var/mail/testuser dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Quota rule: root=storage=102400 mailbox= storage=256000kB messages=0 dovecot: Aug 09 11:04:25 Info: IMAP(testuser): Namespace: type=private, prefix=, sep=., inbox=yes, hidden=no, list=yes dovecot: Aug 09 11:04:25 Info: IMAP(testuser): maildir: data=/mailstore/testuser/Maildir:INDEX=MEMORY dovecot: Aug 09 11:04:25 Info: IMAP(testuser): maildir++: root=/mailstore/testuser/Maildir, index=, control=, inbox=/mailstore/testuser/Maildir dovecot: Aug 09 11:04:25 Info: IMAP(testuser): acl: initializing backend with data: vfile:/adminstore/configs/dovecot-acls:cache_secs=600 dovecot: Aug 09 11:04:25 Error: IMAP(testuser): Sending log messages too fast, throttling.. dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: acl username = testuser dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: owner = 1 dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl vfile: Global ACL directory: /adminstore/configs/dovecot-acls dovecot: Aug 09 11:04:26 Info: IMAP(testuser): Namespace: type=private, prefix=.EXPUNGED/, sep=., inbox=no, hidden=yes, list=no dovecot: Aug 09 11:04:26 Info: IMAP(testuser): maildir: data=/mailstore/testuser/Expunged:INDEX=MEMORY dovecot: Aug 09 11:04:26 Info: IMAP(testuser): maildir++: root=/mailstore/testuser/Expunged, index=, control=, inbox=/mailstore/testuser/Expunged dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: initializing backend with data: vfile:/adminstore/configs/dovecot-acls:cache_secs=600 dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: acl username = testuser dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl: owner = 1 dovecot: Aug 09 11:04:26 Info: IMAP(testuser): acl vfile: Global ACL directory: /adminstore/configs/dovecot-acls dovecot: Aug 09 11:04:28 Info: IMAP(testuser): acl vfile: reading file /adminstore/configs/dovecot-acls/Junk dovecot: Aug 09 11:04:28 Info: IMAP(testuser): acl vfile: file /mailstore/testuser/Maildir/.Junk/dovecot-acl not found dovecot: Aug 09 11:04:41 Info: IMAP(testuser): acl vfile: reading file /adminstore/configs/dovecot-acls/Junk dovecot: Aug 09 11:04:41 Info: IMAP(testuser): acl vfile: file /mailstore/testuser/Expunged/.Junk/dovecot-acl not found dovecot: Aug 09 11:04:41 Error: IMAP(testuser): file mailbox-list-maildir.c: line 161 (maildir_list_get_path): assertion failed: (mailbox_list_is_valid_existing_name(_list, name)) dovecot: Aug 09 11:04:41 Error: IMAP(testuser): Raw backtrace: imap [0x80c5df1] -> imap [0x80c5d0c] -> imap [0x806ba2d] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0x46cfab] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_object_init_from_name+0x1d) [0x46b93d] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_backend_vfile_acllist_rebuild+0x1c7) [0x46d627] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_backend_vfile_acllist_refresh+0x1fd) [0x46db5d] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_backend_vfile_acllist_verify+0x1f) [0x46dcdf] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0x46cf13] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_object_have_right+0x2d) [0x46bc6d] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so(acl_storage_rights_ctx_have_right+0x5a) [0x4703aa] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0x470466] -> /usr/local/lib/dovecot/imap/lib01_acl_plugin.so [0x4707d8] -> /usr/local/lib/dovecot/imap/lib02_lazy_expunge_plugin.so [0xf5ad3a] -> /usr/local/lib/dovecot/imap/lib10_q dovecot: Aug 09 11:04:41 Error: IMAP(testuser): uota_plugin.so [0x51b92a] -> imap(mailbox_open+0x46) [0x80b6ff6] -> /usr/local/lib/dovecot/imap/lib02_lazy_expunge_plugin.so [0xf5b092] -> /usr/local/lib/dovecot/imap/lib10_quota_plugin.so [0x51b0e8] -> imap(imap_expunge+0xb4) [0x8060034] -> imap(cmd_expunge+0x43) [0x805a4d3] -> imap [0x805e649] -> imap [0x805e6e3] -> imap(_client_input+0x65) [0x805ecb5] -> imap(io_loop_handler_run+0x10f) [0x80cba3f] -> imap(io_loop_run+0x28) [0x80cb3a8] -> imap(main+0x4ec) [0x806637c] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x707dec] -> imap [0x8058e41] dovecot: Aug 09 11:04:41 Error: child 8596 (imap) killed with signal 6

1 0

[Dovecot] UW-IMAP style mbox snarfing from /var/mail/ to ~/mbox
by Timo Sirainen 09 Aug '07

09 Aug '07

http://dovecot.org/patches/mbox-snarf-plugin.c Also committed to CVS HEAD. Usage: mail_location = mbox:~/mail:INBOX=/var/mail/%u protocol imap { mail_plugins = mbox_snarf } protocol pop3 { mail_plugins = mbox_snarf } plugin { mbox_snarf = ~/mbox } If ~/mbox doesn't exist, nothing special is done. If ~/mbox exists, it's treated as INBOX and mails are moved from /var/mail/%u whenever the mailbox is synchronized. If all the messages couldn't be copied, for example because of out of quota, then none of the messages are copied. I suppose that could be a problem. It might be possible to fix that by changing: if (mailbox_copy(dest_trans, mail, 0, NULL, NULL) < 0) { if (!mail->expunged) { ret = -1; break; } } to just: if (mailbox_copy(dest_trans, mail, 0, NULL, NULL) < 0) { if (!mail->expunged) break; } But I'm not sure about that. Try and tell me. :)

2 18

Re: [Dovecot] assertion failed with KMail 3.5.6 and dovecot 1.0.0
by Timo Sirainen 09 Aug '07

09 Aug '07

On Mon, 2007-07-30 at 15:07 +0200, Sylvain Joyeux wrote: > > > IMAP(doudou): file ostream-crlf.c: line 339 (_send_istream): assertion > > > failed: ((size_t)ret <= iov.iov_len) > > Hmm. Can you get Dovecot to dump a core file? > > Probably easiest way to get this fixed would be then if you sent me > > the core file and also the imap binary and I'll debug it further. Or > > I could also send you several gdb commands you could run. > > Here are the imap executable and core dump files (compressed). They are > generated on a powerpc machine, so I'm not sure it will be useful to you. > Moreover, Debian strips its executables, so no line numbers ... Debugging information would have been really useful, but I did fix one bug and added some more asserts: http://hg.dovecot.org/dovecot-1.0/rev/bd113e9fe67b If it still wasn't fixed, maybe with this change it gives another assert.

1 0

[Dovecot] Outlook 2000/2003 frequent disconnect issue
by Jeff Ramsey 09 Aug '07

09 Aug '07

I have been using Dovecot for an IMAP server for a few years now, with no hitch. Even using Outlook 2K/2K3 as a client. Yesterday, I had a user experience the 'Negative UIDs' issue spoken of here: http://wiki.dovecot.org/Clients/NegativeUIDs I performed all of the steps mentioned in this article, and it seemed like it would work properly the first time the user checked their email, and then after that, they would get this error again. I checked to see what the latest stable version of Dovecot was, and decided to upgrade. I was at 0.99.11-8 and the latest stable rpm for my distro was 1.0.2-2. The upgrade went fine. Or so I thought. I am now getting the following message on all Outlook Clients: "Your IMAP Server closed the connection....this can occur if the connection is idle for too long" I have scoured the Internet for this error and have come up with many suggestions, none of which have worked. I have increased Outlook's timeout period to the full 10 minutes, and I have disabled SELinux. None of this seems to have worked. Is there anyone out there who has actually had this issue and resolved it? Can you please help? Thanks, Jeff Ramsey MIS Administrator TMI Forest Products, Inc. jefframsey(a)tubafor.com 360.477.0738 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

4 12

[Dovecot] Database server failure causes endless loop
by Andy Shellam 09 Aug '07

09 Aug '07

Hi, I've just started setting up Dovecot 1.0.1, and made an error in my configuration, which I think has found a potential problem in Dovecot. I'm using PostgreSQL authentication, and set the database host to "localhost", which PostgreSQL doesn't listen on, so libpq is throwing the standard "is the server running?" message. The problem, however, is Dovecot isn't seeming to understand this, and is endlessly looping, trying to query it every 5 seconds. My client (telnet during testing) is simply sitting there waiting for a response, which it's never going to get. After about 5 minutes, Dovecot killed the connection, saying "* BYE Disconnected for inactivity." If this was from an IMAP client, I'm guessing the client would time-out after so long when it doesn't get a response back. Wouldn't it be more sensible for Dovecot to try PostgreSQL, say, 3 times. If unsuccessful, send the client an "internal server error" or something similar? Otherwise if the database server failed, and the client tries to connect, it'd be waiting for at least a minute (or whatever the standard time-out interval is) before failing, whereas it'd be better to see almost instantly if the server's down. Regards, Andy. Log output: dovecot: Jul 01 11:31:03 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:03 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:03 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:08 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:08 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:08 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:13 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:13 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:13 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:18 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:18 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:18 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:23 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:23 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:23 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:28 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:28 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:28 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:33 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:33 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:33 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:38 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:38 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:38 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:43 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:43 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:43 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:48 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:48 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:48 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:53 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:53 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:53 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:31:58 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:31:58 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:31:58 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:03 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:03 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:03 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:08 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:08 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:08 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:13 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:13 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:13 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:18 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:18 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:18 Error: auth(default): TCP/IP connections on port 5432? dovecot: Jul 01 11:32:23 Error: auth(default): pgsql: Connect failed to <database>: could not connect to server: Connection refused dovecot: Jul 01 11:32:23 Error: auth(default): Is the server running on host "localhost" and accepting dovecot: Jul 01 11:32:23 Error: auth(default): TCP/IP connections on port 5432?

2 1

[Dovecot] Moving mboxes around
by tomas＠tuxteam.de 09 Aug '07

09 Aug '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dovecot gurus, I have a couple of questions for which I haven't found answers in the docs (which may be well more a limitation of my capabilities than anything else). Here they go: - Is it OK to move mailboxes around from under Dovecot? Case in point: I'm using procmail to pass incoming mail through bogofilter (the standard recipe mentioned in their manpage, which more or less funnels spam into a "spam" mailbox, unsure into an "unsure" and non-spam into "inbox"). From time to time I'd like to clear the spam and unsure mailboxes, using logrotate. Dovecot seems to cope with it. Am I tempting my luck? - Is there a way to tell an external application when mail has been moved by a client? Again: dovecot+bogofilter: from time to time a client checks incoming, unsure and sometimes spam and decides to move --say-- a mail from unsure to spam (deciding it's spam, after all) or similar. This is of course important for the training of bogofilter, so I'd like to trigger a backend action. I see basically two possibilities: - create two more mailboxes, say "spam-indeed" and "ham-indeed". User is told to move mail into these. Ham-indeed gets re-funneled to inbox (or something like that). Manual and error prone. - Use the mail_log plugin (seems more attractive). I still have (distro-provided) dovecot 0.99.14, but this would be a good reason to upgrade. (I still don't see where I get the source mailbox in the mail_log messages from, but that's details now). You get the idea, I think. Anyway, I am interested in any ways to combine dovecot and bogofilter in the backend in a way that I can route user feedback to the filter without putting too much burden on the user. Ideas? Thanks - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGtuS4Bcgs9XrR2kYRAkiXAJoDJYZC8DYIxFqCw+HEIn0CCNssQwCfaZjh z533XFMH36c4Lemv/+gSn9A= =s87z -----END PGP SIGNATURE-----

2 2

[Dovecot] dotlock file was deleted error
by Joe Wong 09 Aug '07

09 Aug '07

Hello, under what situation the error: dovecot-uidlist.lock was deleted (kept it 0 seconds ) will happen? I saw quite some of these in dovecot log. Thanks, - Joe

4 6