Mail Flow during migration

Message Server 6.3 with patch 120229-25
I'd like to keep both email systems online while I migrate our users from our old server to the new server.
So far, i have been able to route COMs5 mail to our external mail server if it's destined for the internet with tcp_local and domain mail.example.com
What i would like to have happen now is the following:
If the destination address is @example.com and the account does not exist , forward it to mail.example.com
tcp_intranet seems to be the channel i want but i'm unsure how to configure it.
! tcp_intranet
tcp_intranet smtp mx single_sys subdirs 20 dequeue_removeroute maxjobs 7 pool SMTP_POOL maytlsserver allowswitchchannel saslswitchchannel tcp_auth missingrecipientpolicy 4 logging daemon mail.example.com
tcp_intranet-daemonEdited by: karl.rossing on Feb 8, 2008 11:43 AM
Edited by: karl.rossing on Feb 8, 2008 11:44 AM

karl.rossing wrote:
Message Server 6.3 with patch 120229-25
I'd like to keep both email systems online while I migrate our users from our old server to the new server.
So far, i have been able to route COMs5 mail to our external mail server if it's destined for the internet with tcp_local and domain mail.example.comI assume you mean "daemon mail.example.com".
What i would like to have happen now is the following:
If the destination address is @example.com and the account does not exist , forward it to mail.example.comIt sounds like you need to use the mailroutingsmarthost: domain attribute as discussed here:
http://forum.java.sun.com/thread.jspa?threadID=5236277&messageID=9968995
and here:
http://docs.sun.com/app/docs/doc/819-2657/6n4ub3hn6?a=view
Regards,
Shane.

Similar Messages

Mail-routing during migration

Hi,
I am working with a migration-project where we want to move all mailbox'es from an Exchange-org in domain a.com to a new Exchange-org in a new domain b.com. The users email-addresses will be the same in the new domain as in the current
domain. My question is: How can I configure the system so that email will be delivered correctly to users in the current domain and to the same user after it is migrated to the new domain?
Can a solution be to create a send-connector with type=internal in the current domain a.com with address space
*.a.com and send the emails to a smart host in the new domain b.com? Will the system first try to deliver the email locally to the existing Exchange-server before it sendt it via the send-connector to the new Exchange-server if the user does
not exist in the current domain (because the user is moved to the new domain)?
Thor-Egil

The simplest way to do this is to have a send connector for sending mail directly from a.com's email systems to b.com's, and vice versa. Here are the steps I've used many times for this and it's worked every time:
Give all addresses in the current organization a new proxy address - I normally use something like "<alias>@pre.company.com"
Create mail conacts for all mailboxes in a.com in the b.com organization - and make sure this proxy address is the External Email Address
Have a proxy address available for all migrated mailboxes - I use something like "<alias>@post.company.com"
Configure a send connector in a.com that sends anything with an address of post.company.com directly to the b.com servers
Configure a send connector in b.com that sends anything with an address of pre.company.com directly to the a.com servers
If a mailbox is moved from a.com to b.com, in a.com, create a mail contact with an External Email Address of <alias>@post.company.com; and in b.com, make sure you change the pre.company.com address to post.company.com
Now, let's go through what happens to inbound email:
Before any mailboxes are moved, mail comes in and is delivered in a.com - there are no mailboxes in b.com to worry about.
Once a mailbox is moved to b.com, if someone in a.com sends to that mailbox, the mail contact for the mailbox changes the <alias>@company.com address to <alias>@post.company.com and sends the message on to the other system
If someone on b.com sends mail to an a.com mailbox, the opposite happens - the mail contact for the mailbox changes the <alias>@company.com address to <alias>@pre.company.com and sends the message on to the other system
You let this run until all mailboxes have been moved from a.com to b.com. The beauty of this solution is that at any point, you can change the MX record to point to b.com's servers and mail flow will not be impeded, and both sides can be configured
so that it is authoritative for the company.com namespace, and it will directly handle sending delivery reports. The bad thing is that you need to keep the directories up-to-date on each side, making sure you create new mail contacts as mailboxes are
added - but you have that issue in any co-existence scenario.
HTH ...

