Re: [Dovecot] v1.1.0 released
On Fri, 2008-07-18 at 14:28 +0200, Anders wrote: > Johannes Berg wrote: > > > On Sat, 2008-06-21 at 04:46 +0300, Timo Sirainen wrote: > >> http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz > > > Cool. I guess now I really have to debug why antispam+quota segfaults. > > How is this coming along? Apart from this quota issue, do you consider > antispam stable for Dovecot v1.1? Haven't even had a chance to look at it. It appears to work fine until you have quota and antispam enabled, where it segfaults on new messages, but I don't know why yet. johannes signature.asc Description: This is a digitally signed message part
Re: [Dovecot] v1.1.0 released
Johannes Berg wrote: > On Sat, 2008-06-21 at 04:46 +0300, Timo Sirainen wrote: >> http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz > Cool. I guess now I really have to debug why antispam+quota segfaults. How is this coming along? Apart from this quota issue, do you consider antispam stable for Dovecot v1.1? Cheers, Anders.
Re: [Dovecot] v1.1.0 released
On 6/23/2008, Philipp Kolmann ([EMAIL PROTECTED]) wrote: It fails on random files, since the system is running a few daemons without any problem I'd go for the gcc bug. Actually, failing at random point when compiling is *much* more likely to be a memory error. If the 'few daemons' don't happen to ever hit the bad ram, that would explain why they don't fail. Just try replacing the RAM (RAM is chep nowadays), and see if it fixes the problem. or test with memtest (if x86): I have seen bad memory pass memtest for hours on end, so memtest is not a 100% reliable way to test it. The best almost sure-fire test I have found is compiling something big (like X, or even a kernel)... Again... ram is chep... just replace it and see. -- Best regards, Charles
Re: [Dovecot] v1.1.0 released
Charles Marcus wrote: On 6/23/2008, Luca Corti ([EMAIL PROTECTED]) wrote: It fails on random files, since the system is running a few daemons without any problem I'd go for the gcc bug. Actually, failing at random point when compiling is *much* more likely to be a memory error. If the 'few daemons' don't happen to ever hit the bad ram, that would explain why they don't fail. Just try replacing the RAM (RAM is chep nowadays), and see if it fixes the problem. or test with memtest (if x86): http://www.memtest.org/ hth Philipp
Re: [Dovecot] v1.1.0 released
On 6/23/2008, Luca Corti ([EMAIL PROTECTED]) wrote: It fails on random files, since the system is running a few daemons without any problem I'd go for the gcc bug. Actually, failing at random point when compiling is *much* more likely to be a memory error. If the 'few daemons' don't happen to ever hit the bad ram, that would explain why they don't fail. Just try replacing the RAM (RAM is chep nowadays), and see if it fixes the problem. -- Best regards, Charles
Re: [Dovecot] v1.1.0 released
--On June 21, 2008 6:02:58 AM +0300 Timo Sirainen <[EMAIL PROTECTED]> wrote: Always at the same source file or just somewhat randomly? Either a gcc bug or your memory is broken. It fails on random files, since the system is running a few daemons without any problem I'd go for the gcc bug. $ gcc -v Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.2.4 (Debian 4.2.4-2+b1) ciao Luca
Re: [Dovecot] v1.1.0 released
On Jun 21, 2008, at 9:09 PM, Alex Jurkiewicz wrote: Timo Sirainen wrote: * See doc/wiki/Upgrading.1.1.txt (or for latest changes, http://wiki.dovecot.org/Upgrading/1.1) for list of changes since v1.0 that you should be aware of when upgrading. "By default the number of connections for user from the same IP is limited to 10. You can change this from mail_max_userip_connections setting. " Is this per-user per-IP, or simply per-IP? Per-user per-IP. So it doesn't try to prevent intentional DoS, just accidental DoS. v2.0 will hopefully have both. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] v1.1.0 released
Timo Sirainen wrote: * See doc/wiki/Upgrading.1.1.txt (or for latest changes, http://wiki.dovecot.org/Upgrading/1.1) for list of changes since v1.0 that you should be aware of when upgrading. "By default the number of connections for user from the same IP is limited to 10. You can change this from mail_max_userip_connections setting. " Is this per-user per-IP, or simply per-IP? Cheers, Alex Jurkiewicz
Re: [Dovecot] v1.1.0 released
> gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-sql
> -I../../src/lib-settings -I../../src/lib-ntlm -I../../src/lib-otp
> -DAUTH_MODULE_DIR=\""/usr/local/lib/dovecot/auth"\" -DPKG_LIBEXECDIR=
> \""/usr/local/libexec/dovecot"\"-std=gnu99 -g -O2 -Wall -W
> -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith
> -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2
> -MT auth-master-listener.o -MD -MP -MF .deps/auth-master-listener.Tpo -c
> -o auth-master-listener.o auth-master-listener.c
> make[3]: *** [auth-master-listener.o] Segmentation fault
Check your memory. Last time I had gcc crash like this, the machine was
dieing. Error messages in the mem test where lighting up like a
Christmas tree within seconds.
> But if I type just 'make' again after this the build completes
> successfully. Everything else is fine. Is this dovecot related?
Maybe an early stage of mem failure, if it does succeed sporadically.
Probably going to change soon, though...
guenther
--
char *t="[EMAIL PROTECTED]";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: [Dovecot] v1.1.0 released
* Timo Sirainen <[EMAIL PROTECTED]>:
> They probably come from files that were already corrupted by the
> previous version. At least I can't reproduce the error anymore myself.
Well, OK
> Here's a script that can detect them:
>
> perl -e '$hdr=0; while (<>) { if (!$hdr) { $oldhdr = 1 if (/^1/); $hdr=1; }
> elsif ($oldhdr && /^\d+ :/) { print "broken\n"; last; } }' < dovecot-uidlist
>
> You could fix the files by dropping those lines that have ':' character.
> Although then it'll probably give errors about expunged messages
> reappearing, or something like that.
I'll try that.
--
Ralf Hildebrandt ([EMAIL PROTECTED]) [EMAIL PROTECTED]
Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155
http://www.arschkrebs.de
And others again have been told what a Unix would be and how it is
working. If this people are extraterrestrial or an ancient
mainframe-team of IBM (the difference is not that big), and they then
try to build a Unix, you will get a AIX 2 and 3 - a hybride monster
with green blood which will not kill you maybe, but when you look at
the innwards you wish you where dead afterwards.
Re: [Dovecot] v1.1.0 released
On Sat, 2008-06-21 at 15:12 +0200, Ralf Hildebrandt wrote:
> * Ralf Hildebrandt <[EMAIL PROTECTED]>:
> > * Timo Sirainen <[EMAIL PROTECTED]>:
> >
> > > http://hg.dovecot.org/dovecot-1.1/rev/5a1cc688483b fixes this. I guess
> > > it's time for v1.1.1 soon. :(
> >
> > Checking out, rebuilding...
>
> Nope, still there (the change is in my sources, I restarted dovecot):
>
> Jun 21 15:06:36 postamt dovecot: Dovecot v1.1.0 starting up
> Jun 21 15:09:02 postamt dovecot: IMAP(hwaiczie): Broken file
> /home/h/w/hwaiczie/Maildir/dovecot-uidlist line 460: UID larger than next_uid
> (12528 >= 12528)
They probably come from files that were already corrupted by the
previous version. At least I can't reproduce the error anymore myself.
Here's a script that can detect them:
perl -e '$hdr=0; while (<>) { if (!$hdr) { $oldhdr = 1 if (/^1/); $hdr=1; }
elsif ($oldhdr && /^\d+ :/) { print "broken\n"; last; } }' < dovecot-uidlist
You could fix the files by dropping those lines that have ':' character.
Although then it'll probably give errors about expunged messages
reappearing, or something like that.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] v1.1.0 released
* Ralf Hildebrandt <[EMAIL PROTECTED]>: > * Timo Sirainen <[EMAIL PROTECTED]>: > > > http://hg.dovecot.org/dovecot-1.1/rev/5a1cc688483b fixes this. I guess > > it's time for v1.1.1 soon. :( > > Checking out, rebuilding... Nope, still there (the change is in my sources, I restarted dovecot): Jun 21 15:06:36 postamt dovecot: Dovecot v1.1.0 starting up Jun 21 15:09:02 postamt dovecot: IMAP(hwaiczie): Broken file /home/h/w/hwaiczie/Maildir/dovecot-uidlist line 460: UID larger than next_uid (12528 >= 12528) -- Ralf Hildebrandt ([EMAIL PROTECTED]) [EMAIL PROTECTED] Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Es geht ja nicht nur um Kartoffeln - obwohl die ja auch wichtig sind. -- Prof. Grosch-Wörner
Re: [Dovecot] v1.1.0 released
* Timo Sirainen <[EMAIL PROTECTED]>: > http://hg.dovecot.org/dovecot-1.1/rev/5a1cc688483b fixes this. I guess > it's time for v1.1.1 soon. :( Checking out, rebuilding... -- Ralf Hildebrandt ([EMAIL PROTECTED]) [EMAIL PROTECTED] Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de "All programmers are playwrights and all computers are lousy actors." -Anon.
Re: [Dovecot] v1.1.0 released
On Sat, 2008-06-21 at 15:30 +0300, Timo Sirainen wrote: > On Sat, 2008-06-21 at 14:20 +0200, Ralf Hildebrandt wrote: > > * Timo Sirainen <[EMAIL PROTECTED]>: > > > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz > > > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig > > > > > > Two hours later than promised, I slept longer than intended. :) > > > > > > No changes since v1.1.rc13. Below are the largest changes since v1.0: > > > > After the switch I'm getting a lot of these messages: > > > > Jun 21 13:32:28 postamt dovecot: IMAP(haettasr): Broken file > > /home/h/a/haettasr/Maildir/.Sent Messages/dovecot-uidlist line 59: UID > > larger than next_uid (58 >= 58) > > These fix themselves automatically, but it would have been nice if they > didn't happen in the first place. I know I've seen them once in a while > myself while switching between v1.0 and v1.1, but I don't really know > how to reproduce it. Oh, I figured it out: 1. dovecot-uidlist is created by dovecot v1.0. 2. Dovecot v1.1 opens the mailbox and synchronizes it 3. Dovecot v1.1 writes a new mail, sees the mailbox is fully synced and doesn't bother actually reading dovecot-uidlist, just appends the new line using the new format. 4. IMAP/POP3 opens dovecot-uidlist, sees that the uidlist is in old format but there's a newly added line in new format. http://hg.dovecot.org/dovecot-1.1/rev/5a1cc688483b fixes this. I guess it's time for v1.1.1 soon. :( signature.asc Description: This is a digitally signed message part
Re: [Dovecot] v1.1.0 released
* Timo Sirainen <[EMAIL PROTECTED]>: > > Jun 21 13:32:28 postamt dovecot: IMAP(haettasr): Broken file > > /home/h/a/haettasr/Maildir/.Sent Messages/dovecot-uidlist line 59: UID > > larger than next_uid (58 >= 58) > > These fix themselves automatically, Yes. > but it would have been nice if they didn't happen in the first place. My point exactly. I'm afraid I'm getting these a lot when everybody will be logging in on Monday. -- Ralf Hildebrandt ([EMAIL PROTECTED]) [EMAIL PROTECTED] Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty nor safety.-- Benjamin Franklin, 1759
Re: [Dovecot] v1.1.0 released
On Sat, 2008-06-21 at 14:20 +0200, Ralf Hildebrandt wrote: > * Timo Sirainen <[EMAIL PROTECTED]>: > > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz > > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig > > > > Two hours later than promised, I slept longer than intended. :) > > > > No changes since v1.1.rc13. Below are the largest changes since v1.0: > > After the switch I'm getting a lot of these messages: > > Jun 21 13:32:28 postamt dovecot: IMAP(haettasr): Broken file > /home/h/a/haettasr/Maildir/.Sent Messages/dovecot-uidlist line 59: UID larger > than next_uid (58 >= 58) These fix themselves automatically, but it would have been nice if they didn't happen in the first place. I know I've seen them once in a while myself while switching between v1.0 and v1.1, but I don't really know how to reproduce it. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] v1.1.0 released
* Timo Sirainen <[EMAIL PROTECTED]>: > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig > > Two hours later than promised, I slept longer than intended. :) > > No changes since v1.1.rc13. Below are the largest changes since v1.0: After the switch I'm getting a lot of these messages: Jun 21 13:32:28 postamt dovecot: IMAP(haettasr): Broken file /home/h/a/haettasr/Maildir/.Sent Messages/dovecot-uidlist line 59: UID larger than next_uid (58 >= 58) Jun 21 13:40:35 postamt dovecot: IMAP(skroeger): Broken file /home/s/k/skroeger/Maildir/dovecot-uidlist line 332: UID larger than next_uid (1402 >= 1402) Jun 21 13:41:39 postamt dovecot: IMAP(raullric): Broken file /home/r/a/raullric/Maildir/.spam/dovecot-uidlist line 8: UID larger than next_uid (3433 >= 3433) Jun 21 13:41:47 postamt dovecot: IMAP(jhilpert): Broken file /home/j/h/jhilpert/Maildir/dovecot-uidlist line 3228: UID larger than next_uid (3396 >= 3396) Jun 21 13:55:59 postamt dovecot: IMAP(msynowit): Broken file /home/m/s/msynowit/Maildir/.Sent Messages/dovecot-uidlist line 70: UID larger than next_uid (69 >= 69) -- Ralf Hildebrandt ([EMAIL PROTECTED]) [EMAIL PROTECTED] Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Nothing is faster than the speed of light. To prove this to yourself, try opening the refrigerator door before the light comes on.
Re: [Dovecot] v1.1.0 released
* Ralf Hildebrandt <[EMAIL PROTECTED]>: > * Timo Sirainen <[EMAIL PROTECTED]>: > > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz > > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig > > > > Two hours later than promised, I slept longer than intended. :) > > > > No changes since v1.1.rc13. Below are the largest changes since v1.0: > > I'm getting errors from deliver: > > Jun 21 09:39:14 postamt deliver(sparis): > dlopen(/usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so) failed: > /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so: undefined symbol: strocpy I suck. I forgot to update the sieve plugin -- Ralf Hildebrandt ([EMAIL PROTECTED]) [EMAIL PROTECTED] Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de The government is CLEARLY an out of control robot that has decided the greatest danger to America is Americans.
Re: [Dovecot] v1.1.0 released
On Sat, 2008-06-21 at 09:40 +0200, Ralf Hildebrandt wrote: > * Timo Sirainen <[EMAIL PROTECTED]>: > > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz > > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig > > > > Two hours later than promised, I slept longer than intended. :) > > > > No changes since v1.1.rc13. Below are the largest changes since v1.0: > > I'm getting errors from deliver: > > Jun 21 09:39:14 postamt deliver(sparis): > dlopen(/usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so) failed: > /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so: undefined symbol: strocpy You'll have to upgrade Sieve plugin to v1.1.x version also. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] v1.1.0 released
On Sat, 21 Jun 2008 04:46:37 +0300 Timo Sirainen <[EMAIL PROTECTED]> wrote: > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig > > Two hours later than promised, I slept longer than intended. :) > > No changes since v1.1.rc13. Below are the largest changes since v1.0: > > * After Dovecot v1.1 has modified index or dovecot-uidlist files, > they can't be opened anymore with Dovecot versions earlier than > v1.0.2. > * See doc/wiki/Upgrading.1.1.txt (or for latest changes, > http://wiki.dovecot.org/Upgrading/1.1) for list of changes since > v1.0 that you should be aware of when upgrading. > > + IMAP: Added support for UIDPLUS and LIST-EXTENDED extensions. > + IMAP SORT: Sort keys are indexed, which makes SORT commands faster. > + When saving messages, update cache file immediately with the data > that we expect client to fetch later. > + NFS caches are are flushed whenever needed. See mail_nfs_storage and > mail_nfs_index settings. > + Out of order command execution (SEARCH, FETCH, LIST), nonstandard > command cancellation (X-CANCEL ) > + IMAP: STATUS-IN-LIST draft implementation > + Expire plugin can be used to keep track of oldest messages in > specific mailboxes. A nightly run can then quickly expunge old > messages from the mailboxes that have them. The tracking is done > using lib-dict, so you can use either Berkeley DB or SQL database. > + Namespaces are supported everywhere now. > + Namespaces have new list and subscriptions settings. > + Full text search indexing support with Lucene and Squat backends. > + OTP and S/KEY authentication mechanisms (by Andrey Panin). > + mbox and Maildir works with both Maildir++ and FS layouts. You can > change these by appending :LAYOUT=maildir++ or :LAYOUT=fs to > mail_location. > + LDAP: Support templates in pass_attrs and user_attrs > + Support for listening in multiple IPs/ports. > + Quota plugin rewrite: Support for multiple quota roots, warnings, > allow giving storage size in bytes or kilo/mega/giga/terabytes, > per-mailbox quota rules. > + Filesystem quota backend supports inode limits, group quota and > RPC quota for NFS. > + SEARCH and SORT finally compare non-ASCII characters > case-insensitively. We use i;unicode-casemap algorithm. > + Config files support splitting values to multiple lines with \ > > Congratulations! I'm waiting for the FreeBSD port before test and use the 1.1 version :-) -- -Nicolas.
Re: [Dovecot] v1.1.0 released
* Timo Sirainen <[EMAIL PROTECTED]>: > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig > > Two hours later than promised, I slept longer than intended. :) > > No changes since v1.1.rc13. Below are the largest changes since v1.0: I'm getting errors from deliver: Jun 21 09:39:14 postamt deliver(sparis): dlopen(/usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so) failed: /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so: undefined symbol: strocpy Jun 21 09:39:14 postamt deliver(sparis): Fatal: Couldn't load required plugins Jun 21 09:39:14 postamt deliver(sparis): dlopen(/usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so) failed: /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so: undefined symbol: strocpy Jun 21 09:39:14 postamt deliver(sparis): Fatal: Couldn't load required plugins Jun 21 09:39:14 postamt deliver(sparis): dlopen(/usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so) failed: /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so: undefined symbol: strocpy Jun 21 09:39:14 postamt deliver(sparis): Fatal: Couldn't load required plugins Jun 21 09:39:14 postamt deliver(sparis): dlopen(/usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so) failed: /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so: undefined symbol: strocpy Jun 21 09:39:14 postamt deliver(sparis): Fatal: Couldn't load required plugins Jun 21 09:39:14 postamt postfix/local[2408]: 709BAB31F6: to=<[EMAIL PROTECTED]>, relay=local, delay=0.07, delays=0.01/0/0/0.07, dsn=4.3.0, status=deferred (temporary failure) -- Ralf Hildebrandt ([EMAIL PROTECTED]) [EMAIL PROTECTED] Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Due to a lack of imagination, this signature will remain under construction indefinitely.
Re: [Dovecot] v1.1.0 released
On Sat, 2008-06-21 at 04:46 +0300, Timo Sirainen wrote: > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig > > Two hours later than promised, I slept longer than intended. :) > > No changes since v1.1.rc13. Below are the largest changes since v1.0: Cool. I guess now I really have to debug why antispam+quota segfaults. johannes signature.asc Description: This is a digitally signed message part
Re: [Dovecot] v1.1.0 released
Congrats timo! Cor
Re: [Dovecot] v1.1.0 released
Congratulations on your new major release. We all appreciate the fine work you are doing.
Re: [Dovecot] v1.1.0 released
On Jun 21, 2008, at 5:58 AM, Luca Corti wrote: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-sql -I../../src/lib-settings -I../../src/lib-ntlm -I../../src/lib-otp -DAUTH_MODULE_DIR=\""/usr/local/lib/dovecot/auth"\" -DPKG_LIBEXECDIR= \""/usr/local/libexec/dovecot"\"-std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT auth-master-listener.o -MD -MP -MF .deps/auth-master- listener.Tpo -c -o auth-master-listener.o auth-master-listener.c make[3]: *** [auth-master-listener.o] Segmentation fault make[3]: Leaving directory `/usr/local/src/dovecot/dovecot-1.1.0/src/auth' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/dovecot/dovecot-1.1.0/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dovecot/dovecot-1.1.0' make: *** [all] Error 2 But if I type just 'make' again after this the build completes successfully. Everything else is fine. Is this dovecot related? Always at the same source file or just somewhat randomly? Either a gcc bug or your memory is broken. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] v1.1.0 released
On Sat, 2008-06-21 at 04:46 +0300, Timo Sirainen wrote: > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz > http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig > > Two hours later than promised, I slept longer than intended. :) First of all, great work... > No changes since v1.1.rc13. Below are the largest changes since v1.0: I've been testing 1.1 betas/rcs since a long time with my few gigabites of maildirs. Noticed no big isses. All I had to do lately was $ ./configure && make an then rebuild sieve, install and restart dovecot. With 1.1rc3/1.1.0 i experience this minor compile issue. Basically if I do: $ ./configure && make build fails with gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-sql -I../../src/lib-settings -I../../src/lib-ntlm -I../../src/lib-otp -DAUTH_MODULE_DIR=\""/usr/local/lib/dovecot/auth"\" -DPKG_LIBEXECDIR= \""/usr/local/libexec/dovecot"\"-std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT auth-master-listener.o -MD -MP -MF .deps/auth-master-listener.Tpo -c -o auth-master-listener.o auth-master-listener.c make[3]: *** [auth-master-listener.o] Segmentation fault make[3]: Leaving directory `/usr/local/src/dovecot/dovecot-1.1.0/src/auth' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/dovecot/dovecot-1.1.0/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dovecot/dovecot-1.1.0' make: *** [all] Error 2 But if I type just 'make' again after this the build completes successfully. Everything else is fine. Is this dovecot related? ciao Luca
[Dovecot] v1.1.0 released
http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig Two hours later than promised, I slept longer than intended. :) No changes since v1.1.rc13. Below are the largest changes since v1.0: * After Dovecot v1.1 has modified index or dovecot-uidlist files, they can't be opened anymore with Dovecot versions earlier than v1.0.2. * See doc/wiki/Upgrading.1.1.txt (or for latest changes, http://wiki.dovecot.org/Upgrading/1.1) for list of changes since v1.0 that you should be aware of when upgrading. + IMAP: Added support for UIDPLUS and LIST-EXTENDED extensions. + IMAP SORT: Sort keys are indexed, which makes SORT commands faster. + When saving messages, update cache file immediately with the data that we expect client to fetch later. + NFS caches are are flushed whenever needed. See mail_nfs_storage and mail_nfs_index settings. + Out of order command execution (SEARCH, FETCH, LIST), nonstandard command cancellation (X-CANCEL ) + IMAP: STATUS-IN-LIST draft implementation + Expire plugin can be used to keep track of oldest messages in specific mailboxes. A nightly run can then quickly expunge old messages from the mailboxes that have them. The tracking is done using lib-dict, so you can use either Berkeley DB or SQL database. + Namespaces are supported everywhere now. + Namespaces have new list and subscriptions settings. + Full text search indexing support with Lucene and Squat backends. + OTP and S/KEY authentication mechanisms (by Andrey Panin). + mbox and Maildir works with both Maildir++ and FS layouts. You can change these by appending :LAYOUT=maildir++ or :LAYOUT=fs to mail_location. + LDAP: Support templates in pass_attrs and user_attrs + Support for listening in multiple IPs/ports. + Quota plugin rewrite: Support for multiple quota roots, warnings, allow giving storage size in bytes or kilo/mega/giga/terabytes, per-mailbox quota rules. + Filesystem quota backend supports inode limits, group quota and RPC quota for NFS. + SEARCH and SORT finally compare non-ASCII characters case-insensitively. We use i;unicode-casemap algorithm. + Config files support splitting values to multiple lines with \ signature.asc Description: This is a digitally signed message part
