Pkg exim4 users - May 2005 - Using exim4 internally on a 10.x.x.x network

Hello, all.

I am running Debian sarge updated, with Apache2, PHP4, exim4, and Issue
Tracker (http://www.issue-tracker.com).  This box is intended as a stopgap
trouble ticket system.

Issue Tracker uses the local MTA to send and receive email.  exim4 was set
up on install as an Internet mail server, since I need it to both send and
receive email from other servers (internal Exchange servers).  The internal
network uses a 10.0.0.0/23 address range, and this box does not need to send
or receive email outside of the internal network.

exim4 is throwing the "unrouteable address" error.  Below is the
output of
exim4 -d -bt chris.doherty@cromptoncorp.com.  It looks to me like 1) the
local internal DNS server does not have an MX record for the mail domain,
and 2) exim4 is refusing to send to any IP address in a 10.0.0.0/8 range.

Is that correct?  (Please bear in mind that I know almost nothing about
exim4, and very little about MTAs on Unix/Linux in general, although I have
a good background in SMTP).
Is there a more sensible option for autoconfiguring exim4, perhaps through
dpkg-reconfigure?  Or is there a simple and recommended way of configuring
exim4 as an internal mail server (i.e. not connected to the Internet)?

Exim version 4.50 uid=0 gid=0 pid=2022 D=fbb95cfd
Berkeley DB: Sleepycat Software: Berkeley DB 4.2.52: (December  3, 2003)
Support for: iconv() IPv6 GnuTLS
Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dsearch
nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
changed uid/gid: forcing real = effective
  uid=0 gid=0 pid=2022
  auxiliary group list: <none>
configuration file is /var/lib/exim4/config.autogenerated
log selectors = 00000ffc 00020800
trusted user
admin user
user name "root" extracted from gecos field "root"
originator: uid=0 gid=0 login=root name=root
sender address = root@caelm-it01.cromptoncorp.com
Address testing: uid=0 gid=102 euid=0 egid=102
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Testing chris.doherty@cromptoncorp.com
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Considering chris.doherty@cromptoncorp.com
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
routing chris.doherty@cromptoncorp.com
--------> hubbed_hosts router <--------
local_part=chris.doherty domain=cromptoncorp.com
checking domains
expansion of "${if
exists{/etc/exim4/hubbed_hosts}{partial-lsearch;/etc/exim4/hubbed_hosts}fail
}" forced failure: assume not in this list
hubbed_hosts router skipped: domains mismatch
--------> dnslookup_relay_to_domains router <--------
local_part=chris.doherty domain=cromptoncorp.com
checking domains
cromptoncorp.com in "@:localhost:caelm-it01.cromptoncorp.com"? no (end
of
list)
cromptoncorp.com in ""? no (end of list)
cromptoncorp.com in "! +local_domains : +relay_to_domains"? no (end of
list)
dnslookup_relay_to_domains router skipped: domains mismatch
--------> dnslookup router <--------
local_part=chris.doherty domain=cromptoncorp.com
checking domains
cached no match for +local_domains
cached lookup data = NULL
cromptoncorp.com in "! +local_domains"? yes (end of list)
R: dnslookup for chris.doherty@cromptoncorp.com
calling dnslookup router
dnslookup router called for chris.doherty@cromptoncorp.com
  domain = cromptoncorp.com
DNS lookup of cromptoncorp.com (MX) gave NO_DATA
returning DNS_NODATA
DNS lookup of cromptoncorp.com (AAAA) gave NO_DATA
returning DNS_NODATA
DNS lookup of cromptoncorp.com (A) succeeded
10.30.1.18 in "0.0.0.0 : 127.0.0.0/8 : 192.168.0.0/16 :172.16.0.0/12 :
10.0.0.0/8 : 169.254.0.0/16"? yes (matched "10.0.0.0/8")
ignored host cromptoncorp.com [10.30.1.18]
10.30.1.17 in "0.0.0.0 : 127.0.0.0/8 : 192.168.0.0/16 :172.16.0.0/12 :
10.0.0.0/8 : 169.254.0.0/16"? yes (matched "10.0.0.0/8")
ignored host cromptoncorp.com [10.30.1.17]
10.20.83.5 in "0.0.0.0 : 127.0.0.0/8 : 192.168.0.0/16 :172.16.0.0/12 :
10.0.0.0/8 : 169.254.0.0/16"? yes (matched "10.0.0.0/8")
ignored host cromptoncorp.com [10.20.83.5]
10.100.1.2 in "0.0.0.0 : 127.0.0.0/8 : 192.168.0.0/16 :172.16.0.0/12 :
10.0.0.0/8 : 169.254.0.0/16"? yes (matched "10.0.0.0/8")
ignored host cromptoncorp.com [10.100.1.2]
10.100.1.1 in "0.0.0.0 : 127.0.0.0/8 : 192.168.0.0/16 :172.16.0.0/12 :
10.0.0.0/8 : 169.254.0.0/16"? yes (matched "10.0.0.0/8")
ignored host cromptoncorp.com [10.100.1.1]
dnslookup router declined for chris.doherty@cromptoncorp.com
"more" is false: skipping remaining routers
no more routers
search_tidyup called
>>>>>>>>>>>>>>>> Exim pid=2022
terminating with rc=2
>>>>>>>>>>>>>>>>

Chris Doherty
On contract to Crompton Co./Cie
Elmira: (519) 669-1671 x319

Hi,

* Doherty, Chris - Elmira, ON (chris.doherty@cromptoncorp.com) [050531
20:53]:
> Issue Tracker uses the local MTA to send and receive email.  exim4 was set
> up on install as an Internet mail server, since I need it to both send and
> receive email from other servers (internal Exchange servers).  The internal
> network uses a 10.0.0.0/23 address range, and this box does not need to
send
> or receive email outside of the internal network.
Please take a look at exims dns routers (depends on your setup where it
is stored). IPs from that range are automatically ignored by exim (which
is sane for internet). So, just drop that from the config, and it should
work.


Cheers,
Andi

Hi,

On Tue, May 31, 2005 at 02:48:19PM -0400, Doherty, Chris - Elmira, ON
wrote:
> Issue Tracker uses the local MTA to send and receive email.  exim4 was set
> up on install as an Internet mail server, since I need it to both send and
> receive email from other servers (internal Exchange servers).  The internal
> network uses a 10.0.0.0/23 address range, and this box does not need to
send
> or receive email outside of the internal network.
> 
> exim4 is throwing the "unrouteable address" error.  Below is the
output of
> exim4 -d -bt chris.doherty@cromptoncorp.com.  It looks to me like 1) the
> local internal DNS server does not have an MX record for the mail domain,
> and 2) exim4 is refusing to send to any IP address in a 10.0.0.0/8 range.
exim4 is by default ignoring target hosts in the site local, link
local and host local IP ranges for "foreign" domains since we assume
that the local admin doesn''t have control about these domains.

It does not have these ignores in place for domains it is configured
to relay to, since we assume that the operator of a backup MX does
have at least a vague connection to the domain owner and could
therefore have DNS errors corrected.

You could try putting your internal domain in the dc_relay_domains
field in /etc/exim4/update-exim4.conf.conf. This will solve your issue
as a side effect.

I''d like to compliment your report. You have delivered a correct
analysis, and debugging info which allowed me to verify my assumption.

If there is anything more I can do, please get in touch.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don''t trust Computers. They | Mailadresse
im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 72739835