On Thu, 18 Jun 2015 12:29:44 +0200
Matus UHLAR - fantomas wrote:
> On 18.06.15 09:11, Franz Schwartau wrote:
> >The lastest (third) Received header causes $helo to be set to
> >'localhost'.
> >
> >It would make more sense if TxRep uses the lastest (first) Received
> >header setting $helo to 'mail
On 18.06.15 09:11, Franz Schwartau wrote:
Yes, TxRep right now uses the _last_ Received header. IMHO it should use
the _latest_ Received header, only.
Let's have a look at the following series of Received header which cause
the problem:
Received: from mail-wi0-f175.google.com (mail-wi0-f175.goo
Hi!
On 18.06.2015 00:39, RW wrote:
> On Wed, 17 Jun 2015 23:08:55 +0200
> Franz Schwartau wrote:
>
>> Hi!
>>
>> A few days ago I replaced AWL with TxRep. From time to time I get
>> unusual high scores caused by TxRep since then.
>>
>> So I started debugging the TxRep plugin a bit. The high scores
On Wed, 17 Jun 2015 23:08:55 +0200
Franz Schwartau wrote:
> Hi!
>
> A few days ago I replaced AWL with TxRep. From time to time I get
> unusual high scores caused by TxRep since then.
>
> So I started debugging the TxRep plugin a bit. The high scores are
> caused by "HELO: localhost" after sa-le
Hi!
A few days ago I replaced AWL with TxRep. From time to time I get
unusual high scores caused by TxRep since then.
So I started debugging the TxRep plugin a bit. The high scores are
caused by "HELO: localhost" after sa-learn of a spam mailbox.
In check_senders_reputation() line 1252 reads:
f
