spamd in blacklist only mode

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

spamd in blacklist only mode

Maurice Janssen-2
Hi,

If I understand the man pages correctly, you should start both spamd and
spamd-setup with the -b option when you want to use spamd in blacklist
only mode.
In /etc/rc.d/spamd, the -b option is set when you have spamd_black=yes
in your rc.conf.local.
However, spamd-setup is always started with -D only from /etc/rc. It
doesn't check for the spamd_black environment variable and therefore set -b.

So it seems that you have to adapt /etc/rc when you want to run spamd in
blacklist only mode.

This seems a bit odd, doesn't it?  Am I missing something, or is this
intended?

Thanks,
Maurice

Reply | Threaded
Open this post in threaded view
|

Re: spamd in blacklist only mode

Jason McIntyre-2
On Sun, Dec 08, 2013 at 07:59:48PM +0100, Maurice Janssen wrote:

> Hi,
>
> If I understand the man pages correctly, you should start both spamd and
> spamd-setup with the -b option when you want to use spamd in blacklist only
> mode.
> In /etc/rc.d/spamd, the -b option is set when you have spamd_black=yes in
> your rc.conf.local.
> However, spamd-setup is always started with -D only from /etc/rc. It doesn't
> check for the spamd_black environment variable and therefore set -b.
>
> So it seems that you have to adapt /etc/rc when you want to run spamd in
> blacklist only mode.
>
> This seems a bit odd, doesn't it?  Am I missing something, or is this
> intended?
>
> Thanks,
> Maurice
>

you shouldn;t have to mess about with the rc.d stuff at all.

you run spamd with the -b flag on the command line, or set spamd_black
in rc.conf.local.

then, following through the man page:

        spamd-setup(8) should be run periodically by cron(8).  When
        run in blacklist-only mode, the -b flag should be specified.
        Use crontab(1) to uncomment the entry in root's crontab.

hope that's clear.

jmc

Reply | Threaded
Open this post in threaded view
|

Re: spamd in blacklist only mode

Maurice Janssen-2
On 12/09/13 08:41, Jason McIntyre wrote:

> On Sun, Dec 08, 2013 at 07:59:48PM +0100, Maurice Janssen wrote:
>> Hi,
>>
>> If I understand the man pages correctly, you should start both spamd and
>> spamd-setup with the -b option when you want to use spamd in blacklist only
>> mode.
>> In /etc/rc.d/spamd, the -b option is set when you have spamd_black=yes in
>> your rc.conf.local.
>> However, spamd-setup is always started with -D only from /etc/rc. It doesn't
>> check for the spamd_black environment variable and therefore set -b.
>>
>> So it seems that you have to adapt /etc/rc when you want to run spamd in
>> blacklist only mode.
>>
>> This seems a bit odd, doesn't it?  Am I missing something, or is this
>> intended?
>>
>> Thanks,
>> Maurice
>>
> you shouldn;t have to mess about with the rc.d stuff at all.
>
> you run spamd with the -b flag on the command line, or set spamd_black
> in rc.conf.local.
>
> then, following through the man page:
>
>          spamd-setup(8) should be run periodically by cron(8).  When
>          run in blacklist-only mode, the -b flag should be specified.
>          Use crontab(1) to uncomment the entry in root's crontab.
>
> hope that's clear.
>
> jmc
>

Thanks, the cron part is clear. When spamd-setup is run from cron (with
-b), spamd-setup downloads the blacklists as configured in spamd.conf
and sends the data to the pf table <spamd> and to the spamd process.  So
far so good.

But when spamd-setup is run during boot from /etc/rc (without -b), it
doesn't send the IPs from the blacklists to pf.   Therefore, connections
from blacklisted IP's are not redirected to spamd and spamd is not
operational until spamd-setup is run from crontab (with -b).  This can
take up to an hour with the default crontab entry. Not a big deal, but
annoying.

So why not check for spamd_black in /etc/rc and run spamd-setup with -b
in case it is set?

Maurice

Reply | Threaded
Open this post in threaded view
|

Re: spamd in blacklist only modexd

Jason McIntyre-2
On Mon, Dec 09, 2013 at 10:35:36PM +0100, Maurice Janssen wrote:

