Brandon Phelps wrote:
> Ah sorry guys.
There's a very valid reason why you are asked not to obfuscate.
We end up wasting time trying to fix problems in your Exim configuration
when the problem is actually in the DNS.
> The domain in question is pickhoops.com -
You mean this one:
$ nslookup -query=mx pickhoops.com
Non-authoritative answer:
pickhoops.com mail exchanger = 50 mailwash43.pair.com.
Authoritative answers can be found from:
pickhoops.com nameserver = ns296.pair.com.
pickhoops.com nameserver = ns0000.ns0.com.
$whois pickhoops.com
...
Domain Name: PICKHOOPS.COM
Registrar: GODADDY.COM, INC.
Whois Server: whois.godaddy.com
Referral URL: http://registrar.godaddy.com
Name Server: NS0000.NS0.COM
Name Server: NS296.PAIR.COM
> my primary
> domain is dellsports.com. dellsports.com works perfectly, I am able to
> receive mail from any host. pickhoops.com is the one that doesn't want
> to cooperate. I have an MX record setup on pickhoops.com with a
> priority of 10, set to deliver to mail.dellsports.com.,
DNS doesn't agree with that.
> which also
> happens to be on the same box, and is the same MX record dellsports.com
> uses.
>
--
Nigel Wade, System Administrator, Space Plasma Physics Group,
University of Leicester, Leicester, LE1 7RH, UK
E-mail : [EMAIL PROTECTED]
Phone : +44 (0)116 2523548, Fax : +44 (0)116 2523555
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
