sharepoint v3 has the new feature of sending email to sharepoint lists.
cool right?
there is even a built in sharepoint list template called "discussion boards" which is ideal for incoming emails, and acts as a threading tool for grouping messages together.
<soon i'll insert an image of a discussion board list>
this is handy for a lot of reasons but one potential usage of emailing to sharepoint could be archival storage of team discussion groups or Discussion Groups / Security Groups (DGs / SGs).
to setup DG archiving to sharepoint, here is a quick overview of what you'll have to do:
pretty sweet right? this can all be automated as well with some not too complex code.
now before you start going email crazy there's a couple of concerns to consider first.
lists in sharepoint are supposed to remain under 2,000 items (being returned to the view). you'll need to consider that you'll likely hit this limitation quickly, as some email DGs can get more 2,000 mail items in only a few days (or less).
ok fine.. i'll admit it...
in sharepoint technically you can have more than 2,000 items in a list... you could even have millions.
the key is that you need to ensure that the view you are using for displaying the list, is not returning any more than 2,000 items.
as an example, setup the default view of a list to filter for the last 7 days or something which you know will always have a result set of under 2,000 items. the rest of the items can be found by searching, which is likely what people will do anyway. whose gonna browse a list of thousands of items?
so that is one consideration. ensuring there are default views which limit the items displayed for all email enabled lists.
another issue is storage. most companies have lots of DGs and if all of a sudden they're going to sharepoint you'll run out of storage the first day!
that's why you'd need to figure out a rollout plan. slowly scale up and watch how much space is needed.
of course, this should all be tested in a lab first too, to get some ballpark estimates of how much space is required for 1 email message, how many messages sent on average per day to this DG, etc...
hey sean, what about legal ramifications?
many companies are starting to adopt (or have already) some type of retention period setting for old emails. lawyers don't want any extra documents around that could be used against the company as soon as they become inadmissible in court. i think emails minimum retention period are 1 year (unless its business critical) but i'm not a lawyer, and that depends on your organization.
the bottom line is, you're gonna want to consult your companies' lawyers and find out what their policy is. sharepoint allows you to set policies on sites to expire content after a certain period of time so that is pretty much exactly what you'll need.
now you could do this for every site collection programmatically, but what if admins of the site just go in there and turn of the policy?
so are you going to run this policy setting application nightly on a timer to always ensure all sites have the correct settings?
another whole issue to deal with.
there are plenty of things to think about, but sending email to sharepoint is a really cool feature and i imagine this will only gain popularity in the future.
in a future post (and my team's upcoming book MOSS for Architects and Engineers) i'll cover some more in depth / best practice configuration settings for exchange and sharepoint to get incoming email to sharepoint working.
-sean
I just have one comment to the way you can handle emails in Sharepoint site. Check out our solution for MOSS 2007. You can automatically capture emails from the exchange server, store them in a n SQL DB and via a set of webservices and a webpart make them available within Sharepoint. The emails can be selected, using Sharepoint lists as a filter. This allows everybody who has access to the team site, to view emails and documents related to i.e. an Account , customer or project. So this really removes the issue of having emails in your local inbox, as they automatically are made available within Sharepoint.
Check out Email-Manager at www.email-manager.com or watch a recorded live demo at www.emmdownload.com/sharepoint
Hi,
I configured the incoming email settings as described.I also enabled the incoming email for the document list. But when I try to send the email from my Outlook I am getting the failure notice "The following addresses had delivery problems<sample@myservername.somecompany.com>Reply from(some IP Addrees)Unable to relay for sample@myservername.somecompany.com".
and I am unable to receive any mail in Sharepoint document list. Any help would be greatly appreciated.
Thank you.
I would suggest that you talk to your company Exchange Administrator. To allow smtp relay some environments are set to only pass traffic from known devices (ie. ip address, hostname,validated username)
A 3rd party solution http://anurasoftware.com/ allows sending email to SharePoint custom list, issue list or any types of list through SMTP from your email client such outlook.
http://anurasoftware.com/AnuraEmailEnabledList.aspx
To create the AD object, does the box having the Sharepoint Server, need to have the Exchange Server as well installed... ?! or am'I missing something here... ??!!?
Hi there,
i have a calendar in outlook, which is used for summoning meetings for a meeting room. i want to automatincally reflect the meetings there to a sharepoint calendar so everyone in the organization can see.
do you know of a way to do that? by a rule or by sending an email to the SharePoint calendar maybe?
any thoughts?
thanks in advance,
Sion