<div>
<div class="content wysiwyg-content">
We have 3 locations. One location (Westside) uses the pop3 connector to download to the exchange server and the other two location just bring email down into Outlook via pop3.<br />
<br />
When a message is sent from Westside to one of the other branches we get a message back saying &quot;the email account does not exsist at the organization this message was sent to.&quot;<br />
<br />
It looks like exchange is trying to take full control over our domain name. I know there is a way to tell exchange not to not to take control of the domain name. I just cant remember.<br />
<br />
Any help would be great. Thanks in advance!<br />
<br />

</div>
</div>


We have 3 locations. One location (Westside) uses the pop3 connector to download to the exchange server and the other two location just bring email down into Outlook via pop3.

When a message is sent from Westside to one of the other branches we get a message back saying "the email account does not exsist at the organization this message was sent to."

It looks like exchange is trying to take full control over our domain name. I know there is a way to tell exchange not to not to take control of the domain name. I just cant remember.

Any help would be great. Thanks in advance!



Exchange 2003 Pop3 Connector sending issue

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.

Email Protocols

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.