Thank you for the quick response. It a 3ghz xeon with 1gig of ram. And old dell 850. I may have to beef it up. Though it should be up for the task i think something else is the issue. I get no spam scores and it's waiting on something. When i run the lint test i only see this.

with regards to the clam error. I had amavis installed and the proc was running as that user not clamav. I removed amavis and set clamav conf to the proper user and the error has gone. so i think it's working though i get a freshclam error.

a few bugs no worries i have the time to sort them out. I like the implementation and baruwa very much so i am willing to sort them out.

I used to be a qmailrocks fan for years but it wasn't updated for a long time. Now i'm running exchange servers so this is just perfect and gives me piece of mind that linux is in front

Yes, it's great to have some flavor of linux in the mix, preferably infront of MS..lol

So are the issue gone? It looks like the user setting for clamd was causing the errors and delays. Since you changed it to the correct setting, have you have any problems or are mails being delivered normally?

Yes, Baruwa is something to talk about. It'll get better with time and I'm looking forward to it.

For Clamd, you should just remove and purge it and reinstall it using the guide.

This is by far the best setup I've come up with. Everything is running really smooth and fast.

You can start by backing up baruwa's db, mailscanner.conf, baruwa.conf and baruwa.ini. If the system crashes, you'll be able to import those files back into a build for a quick restore. Otherwise, if you're running a vm, you can just export the whole vm as a backup. Therefore, you'll be able to restore it in working order, with all the settings already applied.