> look at your logs I did that (before posting).
> it was first tried on low mx There was no delivery attempt made on the low MX. > then fallback to higher one All attempts where made against the high MX. > unless you havent configured another mailrouting > by transport etc Now I configured a transport rule to route mail to the domain explicitly through relay1.netnames.net. relay1.netnames.net is reachable, but fails with the same error (lowest numbered MX record points to local host (in reply to RCPT TO command)). So both MX for that domain seem to be broken. But that does not explain why there was no delivery attempt made on the low MX. I also queried different DNS servers for MX records on the domain, they all returned the same results as in my first post (and yes, I do have local resolvers running). So I guess this is not a DNS issue (at least not on my end). Regards, Thomas
