No idea who sim scan calls spamassin but 4 seems a little low to be
quarantining
Also simacan could be adding it own config somehow such a common bayes db
or other rules the running SA independently night not be licking up
Martin
On Wednesday, 28 March 2012, FC Mario Patty wrote:
> Well.. it was simscan. But I just check current log and find out that the
> score that email got when spamassassin cooperating with simscan is 4.6
> (higher than spam-hits, that is 4.0). When I scan manually with
> spamassassin -D, it only get 1.7. Is it ok? Thanks.
>
> Regards,
> Mario
>
> On Wed, Mar 28, 2012 at 1:21 PM, Martin Hepworth
> <max...@gmail.com<javascript:_e({}, 'cvml', 'max...@gmail.com');>
> > wrote:
>
>> Spammassin itself doesnt do anything with the email , but merely scores
>> it for other things to use that score to move it deliver it or send it
>> somewhere different
>>
>> So the question is
>>
>> What is calling spamassassin and what's moving the emails to your
>> quarantine faculty ??
>>
>> Martin
>>
>>
>> On Wednesday, 28 March 2012, FC Mario Patty wrote:
>>
>>> Guys,
>>>
>>> I need some help about spamassassin. An email was scored 1.7 below the
>>> hits score but it was quarantined either. I don't understand why this could
>>> happen. Thanks. *snippet of spamassassin's scan result as follow.
>>>
>>> X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
>>> mail.ourdomain.com
>>> X-Spam-Level: *
>>> X-Spam-Status: No, score=1.7 required=4.0 tests=DATE_IN_FUTURE_06_12,
>>> INVALID_DATE,RDNS_NONE,T_MIME_NO_TEXT autolearn=no version=3.3.2
>>> Received: from unknown (HELO mail.remote_domain.com)
>>> ([remote_server_ip_addr])
>>> (envelope-sender <some.guy@remote_domain.com>)
>>> by mail.ourdomain.com (qmail-ldap-1.03) with SMTP
>>> for <our.u...@ourdomain.com>; 28 Mar 2012 04:36:08 -0000
>>> X-TM-IMSS-Message-ID:<52eaa1080005e863@remote_domain.com>
>>> Received: from mail.remote_domain.com ([a_local_ip_addr]) by
>>> remote_domain.com ([another_ip_addr]) with ESMTP (TREND IMSS SMTP
>>> Service 7.1) id 52eaa1080005e863 ; Wed, 28 Mar 2012 11:34:30 +0700
>>> Received: from mail.remote_domain.com ([a_local_ip_addr]) by
>>> mail.remote_domain.com with Microsoft SMTPSVC(6.0.3790.1830);
>>> Wed, 28 Mar 2012 11:34:30 +0700
>>> Date: 28 Mar 12 11:36:01
>>> From: some.guy@remote_domain.com
>>> Subject: Some title here...
>>> To: a_u...@ourdomain.com
>>> Cc:
>>> Bcc:
>>> Mime-Version: 1.0
>>> Content-Type: multipart/mixed; boundary="DMW.Boundary.605592468"
>>> Return-Path: some.guy@remote_domain.com
>>> Message-ID: <TBEXC01u59Vvjvxo6Am000004d6@mail.remote_domain.com>
>>> X-OriginalArrivalTime: 28 Mar 2012 04:34:30.0677 (UTC)
>>> FILETIME=[11359C50:01CD0C9C]
>>> X-TM-AS-Product-Ver: IMSS-7.1.0.1433-6.8.0.1017-18802.004
>>> X-TM-AS-Result: No--5.693-7.0-31-10
>>> X-imss-scan-details: No--5.693-7.0-31-10
>>> X-TM-AS-User-Blocked-Sender: No
>>>
>>> This is a Mime message, which your current mail reader may not
>>> understand. Parts of the message will appear as text. If the remainder
>>> appears as random characters in the message body, instead of as
>>> attachments, then you'll have to extract these parts and decode them
>>> manually.
>>>
>>> --DMW.Boundary.605592468
>>> Content-Transfer-Encoding: 7bit
>>>
>>> etc...
>>>
>>
>>
>> --
>> --
>> Martin Hepworth
>> Oxford, UK
>>
>
>
--
--
Martin Hepworth
Oxford, UK
