[Expired for spamassassin (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: spamassassin (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It sounds like this happens after local changes involving hardening,
then? Could you please narrow it down to a specific series of steps
after which spamassassin/sa-compile would reasonably be expected to
work,
Been running, testing, re-installing and rebooting a lot of times since
my post above.
I've noted that in
/etc/cron.daily/spamassassin
there is umask 022 to updated the spam assassin rules, and consistently
"the system" will fail to install or fall over if login.defs is changed
to 027 on reboot
[SOLVED] (possibly I don't want to appear too arrogant on my first post
:)
I updated my 12.04 to 14.04 with no problems and then recently I decided
to increase my security with various tools like tripwire, ,tiger and
lynis and one of the "recommendations" was to tighten up the security on
gcc
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: spamassassin (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
** Package changed: ubuntu = spamassassin (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.net/bugs/1313133
Title:
sa-compile error on ubuntu 14.04 LTS upgrade
To manage
