Re: [Exim] Problem with exim on internal network

Top Page
Delete this message
Reply to this message
Author: Willie Viljoen
Date:  
To: syn uw, exim-users
Subject: Re: [Exim] Problem with exim on internal network
(Again, sorry for the top post)

Yes, this can be done with Exim 3, I havn't used this for some time, check
your specifications to make sure this is right before using it.

Try adding this router in the appropriate spot in your configuration file:

internal_domains:
driver = domainlist
transport = remote_smtp
route_list = intdomain1.com:intdomain2.com:example.com:myname.org 1.2.3.4
byname

I'm not sure if this will work, but it might, give it a bash.

As a side note, I strongly recommend upgrading to Exim 4.2x, anything prior
to that has become obsolete and is no longer supported officially or by the
mailing lists. You should be able to upgrade easily on Debian with apt,
upgrading is worth the effort, Exim 4 has many useful new features and is
easier to admin.

Will

----- Original Message -----
From: "syn uw" <syn_uw@???>
To: <will@???>; <exim-users@???>
Sent: Sunday, January 04, 2004 12:23 AM
Subject: Re: [Exim] Problem with exim on internal network


> Many many thanks for your answer, this looks exactly to be the solution to
> my problem... Now the problem is that I am using EXIM 3.35 which is the
> default of our Debian GNU/Linux 3.0r1 server. Is it still possible to use
> your configuration example ? Or is there another way then ?
>
> Regards
>
>
> >(Top post - on account of stupid temporary MS mail client - Sorry)
> >
> >The best way to get around this is to use a "smart host" for the internal
> >domains. This means routing mail for internal domains via a server that

can
> >deliver to the internal domains. If all the domains are on one server,

you
> >can use that server as a smart host and all mail to internal domains will
> >go
> >right to the destination, skipping DNS lookups and other checks. If there
> >is
> >a server on your network that can deliver to all these domains, using

that
> >server as a smart host will forward all internal mail via that machine.
> >
> >Setting up the route for this is very simple. Just place this directly
> >above
> >the "dnslookup" router in your routers configuration:
> >
> >        #This example assumes you are running Exim 4.
> >        direct_internal:
> >          driver = manualroute
> >          transport = remote_smtp
> >          route_list = !+internal_domains 1.2.3.4

> >
> >Here 1.2.3.4 should be the address of the internal server you plan to

use.
> >You also need to specify the domains. The best way to do this is to add
> >this
> >in the primary configuration, preferably near to where the other domain
> >lists, like local_domains, relay_for_domains, etc. are located:
> >
> >         domainlist    internal_domains    =
> >/usr/local/etc/internal_domains

> >
> >Now, in the file /usr/local/etc/internal_domains, create a newline

seperate
> >list of domains that are to be handled in this way, for example:
> >
> >example.com
> >customer1.com
> >customer2.com
> >myfamily.org
> >
> >In this way, you need only modify the file when a new domain is to be
> >added,
> >and no reload of the Exim configuration file as needed each time you add

a
> >domain. The flat file can also be handled with a shell script, or, if you
> >prefer, you may use a database to do this lookup, check the Exim
> >specifications.
> >
> >Will
> >
> >----- Original Message -----
> >From: "syn uw" <syn_uw@???>
> >To: <exim-users@???>
> >Sent: Saturday, January 03, 2004 11:38 PM
> >Subject: [Exim] Problem with exim on internal network
> >
> >
> >Hello,
> >
> >We are running EXIM on Linux on an internal web server running on a
> >internal
> >private network (hidden by NAT). EXIM is only responsible for sending out
> >mails from our webmail system. The problem that we are encountering is

when
> >we are sending mails to domains that are hosted on our server: EXIM does

an
> >MX lookup for a domain hosted on our servers and then gets the external

IP
> >address of that our server and not the internal address. I tryed to force
> >this by entering our mail server host's internal IP in /etc/hosts but

still
> >it takes the external address. Thus mails get undelivered as from the
> >internal network it's not posible to use external IP addresses (that's

how
> >our OpenBSD firewall works).
> >
> >Does anyone have an idea ?
> >
> >Many thanks in advance for your help!
> >
> >Regards
> >
> >_________________________________________________________________
> >MSN - More useful every day http://www.msn.ch Schluß mit Spam - MSN

hilft
> >Ihnen hier weiter.
> >
> >
> >--
> >
> >## List details at http://www.exim.org/mailman/listinfo/exim-users Exim
> >details at http://www.exim.org/ ##
> >
> >
> >
> >
>
> _________________________________________________________________
> The new MSN 8: advanced junk mail protection and 2 months FREE*
> http://join.msn.com/?page=features/junkmail
>
>
>