Re: configuring accounts




"Mark Arnold [MVP]" <mark@xxxxxxxx> wrote in message news:jncps2d815sb8slreaog71do8df1ir6b21@xxxxxxxxxx
On Thu, 8 Feb 2007 23:03:28 +0100, "Jan Kucera"
<miloush@xxxxxxxxxxxxxxxx> wrote:

Hi,
I would like to ask how should I configure Exchange, AD and clients to fill
this scenario:

The company has its own e-mail, company@xxxxxxxxxxx, to which has some of
the employers access for reading as well as for sending e-mails.
Each person has two e-mails, one for business, surname@xxxxxxxxxxx and one
personal, firstname@xxxxxxxxxxxx

Company is running Win 2003 SBS Standard, Exchange 2003.
My current solution was:
- AD account with "surname" login
- AD account with "firstname" login, with loging in disabled
- AD account with "company" login, also disabled.

On the server side, company e-mail was allowed to be accessed from some
employers, and each firstname e-mail was allowed to be accesed by lastname
account.

On the client however (Outlook 2007), there had to be Exchange account,
automaticaly the loging-in account, which is lastname. Then, additional
Exchange accounts are the firstname one and the company one if applicable.
However, additional IMAP accounts were needed to be able to send e-mails
from company or firstname mails, the Exchange way did not worked, perhaps
because of security settings.

Now we are going to do full reinstallation, so my question is, if this
solution is the only possible, since I don't like it very much. Do I need to
create the AD accounts only for mails? Could the Outlook 2007 load all the
Exchange accounts which are available for the particular user? Do I have to
set up these duplicate IMAP accounts? Or how do I set up the Exchange to
allow sending e-mails from the Exchange alternative accounts? Is it possible
without this "from firstname/company on behalf of secondname" header?

How would you solve this?
Thank you for any idea,
Jan
This took some reading and working out.
Can you explain exactly why you need different mailboxes for the three
functions?
Given that I'm fairly sure you will know that you can have as many
SMTP addresses attached to a user account as you want and the users
can separate the mail into the three parts. (Any reason you're
allowing users to get personal emails into your Exchange anyway?)




The company mailbox is needed because
1) customers mostly don't know who works on their order. So they just send data to the company mail. Also orders unrelated mail is being sent there.
2) at the time the company didn't have its own server (and so many employers), it had three company mailboxes from public providers (just because sometimes some didn't work at these times) so the server regularly picks up these and stores them in the company exchange account.

The surname mailbox is needed just as you would expect, also some people just do work from another branch and this would be more mess than necessary if mixed in the common mailbox.

The personal mailbox is not my business. Let's take it as a company politics, that they offer personal e-mails for their employers. This is not america and half of them even don't have access to internet at home...

By the way, we are talking about maximum of ten employers, if this explains something. :-)

How can I add SMTP addresses to the user account without creating separate outlook account?

Thank you for your patience,
Jan

.



Relevant Pages

  • Re: OWA doesnt work for some migrated user E2K3 -> E2K7
    ... Back when we migrated from Exchange 5.5 to Exchange 2003, ... mailbox through OWA and Outlook in Exchange 2003, ... Exchange backup account - full mailbox rights ...
    (microsoft.public.exchange.admin)
  • Re: Access denied to mailboxes with Exchange Full Admin account
    ... Exchange Admins do exactly what they say on the tin. ... User A goes to File, Open, Other Users Mailbox. ... Your account must have ...
    (microsoft.public.exchange.admin)
  • RE: Exchange account - sending but not receiving
    ... Thank you for posting in the SBS newsgroup. ... Does this issue only occur with the specific user account? ... How to Enable Message Tracking in Exchange 2000 Server ... Make sure the specific user's mailbox size does not exceed the ...
    (microsoft.public.windows.server.sbs)
  • Re: LegacyExchangeDN is wrong for a user
    ... The cleanup for a crosslinked account is relatively easy for a single ... IMPORTANT - An Exchange 5.5 object that has been replicated to Active ... mailbox, and any changes on either side will replicate to the ... be deleted after the next ADC replication cycle. ...
    (microsoft.public.exchange2000.active.directory.integration)
  • Re: Accessing an email account programmatically
    ... right click on the user account for the Exchange Mailbox that you want ... Click on the "Exchange Advanced" tab and then click on the "Exchange Rights" ... An Event Sink can be thought of as a true server side ...
    (microsoft.public.exchange.admin)