Vince LaMonica wrote:
On Tue, 13 Jan 2009, Kyle Johnson wrote:
} I think your problem might be "Opt in". When using an Opt in configuration,
} users must opt in for filtering with a user preference. Try changing "Opt in"
} to "Opt out" in your dspam.conf file, restarting your daemon, and then seeing
} what is up. When using "Opt out", users are automatically oppted in, and if
} they want, they can then opt out.
Thanks, Kyle, but I really don't [yet] want to go that route. While
testing, I only want one user [vjl, me] to be opted in while I go through
testing this out. It's much easier to opt in one user than opt out all the
rest! :) Perhaps I am not opting myself in correctly? I simply touched
[created a blank file] at: /usr/local/var/dspam/opt-in/vjl.dspan
Oh. Umm..
Bleep.
That says, "vjl.dspan", not "vjl.dspam". Ok, I just fixed my dumb typo,
restarted dspam --daemon as well as postfix and sent myself some e.mail
from another server. I'm still not getting a signature in the e.mail body
[nor header, which is where i eventually want the signature to be, but one
step at a time]. There is still no dspam log file and no history file for
user vjl. I would have expected dspam to log the fact that it had been
started/stopped at least. Does the vjl.dspam file need to contain
anything? Does the fact that I started dspam --daemon as root matter?
Should I be starting it as user dspam? [and if so, i guess i would need to
give user dspam a shell other than /bin/false :) ].
I'm getting closer [i hope!]. What else am I missing?
Thanks again!
/vjl/
I can certainly understand what you are saying. I noticed that you
compiled with --enable-preferences-extension and as such, perhaps dspam
is looking for the Opt in in the database, and not the flat file - README:
Opt-In/Out
If you would like your users to be able to opt in/out of DSPAM filtering,
add the correct option to the nav_preferences.html template, depending on
your configuration (for example, if you have an opt-in system, you'll want to
add the opt-in option). Note: This currently only works with the preferences
extension, and not drop files.
<INPUT TYPE=CHECKBOX NAME=optIn $C_OPTIN$>
Opt into DSPAM filtering
<INPUT TYPE=CHECKBOX NAME=optOut $C_OPTOUT$>
Opt out of DSPAM filtering
That leads me to believe that, when using preferences extension, you
should be storing the opt information in the database. Give that a shot.
I am pretty sure that dspam does not log that it is starting / stopping
(which it should). As far as what user to run dspam as, starting it as
root shouldn't matter, but it should be owned by user dspam, with the
sticky bit set (chmod 4510 ?). This will run dspam as dspam, and should
help with permissions problems with the WebUI, when trying to access
data in dspam's home directory. Short answer: No - starting dspam as
root doesn't matter.
-Kyle
!DSPAM:1011,496cc042150921061010409!
