Re: How to force Postfix to rewrite (or masquerade) Received: header

2 msg	Deliver mail using my ISP server
3 msg	How can I avoid mime 8-bit errors in incoming e...
3 msg	non standard .forward location
2 msg	Cannot send mail from command line
2 msg	Address rewriting - converting an old domain to...
4 msg	Email routing like MX functionality
4 msg	3rd party spam filter and virtual users
2 msg	I don't understand how does postfix work with a...
2 msg	Sanitize 'Undelivered Mail Returned to Sender'
5 msg	Suggestion
3 msg	Virtual alias query question

How to force Postfix to rewrite (or masquerade)...
\ Dmitry Hazin (15 May 2007)
. \ Noel Jones (15 May 2007)
. . \ Gary V (15 May 2007)
. \ mouss (15 May 2007)

4 msg	Unknown error
9 msg	Trouble with mailbox_transport=error:foo
1 msg	per domain reporting ?
7 msg	make error
1 msg	postfix + procmail delivery
3 msg	Where's snapshot -20070511?
1 msg	tlsmgr on solaris9
6 msg	sasl problem

Subject:	Re: How to force Postfix to rewrite (or masquerade) Received: header
Group:	Postfix-users
From:	mouss
Date:	15 May 2007

Dmitry Hazin wrote:
> Hi,
>
> I'm using postfix (2.3.7 on debian sarge) as my smtp server with tls
> encryption and plain authentication.
>
> However, the mail sent to some domains is returned with the
> "Considered UNSOLICITED BULK EMAIL" message. It seems to happen
> because my original IP that is recorder into the first Received header
> hasn't corresponding dns record.
>
> Return-Path: <user>
> Received: from domain.com (domain.com [xxx.xxx.xxx.xxx])
> by mail.somesite.ru (Postfix) with ESMTP id 056107E82B
> for <user>; Tue, 15 May 2007 12:35:38 +0700 (OMSST)
> Received: from localhost (localhost [127.0.0.1])
> by domain.com (Postfix) with ESMTP id 1E7F011201DA
> for <user>; Tue, 15 May 2007 12:35:56 +0700 (NOVST)
> X-Virus-Scanned: Debian amavisd-new at domain.com
> Received: from domain.com ([127.0.0.1])
> by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024)
> with ESMTP id 1GYG1hdCuSdR for <user>;
> Tue, 15 May 2007 12:35:53 +0700 (NOVST)
> Received: from user (unknown [xx.xx.xx.xx])
> by domain.com (Postfix) with ESMTP id E0F4911201A6
> for <user>; Tue, 15 May 2007 12:35:52 +0700 (NOVST)

why did some program helo with 'user'?
>
> (I replaced my hostname with domain.com, it's ip with xxx.xxx.xxx.xxx;
> my email with user, my original ip with xx.xx.xx.xx and
> recipient email with user)
>
> So as it's written in the bounced email:
>
> First upstream SMTP client IP address: [xxx.xxx.xxx.xxx] domain.com
> According to a 'Received:' trace, the message originated at:
> [xx.xx.xx.xx],
> user (unknown [xx.xx.xx.xx])
>
> The question is: is there any way to skip adding first Received: header;
> the best will be if it will be looking like I'm sending emails
> directly from the domain.com server. I found something that seems to
> be related to this configuration but couldn't point out right way to
> do this this.

If they really used the Received headers to block you, they are broken.
if so, use header_checks to rewrite the Received header to an X-Received
header. something like:
/^(Received: .*)/ REPLACE X-$1

if you use spamassassin or any filter that relies on such headers, do
the rewrite after filtering.