WARNING: Ignoring deprecated option --unzip
Simon Jones
simonmjones at gmail.com
Mon Jan 26 17:10:57 GMT 2009
2009/1/26 Simon Jones <simonmjones at gmail.com>:
> 2009/1/26 Jason Ede <J.Ede at birchenallhowden.co.uk>:
>>> -----Original Message-----
>>> From: mailscanner-bounces at lists.mailscanner.info [mailto:mailscanner-
>>> bounces at lists.mailscanner.info] On Behalf Of Simon Jones
>>> Sent: 26 January 2009 16:26
>>> To: MailScanner discussion
>>> Subject: Re: WARNING: Ignoring deprecated option --unzip
>>>
>>> 2009/1/26 Simon Jones <simonmjones at gmail.com>:
>>> > 2009/1/26 Glenn Steen <glenn.steen at gmail.com>:
>>> >> 2009/1/26 Simon Jones <simonmjones at gmail.com>:
>>> >>> 2009/1/26 Simon Jones <simonmjones at gmail.com>:
>>> >>>> 2009/1/26 Glenn Steen <glenn.steen at gmail.com>:
>>> >>>>> 2009/1/26 Simon Jones <simonmjones at gmail.com>:
>>> >>>>>> 2009/1/25 Julian Field <MailScanner at ecs.soton.ac.uk>:
>>> >>>>>>> This is documented in the MailScanner ChangeLog. You have
>>> updated ClamAV,
>>> >>>>>>> and you require a MailScanner update as well to match the new
>>> command-line
>>> >>>>>>> syntax. It was mentioned in my "new version announcement" to
>>> the
>>> >>>>>>> MailScanner-Announce list a while back.
>>> >>>>>>>
>>> >>>>>>> On 24/1/09 19:47, Simon Jones wrote:
>>> >>>>>>>>
>>> >>>>>>>> Evening chaps, gateway still running like a dog! I've
>>> noticed in
>>> >>>>>>>> /var/log/maillog the following;
>>> >>>>>>>>
>>> >>>>>>>> Jan 24 19:27:29 mailgate1 MailScanner[6685]: WARNING: Ignoring
>>> >>>>>>>> deprecated option --unzip
>>> >>>>>>>> Jan 24 19:27:29 mailgate1 MailScanner[6685]: WARNING: Ignoring
>>> >>>>>>>> deprecated option --jar
>>> >>>>>>>> Jan 24 19:27:29 mailgate1 MailScanner[6685]: WARNING: Ignoring
>>> >>>>>>>> deprecated option --tar
>>> >>>>>>>> Jan 24 19:27:29 mailgate1 MailScanner[6685]: WARNING: Ignoring
>>> >>>>>>>> deprecated option --tgz
>>> >>>>>>>> Jan 24 19:27:29 mailgate1 MailScanner[6685]: WARNING: Ignoring
>>> >>>>>>>> deprecated option --deb
>>> >>>>>>>> Jan 24 19:27:29 mailgate1 MailScanner[6685]: WARNING: Ignoring
>>> >>>>>>>> deprecated option --max-ratio
>>> >>>>>>>> Jan 24 19:27:29 mailgate1 MailScanner[6685]: WARNING: Ignoring
>>> >>>>>>>> deprecated option --unrar
>>> >>>>>>>>
>>> >>>>>>>> I'm assuming it won't hurt performance and I'm sure someone's
>>> come
>>> >>>>>>>> across this before so if you could point me in the direction
>>> to the
>>> >>>>>>>> fix it'd be great,
>>> >>>>>>>>
>>> >>>>>>>> thanks
>>> >>>>>>>>
>>> >>>>>>>> Simon
>>> >>>>>>>>
>>> >>>>>>>
>>> >>>>>>> Jules
>>> >>>>>>>
>>> >>>>>> hello chaps, thanks for that - I've updated MS and configured it
>>> to
>>> >>>>>> use clamd which works a treat, the machines are chewing spam
>>> like they
>>> >>>>>> haven't eaten in a month! I do have a spot of trouble with the
>>> >>>>>> MailScanner -d --lint test though -
>>> >>>>>>
>>> >>>>>> bayes: failed rename /etc/MailScanner/bayes/bayes_journal to
>>> >>>>>> /etc/MailScanner/bayes/bayes_journal.old
>>> >>>>>> bayes: failed rename /etc/MailScanner/bayes/bayes_journal to
>>> >>>>>> /etc/MailScanner/bayes/bayes_journal.old
>>> >>>>>> bayes: failed rename /etc/MailScanner/bayes/bayes_journal to
>>> >>>>>> /etc/MailScanner/bayes/bayes_journal.old
>>> >>>>>>
>>> >>>>>> Previous error complained of not being able to read the files so
>>> i
>>> >>>>>> chown postfix:root * in the directory, now I'm getting the
>>> above.
>>> >>>>>> Seems to have fixed the read error though...
>>> >>>>>>
>>> >>>>>> thanks again,
>>> >>>>>>
>>> >>>>>> Simon
>>> >>>>> This is how this looks for me (I use MailWatch where the apache
>>> user
>>> >>>>> and group is named "apache"):
>>> >>>>>
>>> >>>>> # ls -ld /etc/MailScanner/bayes
>>> >>>>> drwxrwsrwx 2 postfix apache 4096 2009-01-26 14:58
>>> /etc/MailScanner/bayes/
>>> >>>>> # ls -l /etc/MailScanner/bayes
>>> >>>>> totalt 6004
>>> >>>>> -rw-rw---- 1 postfix apache 2334 2009-01-26 14:58 bayes.mutex
>>> >>>>> -rw-r----- 1 apache apache 12288 2009-01-26 14:58 bayes_seen
>>> >>>>> -rw-rw---- 1 postfix apache 5984256 2009-01-26 14:58 bayes_toks
>>> >>>>> #
>>> >>>>>
>>> >>>>> Cheers
>>> >>>>> --
>>> >>>>> -- Glenn
>>> >>>>> email: glenn < dot > steen < at > gmail < dot > com
>>> >>>>
>>> >>>> looks good! so simple I didn't think it could be that. finally
>>> since
>>> >>>> the upgrade I'm gettin commit ineffective with AutoCommit enabled
>>> at
>>> >>>> /usr/lib/MailScanner/MailScanner/CustomFunctions/MailWatch.pm line
>>> 93,
>>> >>>> <CLIENT> line 1
>>> >>>>
>>> >>>> when i restart the MailScanner service, doesn't seem to be a
>>> problem
>>> >>>> but can it be tidied up?
>>> >>>>
>>> >>>> Simon
>>> >>>>
>>> >>>
>>> >>> Guys, also just noticed quite a lot of SA time outs on one of the
>>> >>> gateways, the other gateways are fine and responding so I don't
>>> think
>>> >>> it's a slow blacklist - CPU seems to be IRO 50% on average so the
>>> >>> system isn't way busy. Did the MS upgrade break something with SA?
>>> >>>
>>> >>> SpamAssassin timed out and was killed, failure 1 of 10
>>> >>
>>> >> Check that your bayes_seen file is of a reasonable size, else ...
>>> >> remove it. Also check that your SA expire runs complete (no "expire"
>>> >> files in your bayes directory)... Try up the "SpamAssassin Timeout"
>>> to
>>> >> something fairly large in /etc/MailScanner/MailScanner.conf (mine is
>>> >> at 10 minutes... == 600 seconds).
>>> >>
>>> >> Cheers
>>> >> --
>>> >> -- Glenn
>>> >
>>> > Hello lads, thanks again - cleaned up the error (thanks Steve, we
>>> > don't like messy bits do we!) and Glenn, on the money with the
>>> timeout
>>> > setting for SA - it was set to 10 secs on the gateway that was
>>> playing
>>> > up and 600 on the others, not sure how that happened but I guess the
>>> > part of the system between the chair and they keyboard may have got
>>> > distracted!.
>>> >
>>> > all working beautifully again!
>>> >
>>> > Simon
>>> >
>>> slllllooooooooooowwweedddd down to a crawl again and is stacking
>>> messages in the hold queue. I can't figure out what's going on here.
>>> restart MS and it works really fast but leave it to run for five
>>> minutes or so and the whole things slows to a crawl, it backs up
>>> messages in the hold queue and is really slow answering on port 25 or
>>> times out completely. I've commented out the lists in
>>> /etc/MailScanner/spam.lists.conf - does SA have any others configured
>>> somewhere else? I'm clutching at straws now. no errors in the lint
>>> tests and everything seems normal.
>>
>> It's not starting to swap is it? Have you tried dropping the number of mailscanner processes down a bit?
>>
>> Jason
>> --
>> MailScanner mailing list
>> mailscanner at lists.mailscanner.info
>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>
>> Before posting, read http://wiki.mailscanner.info/posting
>>
>> Support MailScanner development - buy the book off the website!
>>
>
> Hi Jason,
>
> nope not swapping - they have 8gb ram and 15k rpm sas drives
>
> free -m
> total used free shared buffers cached
> Mem: 3948 2624 1324 0 206 444
> -/+ buffers/cache: 1973 1975
> Swap: 1983 0 1983
>
> its really strange, I've commented out all the lists in
> spam.lists.conf and disabled bayes in spam.assassin.prefs.conf dropped
> the max children to 20 from 40 (which its been happy with for months)
> but its still stacking mail in the hold queue - I just checked again
> tail -f /var/log/maillog | grep Found and it seems to have just
> shifted 500+ messages in one big lump! hold is now clear... what
> the....
>
does anyone know a king kong ding-a-ling command to show if some pesky
spammer has hooked on to the system and is pumping masses of mail at
it? I can see lots of connections on 25 from random IP's but I'd
expect this netstat -an shows me this, I could perhaps use something
to narrow it down a little or even show high traffic from a particular
IP etc... not sure, I don't think my config is bad, it just seems the
systems are working really hard to keep up with the flow of junk.
More information about the MailScanner
mailing list