similar to: v1.1.beta14 released

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

On Jan 20, 2008, at 12:15 PM, dovecot-request at dovecot.org wrote: > > Message: 5 > Date: Sun, 20 Jan 2008 15:48:09 +0200 > From: Timo Sirainen <tss at iki.fi> > Subject: [Dovecot] v1.1.beta14 released > To: dovecot at dovecot.org > Message-ID: <1200836889.12450.99.camel at hurina> > Content-Type: text/plain; charset="us-ascii" > >

Hi, I'm testing dovecot 1.1.beta14 on two debian etch with drbd+ocfs2[active/active], I use qmail+vpopmail(userdb) and three front-end with openbsd 4.2 with dovecot 1.1.beta14 as proxy with passdb sql through vpopmail database. Is posible to add logs into vpopmail.vlog from proxys?, like "update vlog blah blah..." or in other sql database? I tried with post login scripting but I

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta13.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta13.tar.gz.sig Changes since beta12: - Half of LDAP code was rewritten to fix reconnect/queuing problems. I did test that the new code works with and without auth binds, but be careful. - \Recent flags should finally work correctly with maildir. - last_used field wasn't

I've been glancing at the hg changelogs, watching a number of basic fixes going in, including squat and uidlist fixes. Are there any plans for a beta14 release soon to increase exposure to these fixes, or is it in flux too much? My time lately to spend on dovecot has been sparse but I can definitely afford the time right now to roll betas into service because it is convenient. I have some

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 :::*

All betas so far have compiled without problems on my setup, but something breaks in b13. This problem occurs with both make and gmake. Below are outputs from make and gmake. Regards, Mikkel make all-recursive Making all in src Making all in lib make all-am if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/opt/pkgsrc/pkg/include/mysql -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes

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

My production DC machine owns the mail filesystems and is running DC V1.0.15 and mbox folder format. I am looking to test V1.1.3 on another machine, which NFS mounts the mail filesystems, but has its own local index FS. I have made this test environment my default connection in TBird, and it seems to work just fine. Also, I have made sure that my TBird client isn't connecting to the

In the past I dabbled with the imap quota plugin with the fs backend because I wanted to report usage to my users (not limit them). At the time, the quota plugin would make dovecot crash when trying to write to a folder (I can bring up this report if needed). However, in a later beta of dovecot 1.1 I tried quota again but I cannot get it to report any results. I've been wanting to use

Hi, Thank you for pointing me about -xc99 flag, I have compiled and installed dovecot inplace of version 1.0.5 without any special actions on the upgrade. And after starting it immediately got in it's log file messages like: --- dovecot: Oct 16 23:10:18 Error: IMAP(seriv): file_set_size() failed with index cache file /var/spool/imap/seriv/.imap/.git-altlinux-ru/dovecot.index.cache: Invalid

Hi, on a clustered Dovecot server installation that was recently moved from a shared GPFS filesystem to GFS2, occasional corruptions in the users' INBOXes started appearing, where a new incoming message would be appended directly after a block of NUL bytes, and be scanned by dovecot as being glued to the preceding message. I traced this to the file extension operation performed in

Is there anything that can be done so that when users IMAP to their inbox and have reached their filesystem quota, that they can still DELETE their mail? They can login, but when they go to delete/expunge this is the error I get in syslog. I have tried mail_read_mmaped to yes and no, and same result. Mar 25 14:54:27 penguin1 imap(bob): file_set_size() failed with index data file

Hi, Can sameone explain me why my logs are full of such errors: Jul 11 12:07:32 mxhost deliver(user1): pwrite() failed: File too large Jul 11 12:07:32 mxhost deliver(user1): file_set_size() failed with index cache file /mail/user1/Maildir/.parser/dovecot.index.cache: File too large mxhost# ls -lh /mail/user1/Maildir/.parser/dovecot.index.cache -rw------- 1 user1 emails 64M Jul 11 10:01

I hope this ml is the right place to send this... Anyway, I'd very much like for the MySQL backend to call mysql_options, so that it'll read the settings defined in MySQL's my.cnf under the [client] section. This allows to set a whole slew of MySQL specific settings for the MySQL connection, for example to enable the compressed protocol, set charsets, enable SSL client verification,

I feel like I'm going totally crazy. Is it just me, or have embedded From_ lines really been breaking mbox messages since (at least) dovecot 1.0? I found a whole lot of broken messages in an old mailbox of mine and when I looked closer at it, it seemed like Dovecot was ignoring the Content-Length header and truncating the messages at the first embedded From_ line instead. Figuring

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, --

I noticed these happen when one of my users searches his Trash folder which he doesn't empty. He uses thunderbird and it is reproducable. Feb 5 22:47:39 boomhauer dovecot: IMAP(username): file message-header-parser.c: line 350 (message_parse_header_next): assertion failed: +(IS_LWSP(line->value[0])) Feb 5 22:47:41 boomhauer dovecot: child 8022 (imap) killed with signal 6 Feb 5

On Sat, 23 May 1998, Torkil Zachariassen wrote: > >I have browsed various versions of libc and found a handful of weak points > >where the value of an enviroment variable is trusted more than necessary. > [1] > Could you explain to programming novices on linux-security - people like > myself 8) - hwo this could affect security on a firewall (proxy and/or > IP-router,

Hello Rowland Yes i have a timeserver and time in correct and in sync with the client und server. named.conf ---------- include "/etc/bind/named.conf.options"; include "/etc/bind/named.conf.local"; include "/etc/bind/named.conf.default-zones"; # samba include "/etc/bind/named.conf.samba"; // logging logging { channel default_file { file