Exchange and Scalix co-existing

[gbecker]

The company I currently work for is currently trying to migrate to an open source format for certain portions of the company. I am running into the following problem.

All VP's and Directors will keep their email on our exchange 2003 server, all other employees will be moved to a Scalix (linux email server). I am trying to keep everyone on the same domain (xxx.net)

I figured out how to get email to follow into Scalix and if the account does not exist pass the smtp message to exchange. So scalix is not the issue.

The problem I am having is getting exchange to pass messages to scalix. If a director sends a message from his exchange account to a general user, he gets an undeliverable message because exchange is not sending the message to scalix after checking its own mailboxes.

Any Ideas??

this is a basic diagram on how email should flow for the company.

incoming smtp message--Firewall-->Email scanner->Checks Scalix<--->Checks Exchange

Basically trying to setup just like if you had two exchange servers. exchange 1 for one half of the company and exchange 2 for the second half.

Thanks
Glen

 

[nsantin]

On the SMTP Virtual Server properties, goto the Message tab and set the other server in the "Forward unresolved messages" box. This will forward any messages for addresses that exchange doesn;t know about but are part of the recipient policy.

 

[gbecker]

Thanks that worked

 

[gbecker]

Quick Question.
If I have both servers sending undeliverable messages to each other will that cause a loop?

 

[nsantin]

Im not sure, since its forwading as an SMTP message then I suspect it would loop if it was an invalid address.
Try it and advise

 

[58sniper]

Yes - that'll cause a mail loop. That's the price you pay for having two different solutions in place.

Set it up that way, intentionally cause the loop, then show the boss why going to an open source solution was a mistake!

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)

Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt