[rickyratliff]

Hello. I am currently administering a Windows Server 2008 R2 Standard with Exchange 2010 environment.

I have previously used the following method to forward messages to an external account:

First, I create a mail contact in Exchange with the e-mail address being that of the external account. I then create a rule in the local account for all messages received to be forwarded to the mail contact(external account). This method gets the job done, but i'm curious if any of you have a better (easier) way of doing this.

FYI, the reason i'm forwarding messages to external accounts is because the executives don't like having to check more than one account for e-mail.

Thanks.

[Spyderturbo007]

Unfortunately if you take a look at the sites Terms of Use you will see the following under section 3b:

Quote

We offer free computer help and tech support for home and personal use. We are not here to support others that work for profit, or to support/replace your company's IT department.

So you probably won't be eligible to receive free help. Sorry.

[rickyratliff]

And thats what happens when you don't read the terms.

Sorry, hope you won't think less of me, I misinterpreted the intention of the site.

[Spyderturbo007]

I don't normally read the TOU either.

Just remember though, if you have problems with your home PC in the future we will be more than happy to lend any assistance possible!

[mbond65]

That is currently the best practice. Of course, you can then create a distribution group and foward the distribution group if you want various internal or external addresses to receive the fowarded emails

Best practice is checking that the foward is configured to send both the mailbox and the address you want the mail fowarded to

[Troy]

What I prefer to do is use the POP3 Connector to receive other emails and deliver them to the one address as required. I'm not sure if you have access to this on Server 2008 R2 Standard as I mainly work with Small Business Server which includes this. That way the only email they have to check is their work email upon which we can place security restrictions as necessary to ensure that confidential business emails aren't simply forwarded elsewhere.

Otherwise I have set up forwarding in the method you describe also - it depends on what the client wants to achieve.

[dsenette]

it would be quicker to create a transport rule at the server level for all of the email redirects that way it doesn't have to filter all the way down to the mailbox before it get's forwarded on to the external user. especially if you're just forwarding everything that comes in for the user in question.

[ChiliTech]

Not sure what you mean by "at the local user", but do that all from the exchange server. Create the external contact, then go to "Delivery Options" for that executive and chose the "forward mail to" option and choose the new contact. That way you are not involving the client side and relying on a PC being powered on and logged in.

[dsenette]

of course, that method uses an exchange CAL for the external contact and the executive's local exchange account. if the executive doesn't actually have a local account at all( which in this case, seems to be what's going on) creating a transport rule will apply without needing a contact or an exchange user at all.