Submitted by rjrsinc on Tue, 04/27/2010 - 08:27 Pro Licensee
I see this message:
Warning! This user is within 908 kB of his disk quota. Spam filtering has been disabled.
Is this accurate? It seems to me that stopping the spam filter is just going to make the mailbox fill up faster.
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Tue, 04/27/2010 - 15:30 Comment #1
Yes, that message is correct. Virtualmin disables spam filtering when a user is close to his disk quota as spamassassin can hang in this case, causing mail processes to get stuck.
The work-around is to use spamd/spamc instead of the spamassassin stand-along program - this can be setup at Email Messages -> Spam and Virus Scanning.
Submitted by rjrsinc on Wed, 04/28/2010 - 08:02 Pro Licensee Comment #2
Will that increase the load on the server?
Submitted by andreychek on Wed, 04/28/2010 - 09:25 Comment #3
Using spamd and spamc uses more RAM, since it's a daemon, but it actually reduces the CPU requirements of spam processing... it does that by keeping SpamAssassin in memory, rather than launching it for every email that comes in.
I personally use spamd/spamc on any server I maintain.
Submitted by rjrsinc on Wed, 04/28/2010 - 09:47 Pro Licensee Comment #4
Well, I went to the Email Messages>Spam and Virus Scanning
spamc is already selected for SpamAssassin client program
Virus scanning program is set to Server scanner (clamdscan)
Isn't this what you are referring to?
Submitted by JamieCameron on Wed, 04/28/2010 - 12:51 Comment #5
Ok, it looks like you are using spamc already then .. so that warning is actually incorrect - spam will always be filtered.
I will fix Virtualmin's user list to not show that warning when spamc/spamd are being used.
Submitted by rjrsinc on Wed, 04/28/2010 - 13:37 Pro Licensee Comment #6
Hey thanks Jamie! BTW, no one reported any spam, and our end users most likely would have. Realtors tend to make their concerns known, to put it politely.
Submitted by Issues on Sun, 05/16/2010 - 01:53 Comment #7
Automatically closed -- issue fixed for 2 weeks with no activity.