WARNING: Ignoring deprecated option --unzip

Glenn Steen glenn.steen at gmail.com
Mon Jan 26 14:55:00 GMT 2009


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
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se


More information about the MailScanner mailing list