need to figure out a nicer way of using CLOUD_BASE
in scripts like move spams, so there can be a generalized
thing that anyone could use, instead of it depending on my specific cloud
structure.
##############
- # logged historical file where we append our latest report.
-# define_yeti_variable FRED_HAMSTER_OVERLOAD_REPORT_FILE="$CLOUD_BASE/stats/overload_history.txt"
-
- ##############
-
# set the SHUNIT_PATH so our shunit tests can find the codebase.
define_yeti_variable SHUNIT_PATH="$FEISTY_MEOW_SCRIPTS/testkit/shunit"
SPAM_SPOOL="/var/spool/sa-exim"
# a temporary directory where we'll move all the spam for analysis.
SPAM_HOLD="$HOME/spamcrud"
+
# the white list needs to be a file of good email addresses that will
# probably never send spam. it should be formatted one address to a line.
EMAIL_WHITE_LIST="$CLOUD_BASE/magic_cabinet/lists/email_addresses.txt"
+#hmmm: very personal and specific location for that file!!!
+
# we'll save a report of the spam checks in the file below.
REPORT_FILE="$HOME/spam_check_report_$(date_stringer).txt"