Re: Tough E-Mail Problem
- From: Jon-Alfred Smith <jonsmi@xxxxxxxxxxxxxxxx>
- Date: Sun, 10 Feb 2008 12:45:11 +0100
On Sat, 09 Feb 2008 18:31:00 -0600, Bilbo
<wlp<faux>fake<at>email<dot>hal-pc.org> wrote:
An ISP currently hosts the e-mail domain and there are two people
currently having mailboxes in that domain who will do not have Windows
desktop accounts. By all rights, they shouldn't have such accounts.
They currently send/receive mail on that domain using POP3 clients
(Outlook 2003 and Eudora 5.1). They'll need to have their mailboxes
hosted by Exchange too and they'll need access to them.
Is there a way to set up an e-mail only account in SBS?
For all practical purposes: Yes. As was pointed out here, technically
there is no such thing as an "e-mail only account." In Exchange 2003,
all mailbox accounts are mailbox-enabled user accounts. Thus each
"e-mail only account" will require a user account and a CAL.
The trick is to prevent these accounts from logging on to the domain
or forest.
In larger environments you would establish a resource forest with
disabled mailbox accounts, so that users cannot use that account to
log on to the forest directly.
With SBS the easiest approach is likely to be:
* Add these two people as users with the user template
* Double-click the account
* Chose the account tab
* Chose Log On To
* The following computers
* Add the SBS server
The effect is. They can only log on to the computers listed under The
following computers. However, as users they cannot log on to the SBS
Server directly. But they will be able to access their mailboxes.
If they try to log on to the SBS server, they will receive this
message: "The local policy of this system does not permit you to log
on interactively."
If they try to log on to a workstation, they will receive this
message: "Your account is configured to prevent you from using this
computer. Please try another computer."
Is there a way to give these two external users POP3 access to
Exchange?
As discussed here, POP3 is not your best option. OWA or Outlook
Anywhere (RPC over HTTPS) with caching enabled works a lot better. You
can customize address lists and permissions for Public Folders.
NOTE: I have only tested the approach described above with OWA. But I
would be surprised if it wouldn't work with Outlook Anywhere or POP3.
Given that they will NOT be needing Windows accounts for any other
purpose, is there a "better" way of meeting their e-mail needs within
the current e-mail domain without setting up desktop accounts?
You could chose Logon hours and deny all hours of the week, and
forward the mail to another e-mail address.
jas
.
- Follow-Ups:
- Re: Tough E-Mail Problem
- From: Bilbo
- Re: Tough E-Mail Problem
- From: Bilbo
- Re: Tough E-Mail Problem
- References:
- Tough E-Mail Problem
- From: Bilbo
- Tough E-Mail Problem
- Prev by Date: SBS ISA 2004 + Publishing Terminal Server
- Next by Date: Re: Tough E-Mail Problem
- Previous by thread: Tough E-Mail Problem
- Next by thread: Re: Tough E-Mail Problem
- Index(es):
Relevant Pages
|