> On 12/09/13 08:41, Jason McIntyre wrote:
> >On Sun, Dec 08, 2013 at 07:59:48PM +0100, Maurice Janssen wrote:
> >>Hi,
> >>
> >>If I understand the man pages correctly, you should start both spamd and
> >>spamd-setup with the -b option when you want to use spamd in blacklist only
> >>mode.
> >>In /etc/rc.d/spamd, the -b option is set when you have spamd_black=yes in
> >>your rc.conf.local.
> >>However, spamd-setup is always started with -D only from /etc/rc. It doesn't
> >>check for the spamd_black environment variable and therefore set -b.
> >>
> >>So it seems that you have to adapt /etc/rc when you want to run spamd in
> >>blacklist only mode.
> >>
> >>This seems a bit odd, doesn't it?  Am I missing something, or is this
> >>intended?
> >>
> >>Thanks,
> >>Maurice
> >>
> >you shouldn;t have to mess about with the rc.d stuff at all.
> >
> >you run spamd with the -b flag on the command line, or set spamd_black
> >in rc.conf.local.
> >
> >then, following through the man page:
> >
> >         spamd-setup(8) should be run periodically by cron(8).  When
> >         run in blacklist-only mode, the -b flag should be specified.
> >         Use crontab(1) to uncomment the entry in root's crontab.
> >
> >hope that's clear.
> >
> >jmc
> >
>
> Thanks, the cron part is clear. When spamd-setup is run from cron (with -b),
> spamd-setup downloads the blacklists as configured in spamd.conf and sends
> the data to the pf table <spamd> and to the spamd process.  So far so good.
>
> But when spamd-setup is run during boot from /etc/rc (without -b), it
> doesn't send the IPs from the blacklists to pf.   Therefore, connections
> from blacklisted IP's are not redirected to spamd and spamd is not
> operational until spamd-setup is run from crontab (with -b).  This can take
> up to an hour with the default crontab entry. Not a big deal, but annoying.
>
> So why not check for spamd_black in /etc/rc and run spamd-setup with -b in
> case it is set?
>
> Maurice
>

hi. i'm not the right person to answer that question. feel free to
mail a diff to tech and see if anyone replies.

you'll be aware, obviously, that you can tweak the crontab entry
to your liking if the suggested example doesn;t suit.

jmc

Reply | Threaded
Open this post in threaded view
|

Re: spamd in blacklist only modexd

Alexander Hall
On 12/10/13 08:28, Jason McIntyre wrote:

> On Mon, Dec 09, 2013 at 10:35:36PM +0100, Maurice Janssen wrote:
>> On 12/09/13 08:41, Jason McIntyre wrote:
>>> On Sun, Dec 08, 2013 at 07:59:48PM +0100, Maurice Janssen wrote:
>>>> Hi,
>>>>
>>>> If I understand the man pages correctly, you should start both spamd and
>>>> spamd-setup with the -b option when you want to use spamd in blacklist only
>>>> mode.
>>>> In /etc/rc.d/spamd, the -b option is set when you have spamd_black=yes in
>>>> your rc.conf.local.
>>>> However, spamd-setup is always started with -D only from /etc/rc. It doesn't
>>>> check for the spamd_black environment variable and therefore set -b.
>>>>
>>>> So it seems that you have to adapt /etc/rc when you want to run spamd in
>>>> blacklist only mode.
>>>>
>>>> This seems a bit odd, doesn't it?  Am I missing something, or is this
>>>> intended?
>>>>
>>>> Thanks,
>>>> Maurice
>>>>
>>> you shouldn;t have to mess about with the rc.d stuff at all.
>>>
>>> you run spamd with the -b flag on the command line, or set spamd_black
>>> in rc.conf.local.
>>>
>>> then, following through the man page:
>>>
>>>          spamd-setup(8) should be run periodically by cron(8).  When
>>>          run in blacklist-only mode, the -b flag should be specified.
>>>          Use crontab(1) to uncomment the entry in root's crontab.
>>>
>>> hope that's clear.
>>>
>>> jmc
>>>
>>
>> Thanks, the cron part is clear. When spamd-setup is run from cron (with -b),
>> spamd-setup downloads the blacklists as configured in spamd.conf and sends
>> the data to the pf table <spamd> and to the spamd process.  So far so good.
>>
>> But when spamd-setup is run during boot from /etc/rc (without -b), it
>> doesn't send the IPs from the blacklists to pf.   Therefore, connections
>> from blacklisted IP's are not redirected to spamd and spamd is not
>> operational until spamd-setup is run from crontab (with -b).  This can take
>> up to an hour with the default crontab entry. Not a big deal, but annoying.
>>
>> So why not check for spamd_black in /etc/rc and run spamd-setup with -b in
>> case it is set?
>>
>> Maurice
>>
>
> hi. i'm not the right person to answer that question. feel free to
> mail a diff to tech and see if anyone replies.
>
> you'll be aware, obviously, that you can tweak the crontab entry
> to your liking if the suggested example doesn;t suit.
>
> jmc
>

