You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Giorgio Volpe <gi...@movi.fvg.it> on 2006/07/14 19:40:15 UTC

Problem with exim and spamd set for my own user (fall back to nobody?)

I'm running spamassassin

    SpamAssassin Server version 3.1.1
      running on Perl 5.8.8
      with SSL support (IO::Socket::SSL 0.97)

on a debian whith exim 4.62

I've set in /etc/defaults  -u spamd (a user I created ...)
and correctly I can see:

    # ps aux | grep spamd
    root     32646  0.1  4.8  28576 24820 ?        Ss   19:27   0:00
    /usr/sbin/spamd --create-prefs --max-children 5 --helper-home-dir -u
    spamd -d --pidfile=/var/run/spamd/spamd.pid
    102      32647  2.5  5.1  30720 26752 ?        S    19:27   0:11
    spamd child
    102      32648  0.0  4.5  28576 23348 ?        S    19:27   0:00
    spamd child
    root       306  0.0  0.1   2348   792 pts/2    S+   19:35   0:00
    grep spamd

But when exim tries to call spamd ... I get:

    Jul 14 19:28:01 movi spamd[32647]: spamd: connection from movifvg
    [127.0.0.1] at port 43554
    Jul 14 19:28:01 movi spamd[32647]: spamd: creating default_prefs:
    /nonexistent/.spamassassin/user_prefs
    Jul 14 19:28:01 movi spamd[32647]: config: cannot write to
    /nonexistent/.spamassassin/user_prefs: No such file or directory
    Jul 14 19:28:01 movi spamd[32647]: spamd: failed to create readable
    default_prefs: /nonexistent/.spamassassin/user_prefs
    Jul 14 19:28:01 movi spamd[32647]: mkdir /nonexistent: Permission
    denied at /usr/share/perl5/Mail/SpamAssassin.pm line 1469
    Jul 14 19:28:01 movi spamd[32647]: spamd: checking message
    <44...@movi.fvg.it> for nobody:102
                                                                                                                                                                   
    ^^^^^^^^^
    Jul 14 19:28:06 movi spamd[32647]: mkdir /nonexistent: Permission
    denied at /usr/share/perl5/Mail/SpamAssassin.pm line 1469
    Jul 14 19:28:06 movi spamd[32647]: locker: safe_lock: cannot create
    tmp lockfile
    /nonexistent/.spamassassin/auto-whitelist.lock.movi.fvg.it.32647 for
    /nonexistent/.spamassassin/auto-whitelist.lock: No such file or
    directoryJul 14 19:28:06 movi spamd[32647]: auto-whitelist: open of
    auto-whitelist file failed: locker: safe_lock: cannot create tmp
    lockfile
    /nonexistent/.spamassassin/auto-whitelist.lock.movi.fvg.it.32647 for
    /nonexistent/.spamassassin/auto-whitelist.lock: No such file or
    directory


why it falls back to nobody? (but correctly reporting 102, nobody on my 
system is 65534)

Any hint?

thanks

    Giorgio

Re: Problem with exim and spamd set for my own user (fall back to nobody?)

Posted by Stuart Johnston <st...@ebby.com>.
Are you using exiscan?  If so, you need something like this in your acl:

spam = spamd

See for full examples:

http://duncanthrax.net/exiscan-acl/exiscan-acl-examples.txt

Giorgio Volpe wrote:
> I'm running spamassassin
> 
>     SpamAssassin Server version 3.1.1
>       running on Perl 5.8.8
>       with SSL support (IO::Socket::SSL 0.97)
> 
> on a debian whith exim 4.62
> 
> I've set in /etc/defaults  -u spamd (a user I created ...)
> and correctly I can see:
> 
>     # ps aux | grep spamd
>     root     32646  0.1  4.8  28576 24820 ?        Ss   19:27   0:00
>     /usr/sbin/spamd --create-prefs --max-children 5 --helper-home-dir -u
>     spamd -d --pidfile=/var/run/spamd/spamd.pid
>     102      32647  2.5  5.1  30720 26752 ?        S    19:27   0:11
>     spamd child
>     102      32648  0.0  4.5  28576 23348 ?        S    19:27   0:00
>     spamd child
>     root       306  0.0  0.1   2348   792 pts/2    S+   19:35   0:00
>     grep spamd
> 
> But when exim tries to call spamd ... I get:
> 
>     Jul 14 19:28:01 movi spamd[32647]: spamd: connection from movifvg
>     [127.0.0.1] at port 43554
>     Jul 14 19:28:01 movi spamd[32647]: spamd: creating default_prefs:
>     /nonexistent/.spamassassin/user_prefs
>     Jul 14 19:28:01 movi spamd[32647]: config: cannot write to
>     /nonexistent/.spamassassin/user_prefs: No such file or directory
>     Jul 14 19:28:01 movi spamd[32647]: spamd: failed to create readable
>     default_prefs: /nonexistent/.spamassassin/user_prefs
>     Jul 14 19:28:01 movi spamd[32647]: mkdir /nonexistent: Permission
>     denied at /usr/share/perl5/Mail/SpamAssassin.pm line 1469
>     Jul 14 19:28:01 movi spamd[32647]: spamd: checking message
>     <44...@movi.fvg.it> for nobody:102
>                                                                                                                                                                    
>     ^^^^^^^^^
>     Jul 14 19:28:06 movi spamd[32647]: mkdir /nonexistent: Permission
>     denied at /usr/share/perl5/Mail/SpamAssassin.pm line 1469
>     Jul 14 19:28:06 movi spamd[32647]: locker: safe_lock: cannot create
>     tmp lockfile
>     /nonexistent/.spamassassin/auto-whitelist.lock.movi.fvg.it.32647 for
>     /nonexistent/.spamassassin/auto-whitelist.lock: No such file or
>     directoryJul 14 19:28:06 movi spamd[32647]: auto-whitelist: open of
>     auto-whitelist file failed: locker: safe_lock: cannot create tmp
>     lockfile
>     /nonexistent/.spamassassin/auto-whitelist.lock.movi.fvg.it.32647 for
>     /nonexistent/.spamassassin/auto-whitelist.lock: No such file or
>     directory
> 
> 
> why it falls back to nobody? (but correctly reporting 102, nobody on my 
> system is 65534)
> 
> Any hint?
> 
> thanks
> 
>     Giorgio


Re: Problem with exim and spamd set for my own user (fall back to nobody?)

Posted by Theo Van Dinter <fe...@apache.org>.
On Fri, Jul 14, 2006 at 07:40:15PM +0200, Giorgio Volpe wrote:
> why it falls back to nobody? (but correctly reporting 102, nobody on my 
> system is 65534)
> 
> Any hint?

spamc is apparently being run by nobody, and that information gets passed
to spamd.  Perhaps you want to run spamd with -x?

-- 
Randomly Generated Tagline:
"> I'm an idiot.. At least this [bug] took about 5 minutes to find..
  We need to find some new terms to describe the rest of us mere mortals
  then." - Craig Schlenter in response to Linus Torvalds about a kernel bug.