Eric,
Just an update on this..
I have cleaned all the accounts of this and fixed my irritating spam
issue using spam assassin ruleset
I had to write a rawbody rule that filtered the common statement within
the html tags :)
Once done set a score of 30 so it would just drop it.
GOOD STUFF LOL
I'm running Qmailtoaster utilities on CentOS6 VM on a XenServer. Data
is stored on NFS. Over the weekend, the VM went into Read-Only file
system due to a lag in communication. I had to manually run FSCK
(there were errors and I told it to fix them) and reboot after
restoring it to Read-Write mode.
Would you care to share that SA rule? I've been getting some of those
lately too.
Perhaps we can get SA upstream to include that in their rules updates.
Thanks.
--
-Eric 'shubes'
On 06/30/2014 07:05 AM, David wrote:
Eric,
Just an update on this..
I have cleaned all the accounts of this
On 06/30/2014 08:59 AM, Diana Calder wrote:
I'm running Qmailtoaster utilities on CentOS6 VM on a XenServer. Data
is stored on NFS. Over the weekend, the VM went into Read-Only file
system due to a lag in communication. I had to manually run FSCK
(there were errors and I told it to fix them) and
Hi Diana.
Sounds like an error I have seen a couple of times in my QMT running in
KVM : a run files is missing
(/var/qmail/supervise/'smtp|clamd|spamd|send|submission' /run - and
/var/qmail/supervise/ 'smtp|clamd|spamd|send|submission' /log/run )
Check to make sure the run files are present
Monday, June 30, 2014, 1:21:28 PM, Eric wrote:
You shouldn't have a /var/qmail/supervise/log directory. I think if you
simply remove it (or move it aside to /root/ perhaps) then you'll be fine.
I DIDN'T have one when the errors started. I also checked an old
snapshot of the Qmail server and it
Unfortunately, the error message doesn't appear to say which log file
it's having a problem with.
I'm going to guess it's clamav, since that's being moved. I probably
need to have the clamav package remove some leftover stuff.
First, verify that clamav is logging to /var/log/maillog. If it's
Monday, June 30, 2014, 3:05:30 PM, Eric wrote:
Unfortunately, the error message doesn't appear to say which log file
it's having a problem with.
I'm going to guess it's clamav, since that's being moved. I probably
need to have the clamav package remove some leftover stuff.
First, verify
Hi Diana.
I've also had this thing happening to my system - check if You have
clamd starting in the init.d directory - my issue was that I happended
to get clamd installed by another repo file which put the clamd startup
script under /etc/init.d (and linked to which ever rcX.d You are using -
so
