Hi all. I've very recently had the problem of sorting out my work's email spam dropped on my lap and to be honest, I know a little but a little knowledge can be a dangerous thing...
Anyhow. Having spent the last few days making as sure as I can be that the network and exchange is all up to date I'm now looking at our email hosting and seeing what can be done there to cut things down a bit. Enabling the spamassassin (which was turned off) has improved things a little but considering how configurable and flexible it seems to be, I had a couple of thoughts which I was wondering if anyone can shed some light on as to whether it might be a good idea or no. Alot of the spam we're receiving is spoofed so initally I wondered (and tried, just to see what would happen) if I added our own domain to the blacklist. Since all our domain mail is internal I figured anything coming from outside couldn't be 'from' us and therefore could be legitimately blocked. Unsurprisingly his did stop a chunk of spam but I was wondering if there might be any problems with this approach? Secondly, it occurred to me that all the (legit) mail to us will only be to a handful of email addresses and much of the spam still getting through is sent to spurious recipie...@mydomain.com. So with this in mind, is it useful or advisable to setup those legit email addresses as " whitelist_to " and if so, what becomes of the 'rest' of the mail or do you have to define only receive to whitelist_to? Sorry if it seems a little confusing! Many thanks. -- View this message in context: http://old.nabble.com/Setting-Blacklist_from-and-whitelist_to-tp27735054p27735054.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