The OP is referring to this part of /etc/rc, which has nothing to do
with neither crontab nor /etc/rc.d/*.

if [ X"${spamd_flags}" != X"NO" ]; then
         /usr/libexec/spamd-setup -D
fi

Indeed, please suggest a diff.

Maybe we should just incorporate that into /etc/rc.d/spamd instead?

/Alexander

Reply | Threaded
Open this post in threaded view
|

Re: spamd in blacklist only modexd

Craig Skinner-3
On 2013-12-10 Tue 09:26 AM |, Alexander Hall wrote:

>
> The OP is referring to this part of /etc/rc, which has nothing to do
> with neither crontab nor /etc/rc.d/*.
>
> if [ X"${spamd_flags}" != X"NO" ]; then
>         /usr/libexec/spamd-setup -D
> fi
>
> Indeed, please suggest a diff.
>
> Maybe we should just incorporate that into /etc/rc.d/spamd instead?
>

This has worked OK for me for a few months:


Index: rc
===================================================================
RCS file: /cvs/src/etc/rc,v
retrieving revision 1.407
diff -u -u -p -r1.407 rc
--- rc 9 Aug 2013 16:24:54 -0000 1.407
+++ rc 10 Dec 2013 12:59:49 -0000
@@ -499,10 +499,6 @@ start_daemon rbootd mopd popa3d spamd sp
 start_daemon ipropd_master ipropd_slave sndiod
 echo '.'
 
-if [ X"${spamd_flags}" != X"NO" ]; then
- /usr/libexec/spamd-setup -D
-fi
-
 # If rc.firstime exists, run it just once, and make sure it is deleted
 if [ -f /etc/rc.firsttime ]; then
  mv /etc/rc.firsttime /etc/rc.firsttime.run
Index: rc.d/spamd
===================================================================
RCS file: /cvs/src/etc/rc.d/spamd,v
retrieving revision 1.3
diff -u -u -p -r1.3 spamd
--- rc.d/spamd 13 Sep 2013 14:50:56 -0000 1.3
+++ rc.d/spamd 10 Dec 2013 12:59:49 -0000
@@ -1,18 +1,23 @@
 #!/bin/sh
 #
-# $OpenBSD: spamd,v 1.3 2013/09/13 14:50:56 okan Exp $
+# $OpenBSD: spamd,v 1.4 2013/09/05 19:08:22 skinner Exp $
 
-daemon="/usr/libexec/spamd"
+daemon='/usr/libexec/spamd'
 
 . /etc/rc.d/rc.subr
 
 pexp="spamd: \[priv\]"
 rc_reload=NO
 
-rc_pre() {
- [ X"${spamd_black}" != X"NO" ] && \
- daemon_flags="-b ${daemon_flags}"
- return 0
+rc_pre()
+{
+ [[ ${spamd_black} == 'NO' ]] || daemon_flags="-b ${daemon_flags}"
+}
+
+rc_start()
+{
+ ${rcexec} "${daemon} ${daemon_flags} ${_bg}"
+ rc_do rc_wait start && ${daemon}-setup -D
 }
 
 rc_cmd $1



Cheers,
--
Craig Skinner | http://twitter.com/Craig_Skinner | http://linkd.in/yGqkv7

Reply | Threaded
Open this post in threaded view
|

Re: spamd in blacklist only modexd

Maurice Janssen-2
On 12/10/13 14:03, Craig R. Skinner wrote:

> On 2013-12-10 Tue 09:26 AM |, Alexander Hall wrote:
>> The OP is referring to this part of /etc/rc, which has nothing to do
>> with neither crontab nor /etc/rc.d/*.
>>
>> if [ X"${spamd_flags}" != X"NO" ]; then
>>          /usr/libexec/spamd-setup -D
>> fi
>>
>> Indeed, please suggest a diff.
>>
>> Maybe we should just incorporate that into /etc/rc.d/spamd instead?
>>
> This has worked OK for me for a few months:
>
>
> Index: rc
> ===================================================================
> RCS file: /cvs/src/etc/rc,v
> retrieving revision 1.407
> diff -u -u -p -r1.407 rc
> --- rc 9 Aug 2013 16:24:54 -0000 1.407
> +++ rc 10 Dec 2013 12:59:49 -0000
> @@ -499,10 +499,6 @@ start_daemon rbootd mopd popa3d spamd sp
>   start_daemon ipropd_master ipropd_slave sndiod
>   echo '.'
>  
> -if [ X"${spamd_flags}" != X"NO" ]; then
> - /usr/libexec/spamd-setup -D
> -fi
> -
>   # If rc.firstime exists, run it just once, and make sure it is deleted
>   if [ -f /etc/rc.firsttime ]; then
>   mv /etc/rc.firsttime /etc/rc.firsttime.run
> Index: rc.d/spamd
> ===================================================================
> RCS file: /cvs/src/etc/rc.d/spamd,v
> retrieving revision 1.3
> diff -u -u -p -r1.3 spamd
> --- rc.d/spamd 13 Sep 2013 14:50:56 -0000 1.3
> +++ rc.d/spamd 10 Dec 2013 12:59:49 -0000
> @@ -1,18 +1,23 @@
>   #!/bin/sh
>   #
> -# $OpenBSD: spamd,v 1.3 2013/09/13 14:50:56 okan Exp $
> +# $OpenBSD: spamd,v 1.4 2013/09/05 19:08:22 skinner Exp $
>  
> -daemon="/usr/libexec/spamd"
> +daemon='/usr/libexec/spamd'
>  
>   . /etc/rc.d/rc.subr
>  
>   pexp="spamd: \[priv\]"
>   rc_reload=NO
>  
> -rc_pre() {
> - [ X"${spamd_black}" != X"NO" ] && \
> - daemon_flags="-b ${daemon_flags}"
> - return 0
> +rc_pre()
> +{
> + [[ ${spamd_black} == 'NO' ]] || daemon_flags="-b ${daemon_flags}"
> +}
> +
> +rc_start()
> +{
> + ${rcexec} "${daemon} ${daemon_flags} ${_bg}"
> + rc_do rc_wait start && ${daemon}-setup -D
>   }
>  
>   rc_cmd $1
>
>
>
> Cheers,

Nice, but this also fails to add -b to spamd-setup.  How about this (and
of course remove the spamd-setup bits from /etc/rc):

--- spamd.orig  Tue Dec 10 21:24:48 2013
+++ spamd       Tue Dec 10 21:24:14 2013
@@ -15,4 +15,12 @@
         return 0
  }

+rc_start() {
+       ${rcexec} "${daemon} ${daemon_flags} ${_bg}"
+       spamd_setup_flags="-D"
+       [ X"${spamd_black}" != X"NO" ] && \
+               spamd_setup_flags="-b ${spamd_setup_flags}"
+       rc_do rc_wait start && /usr/libexec/spamd-setup ${spamd_setup_flags}
+}
+
  rc_cmd $1

Reply | Threaded
Open this post in threaded view
|

Re: spamd in blacklist only modexd

Alexander Hall
In reply to this post by Craig Skinner-3
On 12/10/13 14:03, Craig R. Skinner wrote:

> On 2013-12-10 Tue 09:26 AM |, Alexander Hall wrote:
>>
>> The OP is referring to this part of /etc/rc, which has nothing to do
>> with neither crontab nor /etc/rc.d/*.
>>
>> if [ X"${spamd_flags}" != X"NO" ]; then
>>          /usr/libexec/spamd-setup -D
>> fi
>>
>> Indeed, please suggest a diff.
>>
>> Maybe we should just incorporate that into /etc/rc.d/spamd instead?
>>
>
> This has worked OK for me for a few months:
>
>
> Index: rc
> ===================================================================
> RCS file: /cvs/src/etc/rc,v
> retrieving revision 1.407
> diff -u -u -p -r1.407 rc
> --- rc 9 Aug 2013 16:24:54 -0000 1.407
> +++ rc 10 Dec 2013 12:59:49 -0000
> @@ -499,10 +499,6 @@ start_daemon rbootd mopd popa3d spamd sp
>   start_daemon ipropd_master ipropd_slave sndiod
>   echo '.'
>
> -if [ X"${spamd_flags}" != X"NO" ]; then
> - /usr/libexec/spamd-setup -D
> -fi
> -

yes

>   # If rc.firstime exists, run it just once, and make sure it is deleted
>   if [ -f /etc/rc.firsttime ]; then
>   mv /etc/rc.firsttime /etc/rc.firsttime.run
> Index: rc.d/spamd
> ===================================================================
> RCS file: /cvs/src/etc/rc.d/spamd,v
> retrieving revision 1.3
> diff -u -u -p -r1.3 spamd
> --- rc.d/spamd 13 Sep 2013 14:50:56 -0000 1.3
> +++ rc.d/spamd 10 Dec 2013 12:59:49 -0000
> @@ -1,18 +1,23 @@
>   #!/bin/sh
>   #
> -# $OpenBSD: spamd,v 1.3 2013/09/13 14:50:56 okan Exp $
> +# $OpenBSD: spamd,v 1.4 2013/09/05 19:08:22 skinner Exp $
>
> -daemon="/usr/libexec/spamd"
> +daemon='/usr/libexec/spamd'

noise

>
>   . /etc/rc.d/rc.subr
>
>   pexp="spamd: \[priv\]"
>   rc_reload=NO
>
> -rc_pre() {
> - [ X"${spamd_black}" != X"NO" ] && \
> - daemon_flags="-b ${daemon_flags}"
> - return 0
> +rc_pre()
> +{
> + [[ ${spamd_black} == 'NO' ]] || daemon_flags="-b ${daemon_flags}"
> +}

noise (and ksh syntax)

> +
> +rc_start()
> +{
> + ${rcexec} "${daemon} ${daemon_flags} ${_bg}"
> + rc_do rc_wait start && ${daemon}-setup -D

useful, but IMO in wrong order and misses the -b flag.

/Alexander

>   }
>
>   rc_cmd $1
>
>
>
> Cheers,

Reply | Threaded
Open this post in threaded view
|

Re: spamd in blacklist only modexd

Alexander Hall
In reply to this post by Maurice Janssen-2
On 12/10/13 21:38, Maurice Janssen wrote:

> On 12/10/13 14:03, Craig R. Skinner wrote:
>> On 2013-12-10 Tue 09:26 AM |, Alexander Hall wrote:
>>> The OP is referring to this part of /etc/rc, which has nothing to do
>>> with neither crontab nor /etc/rc.d/*.
>>>
>>> if [ X"${spamd_flags}" != X"NO" ]; then
>>>          /usr/libexec/spamd-setup -D
>>> fi
>>>
>>> Indeed, please suggest a diff.
>>>
>>> Maybe we should just incorporate that into /etc/rc.d/spamd instead?
>>>
>> This has worked OK for me for a few months:
>>
>>
>> Index: rc
>> ===================================================================
>> RCS file: /cvs/src/etc/rc,v
>> retrieving revision 1.407
>> diff -u -u -p -r1.407 rc
>> --- rc    9 Aug 2013 16:24:54 -0000    1.407
>> +++ rc    10 Dec 2013 12:59:49 -0000
>> @@ -499,10 +499,6 @@ start_daemon rbootd mopd popa3d spamd sp
>>   start_daemon ipropd_master ipropd_slave sndiod
>>   echo '.'
>> -if [ X"${spamd_flags}" != X"NO" ]; then
>> -    /usr/libexec/spamd-setup -D
>> -fi
>> -
>>   # If rc.firstime exists, run it just once, and make sure it is deleted
>>   if [ -f /etc/rc.firsttime ]; then
>>       mv /etc/rc.firsttime /etc/rc.firsttime.run
>> Index: rc.d/spamd
>> ===================================================================
>> RCS file: /cvs/src/etc/rc.d/spamd,v
>> retrieving revision 1.3
>> diff -u -u -p -r1.3 spamd
>> --- rc.d/spamd    13 Sep 2013 14:50:56 -0000    1.3
>> +++ rc.d/spamd    10 Dec 2013 12:59:49 -0000
>> @@ -1,18 +1,23 @@
>>   #!/bin/sh
>>   #
>> -# $OpenBSD: spamd,v 1.3 2013/09/13 14:50:56 okan Exp $
>> +# $OpenBSD: spamd,v 1.4 2013/09/05 19:08:22 skinner Exp $
>> -daemon="/usr/libexec/spamd"
>> +daemon='/usr/libexec/spamd'
>>   . /etc/rc.d/rc.subr
>>   pexp="spamd: \[priv\]"
>>   rc_reload=NO
>> -rc_pre() {
>> -    [ X"${spamd_black}" != X"NO" ] && \
>> -        daemon_flags="-b ${daemon_flags}"
>> -    return 0
>> +rc_pre()
>> +{
>> +    [[ ${spamd_black} == 'NO' ]] || daemon_flags="-b ${daemon_flags}"
>> +}
>> +
>> +rc_start()
>> +{
>> +    ${rcexec} "${daemon} ${daemon_flags} ${_bg}"
>> +    rc_do rc_wait start && ${daemon}-setup -D
>>   }
>>   rc_cmd $1
>>
>>
>>
>> Cheers,
>
> Nice, but this also fails to add -b to spamd-setup.  How about this (and
> of course remove the spamd-setup bits from /etc/rc):
>
> --- spamd.orig  Tue Dec 10 21:24:48 2013
> +++ spamd       Tue Dec 10 21:24:14 2013
> @@ -15,4 +15,12 @@
>          return 0
>   }
>
> +rc_start() {
> +       ${rcexec} "${daemon} ${daemon_flags} ${_bg}"
> +       spamd_setup_flags="-D"
> +       [ X"${spamd_black}" != X"NO" ] && \
> +               spamd_setup_flags="-b ${spamd_setup_flags}"
> +       rc_do rc_wait start && /usr/libexec/spamd-setup
> ${spamd_setup_flags}
> +}

This seems like the wrong order. Currently, we run spamd-setup prior to
starting spamd, which sounds more appropriate to me.

I'd suggest the following, but I leave the decision to people working
in this area. Untested.

rc_start() {
        local _setup=-D
        [ X"${spamd_black}" != X"NO" ] && _setup="-b $_setup"
        /usr/libexec/spamd-setup $_setup
        ${rcexec} "${daemon} ${daemon_flags} ${_bg}"
}

/Alexander

> +
>   rc_cmd $1

Reply | Threaded
Open this post in threaded view
|

Re: spamd in blacklist only modexd

Maurice Janssen-2
On 12/11/13 21:06, Alexander Hall wrote:

> On 12/10/13 21:38, Maurice Janssen wrote:
>>
>> How about this (and of course remove the spamd-setup bits from /etc/rc):
>>
>> --- spamd.orig  Tue Dec 10 21:24:48 2013
>> +++ spamd       Tue Dec 10 21:24:14 2013
>> @@ -15,4 +15,12 @@
>>          return 0
>>   }
>>
>> +rc_start() {
>> +       ${rcexec} "${daemon} ${daemon_flags} ${_bg}"
>> +       spamd_setup_flags="-D"
>> +       [ X"${spamd_black}" != X"NO" ] && \
>> +               spamd_setup_flags="-b ${spamd_setup_flags}"
>> +       rc_do rc_wait start && /usr/libexec/spamd-setup
>> ${spamd_setup_flags}
>> +}
>
> This seems like the wrong order. Currently, we run spamd-setup prior to
> starting spamd, which sounds more appropriate to me.
>

Are you sure?  In /etc/rc, spamd-setup is run after spamd and spamlogd.  
Seems more appropriate to me, as spamd-setup sends blacklist data to spamd.

Maurice

Reply | Threaded
Open this post in threaded view
|

Re: spamd in blacklist only modexd

Alexander Hall
On 12/11/13 21:23, Maurice Janssen wrote:

> On 12/11/13 21:06, Alexander Hall wrote:
>> On 12/10/13 21:38, Maurice Janssen wrote:
>>>
>>> How about this (and of course remove the spamd-setup bits from /etc/rc):
>>>
>>> --- spamd.orig  Tue Dec 10 21:24:48 2013
>>> +++ spamd       Tue Dec 10 21:24:14 2013
>>> @@ -15,4 +15,12 @@
>>>          return 0
>>>   }
>>>
>>> +rc_start() {
>>> +       ${rcexec} "${daemon} ${daemon_flags} ${_bg}"
>>> +       spamd_setup_flags="-D"
>>> +       [ X"${spamd_black}" != X"NO" ] && \
>>> +               spamd_setup_flags="-b ${spamd_setup_flags}"
>>> +       rc_do rc_wait start && /usr/libexec/spamd-setup
>>> ${spamd_setup_flags}
>>> +}
>>
>> This seems like the wrong order. Currently, we run spamd-setup prior to
>> starting spamd, which sounds more appropriate to me.
>>
>
> Are you sure?  In /etc/rc, spamd-setup is run after spamd and spamlogd.
> Seems more appropriate to me, as spamd-setup sends blacklist data to spamd.

Crap, yes. I was thinking of spamd as a package being run through
$pkg_scripts.

Indeed my suggestion makes less sense.

/Alexander

>
> Maurice