similar to: v1.1.beta13 released

Timo, Running v1.1.1 on OS X. What is dovecot trying to tell me here? Jun 24 15:03:50 G518X2 dovecot: IMAP(jjohnson): Sort IDs 4 broken in mailbox INBOX, reseting Thank you! G518X2:~ root# dovecot -n # 1.1.1: /usr/local/etc/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 768). Either grow the limit or change login_max_processes_count

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta12.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta12.tar.gz.sig Still not a release candidate, maybe the next one.. This release fixes a lot of bugs and adds some new sanity checks. Fixes quite a lot of mbox problems. v1.1.beta11 (no other versions) had a potential security hole where memory was free()d multiple times. \Recent

Hi, I continue testing the beta versions and have seen a great improvement over the last few ones. On beta13 I'm seeing the following assert on some client folders: file index-mail.c: line 759 (index_mail_stream_destroy_callback): assertion failed: (mail->data.destroying_stream) If you need I can try and reproduce this in a more controled environment to pinpoint the problem. Thanks, --

Dear Spencer and Prof. Fox, Thank you for your replies. I'll very appreciate, if you have any ideas concerning the problem described below. First, I'd like to describe the model in brief. In general I consider a model with three equations. First one is for annual GRP growth - in general it looks like: 1) GRP growth per capita = G(investment, migration, initial GRP per

Version: dovecot --version: 1.0.0 OS: OS X - 10.4.9 Architecture: G5 Dual/1.8Ghz Had a fairly normal time correction last night: May 9 20:56:56 G518X2 ntpd[219]: time set -1.212733 s Which dovecot duly noted: May 9 20:56:56 G518X2 dovecot: auth(default): Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. This morning all of the dovecot processes are

Hi, dovecot-sieve-1.1.2 + dovecot-1.1.beta13 segfaults with the following sieve filter: --- require ["imapflags"]; if header :contains "subject" ["test"] { addflag "$testflag"; } --- when a message with a subject containing "test" is delivered via dovecot lda. The fault backtrace is: (gdb) run Starting

Hi, I'm having a really really strange problem. After upgrading from 1.1.beta13 to 1.1.rc2 (happened with rc1 as well IIRC) I can't connect to the services using IPv4 anymore. dovecot happily binds to the IPv6 wildcard socket which should accept IPv4 connections as well. root at vs02:~# netstat -lnp --tcp | grep dovecot tcp6 0 0 :::993 :::*

Hi, I patched dovecot-1.1.beta14 to compile under gcc 2.95. __builtin_expect and __attribute__((malloc)) are only available since gcc 3.0, and __builtin_types_compatible_p since 3.1. Also the flexible array members (char a[]) are not available for gcc 2.95. So I replaced them with zero-extent arrays (char a[0]), which should also work, but that is gcc specific. A general pointer (char* a) should

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz.sig Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. There are no release critical bugs left and no known crash bugs.

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz.sig Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. There are no release critical bugs left and no known crash bugs.

Read this in the dovecot sieve wiki: "The envelope sender is taken from a Return-Path: header in the message. The envelope recipient is taken from -d option passed to deliver." Is "-d" still a valid deliver switch? When I configure postfix's main.cf like so... mailbox_command = /usr/local/libexec/dovecot/deliver -d -e ..it sqwaks with, "Jun 18 18:44:50

Hello, v1.1.beta12 deliver crashes: Dec 22 11:05:29 iserver deliver(tests2): file index-mail.c: line 1042 (index_mail_close): assertion failed: (!mail->data.destroying_stream) Dec 22 11:05:29 iserver deliver(tests2): Raw backtrace: /usr/local/dovecot/libexec/dovecot/deliver(i_syslog_fatal_handler+0x2c) [0x80baa8c] -> /usr/local/do vecot/libexec/dovecot/deliver [0x80ba88b] ->

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.

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta14.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta14.tar.gz.sig School has started since beta13 release and I've been a bit busy with it and trying to get my sleeping times fixed (0-2h sleep doesn't seem to be enough). My interest in algorithms has also grown a bit recently. I'm thinking about majoring in CS /

Dear All, We would like to migrate our existing courier to dovecot. After reading document on website and doing some tests, here are some issues we met. 1. According the the wiki, it seems to imply that once migrating from courier to dovecot, pop3 users may "lost/forget" their download "index/ history" which cause them to download again old mails that are kept on

Hello list, I am trying to set up a public mailbox for users to put spam in so that sa-learn can do its job at night. Only I can't seem to fully understand how and which permissions should be set. I've read [1] and am using Dovecot 1.0.1. First some background information: I do not host or care (at the moment) about virtual users or virtual mail hosting. All users have Unix system

Helo all, I'm trying to use Dovecot v1.1.beta13 lda with ldap. I made a tons of change in configurations but still can't set quota from ldap. See below: Log: Jan 16 17:37:09 mailserver-03 dovecot: auth(default): userdb(teste at xxx.com.br,127.0.0.1): Invalid GID value '*:bytes=1033' dovecot-ldap.conf: user_attrs =

After V1.2 had been up for a while, I started seeing tons of syslog error messages like this: Nov 5 09:11:52 mercury mail:err|error dovecot: IMAP(sdean): stat(/var/dcindx/sdean/.imap/DadEstate) failed: Permission denied (euid=202(sdean) egid=200(hcrc) missing +x perm: /var/dcindx) Ownernship and Permissions are: The index filesystem 2726 root at mercury:/var/dcindx ## ls -ald drwx--S---

http://dovecot.org/releases/1.0/dovecot-1.0.10.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.10.tar.gz.sig v1.0.8 and v1.0.9 were a bit bad releases. Hopefully one day I've managed to have written a proper test suite which can be run before doing any releases.. * Security hole with LDAP+auth cache: If base setting contained %variables they weren't included in auth cache key,

http://dovecot.org/releases/1.0/dovecot-1.0.10.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.10.tar.gz.sig v1.0.8 and v1.0.9 were a bit bad releases. Hopefully one day I've managed to have written a proper test suite which can be run before doing any releases.. * Security hole with LDAP+auth cache: If base setting contained %variables they weren't included in auth cache key,