My suggestion would be two seperate subdomains for actual delivery,
such as:
"username@???"
and
"username@???"
And then, setup just "mydomain.de" on the unix box, and put in
.forwards for the accounts on the exchange box. (Or possibly some sort
of LDAP thingy like somebody else said)
On Tue, 1 Jun 1999, Marc Haber wrote:
> Hi!
>
> On one of my sites (call it mydomain.de), we are currenty using exim
> as MTA for the outside connections. The powers want Exchange for
> better collaboration functions (public folders being the first one of
> them).
>
> I refuse to let the exchange server talk directly with the Outside,
> the exim will stay to keep Exchange's harm off the net.
>
> We will continue to keep some users on the UNIX box, so exim will have
> to choose whether e-mail to somebody@??? should be delivered
> locally or forwarded to the exchange machine.
>
> This yields a lot of questions:
>
> Is it possible to have exim try to deliver to Exchange first and
> deliver locally if Exchange says "no such user"?
>
> How do I make Exchange deliver mail for somebody@??? to exim
> if Exchange itself does not have a mailbox for "somebody"? I know this
> is an Exchange question.
>
> Which "bad" things can Exchange do that I should have exim filter?
>
> I'd like to prevent the exim box from having a list of addresses that
> Exchange knows about.
>
> Can I use a domainlist router for "mydomain.de" to try to deliver to
> exchange first? How would that configuration and the director that
> handles the local fallback delivery look like?
>
> Any hints will be appreciated.
>
> Greetings
> Marc
>
> --
> -------------------------------------- !! No courtesy copies, please !! -----
> Marc Haber | " Questions are the | Mailadresse im Header
> Karlsruhe, Germany | Beginning of Wisdom " | Fon: *49 721 966 32 15
> Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fax: *49 721 966 31 29
>
> --
> *** Exim information can be found at http://www.exim.org/ ***
>
>
--
*** Exim information can be found at
http://www.exim.org/ ***
