Holy crap! A technical question which actually provides background and demonstrable context. Are you sure you are on the right list?
What you are seeing is expected (well, expected by Exchange) behavior. How do your other Exchange servers route? Does each have its own IMS or do they route out through that IMS as well? You can modify the scope of your IMS potentially in Exchange 5.5 or you might also consider removing your 5.5 IMS and recalculating routing to allow Exchange 5.5 to handle the routing of mail. There is a bit of a disconnect in costing and routing while in mixed mode which makes sense sort of if you've had enough to drink. You might be thinking... well, I'll just stop the 5.5 IMS and see what happens. Well, you're not the first to think that and unfortunately the 5.5 is not a connector (despite what the "C" in IMC stands for) it's actually a gateway. So mail would just be dropped into the queue waiting for the IMS to come back online. When you're ready for Exchange 2000 to handle the routing take a leap of faith and remove the IMS from your 5.5 box(es). Things should route just fine. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:bounce- > [EMAIL PROTECTED] On Behalf Of Larry Wahlers > Posted At: Tuesday, September 21, 2004 12:29 PM > Posted To: swynk > Conversation: E2K3 server using E55's IMS > Subject: E2K3 server using E55's IMS > > Hi fellow Exchange administrators, > > I've been reading the list for a week or so, and I'm really impressed! You > folks truly know what you're talking about! Anyway, this is my first post, > so please be kind :) > > I manage 4 production Exchange 5.5 (SP4 all patches applied, on Windows > 2000) servers. I just installed our very first Exchange 2003 (with SP1) > server, and it was a bit rocky at first, but all is well now. I've put a > couple test mailboxes on it - one I successfully moved from one 5.5 > server, > and one I created from scratch - and they are able to send and receive > email > just fine using Outlook 2000. > > Here's the strange part. On both the test mailbox I moved, and the new one > I > created on the new E2K3 server, when I send email from either account, > instead of the E2K3 server sending the email directly to my smarthost, it > connects to the IMS of the old E55 server, which then connects to my > smarthost! Here is a chunk of the relevant headers. The real machine names > have been changed to protect the guilty!: > > Received: from E55server.mydomain.myorg.local (E55server.lcms.org > [10.1.3.104]) by > lcms.org (PMDF V6.2-X27 #30879) with ESMTP id > <[EMAIL PROTECTED]> > for [EMAIL PROTECTED]; Tue, 21 Sep 2004 12:07:25 -0500 > (CDT) > Received: by E55server.lcms.org with Internet Mail Service (5.5.2657.72) > id > <RMBGFW7K>; Tue, 21 Sep 2004 12:07:23 -0500 > Content-Return: allowed > Date: Tue, 21 Sep 2004 12:07:11 -0500 > From: Wahlers Test2 <[EMAIL PROTECTED]> > Subject: Test 2 > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > Message-Id: > <[EMAIL PROTECTED]> > > > It's clear from the Message-Id that the message originated from the E2K3 > server. Yet, the Internet Mail Service on the old server handled the mail > before it got to our smart host at lcms.org. I'm concerned that after I > move > all the mailboxes and decommission the old server, email will stop working > altogether, since I can't seem to manage getting the email to go directly > from new server to smart host. I did put the smart host name into the > "Smart > Host" place on the SMTP server properties, too. > > Miraculously, going the other direction, even though I use a smart host, > and > specifically forward email from that host to the 5.5 server, after moving > the mailbox and doing nothing else, the test account could receive mail > just > fine, even without repointing the forward to the new server. Man, does > that > save me a lotta work! So, lots of benefits on the receiving end, but a > quirk > on the sending end. > > Thanks for any light you might shed on this oddity. > > ==================================== > Larry Wahlers, Systems Specialist > Concordia Technologies > The Lutheran Church - Missouri Synod > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: http://intm-dl.sparklist.com/cgi- > bin/lyris.pl?enter=exchange&text_mode=&lang=english > To unsubscribe send a blank email to [EMAIL PROTECTED] > dl.sparklist.com > Exchange List admin: [EMAIL PROTECTED] > To unsubscribe via postal mail, please contact us at: > Jupitermedia Corp. > Attn: Discussion List Management > 475 Park Avenue South > New York, NY 10016 > > Please include the email address which you have been contacted with. > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
