Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of robert@schetterer.org
 designates 212.52.224.25 as permitted sender)
DomainKey-Signature: a=rsa-sha1; s=domkey; d=schetterer.org; c=nofws; q=dns;
	h=x-dkim:dkim-signature:message-id:date:from:user-agent:
	mime-version:to:subject:references:in-reply-to:content-transfer-encoding;
	b=Y8PCJ9Iw4OUmJ+yA1jDOYfAMOG5bhLfIwGFvMnJCBUNTzJhiAq0pbemDW7SUBU1Jv
	zWuhktNsxtHeqWJKIJdug==
Message-ID: <4C08AE16.1090406@schetterer.org>
Date: Fri, 04 Jun 2010 09:41:10 +0200
From: Robert Schetterer <robert@schetterer.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de;
 rv:1.9.1.9) Gecko/20100317 SUSE/3.0.4-75.5 Lightning/1.0b2pre
 Thunderbird/3.0.4
MIME-Version: 1.0
To: users@spamassassin.apache.org
Subject: Re: Problems with spamass-milter, postfix, spamassassin
References: <4C07AFF2.9040800@imelaps.ee> <4C07BF72.2080507@vianet.ca>
In-Reply-To: <4C07BF72.2080507@vianet.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Am 03.06.2010 16:42, schrieb Kris Deugau:
> Tarvo Kurm wrote:
>> Mails coming in thru postfix+spamass-milter+spamassassin have
>> drastically lower scores than those checked manually with spamassasin
>> or spamc. Specifically, mails taking the milter path will not have
>> RCVD_IN rules matched _almost_ never. I'm suspicious of the
>> UNPARSABLE_RELAY match, but not sure what causes it.
> 
> Milters typically see the message before any Received: headers are added
> by the local MTA.  As a result, the milter itself needs to add a
> synthetic one that SA can use.
> 
> Unfortunately, this synthetic header seems to be a lot harder to
> generate than you might think.  I've heard reports now and then for
> several years now that spamass-milter still hasn't quite got this ironed
> out.  My own preferred milter, MIMEDefang, has also had intermittent
> problems generating a correct Received: header to pass to SA.
> 
> The fact that RBL rules are not firing, and you're getting
> UNPARSEABLE_RELAY, says to me that *something* is wrong with the
> generated header you're getting.
> 
> Check and see if there's a way you can get spamass-milter to keep the
> message with the generated header somewhere so you can compare what's
> actually generated with the live header Postfix adds later, and which
> you see in your mailbox.
> 
>> There has been a bug in spamass-milter which might or might not be
>> relevant, but as far as i can see, it's been fixed in the debian
>> package...
>> (See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510665 )
> 
> Fixed in the version you're running, or just unstable/testing?
> 
> -kgd
whatever, i am using spamass-milter since years without any trouble with
local files, with mysql on test bed also no errors
perhaps check all config of all parts

-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria