ISPCONFIG Anti-Spam filter not causing problems for user account

I have an ISPCONFIG box running on CentOS 5.0. ISPCONFIG has been running like a top up until recently. The problem is that one of my user accounts is blocking all or most of my incoming email due to the spam filter or rather spamassasin. Under "Spam Filter and AntiVirus" for the user account I have:

These are the exact same settings as most of my other accounts however inbound email is being blocked all of a sudden just on one account. I have had several persons recently inform me that they cannot get mail through and are getting errors. The only way to allow mail is to "uncheck" Spam Filter which I have done so that I can communicate with the world on this account in question.

I downloaded and installed all of the latest CentOs updates and also upgraded to the latest ISPCONFIG from 2.2.18 to 2.2.23 in hopes that this would be resolved but no luck. What is going on here. Very Strange. Somehow the spam filter is getting way too strict for this user. I am not sure exactly how I should approach resolving this issue. It appears that a "lockfile" cannot be created for this user.

Here is the actual email (minus the real servernames) that got bounced back.

myserver.com is the server in question that is not creating the lock file for this one user. It had been up until about a week ago then all of a sudden things stopped working. My other email accounts are configured exactly the same and have no problems with spam filter enabled for the user. Again, the only way I can get email inbound to my "[email protected]" right now is by unchecking or rather deactivating the spam filter.

I deleted as many useless emails in my mail box that I could just to free up some space and to see what happened. It appears that now I can receive emails even with anti-spam engaged. My quota did not appear to be exceeded previously so I figured I should try deleting old messaged. I am just worried that this problem is going to happen again soon and that something else is really causing the lockout of inbound email. This is my main account and it has caused lots of grief blocking so many clients, customers and friends.

Please let me know if you see anything else that may have caused the problem from the "ls -la /var/www/web4/.spamassassin" printout that you requested.

In creating a new email account today I found that limits were exceeded and that it would not create the account. This must be related to the issue that I have been experiencing with mail being blocked etc. since it appears to be quota related. I dilligently went through all of my domains and email account to lean things out and the system appears to be working as per normal once again.

In short it appears that either ISPCONFIG, quota or the interaction between the 2 are not smart enough to warn before problems like this occur. This is only a guess and I am not trying to start a fueled debate with such a statement that ISPCONFIG is not "smart enough". I love ISPCONFIG and it is a GOD sent in general. I am only mentioning that there may be a problem with quota interaction to hopefully improve development of the next version in the case that there may actually be something here that developers need to address.

That is it. Is this something to do with "procmail" or having no lock file?

Sorry this seems like it must be a simple problem and I still can't fix it. This is only happening to one account. Unfortunately the one I use most. If I just offloaded the email I'm confident that it would fix it but I'd rather keep all my emails online for reference and searching.

Yes, mydomain.com.user is the admin of that domain. I deleted the old symbolic link and created the new one that now points to the actual spamassassan setup files. I have great hopes that this has finally solved the issue unless there is another file or routine that will at some point overwrite this fix. I will know for sure in a month or so as deleting older emails in general for some reason has worked as a temporary fix.

I hope that all of this saves someone else from going through this email problem.