ConfigServer Community Forum

As you can see from the screen dump below.. there 1441 pieces waiting to be delivered.

I recently updated CP on the server and so suspect that has something to do with Mailscanner reporting as stopped and being unable to restart it.

I tried the suggestion /blog/index.php?itemid=419 (I am not allowed to post URLs)
That didn't work and the suggestions in the "Help! MailScanner isn't working/Mail isn't being delivered. What do I do?" FAQ.

Below is the result. Any ideas?

root@alpha [~]# exim -bpc
1441
root@alpha [~]# service MailScanner stop
Shutting down MailScanner daemons:
MailScanner: [FAILED]
Waiting for MailScanner to stop..
root@alpha [~]# killall -9 MailScanner
MailScanner: no process killed
root@alpha [~]# service MailScanner start
Starting MailScanner daemons:
MailScanner: File::Temp version 0.18 required--this is only versi on 0.16 at /usr/lib/perl5/site_perl/5.8.8/MIME/Tools.pm line 14.
BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.8.8/MIME/Tools.p m line 14.
Compilation failed in require at /usr/lib/perl5/site_perl/5.8.8/MIME/Parser.pm l ine 142.
BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.8.8/MIME/Parser. pm line 142.
Compilation failed in require at /usr/mailscanner/lib/MailScanner/MCPMessage.pm line 41.
BEGIN failed--compilation aborted at /usr/mailscanner/lib/MailScanner/MCPMessage .pm line 41.
Compilation failed in require at /usr/mailscanner/bin/MailScanner line 106.
BEGIN failed--compilation aborted at /usr/mailscanner/bin/MailScanner line 106.
[ OK ]

Did you try force installing the File::Temp perl module or running /scripts/checkperlmodules?

Why should I do this? And how exactly? I have made no changes to the system other than updating MSFE and WHM/cPanel.

Why is MailScanner not working? Does it need this PerL module? If so this must be a new requirement as MS has worked without fail since it was installed over a year ago.

So perhaps this module is no longer required for WHM/cPanel and was removed? I recently upgraded to cPanel 11.24.5-R37946 - WHM 11.24.2. Is MailScanner not compatible with this version of WHM/cPanel?

It is just very frustrating to have an error that has no resolution but impacts e-mail delivery to all clients. I see this as major service impact that a fix should be made available for immediately. Please provide some clarity to your response.

Thanks.

Our MailScanner install/configuration is certainly compatible with the version of WHM/cPanel you are running. However, we cannot cater for every possible issue introduced by a cPanel upgrade or an OS upgrade (often due to poor configuration of the OS update system). We do our best to help clients fix problems as soon as we are aware of them. As you are the first person to report this problem at this time, it doesn't look like it is a widespread issue so it's not something we can provide a blanket fix for. Obviously MailScanner requires this perl module since it is reporting the problem in the error message.

To force install this perl module do this in ssh (logged in as root):

/scripts/perlinstaller --force File::Temp

Then restart MailScanner.

If that doesn't fix it, in ssh do:

/scripts/checkperlmodules

And then restart MailScanner. You might also need to manually upgrade MailScanner using the full perl module check (the upgrade in the WHM front-end does not do the full perl module check). This is how to do it:

rm -Rfv msinstall*
wget http://www.configserver.com/free/msinstall.tar.gz
tar -xzf msinstall.tar.gz
cd msinstall/
sh install.sh

Select option 1 for full perl module installation.

Also, you can always disable MailScanner while you are working on it so that email coming into the server will bypass MailScanner. Re-enable it once MailScanner starts sucessfully.

Thanks Sarah I did disable MS after it wouldn't restart but I need those 1141 e-mails to be delivered. So will need to get MS working again. I will what you suggest and let you know.

So I re-enabled and tried the first two options but still it won't start.

It does this:
Restarting MailScanner...

Shutting down MailScanner daemons:
MailScanner:[FAILED]
Waiting for MailScanner to stop..
Starting MailScanner daemons:
MailScanner: [ OK ]

The 'taillog" shows this:

