15 Jan
2012
15 Jan
'12
8:59 p.m.
Five months ago Martin Halford said:
The only problem I had of any significance was with
Dovecot, which was
not delivering mail to virtual users after the upgrade. The problem was
to do with a change to the cmusieve plugin in Dovecot .
[Taken from a recent forum post] The protocol "managesieve" is now
called "lda" and the plugin "cmusieve" is called "sieve"
from V1.2 of
Dovecot.
Having finally got around to doing the upgrade before Lenny security
updates stop, yes, this caught me.
Commenting out two lines in protocol managesieve {
# sieve=~/.dovecot.sieve
# sieve_storage=~/sieve
seems to have done the trick.
Other issues:
1. postgrey (does greylisting for postfix) now listens on a different
port (10023 not 60000) so /etc/postfix/main.cf needs changing to reflect
that.
2. You can only install grub-legacy after doing the dist-upgrade, i.e.
after it has moaned about issues with grub2.
3. MySQL 5.0 is declared removable, but 5.1 is not automatically
installed in its place. Doing the upgrade via
apt-get install mysql-server-5.1
before the dist-upgrade works.
4. Doing the upgrade via the console had an issue with some of the alert
boxes ('you've made changes to this file - do you want to keep them or
install the package maintainer's version' sort of thing) staying on
screen. Towards the end, I had one viewable line of text.
5. suphp didn't work afterwards on the first VPS. This turns out to be
changes to the syntax in /etc/suphp/suphp.conf and accepting the new
version seems to have been ok in the second
6. The oddity common to both is that although BIND9 is up and running..
/etc/init.d/bind9 status
bind9 is running.
.. and it's doing zone transfers, the BIND Webmin 1.570 module doesn't
seem to think that it is. Instead of the usual options to
Apply configuration
or
Stop BIND
.. there's
Start BIND
instead. Does anyone else use Webmin?
Ian