An user at the customer where I'm working at the moment asked the functional application manager of our SharePoint environment whether is was possible to enable the incoming e-mail functionality. So the question was dropped by me and I was going to investigate the matter.. I knew of the existence but never seen it live before so I googled on it and found the following useful information :
Here's a snippet of Neil's post:
This is where I recommend you start, read all this stuff first, before you race off back to your Virtual Machines.
- Plan incoming e-mail (Office SharePoint Server)
- Configure incoming e-mail settings (Office SharePoint Server)
- In addition to the technet site, a very good place to start is
- Read these documents and set it up in a lab exactly as described until it works
- Now introduce incremental changes to the infrastructure and after each one, verify that email is still getting through, or not.
Following his advice I opened up the links and documentation and was horrified to find out that the first step in How to configure email enabled lists in Moss2007 using Exchange 2003 states "Let's get the Active Direcrory ready!". Now summing up that step I came to the following conclusion : if you want to make this work in an Exchange environment you've got to create a separate OU in AD. If my conclusion is right, it's no big deal for smaller companies where Active Directory isn't that big and some customizations can be made in an easy way and matter. But in my case, we are talking about an enterprise level customer.. Now there are several arguments why I dare not to ask the guys who administer AD to create an extra OU.
- Farm level enabling or disabling the functionality (it's not a feature you can turn on or off on site (collection) level)
- Given the fact we have more 600 site-collections (excluding sub-sites) you don't want to know the number of lists that could be e-mail enabled..
- Wild growth in that particular OU we cannot manage (sizing, naming conventions, etc)
- Wild growth in Outlook mailbox per user (forwarding rules from SharePoint to users and vice-versa)
So.. I must say it's really nifty feature.. unfortunately not very suitable in environments like these.. (or is there something I'm not aware of and I miss here?)