Re: [exim] mx_any not expanding

Top Page
Delete this message
Reply to this message
Author: Don Sceifers
Date:  
To: exim-users
Subject: Re: [exim] mx_any not expanding
Don Sceifers wrote:*
> Is there a way I can find out what mx_any is expanding to?
> I have a system running cpanel, using exim for MTA. I finally got an ACL
> written that will block incoming mail unless there is an MX record for

the
> recipient. Unfortunately, all emails are being blocked, including the one
> domain we opened up by pointing an MX record to this box.
>
> We use /etc/resolv.conf to point to our nameservers, but I don't know how

to
> see what @mx_any resolves to.
>
> Is there a way to debug this by printing the contents of @mx_any?
>
> here is the domainlist definition I am using
>
> domainlist local_mx_domains = @mx_any/ignore=127.0.0.1
>
> and I added this to check_recipient:
>
> # Drop those not having an MX record for Recipient drop message = That is
> not a valid email for this domain !domains = local_mx_domains
>
> Any ideas?
> Thanks*


Try reading the docs on this subject ..
http://docs.exim.org/current/spec_html/ch10.html#SECTdomainlist

.. and do a debuging run with "exim -bh ip.ad.dre.ss"

Ted, I actually have read the document, quite extensively. I have also run
the exim command you listed.

What I got never described what mx_any expanded to... here is the relevant
portion:

19:13:31 8402 processing "drop"
19:13:31 8402 check !domains = local_mx_domains
19:13:31 8402 discs.net in "local_mx_domains"? no (end of list)
19:13:31 8402 drop: condition test succeeded
19:13:31 8402 SMTP>> 550 That is not a valid email for this domain
550 That is not a valid email for this domain
19:13:31 8402 LOG: MAIN REJECT


So then, from that machine, I did a dig on the domain to see what the
nameserver in /etc/resolv.conf thought...
dig discs.net any

; <<>> DiG 9.2.4 <<>> discs.net any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55988
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 3, ADDITIONAL: 2

;; QUESTION SECTION:
;discs.net.                     IN      ANY


;; ANSWER SECTION:
discs.net.              86400   IN      SOA     ns1.xxxxxx.com.
hostmaster.xxxxxxx.com. 1228465684 10800 900 86400 7200
discs.net.              85988   IN      A       216.195.78.32
discs.net.              86400   IN      MX      10 mail.discs.net.
discs.net.              86400   IN      NS      ns1.xxxxxx.com.
discs.net.              86400   IN      NS      ns2.xxxxxx.com.
discs.net.              86400   IN      NS      ns3.xxxxxx.com.


this was edited to keep our nameserver semi private, but as you can see
there definitely is an MX record in the DNS.

Any ideas how I can see what mx_any is expanding to?

the doc claims "If a pattern consists of the string @mx_any it matches any
domain that has an MX record pointing to the local host or to any host that
is listed in*hosts_treat_as_local*. " but I am not really seeing that.

eth0:1    Link encap:Ethernet  HWaddr 00:50:56:A2:24:66
          inet addr:216.195.78.32  Bcast:216.195.78.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Base address:0x1070 Memory:f4820000-f4840000


And as you can see the IP listed in dig is indeed bound to this machine.

Don