Putting your domain's addresses in whitelist_recipients pretty much defeats the purpose of spamdyke.
Putting your domain's addresses in whitelist_senders would create a nearly open relay, allowing anyone to use your sever as a relay by simply knowing one of the addresses. Very bad idea. Something that's counter intuitive but very effective is to *blacklist* your local domain(s) in the blackist_senders file, as such: @mydomain.com Since all of your users authenticate (they do authenticate, don't they?), they pass through spamdyke (or better yet use port 587). Anyone attempting to spoof an address at your domain is blocked. This accomplishes what the reject-identical-sender-recipient is intended to remedy and then some, while still allowing users to send email to themselves (which I have a few who do - there's no good reason they shouldn't be able to). This works like a charm. -- -Eric 'shubes' On 06/13/2011 06:12 AM, ron wrote: > That is kind of what I was seeing in the log files, once it hit the > whitelist_recipients, then it seemed that the mail was accepted, even if > it was spam. Not sure where I saw it at, but I remember reading about > putting all recipients into that whitelist. > > > On 6/13/2011 9:05 AM, Angus McIntyre wrote: >> ron wrote: >>> Whats the consensus, good or bad idea to whitelist all email addresses >>> within your company in spamdykes whitelist_recipients? >> Wouldn't that be rather counter-productive? If you whitelist all >> recipients at your company (and assuming that your mail server accepts >> mail only for people at your company) then you've essentially switched off >> spamdyke for all incoming mail. Or am I missing something? >> >> Whitelisting sender addresses at your company is also a poor idea, because >> spammers like to forge mail to make it appear to come from someone at the >> same domain. In other words, if the spammer's list includes >> '[email protected]' and '[email protected]', >> they'll often send mail to >> '[email protected]' with '[email protected]' in the >> 'From' line, and >> vice-versa. >> >> Angus >> >> >> >> _______________________________________________ >> 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
