Heres what happen.... first had anand Exiscan+Clam+Exim setup running but found chirpy setup with mailscanner looked promising so I had chirpy do a test install of his setup on one of my servers. Although it worked great my clients were not happy that spam assassin was taken away form their CP and the load was a little higher than compared to my previous setup. I ran with the mailscanner for about a week then decided to have chirpy place the server back to cpanel default at which time I reinstall anand setup as I have many many times in the past. Immediately all accounts experience 451 local error and mail could not be delivered or sent, furthermore looking at exim logs I notice the following: demime acl condition: error while creating mbox spool file I use Acunett for my server management and they also tried reinstall ClamAV with eximscan and had the same results. 3 techs and myself could not figure this out. So we turned back to chirpy insisting that maybe something left over form the mailscanner install could be causing this. He insisted everything was reverted back to cpanel default. Hmmmm....So then I turned back to anand. First I did this: /scripts/reseteximtodefaults /scripts/exim4 --latest /scripts/buildeximconf Then I check exim log: > > > OK, No errors Run script @cpanelappz.com (use the installer not the clamd updater version). DO NOT make changes to exim.conf through WHM. Check your exim_main log, any errors ? > > > OK, No errors Once you have cleared everything from the above, make exim.conf changes using only WHM exim editor. Restart exim and look for errors. > > > Not OK, in exim_mainlog: demime acl condition: error while creating mbox spool file Then anand told me the following: Well that didn't work and everyone I have talked to is out of ideas. Does anyone on these forums have any clue what might be causing this issue? And before anyone starts anything, this thread is not meant to trash anyone. It is only asking for help.