Posted by: Anonymous Coward
on July 09, 2005 03:31 AM
Yea, Bruce could have saved lots of time and perhaps even writer's cramp by simply updating to a fairly recent version of Evolution.
With that said, I'd like to point out that setting up elaborate filters and spam detection daemons on mail clients is not a good idea. What happens when you use a different client or system? What happens when you are on the road? Why waste your bandwidth transferring spam in the first place?
The better solution is to implement the spam filtering and virus scanning at the system level, preferably on the mail server itself. That means that your filtering rules and training are portable and independent of your location or client software. Having it on the mail server also allows you to use RBL's and other techniques that block the spam before it is even transfered.
Presently, 300 attempts per day are made to deliver spam to me. 60% of those 300 is blocked, before transfer, by RBL checking. The remaining 39% is caught at the mail server by Spamassassin and ClamAV. Approximately 3 spams a week and 0 viruses or worms actually make it to my mailbox. I suppose I could create filters and use Spamassassin on Evolution to deal with those 3 messages, since I already use Evolution and it has these features built in. But, at 3 spams a week, it isn't worth the effort to configure and train the client. The Delete key is much more efficient.
Learn about Linux
Download Linux
Get Linux help
Re:Can't use Junk folder in Debian?
Posted by: Anonymous Coward on July 09, 2005 03:31 AMWith that said, I'd like to point out that setting up elaborate filters and spam detection daemons on mail clients is not a good idea. What happens when you use a different client or system? What happens when you are on the road? Why waste your bandwidth transferring spam in the first place?
The better solution is to implement the spam filtering and virus scanning at the system level, preferably on the mail server itself. That means that your filtering rules and training are portable and independent of your location or client software. Having it on the mail server also allows you to use RBL's and other techniques that block the spam before it is even transfered.
Presently, 300 attempts per day are made to deliver spam to me. 60% of those 300 is blocked, before transfer, by RBL checking. The remaining 39% is caught at the mail server by Spamassassin and ClamAV. Approximately 3 spams a week and 0 viruses or worms actually make it to my mailbox. I suppose I could create filters and use Spamassassin on Evolution to deal with those 3 messages, since I already use Evolution and it has these features built in. But, at 3 spams a week, it isn't worth the effort to configure and train the client. The Delete key is much more efficient.
#