I'm not sure where the text "[EMAIL PROTECTED]" came from -- the mailing
list software shouldn't have made that substitution (it didn't for me,
anyway). Are you subscribed to the list on my server or are you getting
these messages some other way?
Yes, the name of the configuration file matters -- it's how the whole
thing works.
When attempting to make a match, spamdyke will search the configuration
directory for a list of filenames. In your example, you named
"wonderfuldomain.com" for the recipient. Obviously, incoming messages
will have a username in front of the "at" symbol, so let's assume a
username of "foo" (I'll avoid typing the email address or you'll just
see "[EMAIL PROTECTED]" again). spamdyke will search for FILES with the
following paths:
configdir/_recipient_/com/wonderfuldomain/_at_/foo
configdir/_recipient_/com/wonderfuldomain
configdir/_recipient_/com
If any of those files exist, spamdyke will open them and read them like
a configuration file. The first file will only be read for that
specific recipient, since the filename includes the username. If the
first file does not exist but the second one does, it will be read for
any recipient whose email address ends in "wonderfuldomain.com". If the
first and second files do not exist but the third one does, it will be
read for any recipient whose email address ends in "com".
That's why using a crazy filename will not work. If the full path is:
configdir/_recipient_/com/wonderfuldomain/_at_/ilikesmurfswithmarinarasauce.txt
spamdyke will only read that file if the recipient is
"ilikesmurfswithmarinarasauce.txt AT wonderfuldomain.com" (again, I'm
not typing a real email address so it isn't substituted).
In your example, you wanted to whitelist one sender for every recipient
in a domain. The best way to do that is to create a configuration
directory based on the recipient:
mkdir -p configdir/_recipient_/com
echo sender-whitelist-entry=great AT aol.com >
configdir/_recipient_/com/wonderfuldomain (NOTE: type the real email
address, not "AT")
-- Sam Clippinger
Stefan Pausch wrote:
> Hope i post to the correct thread now. For some reasons my "receive eMails"
> setting was "off", while i have never been to the option page until today
> ...
>
>
> The description made me even more confused :)
>
> - does it matter how i name the configuration file? (f.e.
> "ilikesmurfswhentheyturnpurple.txt" would be a correct config file name?)
>
> Do i really write [EMAIL PROTECTED] or do i type in an email addy? How do i
> configure white/blacklist by the configuration directory?
>
> --Stefan
>
>
>
>> Very close -- "_at_" should be a directory, not a file. Inside the
>> "_at_" directory, a file named "great" should contain the configuration
>> directives.
>>
>
>
>> However, you don't really need to create the "_sender_" folder at all.
>> Just create folders named "_recipient_/com", then create a file named
>> "wonderfuldomain". In that file, add the line:
>> [EMAIL PROTECTED]
>>
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature
> database 3300 (20080725) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
> _______________________________________________
> spamdyke-users mailing list
> [email protected]
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>
_______________________________________________
spamdyke-users mailing list
[email protected]
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
