Re: Intersite Communications

Ok.. a little bit of reading and I think I am understanding you.

from the way that I understand things now:
If I send an e-mail from my 2003 mailbox to a 5.5 server is goes via an
MTA/X.400/RPC connection (as provided by my 5.5 server's MTA).

If I send an e-mail from a 2003 mailbox to one on a different 2003
mailserver (within my VPN) it should go via SMTP, but work out the other
mailserver via an "A" record look up?
It works this out becuase it knows that the mailserver for that user is the
OTHER mailserver as this is in the Active Directory.

I take it that this is all established based on routing groups then? If so,
I have an Administrative Group called "Melbourne" (where my current
mailserver resides - it has a Master (my 2003 server) and a member (my 5.5
server) - they communicate via X.400/MTA...).
When I do the same thing in Sydney, won't I have a "routing group" for
Sydney too? In essence - I will have 2 "administrative groups" - one called
Sydney and one called Melbourne...

So - how do I break the bind between the 2003 and 5.5 servers then?
If I upgrade the Sydney 5.5 server - won't I be removing the "site Connector"?
Do I assume that the Sydney 2003 server will "automagically" start sending
e-mail to Melbourne 2003 via SMTP?

I am looking for how the messages get sent here.
The documents/books that I am reading are saying the same as you: Set it up
and it all works....
I intend to test it tomorrow (it's 5:00pm and I am tired!), but if anyone
has done this - I would be keen to know how/if it works!

"Bharat Suneja" wrote:

> Hi Michael,
>
> To summarize, you are wondering how mail is routed between mailboxes
> residing on Exchange Server 2003 boxes in different sites. The easy answer:
> directory lookup tells Exchange on which store/server the internal
> recipient's mailbox resides.
>
> If you have different sites, you can connect them using a routing group
> connector - it uses smtp.
>
> You don't need to setup sub-domains to route mail to the other site. For
> internal mailboxes, delivery is not made based on DNS resolution - as it
> would for external users/domains, where smtp defaults to doing a dns lookup
> for mx records.
>
> --
> Bharat Suneja
> MCSE, MCT
> --------------------------------
>
> "MichaelW - Melb.Aus." <MichaelWMelbAus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message news:31FD1E64-6165-4B09-8D5E-BEACD42CBE9D@xxxxxxxxxxxxxxxx
> >I am running 4x Exchange 5.5 servers and 1x 2003 Server.
> > Each 5.5 server resides in an "Administrative Group", and the 2003 is in
> > one
> > of those groups. ADC is installed and working - basically the whole
> > company
> > has been working on this for the past few months. (OMA/OWA running nicely
> > too..)
> > All servers (except EX2003) are on win2000. The AD is (currently)
> > Win2000 -
> > as are GC's. One DNS domain and one forest. All servers are on one big
> > network (routed via VPN - no Internet connectivity between them.... ping
> > any
> > of them via 192.168.xxx.xxx)
> > The plan is to migrate everyone OFF 5.5 to 2003.
> >
> > My problem is fundimental on how I move forward from here.
> > I am considering using a "swing server" to do the migrations (at opposite
> > ends of Australia - so I will visit each site as the links aren't capable
> > of
> > supporting the 5+Gb of mailboxes just yet!) - drop a server in, migrate
> > the
> > users off the 5.5, drop 5.5 and reinstall with 2003, and migrate back.
> > Seems
> > pretty easy(?)
> >
> > Essentially, my question is:
> > How do the Exchange 2003 server talk to each other once they loose the 5.5
> > "site connectors"?
> > I know, I could put a second server in each state, run 2003 on it and join
> > it to that states Administrative Group - like I have in one state - and
> > mail
> > will pass back and forth using the 5.5 site connectors... it would work -
> > but
> > buying 5x servers just for e-mail is not on the cards... Currently, 5.5
> > and
> > 2003 are in the "Melbourne site". I am on 2003, and when I send mail it
> > goes
> > between 2003 and 5.5, then Melbourne to Sydney via 5.5 connector... I
> > would
> > assume that when I migrate Sydney.. then it will appear in the Sydney
> > mailbox
> > on their 2003 server (when I do it)...
> > But how do I eliminate the 5.5 site connector - how will the 2003 talk to
> > the 2003 in each site?
> >
> > I just cannot find anything that will answer that question.
> >
> > From what I guess is that it uses SMTP... which raises a fundimental
> > problem.
> >
> > We have one "internal" dnsdomain (that we share with an external dnsdomain
> > too).
> > One domainname and no subdomains... so if I send an e-mail from a user on
> > the Melbourne mailserver, how does SMTP resolve/route/know-how-to-route to
> > a
> > Sydney mailserver.
> >
> > In 5.5 - it looks up the mailbox x.400 address - see's what server that is
> > on - send it to the MTA that puts it into the relevant queue to be sent by
> > a
> > site connector.... but there doesn't seem to be any beast.
> > So I can only guess that it sends it to the smtp connector that
> > established
> > based on "WHAT?" to send it to XYZ server??!!!
> >
> > The way I see it - we either have to set up "subdomains" ie..
> > melbourne.company.com.au AND sydney.company.com.au - and then set DNS up
> > with
> > MX records for both servers - that way if someone sends an e-mail to
> > "sydney"
> > SMTP knows how to route up there.
> > OR - we have to get some sort of connector that says "if someone routes to
> > the Sydney mailserver send it this way"...
> >
> > buggered if I can see how this is done...
> >
> > I don't see this domain changing to native mode any time in the next few
> > months.. at least not until all the 5.5 servers are eliminated...
> >
> > This fundimental problem is frealking me out.... anyone give me some
> > input?
> > (PS: for now - the Administration groups are based around the states... I
> > *could* eventually put them all in one group - but it will have to stay
> > this
> > way for now)
> >
> > any input (aside from the "well - you are just an idiot - at can't be
> > done")
> > would be greatly appreciated....
>
>
>
.

Relevant Pages

  • Re: Suche Faxserver mit integriertem Mailserver
    ... Ich suche einen Faxserver mit integriertem Mailserver. ... GFI FAXmaker integrates with Exchange Server 2000/2003 via a standard Exchange SMTP connector. ...
    (microsoft.public.de.german.windows.server.general)
  • Re: sending mails to outside
    ... If you have one server you probably don't need a smtp connector. ... Delivering all mail to another mailserver (could be the mailserver from ... Delivering every mail yourself to the destination mailserver, ...
    (microsoft.public.exchange.connectivity)
  • Re: javascript dns look up
    ... I want to evaluate an email address against a server to see if it is valid, ... Many ISPs reject all outbound SMTP traffic, ... directly with the target user's mailserver. ... and use Telnet to test the process manually. ...
    (comp.lang.javascript)
  • Setting up SMTP Help needed
    ... Setup a Windows 2003 Server Standard Edition. ... Added SMTP / POP to send receive e-mail. ... Configured Outlook Express to access mailserver. ...
    (microsoft.public.inetserver.iis.smtp_nntp)
  • RE: SMTP Server remote queue length alert
    ... Thank you for posting in the SBS newsgroup. ... automatically creates a SMTP connector for outgoing messages. ... bridgehead defines the Exchange server which can use this SMTP connector to ... What method is used to send outgoing email (DNS route or ISP ...
    (microsoft.public.windows.server.sbs)