Aug 6 08:56:40 alpha pop3d-ssl: LOGOUT, user=cng@domainnameremoved, ip=[::ffff:209.121.51.249], port=[4860], top=0, retr=0, rcvd=24, sent=1170, time=1
Aug 6 08:56:40 alpha pop3d-ssl: Connection, ip=[::ffff:209.121.51.249]
Aug 6 08:56:40 alpha pop3d-ssl: LOGIN, user=name@domainnameremoved, ip=[::ffff:209.121.51.249], port=[4861]
Aug 6 08:56:41 alpha pop3d-ssl: LOGOUT, user=name@domainnameremoved, ip=[::ffff:209.121.51.249], port=[4861], top=0, retr=0, rcvd=12, sent=39, time=1
Aug 6 08:58:24 alpha spamd[6671]: spamd: server killed by SIGTERM, shutting down
Aug 6 08:58:26 alpha spamd[14377]: logger: removing stderr method
Aug 6 08:58:29 alpha spamd[14454]: Can't locate Mail/SpamAssassin/CompiledRegexps/body_500.pm in @INC (@INC contains: /var/lib/spamassassin/compiled/3.002004 /var/lib/spamassassin/compiled/3.002004/auto lib /usr/local/cpanel/spamassassin_sandbox /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/
Aug 6 08:58:32 alpha spamd[14454]: spamd: server started on port 783/tcp (running version 3.2.4)
Aug 6 08:58:32 alpha spamd[14454]: spamd: server pid: 14454
Aug 6 08:58:32 alpha spamd[14454]: spamd: server successfully spawned child process, pid 14849
Aug 6 08:58:32 alpha spamd[14454]: spamd: server successfully spawned child process, pid 14850
Aug 6 08:58:32 alpha spamd[14454]: prefork: child states: BS
Aug 6 08:58:32 alpha spamd[14454]: spamd: server successfully spawned child process, pid 14851
Aug 6 08:58:32 alpha spamd[14849]: spamd: connection from localhost [127.0.0.1] at port 34612
Aug 6 08:58:32 alpha spamd[14454]: prefork: child states: BIS
Aug 6 08:58:32 alpha spamd[14849]: spamd: setuid to root succeeded
Aug 6 08:58:32 alpha spamd[14454]: prefork: child states: BII
Aug 6 08:58:32 alpha spamd[14849]: spamd: still running as root: user not specified with -u, not found, or set to root, falling back to nobody
Aug 6 08:58:32 alpha spamd[14849]: spamd: processing message for root:99
Aug 6 08:58:34 alpha spamd[14849]: spamd: identified spam (1001.4/5.0) for root:99 in 1.9 seconds, 834 bytes.
Aug 6 08:58:34 alpha spamd[14849]: spamd: result: Y 1001 - DCC_CHECK,GTUBE,NO_RECEIVED,NO_RELAYS scantime=1.9,size=834,user=root,uid=99,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=34612,mid=,autolearn=no,shortcircuit=no
Aug 6 08:58:34 alpha pop3d: Connection, ip=[::ffff:127.0.0.1]
Aug 6 08:58:34 alpha pop3d: LOGOUT, ip=[::ffff:127.0.0.1]
Aug 6 08:58:34 alpha pop3d: Disconnected, ip=[::ffff:127.0.0.1]
Aug 6 08:58:34 alpha spamd[14454]: prefork: child states: III
Aug 6 08:58:34 alpha spamd[14454]: spamd: handled cleanup of child pid 14851 due to SIGCHLD
Aug 6 08:58:34 alpha spamd[14454]: prefork: child states: II
Aug 6 08:58:35 alpha imapd: Connection, ip=[::ffff:127.0.0.1]
Aug 6 08:58:46 alpha imapd: LOGIN, user=cpanel@localhost, ip=[::ffff:127.0.0.1], port=[56889], protocol=IMAP
Aug 6 08:58:46 alpha imapd: LOGOUT, user=cpanel@localhost, ip=[::ffff:127.0.0.1], headers=0, body=0, rcvd=12, sent=86, time=0

I am weary of the 3rd option as it removed MS and as I said I have mail in the MS queue that I don't want to lose. Is this mail still likely to get processed?

It looks to me like MailScanner DID start successfully:

Starting MailScanner daemons:
MailScanner: [ OK ]

If you didn't see any further errors after that, it should be OK. The failure to stop MS is not necessarily a problem unless you are seeing other errors.

The log excerpts you include don't show any mailscanner lines so it isn't helpful. It shows you are running spamd, which I assume you enabled after you disabled MailScanner, since you should always disable spamassassin in cPanel if you are running MailScanner. You should now disable spamassassin again and try restarting MailScanner at the command prompt in ssh to see if there are any errors.

Hi Sarah, got an entirely new error this time:

root@alpha [~]# service MailScanner stop
Shutting down MailScanner daemons:
MailScanner: [FAILED]
Waiting for MailScanner to stop..
root@alpha [~]# killall -9 MailScanner
MailScanner: no process killed
root@alpha [~]# service MailScanner start
Starting MailScanner daemons:
MailScanner:

**** ERROR: You must upgrade your perl IO module to at least
**** ERROR: version 1.2301 or MailScanner will not work!

[ OK ]
root@alpha [~]#

Also nothing I have done has gotten MS to show that it is "started" in MSFE. And mail is not getting delivered when its enabled.

I guess you'll need to force install the perl IO module, then.

/scripts/perlinstaller --force IO

From a brief search of the mailscanner mailing list it appears this whole thing might be an issue with the CentOS 5 perl install - is that the OS you're running?