I believe what is happening is that evolution is using spamd client side to filter the server side mail before it is loaded into the client.
It's briefly discussed here:
http://www.novell.com/documentation/evolution20/index.html?page=/documentati on/evolution20/evolution/data/usage-mail-organize-spam.html
But I can't find any other mention of it in the evolution documentation.
This is probably not a 'dovecot' specific issue like I previously thought.
Michael
-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Kenneth Porter Sent: Friday, January 21, 2005 4:03 PM To: dovecot@dovecot.org Subject: Re: [Dovecot] Evolution Slowness Fix
--On Friday, January 21, 2005 3:19 PM -0600 Michael David Joy mdjoy@phy.olemiss.edu wrote:
It seems that Evolution has defaulted to checked for spam server side using Spamd on Fedora Core 3 without downloading the mail. It seems that spamd is the culprit in all this as it's trying to analyze pop3 mail without simply downloading all the new mail.
How's it doing that? Is it invoking spamc after each pop3 fetch client-side? Or is it somehow getting Dovecot to do it on the server side?
I normally run SA from sendmail via MIMEDefang to reject the most egregious spam (score higher than 10) and viruses and then run SA again from /etc/procmailrc to mark "probable" spam (scores between 5 and 10) during delivery into my IMAP folders. (I could do it all in MD but my load is small enough that it hasn't been worth the coding effort.)