Migrate Exchange 2010 to 2013 External Mail Flow

Dear All,
I am in the middle of Exchange Server 2010 to 2013 Migration. The scenario is I have single Exchange 2010 server with HUB/CAS/Mailbox and installed new Exchange 2013 with single CAS and single Mailbox server. The internal email flow between Exchange
2010 to 2013 and 2013 to 2010 is working. Having some issues and need assistance to resolve at earliest.
The issue with the external mail flow and I want to Exchange 2010 should be configured to send external email while migrating users to Exchange 2013. Once migrate all users to Exchange 2013 then will configure Exchange 2013 send connector.
How can I configure single name space of web URL for OWA both on Exchange 2010 to Exchange 2013, if user mailbox is in Exchange 2010 can access same OWA URL as user migrate to Exchange 2013.
How to configure SSL certificate, I have single URL certificate this would be enough for OWA, ActiveSync and Anywhere.
Is that possible if directly move the Exchange 2010 database to Exchange 2013 database, this will move all users mailboxes in one go or do I need to migrate users mailbox individual or in bulk.
Kindly guide if any thing missing that need to address during start the migration activity.
Thanks in Advance

Hi ,
Sorry for delay.
Question : Thanks for your valuable response. On
point no.2, I want to use same external URL for Exchange 2010 and Exchange 2013, is this possible if user is on exchange 2010 server or migrated on Exchange 2013 can use same external single name space URL to access OWA ?
Yes you can have the same External URL for the exchange 2010 owa and exchange 2013 owa.So users from exchange
2010 and exchange 2013 can access owa on the same URL from external world.For exchange 2010 users owa connections will be proxied from exchange 2013 to exchange 2010.
For mailbox connectivity issue in exchange 2013 :
1.From internal outlook clients ,Please check the internal outlook anywhere name is resolved to exchange
2013 server and also make sure the authentication set on the outlook anywhere is set to NTLM. Same time we need to have the internal outlook anywhere name on the SAN certificate.
2.Make sure the names used exchange on 2013 URL'S is available on the SAN certificate and also the certificate
needs to installed on the exchange server and that certificate has to be enabled for the required services like iis,pop.imap,smtp.
3.Make sure the outlook client request coming for internal outlook anywhere name and also to autodiscover
service is not reaching the proxy server if you have on your network.
In case if you have proxy server in your environment for internet access ,So for that we need to add the internal outlook anywhere name and autodiscover name
on the internet explorer proxy exceptions for all the internal outlook clients.We can globally achieve it through group policy.
4.please share me the output for the below mentioned command.
get-ClientAccessServer -Identity “server name” | fl AutodiscoverServiceInternalURI
5.If you are having outlook 2007 then make sure it fully patched with latest sp and updates.
6.On which operating system version those outlook 2007 clients are installed?
Please reply me if anything is unclear.
Thanks & Regards S.Nithyanandham

Keep exchange 2007 Hub transport & CAS during migration to Exchange 2010

Hello,
during a migration from exchange 2007 to exchange 2010 is it supported to keep the old exchange 2007HUB and CAS in charge of the outside mail flow (send/receive) and OWA service.
Here is the scenario :
Actual OWA url : https : // webmail . compagnie . com (2007)
Future OWA url : https : // owa . compagnie . com 2010)
Keep the old url accessible for the users which have not be migrated to the new exchange 2010 MBX server.
Indicate to the migrated users to use the new url instead of the old one.
Keep the old hub transport server (2007) handle the mail flow (send/receive) to the outside.
At the end, when all the users will be migrated, configure the new 2010 Hub/cas to handle the mail flow (send/receive) to the outside.
Thanks a lot for your answers.
David

Thanks for your answers.
So if I have understood right, the only thing I have to take care about (in order to let the 2007 cas/hub server handle the external mail flow (on which the MX is bind) until all mailboxes are migrated) is to add the 2010 cas/hub server in :
Organization Configuration ---> send connector ---> Actual 2007 send connector --> Source server
Thanks a lot.
David
That will take care of the outbound message flow, yes.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 to Exchange 2013 mail flow?

We are planning to migrate Exchange 2010 to Exchange 2013.
I understand that we need to upgrade the CAS to 2013 for Internet Facing.
What about mail flow. Currently, Internet mail flows to Exchange 2010 (single site). Can I keep it for sometime after introducing 2013 and do the cutover of HUB once all the mailboxes are moved to 2013? Or I have to get the mail flow to 2013 first.
Also, how does HUB 2010 transfer mail or receive mail from 2013? Does it get from the CAS proxy in 2013 or from HUB?
Thanks!!!

Yes, you can. But my preference is to move the mail routing early in the migration, usually even before moving mailboxes, because I believe it reduces the risk of a service interruption.
I believe it goes through the front-end transport on the CAS, since that is the TCP port 25 service.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

External Mail Flow not coming into Exchange 2013 Server

We just finished migrating from Exchange 2007 to Exchange 2013 and when I disable a certain receive connector on Exchange 2007 we stop receiving external emails. I have reviewed all of the Exchange 2013 Receive Connectors and everything looks to be fine
but the server does not get mail flow. If anyone could assist with this issue that would be great.
Thanks,
Ryan

Hi,
According to your description, all your inbound mails cannot be received in your Exchange 2013 server after you disable a receive connector in your Exchange 2007 server. If I misunderstand your meaning, please feel free to let me know.
If yes, since your MX record has been configured properly for your Exchange 2013 server, we can begin with checking the A record for the Exchange 2013 server and confirm if all external mails cannot come in your organization. And we can depend on the following
troubleshooting to narrow down the mail flow issue:
1. Check the NDR information if there is NDR.
2. Check Telnet to test the mail flow:
http://technet.microsoft.com/en-us/library/bb123686(v=exchg.150).aspx
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

OOF not working for mailboxes homed on Exchange 2010 server during migration

Hi There
I'm troubleshooting an issue during a exchange 2010 to exchange 2013 migration where the OOF is not working for users homed on the exchange 2010 mailbox servers. This applies to users using outlook 2010 and outlook 2013 .OWA works perfectly and you can also
enable OOF via exchange powershell.
Users homed on the exchange 2013 servers does not have any issues.
The exchange 2010 servers is on SP3 rollup 4 and the 2013 servers on SP1 only without any rollups installed.
So my question will be - have anyone experienced this issue during migration and will patching the exchange 2010 servers to rollup 5 or 6 and the exchange 2013 to sp1 rollup 5 fix the OOF issue then? If requested the client to patch to these levels, but
in the meantime I'm checking if anyone else had similar issues.
Any pointers will be welcome.

Hi ,
1.Please check the problematic exchange 2010 user account can able to access the ews virtual directory internal url and you can check that via browser's.It will prompt for the user name and password , please provide that .
EWS url wopuld be like - https://mail.youdomain.com/EWS/Exchange.asmx
2.Then the second step would be autodiscover check for the problematic user account.you can find that via test email configuration .There you came to know whether outlook is fetching up the proper url for ews and autodiscover.
3.Then please un check the proxy settings in browsers and check the same.
4.please use the command to check the auto discover
test-outlookwebservices
Please check the below links also.
http://exchangeserverpro.com/exchange-2013-test-outlook-web-service/
http://www.proexchange.be/blogs/exchange2007/archive/2009/07/14/your-out-of-office-settings-cannot-be-displayed-because-the-server-is-currently-unavailable-try-again-later.aspx
http://port25guy.com/2013/07/20/user-cannot-set-an-out-of-office-in-exchange-20102013-or-eventid-3004-appears-in-your-event-log/
http://www.theemailadmin.com/2010/06/exchange-server-2010-out-of-office/
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Ex2010 Hybrid to O365 mail flow delay

Hi,
Recently migrate the exchange to office 356. Unfortunately we are facing mail flow delay issue from on-premise ex2003 to Hybrid server ex2010. So I disabled 2 settings to make the mail flow from ex2003 to 2010. (Tarpitting and MaxAcknowledgementDelay).
Now the problem come, after disable this 2 settings. The mail flow now stuck at hybrid 2010 to o365. Anyone facing the same issue?
Regards,
Wayne

Hi ,
For mail flow delay :
Please review the headers of the delayed email .There you came to know on which hop it was delayed.Then you start troubleshooting on the problematic hop .
E mail headers will have the time stamp for each and every hop .
Please reply me if you have any queries.
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange 2013 CAS-MBX / Exchange 2007 Edge Mail flow

I am in the process of migrating from Exchange 2007 to Exchange 2013. I have installed my 2013 Cas/MBX into my environment with the existing 2007 Hub/MBX and existing 2007 Edge. Mail flow on the 2007 side is unchanged (working) but on the 2013
side I am able to receive mail but I can't send (from test mailbox). It just sits in the que on the 2013 CAS/MBX until it expires.
Any ideas? My Exchange 2007 servers are both upgraded to SP3 Rollup 13 so the versions should be fine.

I redid my edge subscription (applying the xml on the 2013 hub). All works the same (mail flow on the 2007 side works fine but unable to send out for mailbox's that live on the 2013 side). One thing I noticed is that when I ran start-edgesynchronization
I get the following:
RunspaceId : xxxxxx
Result : CouldNotConnect
Type : Recipients
Name : XXXX
FailureDetails : The LDAP server is unavailable.
StartUTC : 9/15/2014 2:03:23 AM
EndUTC : 9/15/2014 2:03:23 AM
Added : 0
Deleted : 0
Updated : 0
Scanned : 0
TargetScanned : 0
RunspaceId : xxxxxx
Result : CouldNotConnect
Type : Configuration
Name : XXXX
FailureDetails : The LDAP server is unavailable.
StartUTC : 9/15/2014 2:03:23 AM
EndUTC : 9/15/2014 2:03:23 AM
Added : 0
Deleted : 0
Updated : 0
Scanned : 0
TargetScanned : 0
I am able to ping my domain controllers / edge server and I can also telnet to ports 389 & 3268. I have restarted my Active directory topology service

Mail flow is not working Exchange 2010 to 2013 in coexistence mode

Hi ,
We are migrating Exchange 2010 sp3 to Exchange 2013.
mail flow is not working from 2010 to 2013, mails are qued up in smtp relay queueu.
already added 2010 ip address to 2013 receive connector and give anonymous permission.
but still mails are smtp relay queue.

Hi Sujith,
As requested by
Nithyanandham please post the error from Queue Viewer.
Few things to check.
Please remove IP address from "Default Receive connector" first.
Ensure both servers can ping by FQDN and it returns correct IP. i.e. ping exch2013.contoso.com
Make sure both exchange server can communicate each other. if possible try to telnet port 25 by FQDN of the Exchange2013 server and try to send an email from exchange2010 using the URL below. if there is any error please post error.
http://exchange.mvps.org/smtp_frames.htm
Make sure "Exchange server Authentication" is ticked in your default receive connector properties. If not ticked tick it and restart Transport service and check mail flow again.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Mail Flow between 2 AD Sites stops and EMC unavailable on the local server

Hello All,
I'm hoping you can help me find a solution to this recurring problem.
SYMPTOMS :
Mail Flow between 2 EXCH2010 servers in 2 different AD Sites (separate time zones) stops suddenly with no messages in the Event Viewer or exchange logs.
When this happens the EMC is unavailable on the local server : Error message Connection attempt to http://<servername> with the help of "Kerberos" failed : The connection to the remote server failed with the following error : Access Refused
Same error when opening Exchange Powershell
On the OTHER server (ie the one I can connect to in Site 2) I can :
1 - Connect to the first server using EMC with no problems
2 - Using mail queue viewer pointed at the server in Site 2 I can see the following error for email directed to the server in Site 1 : 451 4.4.0 Primary target address responded with: "235 00000804YIIF/<load of alphanumeric characters 80 or so long>
RECOVERY :
A reboot of the server allows access to the EMC and Powershell and mail flow once again starts.... until the next time
OTHER INFORMATION :
When in the above state, ran Exchange Management Troubleshooter which finds errors but cannot identify them : "Unknown Error" then stops !
Ran ExBPA : turns up nothing
Currently needing to reboot every day or so.
I though maybe the local server had a problem with resolving itself correctly, did some troubleshooting around that and turned up nothing. Even added itself to its hosts file in order to resolve its IP : Changed nothing.
Searched on the above error 451 4.4.0 etc and turned up nothing useful.
I think the Kerberos error is telling, but I haven't turned anything up during a search yet.
Any ideas ?
Please AMA if you need more info or clarification.
Matthew

Hello,
When the issue happens, can you telent the target server successfully?
Please refer to the following KB article to see if it helps:
https://support2.microsoft.com/kb/979175?wa=wsignin1.0
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Cisco IronPort Mail Flow Central

Hello,
We are currently in the process of trying to migrate Mail Flow Central from a windows server 2003 VM to a windows server 2008 VM. I have a few questions regarding this migration. Is their any sort of guide that I can follow? Also, what is the latest software download link for MFC? I already have the database installed (for previous version), but in the install it wants me to reinstall it again? If you can provide help files to ease this migration that would be appreciated.
Thanks,
Alex

Stephan is correct - MFC support ended Jul 2011. There may be an external customer that is willing to answer and provide any pointers for your migration. We, as Cisco, do not have any guides or best practices available for MFC. It would be all customer side work and migration supportability only.
http://www.cisco.com/web/ironport/asyncOS_sma_eol_dates.html
-Robert

Establish mail flow from Exchange 2007 to Exchange 2013

I am currently using Exchange 2007 into three sites in three cities and two of the sites are connected to Internet sending and receiving emails via Edge transport servers.
Now I am planning to upgrade to exchange 2013 CU1. I don't find any documentation on how to establish mail flow between Exchange 2007 and Exchange 2013. Will it be automatic or do i need to create specific connectors between them?

Was this question answered. We're in the same situation now as we're upgrading to Exchange 2013 from 2007. The latest CU certainly helped. Initially the test mailboxes on Exchange 2013 couldn't email each other - This was resolved with CU7 and
using "Custom Settings" - manually entered IPs for DNS in the Exchange Admin Center "DNS Lookups".
Issue at the moment Test mailboxes on Exchange 2013 cannot email mailboxes on 2007 or visa-versa and mail from external sources queues on the 2007 box.
Any assistance will be greatly appreciated.

Iphone mail app regularly requires restart to get mail flowing???

Anyone seeing this issue? Advice re how to fix?
My iphone mail app regularly requires restart to get mail flowing. That is it is running (doesn't crash) but will at time just stop getting email updates. I then have to force close the mail app (i.e. kill it) and then restart it. After restarting it the mail flows again.
Notes:
a) I do connect to Gmail for my mail - I'm using the IMAP facility for gmail currently (i.e. not the "Exchange" method)
b) I do also have the Google "Gmail" app running on my device too
c) on iPhone 3GS, latest version of IOS

I have this same problem too. I have both a hotmail and work Microsoft Exchange account setup on my iPhone and have intermitent issues with both. Sometimes the hotmail push works, but my work email doesn't push, other times it's backwards, and sometimes neither work. I can't figure it out. Usually restarting the app (closing out of the multitasking bar), and/or going into settings and disabling the affected mail account works. And to top it, I have an iPad, I'll hear the mail chime go off on my iPad, expecting it to go off on my phone....and it never does, not until I manually fetch it.
Very frustrating.

Exchange 2013 Mail Flow Through VPN

I have 2 Exchange servers in 2 different AD sites. Is it possible to route mail flow between the 2 sites through a VPN tunnel? I want to force mail flow between the 2 servers to route externally through the internet.
Appreciate any feedback.

Hi Chester,
we have a DNS record for mail and this record is pointing to our private IP address of CAS server. Network team has done network configuration for that particular IP to route the traffic through VPN tunnel to the Exchange servers in other site. Another thing
for you to think is Private IP request won't go to internet and will go to DNS server in that site and once the DNS server will resolve that request against IP address the traffic will be routed to that server.
Kindly mark this as answer if found helpful. Thanks.
Regards, Riaz Javed Butt | Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365 | msexchgeek.wordpress.com

Mail Flow during migration

Similar Messages

Maybe you are looking for