Exchange Server Forums

internal email routing

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Message Routing >> internal email routing

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

internal email routing - 23.Aug.2008 7:33:51 AM

marki

Posts: 2
Joined: 23.Aug.2008
Status: offline

My company is migrating from Novell to Windows, we have set up a new active directory with two sites (in two different physical locations) and two exchange 2007 servers in each location. Until now, we have been using Groupwise and while we are migrating both systems have to co-exist, groupwise is receiving emails through an appliance.
I got both groupwise and exchange to send email internally and externally ok, but I have a problem when I send email from the new exchange server to any user inside the company (using the domain that is shared). I have created a dns zone in the new AD with the same name as the one used by Groupwise and created an A- record for the email server (Novell groupwise) and a mx record pointing directly to it so all the internal e-mail would be resolved by this DNS, but I keep getting a non delivery report when any of the exchange users try to send anything to this shared domain, I guess there is something to do with routes but I am a bit lost, I would appreciate any help.

Thanks very much in advance

Post #: 1

Featured Links*

RE: internal email routing - 25.Aug.2008 11:25:29 AM

John Weber

Posts: 584
Joined: 20.Apr.2005
From: Portland, Oregon
Status: offline

OUCH!

IMHO, you are going about the migration all wrong.
1st, you need to have ONE internet connection for both GrpWise and Exchange. And then you create a connector between them. Using Novell Gateway for Exchange (GrpWise 6.5+) typically this is an Exchange 2003 server - otherwise you will have ghastly F/B sync issues.
After you have the migration figured out, choose either SMTP internal routing between grpwise and exchange, OR, use the connector, but not both.
Choose who is going to route your mail...if exchange, then configure for it, and then do it. But don't try to do both, you will get the issue you have right now.

Are you using a 3rd party migration tool or trying to use the internal sh*t?
Depending on the number of users, a 3rd party tool can be very cost effective, seeing as how you can set a schedule, perform the schedule, and stick to the schedule.

How many users?

_____________________________

-jmw
http://tsoorad.blogspot.com

(in reply to marki)

Post #: 2