[Today's post comes to us courtesy of Shawn Sullivan and Justin Crosby from Commercial Technical Support]
Some of you who have worked with SBS 2011 so far may have noticed a change in how archived email for security groups is handled; for details see our previous post . SharePoint document libraries are no longer used for email storage; this job has now been given to Public Folders. As a result, the configuration necessary to allow the routing of email from Exchange to SharePoint is no longer done automatically for you during SBSSetup. However, it is possible to have this functionality on SBS 2011 as well; you just need to perform the configuration manually. This post will show you how and covers the following areas:
Note: The SBS 2011 Add Security Group wizard is hardcoded to give you the option to archive to a Public Folder only. It will remain this way even after following these steps. There is no way to change the wizard’s options.
Incoming email is not enabled in SharePoint 2010 running on SBS 2011 by default. You will need to enable it, choose the “Companyweb” SMTP namespace, and enter the path of the drop directory that the SharePoint Timer service will poll for incoming email:
You’ll need a place inside your Companyweb site to store the archived email that will have an email address for you to send to. To do this:
Now we are ready to create the pieces that will physically connect Exchange and SharePoint as far as SMTP is concerned. Basically, Exchange will use the foreign connector to determine that email destined for the @Companyweb domain should be sent to the drop folder (c:\inetpub\mailroot\drop). SharePoint, on the other side, will pick the email up from this folder, read the recipient, and place the email into the document library that has the matching email address.
To begin testing this, you should be able to send an email to the document library by directly addressing it in OWA. Any mistakes made with the above steps will result in errors that are documented fairly well in the SharePoint Products Event Viewer log: Application and Services Logs > Microsoft > SharePoint Products > Shared > Operational .
In order to route e-mail sent to a security group, you will have to create a contact for the SharePoint document library and add it as a member of the group. You can actually use either a distribution group or a security group here.
In this example, we will create a contact for mylist@companyweb and add it to the new test distribution group. This group’s SMTP address will be derived from the e-mail address policy, which will allow it to receive e-mail from the internet. Unless you specify otherwise, no sender restrictions are placed on the group.
If you wish to add the contact to an existing group, test2 for example:
A group who does not have any restrictions will display the following output:
[PS] C:\Windows\System32>Get-DistributionGroup test2 | fl *accept*,*reject*
AcceptMessagesOnlyFrom : {}
AcceptMessagesOnlyFromDLMembers : {}
AcceptMessagesOnlyFromSendersOrMembers : {}
RejectMessagesFrom : {}
RejectMessagesFromDLMembers : {}
RejectMessagesFromSendersOrMembers : {}
If you do see entries for these parameters that are not intentional, go to the Exchange Management Console > Recipient Configuration > Distribution Group > properties of the group in question > Mail Flow Settings > Message Delivery Options . Adjust the settings from there (it’s much easier than typing a potentially very lengthy command). One common mistake people make is unintentionally allowing the “Require that all senders are authenticated” option to be checked, which kills the ability of external senders to submit to this group. An example of a group that is not applying restrictions looks like this:
If attachments are missing from e-mail messages that are sent to a SharePoint Foundation 2010 document library, it might be because you associated the document library with an e-mail address. When you do this, Directory Management Service may not add the following two attributes:
You must use Active Directory Service Interfaces (ADSI) to manually add these two missing attributes.
To add attributes by using ADSI Edit:
Click Start , and then click Run .
In the Run dialog box, type Adsiedit.msc , and then click OK .
In the ADSI Edit window, expand ADSI Edit , expand Domain [DomainName] , expand DC=DomainName, DC=com , CN=MyBusiness, CN=Users, and then CN=SBSUsers.
Right-click the user name to which you want to add the missing attributes, and then click Properties .
In the Properties dialog box, double-click internet Encoding on the Attribute Editor tab.
In the Integer Attribute Editor dialog box, type 1310720 in the Value box, and then click OK .
In the Properties dialog box, double-click mAPIRecipient on the Attribute Editor tab.
In the Boolean Attribute Editor dialog box, click False , and then click OK two times.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.