[Dovecot] 1.1.9 release candidate
http://dovecot.org/tmp/dovecot-1.1.9.rc.tar.gz
There are a couple of a bit larger changes, so would be nice if a few people tested this on different setups before I released the final v1.1.9.
Changes since v1.1.8:
+ deliver: Added rejection_subject setting, which is used for
rejected mails.
+ pop3: Prevent clients from looping forever trying to fetch an
expunged message.
+ If login process crashes, log the IP address that (maybe) caused it.
+ If core dump limit is 0, add "core dumps disabled" to startup log line.
- mbox: Fixed assert-crash with pop3_lock_session=yes
- dbox: Fixes to handling maildir-converted files.
- Auth cache wasn't working correctly for all fields (e.g. allow_nets)
with blocking passdbs (e.g. mysql).
- pgsql: Handle reconnecting to server without failing auth lookups.
- Berkeley DB memory/resource leak fixes.
- maildir: Fixes to handling over 26 keywords.On 16.01.2009 00:06 Timo Sirainen wrote:
http://dovecot.org/tmp/dovecot-1.1.9.rc.tar.gz
There are a couple of a bit larger changes, so would be nice if a few people tested this on different setups before I released the final v1.1.9.
Changes since v1.1.8:
[…]
- pgsql: Handle reconnecting to server without failing auth lookups. […]
Hi Timo,
I've compiled v1.1.9.rc on OpenBSD 4.2. After restarting the PostgreSQL server I'm getting this error:
Jan 16 16:16:53 vh3 dovecot: auth(default): sql(user@example.org): User query failed: FATAL: terminating connection due to administrator command Jan 16 16:16:53 vh3 dovecot: auth(default): kevent(EV_DELETE, 10) failed: Bad file descriptor Jan 16 16:16:53 vh3 deliver(user@example.org): Auth lookup returned failure
Next time when Postfix tries to deliver messages Dovecot reconnects to the database:
Jan 16 16:20:19 vh3 dovecot: auth(default): pgsql: Connected to mailsys
Regards Pascal
Ubuntu is an ancient African word meaning “I can’t install Debian.” -- unknown
Timo Sirainen wrote:
http://dovecot.org/tmp/dovecot-1.1.9.rc.tar.gz
There are a couple of a bit larger changes, so would be nice if a few people tested this on different setups before I released the final v1.1.9.
It's running here without problem as a pop3 server.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Timo Sirainen pisze:
http://dovecot.org/tmp/dovecot-1.1.9.rc.tar.gz
There are a couple of a bit larger changes, so would be nice if a few people tested this on different setups before I released the final v1.1.9.
I have compiled dovecot(on my test server) with these options: --with-notify=inotify --with-pop3d --with-deliver --with-mysql --disable-ipv6
mail64:~# dovecot -n # 1.1.9: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-6-xen-amd64 x86_64 Debian 4.0 ext3
So far, I haven't noticed any errors.
Tomasz Suchodolski
On Jan 17, 2009, at 5:39 PM, Tomasz Suchodolski wrote:
Timo Sirainen pisze:
http://dovecot.org/tmp/dovecot-1.1.9.rc.tar.gz There are a couple of a bit larger changes, so would be nice if a few people tested this on different setups before I released the final v1.1.9.
I have compiled dovecot(on my test server) with these options:
Doesn't really matter, but:
--with-notify=inotify
This should be detected and used automatically, so it's not necessary.
--with-pop3d --with-deliver
These are enabled by default, so not necessary.
--with-mysql
This is necessary. :)
--disable-ipv6
Why? I'm beginning to think it's time to remove this option entirely.
Originally it was added because of buggy OSes, but those should be
gone by now.
On Jan 17, 2009, at 5:39 PM, Tomasz Suchodolski wrote:
Timo Sirainen pisze:
http://dovecot.org/tmp/dovecot-1.1.9.rc.tar.gz There are a couple of a bit larger changes, so would be nice if a few people tested this on different setups before I released the final v1.1.9.
I have compiled dovecot(on my test server) with these options:
Doesn't really matter, but:
--with-notify=inotify
This should be detected and used automatically, so it's not necessary.
--with-pop3d --with-deliver
These are enabled by default, so not necessary.
Timo Sirainen pisze: like in Windows: Next(./configure) Next(make) Finish(make install) ;)
--with-mysql
This is necessary. :)
--disable-ipv6
Why? I'm beginning to think it's time to remove this option entirely. Originally it was added because of buggy OSes, but those should be gone by now.
I don't need this now and this is a test server so I can :) In my opinion, if something is enabled by default then should be a way to disable it.
On Jan 17, 2009, at 6:43 PM, Tomasz Suchodolski wrote:
--with-mysql This is necessary. :) --disable-ipv6 Why? I'm beginning to think it's time to remove this option
entirely. Originally it was added because of buggy OSes, but those
should be gone by now.I don't need this now and this is a test server so I can :) In my opinion, if something is enabled by default then should be a
way to disable it.
Listening for IPv6 connections is actually disabled by default (listen
setting), the configure option only specifies if the code is being
even built in.
Timo Sirainen pisze:
On Jan 17, 2009, at 6:43 PM, Tomasz Suchodolski wrote:
--with-mysql This is necessary. :) --disable-ipv6 Why? I'm beginning to think it's time to remove this option entirely. Originally it was added because of buggy OSes, but those should be gone by now.
I don't need this now and this is a test server so I can :) In my opinion, if something is enabled by default then should be a way to disable it.
Listening for IPv6 connections is actually disabled by default (listen setting), the configure option only specifies if the code is being even built in.
I realize that. If you still consider removing that option I have nothing against, ipv6 is the near future.
participants (4)
-
Mark Sapiro
-
Pascal Volk
-
Timo Sirainen
-
Tomasz Suchodolski