Dave C. wrote:
>>What I've done successfully is to setup a double-DNS section.
>>Publically, you have
>>
>> IN MX 5 exim.yourhost.com.
>> IN MX 10 exchange.yourhost.com.
>>
>>(the reason exchange is on there is for failover-- the exchange machine
>>will receive mail if exim ever goes down, just that spam/virus/etc will
>>get through-- your risk, of course)
>>
>>Then, you make your intranet DNS servers route mail like this:
>>
>> IN MX 5 exchange.yourhost.com.
>> IN MX 10 exim.yourhost.com.
>
>
>
> Ugh. My god why? Just use a domainlist(exim3) or manualroute(exim4)
> router to tell the exim box where to deliver mail.. You shouldnt list
> internal servers in a public DNS at all.
The reason(s) for the exchange server are outlined below-- in case exim
goes down, etc.
This also allows you to use exim as your smtp server, splitting the load.
I realise this is a bit of a hack, but in the past, it's worked well
when I used mails for mon, et al, and had them routed to different
processes-- it was easy, quick, and it worked. Although,
domainlist/manualroute is a better option.
>>That way, incoming mails will hit the exim host first, then will route
>>to the exchange host.
>>
>>Again, you can (and I recommend) do this without exposing the exchange
>>boxes to the internet-- if you put the exim boxes in your DMZ, you can
>>have your exchange boxes on your intranet.
>>
>>You could also make an exim server with courier-imap, ldap, and some
>>shared calendaring software and get rid of exchange altogether :>
>>
>>-g
>>
>>
>>--
>>
>>## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>>
>>
>
>
>
>
>
--
Glen Mehn
glen at burningman dot com at zerowaitstate dot com at doofdoof dot com
"If u ever devour the universe, remember to spit the dragon back out.xx."
-swan
