Quantcast
Channel: Small Business Server forum
Viewing all articles
Browse latest Browse all 8539

SBS 2011 Exchange 2010 external email conundrum workaround using forwarding

$
0
0

Hello,

We plan to install an SBS 2011 server in the next month or so upgrading from an SBS 2003 server. In the last month or so, I have been experimenting with mailboxes on a test server running SBS 2011.

We have a domain name, for example, example.com. The domain name is managed by our office in New York and the mail server is hosted on a VPS server in the States. All mail on this domain goes through this server.

In our office in London, we have several external email addresses that we need to use to receive and send mail from, such asjoe@example.com, office@example.com and info@example.com. In SBS 2003 it is quite straightforward to set up 'dummy' mailboxes which can be used to download email to (POP3) and to send email from. The mailboxes are just users in AD. In the properties of the user/mailbox the following settings were enabled: Exchange Advanced - Mailbox Right - Full mailbox access and Security - Send AS for the appropriate users. It is then a straighforward matter to set up the POP3 Connectors in Exchange Management Console and to configure the email accounts in Outlook 2003.

Unfortunately in SBS 2011 and Exchange 2010 there doesn't appear to be the same versatility as in SBS 2003. I have encountered all sorts of problems trying to replicate the email setup on the test SBS 2011 server. The only way around which is close to our current setup is to use 'Forwarding' in Exchange 2010.

This was the procedure if anyone is interested:

Setting up External Emails

1. in EMC - OC - Hub Transport - Remote Domains - create the new domain, such as 'example.com'.

2. In SBS 2011 Console create a new user/mailbox for the external email address (such asjoe@example.com, which is the mailbox for receiving and sending email), and set up as a 'Standard User'.

3. Then go to EMC and configure the mailbox for receiving and sending email -  EMC - RC - Mailbox. Check that the user mailbox is displayed - select 'Properties' - Email Addresses tab - Add the External Email address, uncheck 'Automatically update e-mail addresses based on e-mail address policy', click on 'Apply' and then set the External email address as the 'Set as Reply'. Click on OK. Click on 'Mail Flow Settings' tab - Delivery Options - 'Send on Behalf of' select the users who need to use this mailbox to send emails from - click on OK.

4. Then set up a 'Forwarding' mailbox that will act as the internal email mailbox that the external emails will be delivered to. In SBS 2011 Console create a 'Forwarding' new user/mailbox, for example 'ForwardingJoe' and set up as a 'Standard User'. Then go to EMC - RC - Mailbox. Check that the 'Forwarding' user mailbox is displayed - select 'Properties' - Email Addresses tab - Accept the default email address which in this example will be 'ForwardingJoe@the internet domain name' that you registered when setting up the SBS 2011 server for an 'internet presence'.

5. Then select the External mailbox (as in 3. above) Properties - Mail Flow Settings - Delivery Options - Forwarding Address - check 'Forward to' - then browse to the 'Forwarding' mailbox (as in 4. above) that the external emails will be forwarded to. At the same time select the 'Users' that you need to Grant Permissions to 'Send on Behalf of'. Click on OK. Click on OK.

6. The to finish the configuration in EMC - RC - Mailbox highlight the 'Forwarding' mailbox - right click and select 'Manage Full Access Permissions' and once again select the users that will require these permissions which will no doubt be the same users as in 5. above.

6. Lastly, go to the SBS 2011 Console and set up the POP3 connector and remember to select in 'Windows Small Business Server e-mail account' the Forwarding mailbox that the external email address corresponds to.

7. Set up the 'Forwarding' mailbox accounts in Outlook.

A little long-winded but it seems to work well on the test server.

I would be grateful to hear from anyone who is more experienced in Exchange 2010 and perhaps who has reservations about this scenario as being contrary to best practice, as I would like to go live with it in a production environment in August.

Many thanks,
Mark


Viewing all articles
Browse latest Browse all 8539

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>