You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by porterj <je...@gmail.com> on 2007/04/12 16:37:52 UTC
mkdir /root/.spamassasin: permission denied error.
I just set-up spamassassin on a Red Hat Enterprise Linux 4 mail server and it
appears that spamassassin is working as I am seeing messages that are now
tagged as spam.
However, in my /var/log/maillog I keep seeing a message similar to the
following and am unsure how to fix it. Any help would be appreciated.
Begin message in /var/log/maillog
Apr 12 10:27:44 servername spamd[18456]: spamd: setuid to root succeeded
Apr 12 10:27:44 servername spamd[18456]: spamd: still running as root: user
not specified with -u, not found, or set to root, falling back to nobody at
/usr/bin/spamd line 1147, <GEN212> line 4.
Apr 12 10:27:44 servername spamd[18456]: spamd: processing message
<73...@web56611.mail.re3.yahoo.com> for root:99
Apr 12 10:27:45 servername spamd[18456]: mkdir /root/.spamassassin:
Permission denied at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin.pm
line
1536
Apr 12 10:27:45 servername spamd[18456]: locker: safe_lock: cannot create
tmp lockfile /root/.spamassassin/auto-whitelist.lock.servername.domain.com
.18456 for /root/.spamassassin/auto-whitelist.lock: Permission denied
Apr 12 10:27:45 servername spamd[18456]: auto-whitelist: open of
auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile
/root/.spamassassin/auto-whitelist.lock.servername.domain.com.18456 for
/root/.spamassassin/auto-whitelist.lock: Permission denied
Apr 12 10:27:45 servername spamd[18456]: bayes: locker: safe_lock: cannot
create tmp lockfile
/root/.spamassassin/bayes.lock.servername.domain.com.18456 for
/root/.spamassassin/bayes.lock: Permission denied
Apr 12 10:27:45 servername spamd[18456]: spamd: clean message (0.0/3.5) for
root:99 in 0.6 seconds, 8188 bytes.
Apr 12 10:27:45 servername spamd[18456]: spamd: result: . 0 -
scantime=0.6,size=8188,user=root,uid=99,required_score=3.5,rhost=servername,raddr=127.0.0.
1,rport=55310,mid=<73...@web56611.mail.re3.yahoo.com>,autolearn=failed
End message in /var/log/maillog
Thanks,
JP
--
View this message in context: http://www.nabble.com/mkdir--root-.spamassasin%3A-permission-denied-error.-tf3565899.html#a9960786
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: mkdir /root/.spamassasin: permission denied error.
Posted by "John D. Hardin" <jh...@impsec.org>.
On Thu, 12 Apr 2007, maillist wrote:
> I would recommend turning off AWL, and just run sa-learn manually
> on messages that get through, as they come in.
Nit: AWL is not bayes-related.
However, I agree with the point you're probably trying to make, that
bayes auto-learn may be a bad idea in a small-volume environment.
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin@impsec.org FALaholic #11174 pgpk -a jhardin@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
It may be possible to start a programme of weapon registration as a
first step towards the physical collection phase. ... Assurances
must be provided, and met, that the process of registration will
not lead to immediate weapons seizures by security forces.
-- the UN, who "doesn't want to confiscate guns"
-----------------------------------------------------------------------
Tomorrow: Thomas Jefferson's 264th Birthday
Re: mkdir /root/.spamassasin: permission denied error.
Posted by maillist <ma...@emailacs.com>.
porterj wrote:
> Thanks for your replies. I did not realize this message was being spawned by
> 'spamc'. I had established a -u username but had it kicking off with the
> 'spamd' process. I corrected this and the errors went away.
>
> Speaking of auto whitelist. Is this not a good feature to use? I have it
> turned on, I believe, but could turn it off it is not recommended.
>
> Thanks again,
> JP
>
>
>
>
It really depends on your needs. I have a single domain, with under 100
users. I have a few user accounts that I know receive nothing but
spam. I use those users to catch the latest spam, and do all of my
learning manually. Other folks on this list have a *very* different set
of needs. If you can afford the time, I would recommend turning off
AWL, and just run sa-learn manually on messages that get through, as
they come in.
-=Aubrey=-
Re: mkdir /root/.spamassasin: permission denied error.
Posted by porterj <je...@gmail.com>.
Thanks for your replies. I did not realize this message was being spawned by
'spamc'. I had established a -u username but had it kicking off with the
'spamd' process. I corrected this and the errors went away.
Speaking of auto whitelist. Is this not a good feature to use? I have it
turned on, I believe, but could turn it off it is not recommended.
Thanks again,
JP
porterj wrote:
>
> I just set-up spamassassin on a Red Hat Enterprise Linux 4 mail server and
> it appears that spamassassin is working as I am seeing messages that are
> now tagged as spam.
>
> However, in my /var/log/maillog I keep seeing a message similar to the
> following and am unsure how to fix it. Any help would be appreciated.
>
> Begin message in /var/log/maillog
>
> Apr 12 10:27:44 servername spamd[18456]: spamd: setuid to root succeeded
> Apr 12 10:27:44 servername spamd[18456]: spamd: still running as root:
> user not specified with -u, not found, or set to root, falling back to
> nobody at /usr/bin/spamd line 1147, <GEN212> line 4.
> Apr 12 10:27:44 servername spamd[18456]: spamd: processing message
> <73...@web56611.mail.re3.yahoo.com> for root:99
> Apr 12 10:27:45 servername spamd[18456]: mkdir /root/.spamassassin:
> Permission denied at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin.pm
> line
> 1536
> Apr 12 10:27:45 servername spamd[18456]: locker: safe_lock: cannot create
> tmp lockfile /root/.spamassassin/auto-whitelist.lock.servername.domain.com
> .18456 for /root/.spamassassin/auto-whitelist.lock: Permission denied
> Apr 12 10:27:45 servername spamd[18456]: auto-whitelist: open of
> auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile
> /root/.spamassassin/auto-whitelist.lock.servername.domain.com.18456 for
> /root/.spamassassin/auto-whitelist.lock: Permission denied
> Apr 12 10:27:45 servername spamd[18456]: bayes: locker: safe_lock: cannot
> create tmp lockfile
> /root/.spamassassin/bayes.lock.servername.domain.com.18456 for
> /root/.spamassassin/bayes.lock: Permission denied
> Apr 12 10:27:45 servername spamd[18456]: spamd: clean message (0.0/3.5)
> for root:99 in 0.6 seconds, 8188 bytes.
> Apr 12 10:27:45 servername spamd[18456]: spamd: result: . 0 -
> scantime=0.6,size=8188,user=root,uid=99,required_score=3.5,rhost=servername,raddr=127.0.0.
> 1,rport=55310,mid=<73...@web56611.mail.re3.yahoo.com>,autolearn=failed
>
> End message in /var/log/maillog
>
> Thanks,
> JP
>
--
View this message in context: http://www.nabble.com/mkdir--root-.spamassasin%3A-permission-denied-error.-tf3565899.html#a9963550
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: mkdir /root/.spamassasin: permission denied error.
Posted by maillist <ma...@emailacs.com>.
porterj wrote:
> I just set-up spamassassin on a Red Hat Enterprise Linux 4 mail server and it
> appears that spamassassin is working as I am seeing messages that are now
> tagged as spam.
>
> However, in my /var/log/maillog I keep seeing a message similar to the
> following and am unsure how to fix it. Any help would be appreciated.
>
> Begin message in /var/log/maillog
>
> Apr 12 10:27:44 servername spamd[18456]: spamd: setuid to root succeeded
> Apr 12 10:27:44 servername spamd[18456]: spamd: still running as root: user
> not specified with -u, not found, or set to root, falling back to nobody at
> /usr/bin/spamd line 1147, <GEN212> line 4.
> Apr 12 10:27:44 servername spamd[18456]: spamd: processing message
> <73...@web56611.mail.re3.yahoo.com> for root:99
> Apr 12 10:27:45 servername spamd[18456]: mkdir /root/.spamassassin:
> Permission denied at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin.pm
> line
> 1536
> Apr 12 10:27:45 servername spamd[18456]: locker: safe_lock: cannot create
> tmp lockfile /root/.spamassassin/auto-whitelist.lock.servername.domain.com
> .18456 for /root/.spamassassin/auto-whitelist.lock: Permission denied
> Apr 12 10:27:45 servername spamd[18456]: auto-whitelist: open of
> auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile
> /root/.spamassassin/auto-whitelist.lock.servername.domain.com.18456 for
> /root/.spamassassin/auto-whitelist.lock: Permission denied
> Apr 12 10:27:45 servername spamd[18456]: bayes: locker: safe_lock: cannot
> create tmp lockfile
> /root/.spamassassin/bayes.lock.servername.domain.com.18456 for
> /root/.spamassassin/bayes.lock: Permission denied
> Apr 12 10:27:45 servername spamd[18456]: spamd: clean message (0.0/3.5) for
> root:99 in 0.6 seconds, 8188 bytes.
> Apr 12 10:27:45 servername spamd[18456]: spamd: result: . 0 -
> scantime=0.6,size=8188,user=root,uid=99,required_score=3.5,rhost=servername,raddr=127.0.0.
> 1,rport=55310,mid=<73...@web56611.mail.re3.yahoo.com>,autolearn=failed
>
> End message in /var/log/maillog
>
> Thanks,
> JP
>
First of all, you need to start spamd with the -u option as whatever
user you've designated to run spamd, but not as root. Example:
/usr/bin/spamd -r /var/run/spamd.pid -d --username=defang
Also, you may want to specify a directory to use for bayes. In my
local.cf, I use:
bayes_path /etc/mail/spamassassin/bayes/bayes
I do not use autowhitelist, or autolearn. If you want to use them, then
I hope someone else here can help you.
-=Aubrey=-
Re: mkdir /root/.spamassasin: permission denied error.
Posted by Matt Kettler <mk...@verizon.net>.
porterj wrote:
> I just set-up spamassassin on a Red Hat Enterprise Linux 4 mail server and it
> appears that spamassassin is working as I am seeing messages that are now
> tagged as spam.
>
> However, in my /var/log/maillog I keep seeing a message similar to the
> following and am unsure how to fix it. Any help would be appreciated.
>
Apparently you're calling spamc as root.
For safety, spamd will *NEVER* scan mail while executing as root, so it
is falling back to the user "nobody".
Normally, the bayes and AWL databases are stored in a user's home
directory, however, "nobody" does not have a home directory it can write
to (and should not to maintain security!).
I'm not sure how you've set things up for calling spamc. If you're doing
a "per user" config, this will pretty much only happen for mail going to
root, so no big deal.
If you're always calling spamc as root, I'd suggest creating a non-root
user account that has a home directory to scan mail as. You can get
spamc to use this user, instead of the current user, by adding "-u
scanuser" to your spamc command line.
Also be aware you'll need to su to this user before using sa-learn to
maintain your bayes DB, but that's not so bad.
> Begin message in /var/log/maillog
>
> Apr 12 10:27:44 servername spamd[18456]: spamd: setuid to root succeeded
> Apr 12 10:27:44 servername spamd[18456]: spamd: still running as root: user
> not specified with -u, not found, or set to root, falling back to nobody at
> /usr/bin/spamd line 1147, <GEN212> line 4.
> Apr 12 10:27:44 servername spamd[18456]: spamd: processing message
> <73...@web56611.mail.re3.yahoo.com> for root:99
> Apr 12 10:27:45 servername spamd[18456]: mkdir /root/.spamassassin:
> Permission denied at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin.pm
> line
> 1536
> Apr 12 10:27:45 servername spamd[18456]: locker: safe_lock: cannot create
> tmp lockfile /root/.spamassassin/auto-whitelist.lock.servername.domain.com
> .18456 for /root/.spamassassin/auto-whitelist.lock: Permission denied
> Apr 12 10:27:45 servername spamd[18456]: auto-whitelist: open of
> auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile
> /root/.spamassassin/auto-whitelist.lock.servername.domain.com.18456 for
> /root/.spamassassin/auto-whitelist.lock: Permission denied
> Apr 12 10:27:45 servername spamd[18456]: bayes: locker: safe_lock: cannot
> create tmp lockfile
> /root/.spamassassin/bayes.lock.servername.domain.com.18456 for
> /root/.spamassassin/bayes.lock: Permission denied
> Apr 12 10:27:45 servername spamd[18456]: spamd: clean message (0.0/3.5) for
> root:99 in 0.6 seconds, 8188 bytes.
> Apr 12 10:27:45 servername spamd[18456]: spamd: result: . 0 -
> scantime=0.6,size=8188,user=root,uid=99,required_score=3.5,rhost=servername,raddr=127.0.0.
> 1,rport=55310,mid=<73...@web56611.mail.re3.yahoo.com>,autolearn=failed
>
> End message in /var/log/maillog
>
> Thanks,
> JP
>