On Sunday, June 07, 2009 at 21:46 CEST,
Ulrich Mierendorff <ulrich.mierendo...@gmx.net> wrote:
> mouss wrote:
>
> > 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
I wouldn't recommend having hostname == domain name, but we can work
around that.
> (IPs are public IPs)
>
> I do not see, how joe.example.com could solve the problem.
Because the HELO restriction on server A probably wouldn't trigger (that
depends on some configuration details on server A). The point of that
restriction is to make sure hosts from the outside don't say "HELO
example.com", but that restriction must of course not be applied to
inside hosts.
> > 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.
Come on, work with us here. If you're saying "that's impossible" that
least you can do is give us a good reason for it.
--
Magnus Bäck
mag...@dsek.lth.se
