Dovecot v2.0.9 released

[interfasys]

http://dovecot.org/releases/2.0/dovecot-2.0.9.tar.gz
http://dovecot.org/releases/2.0/dovecot-2.0.9.tar.gz.sig

- Linux: Fixed a high system CPU usage / high context switch count performance problem
- Maildir: Avoid unnecessarily reading dovecot-uidlist while opening mailbox.
- Maildir: Fixed renaming child mailboxes when namespace had a prefix.
- mdbox: Don't leave partially written messages to mdbox files when aborting saving.
- Fixed master user logins when using userdb prefetch
- lda: Fixed a crash when trying to send "out of quota" reply
- lmtp: If delivering duplicate messages to same user's INBOX, create different GUIDs for them. This helps to avoid duplicate POP3 UIDLs when pop3_uidl_format=%g.
- virtual storage: Fixed saving multiple mails in a transaction (e.g. copy multiple messages).
- dsync: Saved messages' save-date was set to 1970-01-01.

[-j0]

Man you are fast! god bless you and thanks for this share! huh... i just wanna post that news.

[DirectAdmin Support]

Hello,

FYI, the custombuild code has been updated for 2.x, but testing with it has been limited.

If you wish to try 2.x, be sure you run "./build update" first so you have the new custombuild, then edit your versions.txt and change:
dovecot:1.2.16:8bbdf4e96e2e0f5749432ca9cb209a38to be:
dovecot:2.0.9:then type:
./build dovecotand let us know if there are any issues.

John

[Peter Laws]

I've been using v2.x for a few months (with smtalk's config change instructions) and haven't had any issues - I've just been upgrading by md5'ing the versions.txt.

This is on Debian 5.x.x by the way.

[ditto]

I am running CentOS 5.5 64bit. Does anybody know if I need to manually apply some necessary config changes when upgrading to 2.x using custombuild?

[keefe007]

I've been using v2.x for a few months (with smtalk's config change instructions) and haven't had any issues - I've just been upgrading by md5'ing the versions.txt.

This is on Debian 5.x.x by the way.

Where can we find these instructions?

[DirectAdmin Support]

Hello,

I've just added dovecot 2.0.9 to the versions.txt.
Type:
cd /usr/local/directadmin/custombuild
./build update
./build dovecotJohn

[ditto]

So, should it be safe to upgrade from Dovecot 1.2.16 to Dovecot 2.0.9 using Custombuild? (I am using CentOS 5.5 64bit) Or does we need to manually add some config changes after upgrading?

[DirectAdmin Support]

custombuild does it all for you.
I've found no errors during my testing.
Also, others who have been using it already have also reported no errors.

John

[gate2vn]

Upgraded on 64bits system and got error


Error: service(pop3-login): listen(::, 110) failed: Address family not supported by protocol
Error: socket() failed: Address family not supported by protocol
Error: service(pop3-login): listen(::, 995) failed: Address family not supported by protocol
Error: socket() failed: Address family not supported by protocol
Error: service(imap-login): listen(::, 143) failed: Address family not supported by protocol
Error: socket() failed: Address family not supported by protocol
Error: service(imap-login): listen(::, 993) failed: Address family not supported by protocol
Fatal: Failed to start listeners

[DirectAdmin Support]

Hello,

I believe the "::" is the IPv6 version of "*"

The closest related item I found was this:
http://bugs.gentoo.org/136781

In any case, it probably just means dovecot is trying to use IPv6, but your box may not support it.

Try adding this to the very top of your /etc/dovecot.conf:
listen = *The internal default is
listen = *, ::so by only having the * we're telling dovecot that we only want to listen on IPv4.

John

[nmb]

Just updated from version 1 to 2.09 using Custombuild. Tested it a bit and it seems to work fine.
________
Weed bubblers (http://bubblers.net/)

[gate2vn]

This fixed the issue. Thanks for quick solution :)



Try adding this to the very top of your /etc/dovecot.conf:
listen = *

[Chrysalis]

maybe I am the only one but I am having huge issues with this update and using the default DA config file, webmail and remote pop both are broken although dovecot process is running. Both just simply timeout.

the process listens on all ports but I get weird auth timeout errors in dovecot's log for webmail and it doesnt even show pop connections. I have rolled it back to 1.2 for now and will investigate more later.

[DirectAdmin Support]

Hello,

1) Test the local connection, eg:
telnet localhost 110to see if you can connect.

2) Check /var/log/maillog (or mail.log) for any dovecot errors.

3) With dovecot 2.x, the /etc/dovecot.conf should actually be a link to /etc/dovecot/dovecot.conf, and that file should look like:
http://files.directadmin.com/services/custombuild/dovecot.conf.2.0

John

[Bisoton]

Hi
listen = * solve part of problem now i have new error



Starting dovecot: Error: service(imap-login): listen(*, 143) failed: Address already in use
Fatal: Failed to start listeners

[Chrysalis]

thanks will try this again later, I cannot do it now as is daytime.

my /etc/dovecot.conf is indeed different to the /etc/dovecot/dovecot.conf file.

Both say ## Dovecot 2.0 configuration file at the top so I know they neither are the old config file but they are different, the /etc/dovecot.conf doesnt have the shadow stuff in it.

I sent you more details in email John.

[Bisoton]

Hi
listen = * solve part of problem now i have new error



Starting dovecot: Error: service(imap-login): listen(*, 143) failed: Address already in use
Fatal: Failed to start listeners

my bad process still running on 143 port i just kill it and dovecot run

[Chrysalis]

ok I tested on a less busy server and fixed it.

the config in /etc/dovecot.conf was correct to work. the one in /etc/dovecot/dovecot.conf was wrong.

I changed

passdb {
driver = passwd
}

to

passdb {
driver = shadow
}

and linked the 2 config's.

[IT_Architect]

ok I tested on a less busy server and fixed it.
It doesn't work for me either. I tried it on a single domain server and the mail no longer works. I'm on FreeBSD 64 also. I'm doing a rollback to the snapshot I made before the update for now. I'll try it again when this is fixed.

PS: Just did a rollback and everything works again

[interfasys]

This is a config that should work on FreeBSD, is you're using maildir:

# System users
passdb {
driver = passwd
}

# Virtual users
passdb {
driver = passwd-file
args = username_format=%n /etc/virtual/%d/passwd
}

# System users
userdb {
driver = passwd
args = mail=maildir:/home/%u/Maildir/
}

# Virtual users
userdb {
driver = passwd-file
args = username_format=%n /etc/virtual/%d/passwd
}

[DirectAdmin Support]

Thanks for the info.

This took a bit of head scratching and debugging, but I found out that when one does a perl regex on a symbolic link, perl decides to delete the link and creates a new file, hence they were mistmatched and unlinked.

I've updated the build scripts to check for this case so FreeBSD should be fine now. (shadow will be correctly perl-regexed to passwd), and the link will remain.

John

[IT_Architect]

I re-ran the updates on a couple of my FreeBSD servers this weekend and the updates went fine this time.

[voider]

http://wiki2.dovecot.org/Upgrading/2.0

[Chrysalis]

I can confirm the install issue is fixed for freebsd. However it would be an idea to backup the existing config before overwriting it because if its a custom one it gets lost.

[DirectAdmin Support]

Hello,

I believe it makes a backup to /etc/dovecot.conf.1.2.
Let us know if that isn't working.

John