It is not a packaging issue because otherwise I should have it too.

I am also on FreeBSD and I am also using the port.
After installing the port I used the startup script in /usr/local/etc/rc.d/ to 
start dspam.

Dspam is started like this: /usr/local/bin/dspam –daemon

Who is the owner of 
/var/run/dspam/
/var/db/dspam/ 

Can dspam create /var/run/dspam.sock ?


On 06/11/2016, 10:08, "Colin Brace" <c...@lim.nl> wrote:

    Hi all,
    
    I am encountering what appears to be a packaging issue specific to the
    FreeBSD port, but I'm not entirely sure.
    
    Previously, dspam on FreeBSD ran as root. This changed with release
    v3.10.2_2 dspam which was released in May. From files/UPDATING:
    
    # dspam-3.10.2_2
    #
    
    Port Changes:
    - Runs as dspam:dspam instead of root:mail [1]
    - Default run directory is now /var/run/dspam [1]
    - Default daemon/client communication port is now 2424 [1]
    - New SETUID option to enable old insecure behavior [1]
    
    [1] Questionable ownership and security on mail/dspam (PR #115957)
    
    However, after installing and restarting it, I am unable to get this latest
    version to work. I see this error in maillog:
    
    Nov  2 14:17:07 galatea dspam[94824]: Daemon process starting
    Nov  2 14:17:07 galatea dspam[94824]: Creating local domain socket
    /var/run/dspam.sock
    Nov  2 14:17:07 galatea dspam[94824]: Daemon mode failed to start
    Nov  2 14:17:07 galatea dspam[94824]: Daemon process exiting
    Nov  2 14:19:37 galatea dspam[94843]: Unable to determine the destination
    user
    Nov  2 14:19:37 galatea dspam[94843]: DSPAM agent misconfigured: aborting
    
    If I revert to the previous version, dspam runs fine.
    
    >From the dspam man page:
    
    --user user1 user2 ... userN
                  Specifies the destination users of the incoming message. In
    most
                  cases this is the local user on the system, however some
                  implementations may call for virtual usernames, specific to
                  DSPAM, to be assigned.  The agent processes an incoming
    message
                  once for each user specified. If the message is to be
    delivered,
                  the $u (or %u) parameters of the argument string will be
                  interpolated for the current user being processed.
    
    I'm familiar with "--user" , as I have configured a Roundcube mail plugin to
    use for retraining messages incorrectly classified by dspam and this is one
    of the commmand-line parameters.
    
    However, the previous version of dspam running as root in daemon mode didn't
    require a destination user, AFAIK. Why am I encountering this error now?
    
    Any ideas?
    
    Thanks in advance.
    
    Colin
    
      
    
    
    
    
    
    
    
    
    
    
    --
    View this message in context: 
http://dspam-users.2290790.n4.nabble.com/dspam-daemon-mode-destination-user-error-tp4642071.html
    Sent from the dspam users mailing list archive at Nabble.com.
    
    
------------------------------------------------------------------------------
    Developer Access Program for Intel Xeon Phi Processors
    Access to Intel Xeon Phi processor-based developer platforms.
    With one year of Intel Parallel Studio XE.
    Training and support from Colfax.
    Order your platform today. http://sdm.link/xeonphi
    _______________________________________________
    Dspam-user mailing list
    Dspam-user@lists.sourceforge.net
    https://lists.sourceforge.net/lists/listinfo/dspam-user
    
    



------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Dspam-user mailing list
Dspam-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-user

Reply via email to