For those running MailScanner - Important Information

[chirpy]

cPanel have recently started shipping exim with a new configuration directive set. This directive (split_spool_directory) enables split directories spools in the exim incoming directory. This can help with performance issues on high load mail servers. What it also does is completely break MailScanner

I have made modifications to my scripts to modify existing MailScanner configurations to cater for this change. You should visit the script page at:
http://www.webumake.com/free/mailscanner.htm

You should follow the instructions after:

New Additional Instructions (2nd Nov 2004)

The new script is also required because cPanel haven't bothered updating the cPanel Pro installation to take into account MailScanner installations.

Let me know if anything doesn't work or isn't clear.

[dgbaker]

Thanks for the info Jonathan. I'm not totalled surprised by this. cPanel seems to care less what happens to customizations or third party apps. (let the flame begin)

[chirpy]

It really is frustrating, but there you go - 3 hours of work to get everything going again and to cater for those with and without this new directive. My heart initially sunk when I thought that MailScanner would be a no go until I sorted it out.

I'm sure cPanel will come back with the fact that they don't support 3rd party add-ons, etc. Which is fair enough. It's just a pain when they did support it and Nick did say that they would continue to keep the scripts and that hasn't really happened with cPanel Pro.

[sHORTYWZ]

Ran your script chirpy and it looks like my mail still isn't being processed.. tons of emails sitting on their respective directories in the queue directory. Any ideas?

[sHORTYWZ]

Alright, made the changes and then ran the upgrade and now mailscanner is asking for a newer version of the Mail::ClamAV module.. trying to upgrade it via "/scripts/perlinstaller Mail::ClamAV" doesn't work - getting errors..

  Starting "make" Stage
make[1]: Entering directory `/home/.cpan/build/Mail-ClamAV-0.13/_Inline/build/Mail/ClamAV'
/usr/bin/perl /usr/lib/perl5/5.8.0/ExtUtils/xsubpp  -typemap /usr/lib/perl5/5.8.0/ExtUtils/typemap   ClamAV.xs > ClamAV.xsc && mv ClamAV.xsc ClamAV.c
gcc -c  -I/home/.cpan/build/Mail-ClamAV-0.13 -I/usr/local/include -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBUGGING -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -O2 -g -pipe -march=i386 -mcpu=i686   -DVERSION=\"0.13\" -DXS_VERSION=\"0.13\" -fPIC "-I/usr/lib/perl5/5.8.0/i386-linux-thread-multi/CORE"   ClamAV.c
ClamAV.xs: In function `clamav_perl_constant':
ClamAV.xs:324: `CL_EFORMAT' undeclared (first use in this function)
ClamAV.xs:324: (Each undeclared identifier is reported only once
ClamAV.xs:324: for each function it appears in.)
ClamAV.xs:326: `CL_SCAN_RAW' undeclared (first use in this function)
ClamAV.xs:327: `CL_SCAN_ARCHIVE' undeclared (first use in this function)
ClamAV.xs:328: `CL_SCAN_MAIL' undeclared (first use in this function)
ClamAV.xs:329: `CL_SCAN_DISABLERAR' undeclared (first use in this function)
ClamAV.xs:330: `CL_SCAN_OLE2' undeclared (first use in this function)
ClamAV.xs:331: `CL_SCAN_BLOCKENCRYPTED' undeclared (first use in this function)
ClamAV.xs:332: `CL_SCAN_HTML' undeclared (first use in this function)
ClamAV.xs:333: `CL_SCAN_PE' undeclared (first use in this function)
ClamAV.xs:334: `CL_SCAN_BLOCKBROKEN' undeclared (first use in this function)
ClamAV.xs:335: `CL_SCAN_MAILURL' undeclared (first use in this function)
ClamAV.xs:336: `CL_SCAN_BLOCKMAX' undeclared (first use in this function)
ClamAV.xs:338: `CL_SCAN_STDOPT' undeclared (first use in this function)
make[1]: *** [ClamAV.o] Error 1
make[1]: Leaving directory `/home/.cpan/build/Mail-ClamAV-0.13/_Inline/build/Mail/ClamAV'

