Email Enabled Lists

By -
After lots of digging, I finally got incoming-email-to-list functionality working in MOSS. Take a look at Steve Smith's excellent tutorial on getting things set up here. I had several issues during my setup, but here are the highlights:
  • Get things configured first using a machine-name/sub-domain first (i.e. use email@servername.company.com instead of email@company.com)
  • The MS least-privilege configuration doesn't apply here - each web application with lists that you want to be email-enabled must use the same app-pool identity as Central Administration (i.e. the "farm account"). Note that you can (and should) still have separate app-pools, but they have to run using the same identity.
  • Don't forget to delegate control to the app-pool identity for making changes in AD. After getting frustrated I just granted full-control to the OU and then went back later and fixed it.
  • Make sure the Sharepoint Timer service is running, otherwise the emails will just sit in the maildrop folder on your SMTP server and they'll never make it to a list. Trust me.
  • I should be kicked for this... Make sure the user account that you are using to test actually has rights to post to the list. As far as I can tell, MOSS doesn't send you any sort of "post rejected" email to let you know, so you'll be chasing your tail. Again, trust me.

Comments

Post a Comment

Popular posts from this blog

ERROR: Failed to create feature receiver...

By -
I was working on a STSDev project which deployed a feature with a feature receiver. I had the feature working without the FeatureReceiver but as soon as I added the FeatureReceiver related attributes to my <Feature> element I got the following error: Failed to create feature receiver object from assembly "Org.Project.Solution, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c632353d405b3209", type "Org.Project.Solution.MyFeature.FeatureReceiver" for feature 6a9b2358-ea4e-486d-a4e4-4f813c52ce88: System.ArgumentNullException: Value cannot be null. Parameter name: type at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() After much digging around I discovered that STSDEV's Solution config file refers to a namespace as well as the dll. My FeatureReceiver's namespace was not prefixed with the right namespace So just
Read more

Programmatically Update Page Layouts

By -
I updated my page layouts that I deployed as a feature, but found that I could not overwrite the Layout File. The solution was to add a new page layout and then you would have to associate the new layout with every page on your site that used it. Obviously with a site of any size you'd have a lot of manual work to get this done, so doing it programmatically makes for a much better (and thorough) approach. After you've got your new page layouts, you could do something like this (in your event receiver class): public override void FeatureActivated(SPFeatureReceiverProperties properties) { //replace current page layouts with new page layouts on all pages SPWeb web = SPContext.Current.Web; SwapPageLayout(web, "FullWidthContentWithTitleV1.aspx", "FullWidthContentWithTitleV2.aspx"); } private void SwapPageLayout(SPWeb web, string oldPageLayoutName, string newPageLayoutName) { PublishingWeb pubWeb = PublishingWeb.GetPu
Read more