mouss wrote:
Ulrich Mierendorff a écrit :
Magnus Bäck wrote:
On Sunday, June 07, 2009 at 17:02 CEST,
Ulrich Mierendorff <ulrich.mierendo...@gmx.net> wrote:
My current configuration looks like this one:
...
myhostname = example.com
myorigin = /etc/mailname
mydomain = example.com
mydestination = $mydomain, localhost
Is this server B? If so, why does it think it's the final destination
for example.com when that's server A's assignment
Yes it's server B.. So should I write
mydestination =
?
The log file then says something like
Jun 7 1:2:3 example postfix/smtp[123]: 456: to=<u...@example.com>,
relay=mx0.example.com[ipA]:25, [...], status=bounced (host
mx0.example.com[ipA] refused to talk to me: 550 Forged HELO: you are not
example.com)
I think this is not a problem of server B's postfix configuration, or am
I wrong? By the way: I do not have access to the configuration of
server A.
Then change the hostname of server B. why do you set
myhostname = example.com
try with something like
myhostname = joe.example.com
where joe.example.com resolves in DNS. Ideally it should resolve to the
public IP of server B.
Well, example.com is the domain for serverB.
DNS configuration is like this
example.com
A-record -> IP of server B
MX-record -> IP of server A
Reverse DNS for IP of server B -> example.com
(IPs are public IPs)
I do not see, how joe.example.com could solve the problem.
I have also googled a bit, but could not find an explanation for this
error.
server A has a check_helo_access that rejects inbound mail claiming to
be from "example.com". This is a common check. but you should get server
A to whitelist server B (to not perform such a check for server B).
I think that will not be possible.
