** Also affects: amavisd-new (Linux From Scratch)
Importance: Undecided
Status: New
** Changed in: amavisd-new (Linux From Scratch)
Assignee: (unassigned) = Acidburn_Zero (acidburn0)
** Changed in: amavisd-new (Ubuntu)
Status: Triaged = New
** Also affects:
** Changed in: amavisd-new (Debian)
Status: Unknown = New
--
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
** Tags added: bitesize
--
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
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I couldn't reproduce this on amavisd-new 1:2.7.1-2ubuntu3 on raring:
$ stat /etc/spamassassin/sa-update-hooks.d/amavisd-new
File: ‘/etc/spamassassin/sa-update-hooks.d/amavisd-new’
Size: 710
Thanks for the fast reply! I'm on precise (12.04.1 LTS), and there, the
file was not executable.
--
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:
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
