Xenial is carrying version 3.4.2-0ubuntu0.16.04.2, so I think per the
last comment we can assume this issue is now resolved.
** Changed in: spamassassin (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I ran into this bug as well and checked if it's also present in Debian.
It appears that from spamassassin 3.4.0-2 the relevant code is:
# Update
umask 022
env -i LANG=$LANG PATH=$PATH start-stop-daemon \
--chuid debian-spamd:debian-spamd --start \
--exec /usr/bin/sa-update -- \
I ran into this bug as well and checked if it's also present in Debian.
It appears that from spamassassin 3.4.0-2 the relevant code is:
# Update
umask 022
env -i LANG=$LANG PATH=$PATH start-stop-daemon \
--chuid debian-spamd:debian-spamd --start \
--exec /usr/bin/sa-update -- \
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.
I'm hitting this on mailservers which runs with system wide umask of
007, set in /etc/profile.
After /etc/cron.daily/spamassassin has run, and the first email is
processed, amavis will shut down, since it cant' read
/var/lib/spamassassin/3.004000/updates_spamassassin_org.cf resulting in
an uppile
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373560
Title:
I'm hitting this on mailservers which runs with system wide umask of
007, set in /etc/profile.
After /etc/cron.daily/spamassassin has run, and the first email is
processed, amavis will shut down, since it cant' read
/var/lib/spamassassin/3.004000/updates_spamassassin_org.cf resulting in
an uppile
In my opinion, amavis's ability to read the ruleset created by sa-update
should not rely on the default umask being in effect when sa-update was
run.
Agreed. I just wanted to understand the proportion of users who might be
affected.
This needs to be investigated in Debian.
** Changed in:
On 09/26/2014 08:21, Robie Basak wrote:
In my opinion, amavis's ability to read the ruleset created by sa-update
should not rely on the default umask being in effect when sa-update was
run.
Agreed. I just wanted to understand the proportion of users who might be
affected.
This needs to
In my opinion, amavis's ability to read the ruleset created by sa-update
should not rely on the default umask being in effect when sa-update was
run.
Agreed. I just wanted to understand the proportion of users who might be
affected.
This needs to be investigated in Debian.
** Changed in:
On 09/26/2014 08:21, Robie Basak wrote:
In my opinion, amavis's ability to read the ruleset created by sa-update
should not rely on the default umask being in effect when sa-update was
run.
Agreed. I just wanted to understand the proportion of users who might be
affected.
This needs to
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Is your umask 007 because you changed the system default? I'm asking to
understand whether this will affect all spamassassin/sa-update/amavisd
users by default, or if it only affects others who have changed their
I don't recall for sure, but I have 'UMASK 077' in /etc/login.defs and
believe the default is 022, so I probably have changed the default. I
also have 'USERGROUPS_ENAB yes', resulting in a mask of 007 for the
debian-spamd account.
In my opinion, amavis's ability to read the ruleset created by
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Is your umask 007 because you changed the system default? I'm asking to
understand whether this will affect all spamassassin/sa-update/amavisd
users by default, or if it only affects others who have changed their
I don't recall for sure, but I have 'UMASK 077' in /etc/login.defs and
believe the default is 022, so I probably have changed the default. I
also have 'USERGROUPS_ENAB yes', resulting in a mask of 007 for the
debian-spamd account.
In my opinion, amavis's ability to read the ruleset created by
15 matches
Mail list logo
