<div>
Oh and I forgot to add that I am watching the interface with wireshark. When sending email as b.com, I see no SMTP traffic on the wire. I just get an undeliverable from exchange. So Exchange never tries to send the email out.
</div>


<div>
Is domain b.com an authentication domain or simply a new SMTP suffix? Has Exchange been marked as authoritative for the domain in Recipient Policies? Is there an external DNS infrastructure to support the new domain? ie: MX / PTR records?
</div>


<div>
By default Exchange Server 2003 is authoritative for every SMTP Address space in the Recipient Policies where the Checkbox &quot;This Exchange Organization is responsible for all mail delivery to this address&quot; is activated. <br />
<br />
To see if an SMTP address space is authoritative, follow these steps: <br />

<ul>
<li>Start Exchange System Manager, </li>
<li>Click Recipients, and then click Recipient Policies. </li>
<li>Right-click Default Policy or any other created Policy, and then click Properties. </li>
<li>Click the E-Mail Addresses tab. </li>
<li>Click SMTP and then click Edit. </li>
<li>Check if the Checkbox &quot;This Exchange Organization is responsible for all mail delivery to this address&quot; is activated or not</li>
</ul>
If the checkbox is selected, than Exchange Server is authoritative for that address space. If this checkbox is not selected, this Exchange organization is not authoritative for that e-mail address space. <br />

</div>


<div>
Gupnit,<br />
That checkbox is checked. I believe the recipient policy section works fine, as I can receive inbound mail to b.com just fine.<br />
<br />
It goes without saying that if I can send external email to this b.com domain, all the DNS records are fine. <br />
<br />
As I said, OUTBOUND email when sending from b.com does not work, whereas a.com outbound works fine.
</div>


<div>
OK, now b.com cannot even email a.com, at least from my account. I know another email account worked earlier because they replied to me and I got it. I will check with that user in the morning.
</div>


<div>
<ol type="1">
<li>Do you get any NDR, send the details</li>
<li>What about Message Tracking, send the details</li>
</ol>
 <br />

</div>


<div>
THe exact message back is You do not have permission to send to this recipient. &nbsp;For assistance, contact your system administrator. <br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; MSEXCH:MSExchangeIS:/DC=lo<wbr />cal/DC=Dom<wbr />ainName:Se<wbr />rverName 
</div>


<div>
When I ask for a delivery receipt, i get.<br />
Reporting-MTA: dns;Hostname.domainname.co<wbr />m<br />
<br />
Final-Recipient: rfc822;blah@gmail.com<br />
Action: relayed<br />
Status: 2.5.0<br />
X-Display-Name: blah@gmail.com<br />
<br />
This is an automatically generated Delivery Status Notification.<br />
<br />
Your message has been successfully relayed to the following recipients, but the requested delivery status notifications may not be generated by the destination.<br />
blah@gmail.com<br />
<br />

</div>


<div>
OK,the issue is now something different, and it is more tolerable.<br />
Outbound email WILL work from b.com IF your primary email address is name@b.com. &nbsp;<br />
However, if your primary email address is name@a.com, and you craft an email in Outlook, change the FROM field to name@b.com, then you get the NDR. &nbsp;It's using the FROM that makes it break. Perhaps there is a different way to send email from one of your other email aliases than that?
</div>


<div>
The FQDN in your SMTP Virtual Server has to match the server's external name. If it is different then you will get that error message.
</div>


<div>
Will give you enough food for thought ... <a href="http://searchexchange.techtarget.com/generic/0,295582,sid43_gci1222337,00.html" rel="ugc">http://searchexchange.techtarget.com/generic/0,295582,sid43_gci1222337,00.html</a>
</div>


<div>
Ok, my issue is exactly what is covered here.<br />
<a href="http://www.tek-tips.com/viewthread.cfm?qid=1440355&page=1" rel="ugc">http://www.tek-tips.com/viewthread.cfm?qid=1440355&page=1</a><br />
This seems kinda like bs to me that this is not possible. Can anyone point me to a microsoft article on this? How about the third party tools that they mention?
</div>


<div>
<div class="content wysiwyg-content">
We have had domain a.com working, sending our outbound email thru our spam filter provider. We just added a new domain b.com to our exchange server. We cannot get it to send email our from b.com. &nbsp;a.com can email b.com and vice versa. Externally, anyone can email a.com and b.com. It's just that outbound connections from b.com do not work.<br />
<br />
We use an SMTP connector to do the outbound email for a.com. We select the Forward all mail thru this connector to the following smart hosts. We have our local bridgehead showing. Under address space we have *. &nbsp;We haven't done anything for b.com related to smtp connector, because it should probably just work using a.com's connector, since there is nothing a.com specific in it. However, no joy.<br />
<br />
Any help?
</div>
</div>


We have had domain a.com working, sending our outbound email thru our spam filter provider. We just added a new domain b.com to our exchange server. We cannot get it to send email our from b.com.  a.com can email b.com and vice versa. Externally, anyone can email a.com and b.com. It's just that outbound connections from b.com do not work.

We use an SMTP connector to do the outbound email for a.com. We select the Forward all mail thru this connector to the following smart hosts. We have our local bridgehead showing. Under address space we have *.  We haven't done anything for b.com related to smtp connector, because it should probably just work using a.com's connector, since there is nothing a.com specific in it. However, no joy.

Any help?

Exchange, two domains, SMTP Connectors for outbound email not working for new, second domain

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.