Bug Tracker item #2825171, was opened at 2009-07-22 06:38
Message generated for change (Settings changed) made by itetcu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1126467&aid=2825171&group_id=250683

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: daemon
Group: v3.9.0
Status: Open
Resolution: None
>Priority: 7
Private: No
Submitted By: dsoTm (dsotm)
>Assigned to: Ion-Mihai "IOnut" Tetcu (itetcu)
Summary: Bug with notifications

Initial Comment:
I posted this to the mailing list on 8/19/08 as a bug in the CVS at the time 
but it looks like it still exists. Compiling 3.9.0-Alpha2 on FreeBSD 7.2. 
According to the documentation notifications can be activated by copying the 
txt/ directory into DSPAM's home. However, it seems it is looking for them in 
SYSCONFDIR/txt instead. For example, I compiled with 
'--with-dspam-home=/var/db/dspam' and --sysconfdir is not set, so it is at the 
default of /usr/local/etc. Placing the notifications in /var/db/dspam/txt 
results in "freebsd dspam[90727]: Unable to open file for reading: 
firstrun.txt: No such file or directory". If I copy the txt directory in 
/usr/local/etc (so /usr/local/etc/txt) then notifcations work.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1126467&aid=2825171&group_id=250683

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Dspam-devel mailing list
Dspam-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-devel

Reply via email to