|
|
|
date: Sun, 6 Jan 2008 21:21:01 -0800,
group: microsoft.public.exchange.clients
back
Re: relay / forward mail to remote worker
When I was referring to forwarding, this is what I meant. I did this for
some email accounts I had at a previous employer that were generic mailboxes
(like webmaster, support) and were used by interns that drifted into and out
of the positions.
I would have my standard mailbox like "webmaster", though in your case it
would be the user's domain account. I would then create a new Contact in
Active Directory, and give it the SMTP address of the intern
(homeaddress@comcast.net for example). This creates an object in Active
Directory with that SMTP address, but not an actual mailbox.
Once the mail-enabled Contact is created, I'd go into the properties of the
Active Directory user account for webmaster, go to the Exchange General tab
and then click on the Delivery Options button.
In the Delivery Options in the forwarding address area I'd select "Forward
to:" and click Modify. Here I could type in the name of the mail-enabled
Contact I had created. Once it was in the box I'd click OK to save the
changes to the Delivery Options, then OK again to save and exit the user
properties.
With the above configuration any mail sent to the webmaster mailbox would be
automatically redirected to homeaddress@comcast.net.
This may or may not be the type of setup you want. This will store no mail
on the server (so you won't have any mail to backup for this user, leaving
the integrity of mail entirely in the user's hands). You can check the box
to deliver mail locally as well as forwarding it, but if they user will
never be logging in using an Outlook Client and managing their mail volume
(and you don't have any other archiving taking place) then the mail could
pile up needlessly if this is going to go on for a long period of time.
I agree with Lanwench's suggestion of setting up Outlook Anywhere/RPC over
HTTPS, or at least using Outlook Web Access. These are the most
feature-rich options (and allow access to the Global Address List and
calendar), but if all they need is to be able to receive mails that are sent
to them, you can use the forward-to-contact option.
Joe
"msumner" wrote in message
news:AC024661-7F99-4C85-9CB0-7F3CF4E893C3@microsoft.com...
> The user does have a domain account / network login. Are you saying in
> Active Directory to configure their email to be their home
> name@comast.com?
> Where specifically are you talking about setting up the forwarding?
>
> "Joe Grover" wrote:
>
>> You could do it a number of ways. You could enable POP or IMAP access
>> into
>> your server for that user, or you could create a mail-enabled contact for
>> the user's name@comcast.com address, then forward domain email to that
>> contact.
>>
>>
>> "msumner" wrote in message
>> news:3DBCB60F-A9AE-4738-9C78-44C93D784B7A@microsoft.com...
>> >I have a user that works remotely. They need to receive internal domain
>> > mail. This should be easy. How other than OWA could they get this
>> > mail.
>> > Can I forward the mail to their home address - name@comcast.com? How?
>> > I
>> > saw
>> > how to forward to another Exchange/Domain account. They want to use
>> > their
>> > local Outlook client to access all of their email. I appreciate any
>> > suggestions.
>> >
>> > Mike
>>
>>
date: Thu, 10 Jan 2008 09:52:58 -0500
author: Joe Grover
|
|
