So far the conclusion is that google is inside /etc/MailScanner/phishing.bad.sites.conf .
Any particular reason for doing that?
We have read some threads that google had some large phishing attacks back in 2014 ... but is it necessary to still be in that CONF?
How can we solve that please?
With best regards
Hi. Since today, Clamd is detecting all .DOC files, sent or received in server, as Win.Exploit.CVE_2016_3316-1 virus. Has someone the same problem?. How I can resend emails that have been detected as virus?.
Received: from (port=15889 helo=node-45-112-69-32.alliancebroadband.in)
by panel.uhlhosting.ch with esmtp (Exim 4.87)
(envelope-from )
id 1bIyUG-0009Hq-Fu
for ganja@highacid.com; Fri, 01 Jul 2016 15:28:04 +0200
From:
To:
Date: 1 Jul 2016 22:28:20 +0400
MIME-Version: 1.0
Subject: We offer new vacancy
Message-ID:
Priority: normal
X-mailer: Pegasus Mail for Windows (4.52)...
Running the most recent versions of MailScanner (v3.0.5) and MSFE (and cPanel, v11.56.0.24). I read the blog post that mentioned switching to cPanel's installed clamavconnector. But there's a lot that's not clear in that brief blog post.
Does clamavconnector *replace* clamAV?
And if so, shouldn't the script uninstall clamAV?
Or should I?
I'm still getting the nag warning to upgrade clamAV from...
Since the latest upgrades and changes in Mailscanner I have been receiving the following cron errors:
/etc/cron.daily/freshclam:
ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).
ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!).
Running freshclam manually is updating but nothing is recorded in the log file:
I've just installed Mailscanner using the installation script on a fresh cPanel, Cloud Linux box.
I get an email from the hourly cron
/etc/cron.hourly/update_virus_scanners:
and i get the error message
/etc/cron.hourly/update_virus_scanners: line 63: /usr/mailscanner/usr/lib/MailScanner/wrapper/avg-wrapper: Permission denied
/etc/cron.hourly/update_virus_scanners: line 63:...
There are another errors since last night update:
warn Encountered error in Email::has_spam_as_acl: Email::has_spam_as_acl(1) failed: This feature requires the spamassassin option and is not enabled on your account.
warn Encountered error in Email::spamstatus: Email::spamstatus() failed: This feature requires the spamassassin option and is not enabled on your account.
After upgrading mailscanner today, it is no longer scanning messages and keeps showing the following errors in the log:
Jun 14 08:07:52 server232 MailScanner: Cannot find Socket (/var/clamd) Exiting!
Jun 14 08:07:52 server232 MailScanner: Virus Scanning: No virus scanners worked, so message batch was abandoned and retried!
I have force upgraded mailscanner and also tried using the new...
hello
i install mail scanner free but now i restart exim and have a error:
Mail Queue Queries
Delivery Queue (2016-05-31 20:08:41 Warning: No server certificate defined; TLS connections will fail. emails)
how to fix this error:
root@sv # service exim restart
Shutting down clamd:
Shutting down exim:
Shutting down spamd:
Starting clamd:
Starting exim:
Starting exim-outgoing: 2016-05-31...
I have installed mailscanner using the configserver install script from here:
It installs MailScanner version v4.84.5 which according to the change log was released 5/3/2012. Is it possible to install/support version 4.85.2-2 which was released 13 April 2015?
EDIT:
Is it as simple as changing the following two lines in msinstall.pl?
About 70% of my customers on my small shared hosting service have WordPress installed, and Mailscanner seems to mark all messages from WordPress sites as spam. Whether it's via a contact form on the sites, or even just the automated notifications from WP (such as password change alerts, new user registration alerts, etc...) they all get marked as spam by Mailscanner.
CENTOS 5.11 x86_64 standard – server3 WHM 11.50.0 (build 10)
MailScanner - v4.84.5
ConfigServer MailScanner Script - v2.94
MailScanner Front-End - v5.00
A new version of ClamAV (Current:v New:v0.99) is available
Was initially installed and configured by Way to the Web
Unpacking, building and installing new ClamAV package...
Retrieving ClamAV tarball from Sourceforge......
I have been running the ConfigServer FE to MailScanner for years with very few issues.
But now, when I click on Access Mailwatch, I get the error message
You do not have permission to run this script
If I log on a root, which I prefer not to, I can run it, but when I log on as a whm user that is supposed to have full privileges to run everything I cannot.
I've got a pretty solid config of MS and SA working but some spam slips through no matter how hard I try to nail it down.
Lately for the last few weeks a very specific type of spam keeps getting through. The messages always look about the same. I run the sa-learn stuff on them always but it doesn't seem to be learning as I still get a few of these a day, sometimes up to 10 a day, strait in to...
Hi, running MailScanner v4.84.5 and in the past have always put custom rules scores in /usr/mailscanner/etc/spamassassin.user.prefs.conf
Recently the custom scores in this file are being ignored and a score from somewhere else is being used. For example in spamassassin.user.prefs.conf I have
score URIBL_BLACK 6.0 6.0 6.0 6.0
But when URIBL_BLACK is triggered by an email message, the score is...
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum