<div>
The route connectors are in place, from what I can see?<br />
<br />
[PS] C:\Windows\system32&gt;Get-Ro<wbr />utingGroup<wbr />Connector<br />
<br />

<pre><code class="code-1 nolinks" id="code-20-39770507-1"><span>Name                      SourceRoutingGroup                                            TargetRoutingGroup</span>
<span>----                      ------------------                                            ------------------</span>
<span>Exchnage03-2010           Exchange Routing Group (DWBGZMFD01QNBJR)                      First Routing Group</span>
<span>Exchnage03-2010           First Routing Group                                           Exchange Routing Group (DWBGZMFD01QNBJR)</span>
</code></pre>
</div>


<div>
The mails from internet to the 2010-mailbox are now getting NDRs with the following content, if that'd help:<br />
<br />

<pre><code class="code-1 nolinks" id="code-20-39770511-1"><span>This is an automatically generated Delivery Status Notification.</span>
<span></span>
<span>Unable to deliver message to the following recipients, because the message was forwarded more than the maximum allowed times. This could indicate a mail loop.</span>
</code></pre>
</div>


<div>
Also, I tried moving the delivery from the IMSVA directly to the 2010 instead and then that one in turn can't find mailboxes on the 2003. It's sending NDRs stating that the user doesn't exist.
</div>


<div>
Rerouting the mail actually worked best. Turns out I had another pile of settings that interfered from the IMSVA.<br />
<br />
The IMSVA is now dropping the mails at the 2010 which forwards mails to the 2003 just fine.
</div>


<div>
<div class="content wysiwyg-content">
I'm in a situation where we need to drop our old Exchange 2003 server (don't ask me why it's still alive ;)) in favor of a mid-hop Exchange 2010 and then we'll migrate to 2013 Soon™.<br />
<br />
Anyhow - the 2010 server's set up and I've moved one mailbox to it.<br />
<br />
The mailbox can send and receive mails within the organization (2003&lt;-&gt;2010) just fine. It can send mails to internet, but not receive mails from internet.<br />
<br />
We've got a antispam/antivirus server as a smart host in front of our Exchange 2003.<br />
<br />
So .. Internet -&gt; Trend IMSVA -&gt; Exchange 2003 -&gt; Exchange 2010<br />
<br />
What's needed on the Exchange 2003 in order for it to forward the mails to the mailbox on the 2010 server?<br />
<br />
I've tried all kinds of various methods, but haven't been able to nail it yet.<br />
<br />
I'm pressed in order to get this working ASAP - hence the high points.
</div>
</div>


I'm in a situation where we need to drop our old Exchange 2003 server (don't ask me why it's still alive ;)) in favor of a mid-hop Exchange 2010 and then we'll migrate to 2013 Soon™.

Anyhow - the 2010 server's set up and I've moved one mailbox to it.

The mailbox can send and receive mails within the organization (2003<->2010) just fine. It can send mails to internet, but not receive mails from internet.

We've got a antispam/antivirus server as a smart host in front of our Exchange 2003.

So .. Internet -> Trend IMSVA -> Exchange 2003 -> Exchange 2010

What's needed on the Exchange 2003 in order for it to forward the mails to the mailbox on the 2010 server?

I've tried all kinds of various methods, but haven't been able to nail it yet.

I'm pressed in order to get this working ASAP - hence the high points.

Migration from Exchange 2003 to 2010 - no internet mails reaching 2010

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.