search for: 1.1rc5

This happened from one user near noon on the 17th and 19th (today) of this month. From the backtrace it looks like they were searching, but I won't know for sure unless I need to ask them. Is this possibly fixed already? I just haven't upgraded dovecot in a while due to lack of problems. The sig11 happened a few dozen times, a few seconds apart each day. I have one coredump from

Hi, I do hope this hasn't been covered. I googled and looked in the archives but didn't see anything related, so hopefully I am not covering old ground. I recently upgraded from 1.0.10 to 1.1rc5. I am seeing this error from clients: May 25 11:01:54 finity dovecot: Panic: IMAP(xxx at here.org): file mailbox-tree.c: line 171 (mailbox_tree_iterate_set_next_node): assertion failed:

Not sure about 1.0, I don't run it anymore :) But a few users discovered for a small issue that only affects a very small portion of my userbase where instructional correction will suffice. I guess I am reporting it in the interest of getting it out there, and I can live with it if not fixed but it might be an issue for some people. I'm running through my list of issues. Basically,

Hello List, We just migrated from a PPC Xserve to an Intel Xserve. I used "rsync" to bring everyone's home directories over, and in the back of my mind wondered about how it would handle the binary index files... only one way to find out! :) Once I tried to login to IMAP, I got the following results: May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): Rebuilding index file

Hi All, I just upgraded to the new 1.1rc5 from 1.0 that I had been using and it advised me to increase the file descriptor limit. I'm not sure how to do this. There is a command built into tcsh that allows me to do this called limit, but sudo limit 4224 doesn't work, and usually dovecot is started from the rc.local file if I recall right, and I'm not sure how to set this up from

I'm trying to bring up dovecot on a dual stack machine. I tried search for the answers; the answers I found and tried failed :-(. If I try this: protocol imap { listen = 216.218.228.114:143, [2001:470:1:18::114]:143 ssl_listen = 216.218.228.114:993, [2001:470:1:18::114]:993 } (and similiar for pop3) I get: Fatal: listen: Can't resolve address 216.218.228.114:143,

Hi I have two sieve scripts: # cat /var/vmail/sieve/global require ["include"]; include :global "spam"; include :personal "sieve"; # cat /var/vmail/sieve/spam require "fileinto"; if exists "X-Spam-Flag" { fileinto "Junk"; } # ls -l /var/vmail/sieve/ total 16 -rw-r--r-- 1 mailuser mailgroup 68 2008-05-28 00:40 global -rw------- 1

Hello all, I'm trying to get the expire plugin working, but still having issues even with 1.1RC5. If I run the expire tool I get the following error: server:~# dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool Fatal: setgid(100) failed with euid=2005, gid=0, egid=0: Operation not permitted Same thing with --test: server:~# dovecot --exec-mail ext

I've been having a problem with a crashing Dovecot the last couple of months where it crashes after a couple of weeks of uptime. Been a bit difficult to diagnose. Anyway, we're now running 1.0.9 on a Sun Fire T1000 running Solaris 10. Any good ideas on how to pin-point the problem? - Peter Here's the output from syslog when the last crash happened: May 14 11:46:50 ifm.liu.se