Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Spamd

    Scheduled Pinned Locked Moved pfSense Packages
    4 Posts 3 Posters 3.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P Offline
      peerx
      last edited by

      Is SPAMD working on PfSense 1.2.3?

      1 Reply Last reply Reply Quote 0
      • D Offline
        docjay
        last edited by

        I would like to know this too.  I see a few posts about spamd being confirmed broken in 1.2.1 by cheesyboofs & capitangiaco back in March, but nothing more after that.  It would be great to get spamd running correctly on 1.2.3!  Can anyone confirm this?

        -thanks

        1 Reply Last reply Reply Quote 0
        • D Offline
          docjay
          last edited by

          So, now I know what cheesyboofs went through  :o…I wish this package would play nice with 1.2.3 nano, but it doesn't.  Nor, do I have the expertise to fix the package so that it does.

          some things I've noticed that has to be done initially is give the user '_spamd' the correct permissions.

          1. 'pw user mod_spamd -u 0' to get rid of the errors in the log that state this: '/sbin/pfctl returned status 1'.  From what I have read this error is happening because the user '_spamd' doesn't have the correct rights according to this bug at the bottom of this link:  http://www.openbsd.org/cgi-bin/man.cgi?query=spamd&sektion=8
          BUGS
               spamd currently uses the user ``_spamd'' outside a chroot jail when run-
               ning in default mode, and requires the greylisting database in
               /var/db/spamd to be owned by the ``_spamd'' user.  This is wrong and
               should change to a distinct user from the one used by the chrooted spamd
               process.
          
          
          1. spamd-setup is looking for spamd.conf in /usr/local/etc/spamd, not /usr/local/etc/ as indicated in the documentation, so it won't load the black or white lists because of this.  After the package install the only thing in the /usr/local/etc/spamd folder is the file spamd.conf.sample.  After I made the spamd.conf file from copying the spamd.conf.sample file in the folder and stopped spamd and started it in the shell with:  '/usr/local/etc/rc.d/spamd.sh start' I got this returned to me:
          Getting http://www.openbsd.org/spamd/traplist.gz
          cerberus:/usr/local/etc/spamd#  blacklist uatraps 54496 entries
          Getting http://www.openbsd.org/spamd/nixspam.gz
          blacklist nixspam 40000 entries
          Getting http://www.openbsd.org/spamd/chinacidr.txt.gz
          blacklist china 718 entries
          Getting http://www.openbsd.org/spamd/koreacidr.txt.gz
          blacklist korea 431 entries
          
          

          –-but the GUI still didn't show any entries in the 'SPAMD Database'
          3)  I'm sure there a few more changes that need to happen but I have yet to find the next step to get this package running correctly.  I would be freakin awesome if SPAMD would run.

          I know Sullrich did an extensive overhaul to this package like crazy http://forum.pfsense.org/index.php/topic,526.0.html in January '06 but maybe he can take a look at it again to make sure it works with 1.2.3 nano & HDD install if he has time?   ;)

          I know that we all appreciate his hard work on it in addition to PFSense overall!

          1 Reply Last reply Reply Quote 0
          • D Offline
            danswartz
            last edited by

            I set up for default greylist mode, and noticed nothing was getting thru even after changing the passtime to 5 minutes.  I STF and found the _spamd user issue.  Fixed that.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.