Rudy Gevaert:
> This is my test email:
>
> rgeva...@pimp:~$ telnet smtp1.ugent.be 25
> Trying 157.193.71.182...
> Connected to smtp1.ugent.be.
> Escape character is '^]'.
> 220 smtp.ugent.be ESMTP Postfix (Debian/GNU)
> helo pimp.ugent.be
> 250 smtp1.UGent.be
> mail from:<rgeva...@xchange.ugent.be>
> 250 2.1.0 Ok
> rcpt to:<rudy.geva...@ugent.be>
> 250 2.1.5 Ok
> data
> 354 End data with <CR><LF>.<CR><LF>
> From: rgeva...@xchange.ugent.be
> Subject: test
Note: this submission is from pimp.ugent.be (157.193.44.68) to
smtp1.ugent.be (157.193.71.182). I' almost 100% certain that these
two hosts are in different subnets. The days that universities
were bridging their entire class B network should be long past.
> The email how it arrived:
>
> Return-Path: <rudy.geva...@ugent.be>
...
> From: rgeva...@xchange.ugent.be
> Subject: test
...
This happens when client and server are in different subnets.
When 157.193.44.68 does not match local_header_rewrite_clients
(default: permit_mynetworks) then the From: etc. header from
157.193.44.68 will not be rewritten.
This change was introduced with Postfix 2.2.0. It prevents Postfix
from appending its own domain to malformed spam (which was a source
of confusion) and it also prevents Postfix from breaking DKIM and
DomainKeys signatures.
To fix, you need to update the local_header_rewrite_clients in your
main.cf file and specify network/mask information that includes
all the networks whose headers you want to rewrite. It could be as
simple as the whole class B network (157.193.0.0/16).
I see that you have "smtpd -o local_header_rewrite_clients=" in
your master.cf file for the "after filter" SMTP servers. This is
good.
Wietse
