bug report

[--[ UxBoD ]--]

----- "Rick Cooper" <rcooper at dwford.com> wrote:

> From: mailscanner-bounces at lists.mailscanner.info
> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Ying
> Sent: Wednesday, February 10, 2010 4:53 AM
> To: MailScanner discussion
> Subject: Re: bug report
> 
> 
> 
> I show respect, I did by private bug report, but I get told I need to
> read documentation, I am no newby, but alas mailscanner dev think so,
> so I ask myself why waste my time with bug report when not welcome, I
> have private mail too by someone who has similar problem, they say run
> slackware, we run debian, he think it because run latest perl modules.
> but why I care now after mailscanner dev response. my 5 yo son could
> tell the answers from amavisd is different to what mailscanner be.
> 
> So sorry for wasting my time, wont report bugs anymore here
> [Rick Cooper]
> 
> I am wondering if something was lost in the translation here. Clearly
> English is not your native tongue and you might well have
> misinterpreted his attitude. You must also realize that Julian
> gets/answers thousands of mails in a week and a very large number are
> simple configuration errors. Plus if you upgraded SA and MS did not
> change then the issue is likely permissions or configuration.
> Personally I would be looking to see if the local.cf link is correct
> as this could explain why MS is skipping network tests and amavisd is
> not. there should be a link between /etc/mail/spamassassin/local.cf
> and /opt/MailScanner/etc/spam.assassin.prefs.conf. Also check your MS
> config setting for "SpamAssassin Default Rules Dir", "SpamAssassin
> Local Rules Dir" and "SpamAssassin Site Rules Dir". Clearly if MS
> skips some tests that the others do not they must not be using the
> same rules.
> 
> Also bear in mind your English is so broken it's hard to follow. Of
> course the only way I could possibly write to you in your native
> tongue would be to run it through babblefish and I can tell you from
> experience that what you enter there many times loses much in the
> translation, you might have a very hard time understanding me and
> certainly have issues with context and meaning.
> 
> 
> 
> ----- Original Message -----
> From: Peter Farrow
> To: MailScanner discussion
> Sent: Wednesday, February 10, 2010 11:08 AM
> Subject: Re: bug report
> 
> Ying:
> 
> Show some respect here, I am sure Jules would have read your bug
> report, so no need to adopt that tone.
> 
> If you want help from someone its good start to be on your best
> behaviour, no one this list has an obligation to help you, please
> remember that when you type your replies.
> 
> regards
> 
> Pete
> ps: I am top posting because this thread is in that format.
> 
> On 09/02/2010 23:52, Ying wrote:
> 
> 
> Hello,
> Did you even read my report?
> 
> I state it work with spamassassin directly, it work with amavisd, it
> work with mailscanner until SA upgrade. so very obviously SA works as
> all read /etc/postfix/spamassassin/*, just not properly with
> mailscanner anymore, do you treat everyone like this and dismiss out
> of hand without reading or comprehend what said or investigate?
> 
> and yes /etc/postfix is symlink to /etc/mail, else amavisd would not
> work.
> 
> 
> ----- Original Message -----
> From: Jules Field
> To: Ying
> Sent: Tuesday, February 09, 2010 6:29 PM
> Subject: Re: bug report
> 
> If it is not doing the tests, then you have not enabled them in the
> /etc/mail/spamassassin/v*.pre files.
> This is not a MailScanner problem, I suggest you read the SA
> documentation.
> 
> On 09/02/2010 02:29, Ying wrote:
> 
> 
> 
> 
> BUG REPORT
> 
> MailScanner does not do many SpamAssassin tests, this is local rules
> and
> 
> URI tests, eg: .multi.uribl.com and all others
> 
> Problem only notice after upgrade SA 3.2.5 to 3.3.0. MailScanner work
> fine
> 
> for many month with same configuration even from last version which
> also has
> 
> this problem. In testing we even remove all the whitelists.
> 
> 
> 
> MailScanner-4.79.11-1 source install
> 
> SpamAssassin 3.3.0 from CPAN
> 
> Perl Modules - all required installed and update from CPAN
> 
> MailScanner and SpamAssassin both --lint OK
> 
> MailScanner run as user postfix
> 
> amavisd-new run as user vscan
> 
> /etc/postfix/spamassasin owner is root directory is 0755
> 
> Unreproducable by spamassasin -t < queue file
> 
> Unreproducable by amavisd-new
> 
> both of these tests score as expected.
> 
> Monitor of Bind show MailScanner does not ask URI questions
> 
> also scan real fast and not asking Razor or DCC
> 
> 
> 
> 
> 
> Using MailScanner and amavisd-new together, MailScanner take message
> 
> first before amavisd-new.
> 
> MailScanner say-
> 
> X-YUKI-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
> score=0,
> 
> required 3, autolearn=disabled)
> 
> amavisd-new say-
> 
> X-Virus-Scanned: amavisd-new at YUKI
> 
> X-Spam-Flag: NO
> 
> X-Spam-Score: 1.313
> 
> X-Spam-Level: *
> 
> X-Spam-Status: No, score=1.313 tagged_above=-999 required=3
> 
> tests=[URI_HEX=1.313] autolearn=disabled
> 
> 
> Jules
> 

Which is one of the reasons why we would need to see the output direct from SpamAssassin and not from Amavisd.

-- 
Thanks - Phil