A problem was encountered while attempting to compile and install your Inline
C code. The command that failed was:
  make

The build directory was:
/home/.cpan/build/Mail-ClamAV-0.13/_Inline/build/Mail/ClamAV

To debug the problem, cd to the build directory, and inspect the output files.

 at /home/.cpan/build/Mail-ClamAV-0.13/blib/lib/Mail/ClamAV.pm line 190
BEGIN failed--compilation aborted at /home/.cpan/build/Mail-ClamAV-0.13/blib/lib/Mail/ClamAV.pm line 529.
Compilation failed in require.
BEGIN failed--compilation aborted.
make: *** [ClamAV.inl] Error 2
  /usr/bin/make  -- NOT OK
Running make install
  make had returned bad status, install seems impossible
perlmod--Install done

Help!

[sHORTYWZ]

Alrighty then.. I think I got it.. had to upgrade clamav to .80 which allowed the new connector to install which finally fixed everything, I think. =)

[chirpy]

Just coming in to help and see you've sorted it Yes, the problem is that the latest MailScanner when using clamavmodule must use Mail::ClamAV v0.13 and ClamAV .80, as you discovered.

[puzz1ed1]

thanks Jonathan

I also found that clam needed updating, which took a fair bit of time to sort out, but the mailscanner updates worked seemlessly as ever

[chirpy]

I'll put a note on the website to warn people that they do need to upgrade ClamAV and Mail::ClamAV if they are using it.

[FWC]

Chirpy,

I spent a few hours last night figureing out what broke and coming up with a manual bandaid on the one server I upgraded. I logged on to your site today and saw your script. I suspected you would have one.

I did have to modify mscheck.txt, though. I suspect you copied code from the installer. I had to change two lines to get it to modify an existing MailScanner.conf file properly.

open (IN, "</usr/mailscanner.new/etc/MailScanner.conf");

open (OUT, ">/usr/mailscanner.new/etc/MailScanner.conf");

I needed to take the .new out of the directory path to get it to modify the live one.

Once I did that and made the postupcp file, it all worked like a dream.

Thank you once again for your great service to the Cpanel/MailScanner community.

[mr.wonderful]

I'll put a note on the website to warn people that they do need to upgrade ClamAV and Mail::ClamAV if they are using it.

Your script does not work for those of us using the REAL MAILSCANNER from the MailScanner website. The simple solution is just to turn off split directories in exim.conf. Problem solved! Then all you have to do is write a bash script that will update the Split Directories from YES to NO evertime upcp runs. Thats all!

Sorry to see you are running that hopeless, non support mailscanner modification from Cpanels website.

[chirpy]

Will you ever grow up? There's nothing wrong with either approach, both are documented on the MailScanner site as viable, so neither is "REAL".

Anyway, I posted the solution for those running other forms of MailScanner installation on the other thread that you opened.

[chirpy]

For those that do use it, I've just released a new mscheck.pl which fixes a flaw in the way it works.

[cpanelnick]

Thanks for the info Jonathan. I'm not totalled surprised by this. cPanel seems to care less what happens to customizations or third party apps. (let the flame begin)

Sorry, but we can't exactly test every third party app every time we make a change. This change was done to solve some performance problems.

[cpanelnick]

cPanel have recently started shipping exim with a new configuration directive set. This directive (split_spool_directory) enables split directories spools in the exim incoming directory. This can help with performance issues on high load mail servers. What it also does is completely break MailScanner

I have made modifications to my scripts to modify existing MailScanner configurations to cater for this change. You should visit the script page at:
http://www.webumake.com/free/mailscanner.htm

You should follow the instructions after:

New Additional Instructions (2nd Nov 2004)

The new script is also required because cPanel haven't bothered updating the cPanel Pro installation to take into account MailScanner installations.

Let me know if anything doesn't work or isn't clear.

What would you like us to update ?