Thanks. I've successfully reproduced this on 1:2.6.5-0ubuntu3.2 (precise-updates). It looks like the root cause was fixed in 1:2.7.0-1, so that includes quantal and raring. But there is still an upgrade path problem, so users installing precise who then upgrade will still be affected.
I've reported this in Debian in http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=698446 ** Bug watch added: Debian Bug tracker #698446 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698446 ** Also affects: amavisd-new (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698446 Importance: Unknown Status: Unknown ** Changed in: amavisd-new (Ubuntu) Status: Incomplete => Triaged ** Changed in: amavisd-new (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in Ubuntu. https://bugs.launchpad.net/bugs/1101160 Title: sa-update-hooks.d/amavisd-new needs to be executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1101160/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
