E2K3, E2K7, and Sendmail oh my!
We have a fun enviroment here that is causing some issues with our E2K7 testing. We have an old Sendmail system that handles our legacy .email.ca domain. We have an E2K3 org that also handles our .email.ca domain. Users are in both and will remian that way for long time. We want to add E2K7 to our enviroment that also handles our .email.ca domain. We have no problems with our Sendmail/E2K3 setup. Our mail gateway routes to the correct side of the fence for incoming email and for outgoing mail our E2K3 org is set to use the "forward all mail with unresolved recipients to host" and forward all .email.ca email to our gateway which then sends mail to the Sendmail side. Our problems start when we get to the E2K7 stuff. How do we make E2K7 behave the same way as the unresolved recipients setting in E2K3? The next part of the problem is that we don't want E2K3 sending unresolved email through the E2K7 side initially as it will be rather volitile and may not be reliable. It seems that after we set up the E2K7 server all mail destined for .email.ca that was not in the exchange org would just queue up. We understand that is because E2K7 was not properly configured to send but what we want to stop is E2K3 from sending any of those messages that way until later. We still want them to go straight to the mail gateway. Can we weight the E2K7 side so that the mail gateway is the preferred destination for thoese messages? I realize this is a big post but any help would be greatly appreciated. Thank you, Josh
February 11th, 2007 10:46pm

We seem to have a similar configuration. X3 is non-authoritative for our primary email domain and we send/rec off our Sendmail servers that are Internet exposed and Host the MX records. Also the Sendmail servers know how/where to route mail to other mailnodes that also have mailboxes for our primary email domain. When X7 joined our X3 Org, All Email domains were all upgraded to "Authoritive". X7 clients we unable to route to SendMail for mailnodes that share our primary email domain. We found a workaround, check your Accepted domains in X7 EMC and change your primary domain from "Authoritative" to "Internal Relay" Type Accepted Domain. Let us know if this works for you.
Free Windows Admin Tool Kit Click here and download it now
February 12th, 2007 12:16am

Del, That did solve our internal mail problem, Thank you. Now our only issue is that all such email is flowing from the E2K3 side to the E2K7 side before leaving for the sendmail gateway. We are thinking of uping thecost on our RGC between them to see if that will persuade mail to go out the E2K3 side instead (just until we are done testing the E2K7 side). Josh
February 12th, 2007 10:20pm

That's sounds as designed. Weadded a x7 send connector with a Bridgehead of a x7 HT. We are still testing but it seems x3 mail is handled by it's connector/bridgehead and x7 mail is handled by x7 send connector/bridgehead.
Free Windows Admin Tool Kit Click here and download it now
February 12th, 2007 10:53pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics