SBS2003 Exchange - Bypass Email Services?

I wondered if someone could let me know how to set up Exchange Server 2003 on Small Business Server 2003, after installation, so that email services are bypassed, and only the shared calendar and contacts are utilized. We want the Outlook 2003 Client to access mail over POP3, as it has before, since all the addresses are hosted externally. We want the PST files to be maintained on the client PCs and laptops. However, we want to be able to share calendars and contacts centrally within the domain. What are the steps to go from the default SBS2003 setup to essentially disassociating the email services from Exchange Server, while keeping the other shared resources? What steps to get the Outlook 2003 client, which was pushed from the server during the domain build, so that it does not send or receive email using the Exchange server, but still has the ability to share all other resources?
Thanks for any help!!
johnny5

 

Just set up a pop3 account on each client and set as default.
Then tell outlook to store mail in Personal Folders.

When your building each user acount in the AD it asks you if you want to set up an Exchange Mailbox.

 

So if I already have accounts in AD, how would I tell it to remove their Exchange mailbox? And can I somehow move all their mail from the Exchange mailboxes to local mailboxes (personal folders) on each Outlook client?

 

Haven't done it in a while but.
In Outlook (XP or 2003)
Tools/E Mail Accounts/View or Change Existing E Mail Accounts
And change the Delivery Location to: Personal Folders. (see Below)

Screen Shot

The trickey part is sometimes the mail will automatically move to the personal folder when you close Outlook and re open and sometimes you have to import/export the .pst file from the exchange mail box to the personal folder.

Now to remove the Exchange Mail box from the AD (after you moved the mail) thats an easy one.
Right click on the user name in the AD and select Exchange task. It's pretty self explainatory from there.

I do have one question? Why in the world would you want to dump the exchange mail box?
That elliminates local E Mail and several other features. It may also elliminate public folders.
That's kinda like having a prize stud Bull and making him a Steer.

 

I am looking into this scenario in order to alleviate these recurring errors:

> The following recipient(s) could not be reached:
>
> <name@domain.com> on 7/7/2004 8:38 AM
> You do not have permission to send to this recipient.
> For assistance, contact your system administrator.
> <exchangedomain.com #5.7.1 smtp;550 5.7.1 *** We do not accept
> spam <http://home.core.com/spamblock> http://home.core.com/spamblock
> 381272 ***>

And

This is an automatically generated Delivery Status Notification.
>>
>> THIS IS A WARNING MESSAGE ONLY.
>>
>> YOU DO NOT NEED TO RESEND YOUR MESSAGE.
>>
>> Delivery to the following recipients has been delayed.
<name@aol.com> or <name@cs.com>

ALWAYS aol or cs are delayed

And

The following recipient(s) could not be reached:

'name1@domain.com' on 6/30/2004 11:29 AM
550 5.7.1 <name1@domain.com>... we do not relay <sendername@exchangedomain.com>

None of these errors were encountered before installing the exchange server, so I assumed that the virtual SMTP server was to blame and that bypassing mail services would alleviate these errors. Do you think that is accurate or should I be attacking this from another angle?
Additionally, the same recipients who are bounced back or delayed can be sent to successfully from the web interface of the externally hosted ISP email addresses. In other words, the messages only fail if sent from the Outlook client, even after setting the client to POP3 as default (but mail is delivered to Exchange Mailbox still). This tells me that it is somehting in the Exchange Mail service that is causing these rejections and delays.

 

The easy fix is to build a pop3 account in outlook and set it as the default.

Your incomming/outgoing pop/smtp mail will never go through exchange this way.
However, this is not going to clean up your error logs as you have some DNS issues and I'm not the one to guide you on that because I struggle with it myself.

If port 23 is not forwarded through your firewall to the server your not getting Spamed.