chirpy mailscanner / anand Exiscan+Clam+Exim = trouble, Can you assist??

Status
Not open for further replies.

XPerties

Well-Known Member
Apr 10, 2003
401
0
166
New Jersey, USA
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:

Very surprising.

Try these
/scripts/reseteximtodefaults
Install using my instructions from cpanelappz.com and make all changes as mentioned there.

If still there are errors probably chirpy's installation of mailscanner has something left on the server which could be causing this problem. You could probably hire some sys admin / your own admin guy to look at the exim mail spool.
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.
 

XPerties

Well-Known Member
Apr 10, 2003
401
0
166
New Jersey, USA
rvskin said:
Please show your owner, group and permission for this folder.

ls -al /var/spool/exim

drwxr-x--- 6 mailnull mail 4096 Nov 11 11:45 ./
drwxr-xr-x 16 root root 4096 Dec 15 16:06 ../
drwxr-x--- 2 mailnull mail 4096 Dec 17 10:43 db/
-rw-r--r-- 1 mailnull mail 6 Dec 17 10:48 exim-daemon.pid
drwxr-x--- 64 mailnull mail 4096 Dec 1 12:49 input/
drwxr-x--- 64 mailnull mail 4096 Dec 1 12:49 msglog/
drwxr-x--- 3 mailnull mail 4096 Dec 3 16:31 scan/
 

rvskin

Well-Known Member
PartnerNOC
Feb 19, 2003
400
1
168
Not sure what cause the problem. I believe that exiscan is broken. I would suggest you run
/scripts/reseteximtodefaults
/scripts/exim4 --latest
and install clamavconnector within WHM/addmon module, don't install cpanelappz EXISCAN-CLAM-EXIM-INSTALLER, it conflicts with clamavconnector. And then configure exim using WHM exim editor same as cpanelappz.com but change the av_scanner line from
av_scanner = clamd:/var/run/clamav/clamd
to
av_scanner = clamd:/var/clamd

Warning that someone don't like clamavconnector, you should search the forum for its pro and cron before install it.
 
Last edited:

XPerties

Well-Known Member
Apr 10, 2003
401
0
166
New Jersey, USA
While I appreciate your suggestion I'm not looking for alternative methods. I'm more after a solution to get back to my normal setup.
 

XPerties

Well-Known Member
Apr 10, 2003
401
0
166
New Jersey, USA
Anyone else every have this issue? It still exist for me.
 

ispro

Well-Known Member
Verifed Vendor
Apr 8, 2004
628
2
168
I'm refresh the old thread, but another possible reason is /tmp partition corruption.
We have noticed this on several servers of us and always it was fixed by umounting (with lazy, e.g. -l switch) /tmp, checking it via fsck and mount back via "mount -a".

Perhaps this would helps someone searching for "error while creating mbox spool file" in this forum :)
 
Status
Not open for further replies.