<div>
If your server hosts @domain.com, where is this supposed to go? If you ARE @domain.com and you send to support@domain.com which does not exist this naturally creates a delivery failure.<br />
<br />
Do you want support@domain.com to be forwarded to another address?
</div>


<div>
As I understand it, you want an internal email address (with no user account) to forward to an external email address. &nbsp;I believe this is how you'd do it:<br />
You will have to create a user with a mailbox, but you can disable the user account so that noone logs in with it. &nbsp;The email address he gets is support@domain.com. &nbsp;Now create a contact with your extarnal email address e.g. someguy@hotmail.com. &nbsp;Now on the disabled user, go to Properties, Exchange General, Delivery Options, Forwarding. &nbsp;You can set forwarding to the external contact.<br />
I can't remmeber if this type of forward is a move or a copy, so it's possible that the internal mailbox will fill up over time, unless you check it and delete periodically.
</div>


<div>
Syedm2: Split domains are tricky and might not be what he requires in this scenario. <br />
<br />
@theras2000: If he only wants forwarding he needs to create a contact. No reason for a user account. &nbsp;The contact gets the external address as you stated, plus a secondary address support@domain.com.
</div>


<div>
Wonko:Check the article...<br />
Lojkop:Enter forward all unresolved recipients to host entry.
</div>


<div>
I do know the article and use this myself and I am pretty convinced that she or he needs something else :) <br />
Let's see what the author says.
</div>


<div>
This why I love experts exchange (sometimes) -- if google doesn't work, then EE probably will. If it doesn't then I have to research it myself :'(<br />
<br />
@Sysedm2: You're right &amp;&nbsp;thanks!<br />
@Wonko: I needed Exchange to pass along the messages to the STMP connector, instead of generating a NDR because its authoritative on domain.com. I use Exchange with STMP/POP connectors as I don't trust it standalone. Sysedm2's solution was exactly what I wanted accomplished.
</div>


<div>
<div class="content wysiwyg-content">
How can I use an email that isn't added to the local SBS 2003 / Exchange server (because there is no physical user) and allow it to go through?<br />
<br />
E.g. let's assume the email is support@domain.com, and domain.com is registered within Exchange. I don't have a physical user that uses or can use an alias for support@domain.com. I'd like that to be forwarded via the STMP connector and etc to the Internet. Instead what happens is Exchange notices it handles domain.com, and replies back with mail delivery failure because it can't find that mailbox.<br />
<br />
Thanks guys.
</div>
</div>


How can I use an email that isn't added to the local SBS 2003 / Exchange server (because there is no physical user) and allow it to go through?

E.g. let's assume the email is support@domain.com, and domain.com is registered within Exchange. I don't have a physical user that uses or can use an alias for support@domain.com. I'd like that to be forwarded via the STMP connector and etc to the Internet. Instead what happens is Exchange notices it handles domain.com, and replies back with mail delivery failure because it can't find that mailbox.

Thanks guys.

SBS 2003 Exchange email bounce back

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

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).