Upgrade Wrecks MailScanner

Tue Oct 11 18:44:51 UTC 2016

LMFAO :)

-----Original Message-----
From: MailScanner [mailto:mailscanner-bounces+mailscanner-list=okla.com at lists.mailscanner.info] On Behalf Of Jerry Benton
Sent: Tuesday, October 11, 2016 1:42 PM
To: MailScanner Discussion
Subject: RE: Upgrade Wrecks MailScanner

Many items have been moved in MailScanner v5. The standard of using the /conf.d/ directory has been a standard for longer than that. Your MailScanner.conf is still pointing to the ./CustomFunctions/ directory, which no longer exists.

The README contains the new file locations. (Maybe I should change the file name to DO_NOT_README so more people will read it.) Changing to those directories and looking at the structure is very simple and should be very intuative.

-
Jerry Benton
www.mailborder.com
+1 - 844-436-6245

-----Original Message-----
From: Paul Scott <sales at edenusa.com>
Reply: MailScanner Discussion <mailscanner at lists.mailscanner.info>
Date: October 11, 2016 at 2:31:37 PM
To: MailScanner Discussion <mailscanner at lists.mailscanner.info>
Subject:  RE: Upgrade Wrecks MailScanner

> Hello Thom,
>
> Yes, I did run the ms-upgrade-conf command, and the results are
> exactly the same. I’ve also found that MailScanner is literally doing
> nothing at all (as evidenced in the log files). It loads up, but is not actually scanning any incoming email.
>
> Upgrading the OS and performing a clean install, we will do, but is
> not an option at this time. Perhaps I should run the install script
> again? I have no idea where the NEW MailScanner.conf file is. It is not in the /etc/MailScanner directory.
>
> Thank you so much for your help!
> Paul
>
> From: MailScanner
> [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info]
> On Behalf Of Thom van der Boon
> Sent: Tuesday, October 11, 2016 11:25 AM
> To: MailScanner Discussion
> Subject: Re: Upgrade Wrecks MailScanner
>
> Paul,
>
>
> Linux mail.edenhosting.net 2.6.18-412.el5 #1 SMP Mon Sep 5 22:22:21
> UTC 2016 i686 i686
> i386 GNU/Linux
>
>
>
> This is CentOS 5.x. Support for CentOS 5.x will end March 2017. Moving
> to a newer CentOS is advisable.
> https://access.redhat.com/support/policy/updates/errata/
>
>
>
> If I were you, I would do a clean install with Centos 6 with
> MailScanner with postfix. Moving to CentOS 7 is a big leap from CentOS 5. !!!!
>
>
>
> -----
>
>
>
> Looking at the output of MailScanner --lint you have multiple problems:
>
>
>
> Most important is:
>
>
>
> Checking version numbers...
>
> Version installed (5.0.3) does not match version stated in
>
> MailScanner.conf file (4.84.5), you may want to run ms-upgrade-conf
>
> to ensure your MailScanner.conf file contains all the latest settings.
>
>
>
> You are running a old config file, with a newer MailScanner. You need
> to update it using the ms-upgrade-conf command.
>
>
>
> And keep solving problems until MailScanner --lint does not give any
> error messages
>
>
>
> Met vriendelijke groet, Best regards,
>
>
> Thom van der Boon
> E-Mail: thom at vdb.nl
>
>
>
> =====
>
>
>
> Thom.H. van der Boon b.v.
> Transito 4
> 6909 DA Babberich
> Tel.: +31 (0)88 4272727
> Fax: +31 (0)88 4272789
> Home Page: http://www.vdb.nl/
>
> ________________________________
> Van: "Paul Scott" >
> Aan: "MailScanner Discussion" >
> Verzonden: Dinsdag 11 oktober 2016 19:48:07
> Onderwerp: RE: Upgrade Wrecks MailScanner
>
> Hello Thom,
>
> In answer to your questions, I have the following:
>
> Linux mail.edenhosting.net 2.6.18-412.el5 #1 SMP Mon Sep 5 22:22:21
> UTC 2016 i686 i686
> i386 GNU/Linux
>
> The MTA is Sendmail
>
>
> Here is the output of MailScanner –lint:
>
>
> [root at mail ~]# MailScanner --lint
> Trying to setlogsock(unix)
> Could not read Custom Functions directory
> /usr/lib/MailScanner/MailScanner/CustomFunctions
> at /usr/share/MailScanner/perl/MailScanner/Config.pm line 735
>
> Reading configuration file /etc/MailScanner/MailScanner.conf Reading
> configuration file /etc/MailScanner/conf.d/MyMailScannerConfig.conf
> Reading configuration file /etc/MailScanner/conf.d/README Read 501
> hostnames from the phishing whitelist Read 19129 hostnames from the
> phishing blacklists
> Config: calling custom init function SQLBlacklist
> Config: calling custom init function MailWatchLogging
> Config: calling custom init function SQLWhitelist
>
> Checking version numbers...
> Version installed (5.0.3) does not match version stated in
> MailScanner.conf file (4.84.5), you may want to run ms-upgrade-conf to
> ensure your MailScanner.conf file contains all the latest settings.
>
> Your envelope_sender_header in spamassassin.conf is correct.
>
> Checking for SpamAssassin errors (if you use it)...
> Using SpamAssassin results cache
> Connected to SpamAssassin cache database
> dcc: dccifd -> check skipped: dcc: failed to connect to a socket
> /var/dcc/dccifd: Connection refused SpamAssassin reported no errors.
> Connected to Processing Attempts Database Created Processing Attempts
> Database successfully There are 0 messages in the Processing Attempts
> Database Using locktype = flock MailScanner.conf says "Virus Scanners
> = clamav avg"
> mktemp: invalid option -- -
> Usage: mktemp [-V] | [-dqtu] [-p prefix] [template] Found these virus
> scanners installed: clamavmodule
> ======================================================================
> =====
> Virus and Content Scanning: Starting
> mktemp: invalid option -- -
> Usage: mktemp [-V] | [-dqtu] [-p prefix] [template]
> ERROR: Option --tempdir requires a non-empty string argument
> ERROR: Can't parse command line options
> ======================================================================
> =====
>
> If any of your virus scanners (clamavmodule) are not listed there, you
> should check that they are installed correctly and that MailScanner is
> finding them correctly via its virus.scanners.conf.
> Config: calling custom end function SQLBlacklist
> Config: calling custom end function MailWatchLogging
> Config: calling custom end function SQLWhitelist [root at mail ~]#
>
>
> And here are some of the errors that I am getting:
>
> [root at mail MailScanner]# service mailscanner restart Restarting
> MailScanner ...
> Could not read Custom Functions directory
> /usr/lib/MailScanner/MailScanner/CustomFunctions
> at /usr/share/MailScanner/perl/MailScanner/Config.pm line 735
>
> Oct 11 10:13:57 mail MailScanner[24482]: MailScanner Email Processor
> version 5.0.3 starting...
> Oct 11 10:13:57 mail MailScanner[24482]: Could not read Custom
> Functions directory /usr/lib/MailScanner/MailScanner/CustomFunctions
> Oct 11 10:13:57 mail MailScanner[24482]: Reading configuration file
> /etc/MailScanner/MailScanner.conf
>
> Any help would be greatly appreciated! Thank you so much!
>
> Paul Scott
>
> From: MailScanner
> [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info]
> On Behalf Of Thom van der Boon
> Sent: Tuesday, October 11, 2016 12:44 AM
> To: mailscanner at lists.mailscanner.info
> Subject: Re: Upgrade Wrecks MailScanner
>
> Hi Paul,
>
> Wat CentOS version are you using?
> What MTA are you using?
> What is the output of MailScanner --lint ?
>
> I upgraded from 4.8.5 to 5.0.3 and after a initial hickup everything
> is running smoothly now. I did a clean install on a new server. So: My
> old mailscanner was on CentOS 5; created a new virtual machine with
> CentOS 6. Did a clean install and copied all the extra configuration
> files to the new server
>
>
>
> Met vriendelijke groet, Best regards,
>
>
> Thom van der Boon
> E-Mail: thom at vdb.nl
>
>
>
> =====
>
>
>
> Thom.H. van der Boon b.v.
> Transito 4
> 6909 DA Babberich
> Tel.: +31 (0)88 4272727
> Fax: +31 (0)88 4272789
> Home Page: http://www.vdb.nl/
>
> ________________________________
> Van: "Paul Scott" >
> Aan: mailscanner at lists.mailscanner.info
> Verzonden: Dinsdag 11 oktober 2016 06:36:57
> Onderwerp: Upgrade Wrecks MailScanner
>
> An upgrade from 4.85 to 5.0.3 caused a great deal of errors during the
> install, on my CentOS server. After the install, all of the REPORTS
> files were missing from the associated directory. Thank goodness I had
> made a full backup of the original MailScanner files, and was able to
> put all of those files back again. However, a great deal of spam is
> now getting through, and I am afraid that most of the settings in the
> mailscanner.conf file are somehow not working. For example, the ”required_hits” rule no longer seems to work. Also the custom files are no longer readable by mailscanner, in particular, the “Config.pm”
> file that is used by MailWatch. Also, MailWatch is no longer working at all.
>
> Also, I am receiving the following error to the root user, every few minutes:
>
> Date: Wed, 19 Nov 2014 14:50:02 -0800
> From: Cron Daemon >
> To: root at mail.edenhosting.net
> Subject: Cron /usr/local/bin/mailq.php
>
> Cannot find configuration value: include in
> /etc/MailScanner/MailScanner.conf
>
> Any ideas about what happened and what I should do to get back on
> track? I have been using MailScanner for more than 10+ years, and
> EVERY upgrade worked like a charm. This is the first time that an upgrade has failed so badly. Any help is greatly appreciated!
>
> Sincerely,
>
> Paul Scott
> Sales Engineer, Eden USA
> Las Vegas, New York, Los Angeles
>
> Phone: 866.501.3336
> Fax: 866.502.3336
> FACEBOOK: http://www.facebook.com/edenusainc
>
>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>

--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.