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.google.com [209.85.212.175]) by mx1.domain.com (envelope-sender <ale...@price2spy.com>) (MIMEDefang) with ESMTP id t5HJ97If029681 for <recipi...@domain.com>; Wed, 17 Jun 2015 21:09:10 +0200 Received: by wiwd19 with SMTP id d19so1242876wiw.0 for <recipi...@domain.com>; Wed, 17 Jun 2015 12:09:07 -0700 (PDT) Received: from localhost ([188.95.50.54]) by mx.google.com with ESMTPSA id ka7sm8287084wjc.36.2015.06.17.12.09.06 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 17 Jun 2015 12:09:07 -0700 (PDT) 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-wi0-f175.google.com'.
shouldn't that logically be more like lasttrusted header? -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Chernobyl was an Windows 95 beta test site.
