system
32
First the DISadvantages of the plugin versus the emailservice:
- no fancy gui when something is detected
- no extras, like the adding of “message clean/infected” text to messages
The difference between avast emailservice and the plugin is, that the service is a separate program that acts as a mini mail server. You have to get your email from that. That demands some configuration. Also, If you use an other program that way to detect spam, you have to chain them together, that demands some more configuration. I have been struggeling with those two for a while, but fanally got it running (thanks to this forum btw). When checking mail, the bat! accesses avast-mail-service, passing a very difficult string as server, to handle all following software. the mail-service breaks down that string so it can use it and then accesses spamweasel, passing a stripped down serrver string to controll spamweasel. Spamweasel then breaks down that string finally accessing my mail server on the internet. The mail is send back to spamweasel, which after checking passes it back to avast, which after checking, sends it back to the bat! With large attachments you will get timeout problems. Setting the timeout high can cause trouble when the internet connection goes wacky. The plugin is just a little program that is controlled by the bat! and no configuration is nescessary.
No the Advantages (as I see them) of the plugin:
- you can kill the email sevice and thus saving memory and cpu
- the configuration with another spam program is more easy (there are also spam plugins)
- no problems with more accounts on different mail servers (with the service that is still a bit tricky)
If you are happy with the way things are. Don’t change it. I am testing the plugin, because I think it is a fancy extra with the software, saves me the trouble with my spam proxy and enhances performance in my case.
Peter