Access and use shared email addresses - Part 1
In this article we will introduce you to shared email addresses using an example that relates to most administrators.
Neil Hobson
Often companies want their users to be able to access email sent to a common address such as info@neilhobson.com. Ensuring that multiple users can access emails sent to this address is a key requirement, but the ability for them to reply to this email is also essential. In addition, it is also necessary that these replies need to have the addresses of individual users instead of the general info@neilhobson.com address. In this article we will show you some ways to fulfill those requirements. You will see that the term email address in this article will be used instead of the term shared mailbox because an email address can be assigned to multiple mailboxes.
In the example scenario, the target address is info@neilhobson.com as mentioned above. There are a total of three users who have access to emails sent to this address and named Ann, Bob and Carol. So let us first consider some methods for accessing a shared email and will consider the second method in Part 2 of this series.
Distribution lists
The target method is considered here as the distribution list method. With this method, it is possible to create a list and then assign it to info@neilhobson.com and then add Ann, Bob and Carol as members of the list. When someone outside the company sends an email to info@neilhobson.com or a certain user inside selects the group distribute information from Global Address List (GAL), then an email copy will be allocated to Ann, Bob and Carol. Let's see how to set up in Exchange 2007.
The first thing we have to do is create a distribution list. Here's how to do this with the Exchange Management Console:
- Run Exchange Management Console, find the Recipient Configuration and Distribution Group button.
- Right-click Distribution Group and select New Distribution Group . from the right-click menu, or select the menu option with the same name from the Action panel .
- At the Introduction window of New Distribution Group, make sure that the New group option is enabled and then click the Next button.
- On the Group Information window, select the Group type of Distribution because we do not need security groups at this time. Name the group in the Name field and you will see the Name (pre-Windows 2000) and Alias fields appear. In our example, the Info group will look like you see in Figure 1.
- When you click Next on the Group Information window, the New Distribution Group window will be displayed and give you an overview of the configuration. Suppose you like that configuration, then click the New button to create a new group.
We have configured Exchange 2007 with Accepted Domains and E-mail Address Policies settings to ensure that the primary SMTP address created for the new group will receive the neilhobson.com domain name. By using Info 's Alias field as shown in Figure 1, the default SMTP address for this new group has been set to info@neilhobson.com.
When a group is created, go to the properties page of the group in the Exchange Management Console and select the Members tab. Here you can click the Add button to add Ann, Bob and Carol to group members. This is clearly shown in Figure 2.
When someone sends an email message to the Info distribution team, all three Ann, Bob and Carol then receive a copy. The problem with this method is that members of the distribution group cannot guarantee who is processing the request when all households receive their own copies. This means that all copy of the message is initially marked as unread, but if (for example) Bob reads his copy of the message, Ann and Carol's copy is still unread. In addition, if Bob replies to that message, Ann and Carol will not be able to see the reply he sent. One way to fix this problem is to ensure that all members of the group use Outlook All or the Outlook Web Access (OWA) function, but this also means that any external user Every member sees all members of the group unless the Blind Carbon Copy (BCC) option is used. In addition, this method requires the members of the group to remember to use the Reply All feature from the beginning. It can only work with distribution groups that contain a small number of members because larger groups can cause too much messaging activity when the Reply All function is used.
Also, the default reply will appear from a real user address. For example, if Ann replies to a notification, that message is sent from Ann's account and the recipient will see the address is ann@neilhobson.com. In other words, the message will not be sent from the distribution group's email address info@neilhobson.com. To solve this problem, team members must be allowed to send as Info distribution group. Please use the Add-ADPermission command in the Exchange Management Shell as the example below:
Add-ADPermission Info –User 'neilhobsonann' –ExtendedRights 'send as'
The output of the command is shown in Figure 3 below.
The above command itself is easy to understand, allowing the NEILHOBSONAnn account to have 'send as' permission. Therefore, Ann can use the From field in Outlook to send as a distribution group. This is clearly shown in Figure 4 below.
Obviously without the above permission, Ann will definitely not be able to send as a distribution group. In this case, you can see in Figure 5, an error message will appear to indicate your problem.
Conclude
This is part one of the two-part article. In this first part, I showed you the cool method used to allow access to a shared email address, which was previously known to create a distribution group with an attached SMTP address. attached. You can allow individual users to receive email sent to this address and respond by sending as a shared email address. In the second part of this article series, I will show you how to access the shared mailbox with the previous SMTP address on it.
You should read it
- Transfer from Linux Mail Server to Exchange Server 2007 (Part 2)
- Enterprise e-mail management with Exchange Server 2010
- Managing log files of Exchange Server 2007 - Part 2
- Exchange Server 2007's spam filtering feature does not need the Exchange Server 2007 Edge Server
- Transfer MDaemon to Exchange 2007/2003 (P.3)
- Check mail in Exchange 2007 (Part 2)
- Transfer from Linux Mail Server to Exchange Server 2007 (Part 1)
- Managing log files of Exchange Server 2007 - Part 1
- Exchange Server 2010: many outstanding improvements
- Transfer Exchange 2003 to Exchange 2007 (Part 2)
- Check mail in Exchange 2007
- Limit sending and receiving mail in Exchange 2007
Maybe you are interested
18 extremely creative advertising ideas that impress at first sight 30 creative templates make viewers unable to take their eyes off 20 impressive ads where creators can read our thoughts 17 'impressive' advertising ideas on social networks Want to attract users, use these 5 'psychological tricks' 13 extremely creative advertising ideas that cannot be ignored