Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Incoming Email with Meeting Workspace

  Asked By: Madison    Date: Mar 10    Category: Sharepoint    Views: 2836

A co-worker brought to my attention that she couldn't seem to configure a
document library to receive incoming email. I'm guessing this is an intentional
design decision made due to the instanced approach that a meeting workplace
template, but I wanted to check with you guys to keep me honest. :) Anyone
know why this doesn't seem to be possible?



11 Answers Found

Answer #1    Answered By: Trinity Scott     Answered On: Mar 10

Yes, there are some restrictions on the site/list/library types where
this is allowed, but are you sure it's not something more mundane like
the functionality not being enabled in Central Administration?

Answer #2    Answered By: Constance Guerrero     Answered On: Mar 10

Nope, it works fine on the rest of our sites.

Answer #3    Answered By: Chandrabhan Konwar     Answered On: Mar 10

I am not sure if I am responding here without knowing all there is to
need to know. But I am going to give it a shot here. I have had these
type of problems enabling incoming  mail to a document library  if the
central admin pool account and the application pool account were not the
same. Also, at times, I have been able to get this to work if I placed
that same account into the local administrators group on the SharePoint
server and rebooted. I have thought at times, that I had the central
admin pool account and the application pool account set to the same
account, but discovered that I was looking at the wrong application pool
for the site. After reviewing the application pool associated with the
site that I was having problems, I discovered the application pool
account was not the same and after setting it appropriately the incoming
mail worked fine.

Are there any errors associated with the incoming mail to that document
library or list in the logs (C:\Program Files\Common Files\Microsoft
Shared\web server extensions\12\LOGS). Also, I know that you can enable
logging for SMTP and review those logs for troubleshooting purposes.

Answer #4    Answered By: Tina Owens     Answered On: Mar 10

While I'm still not sure what it is, there has to be something else going on
here. It is not necessary for the Application pool and Central Admin to be using
the same account in order for incoming  e-mail to work properly. If in your
environment that is what you needed to do to make it so, something else, under
the hood isn't quite right either and it might worth trying to figure out what.

Answer #5    Answered By: Tiana Whitaker     Answered On: Mar 10

If it is not necessary to ensure the application pool and central admin
pool account are the same then I Steve Smith needs to modify his
whitepaper located at
If you have been able to get it to work under a different configuration
then I would be more than happy to read your white paper on configuring
incoming mail to WSS or MOSS if you could point me to the appropriate
destination. I wasn't aware that this didn't need to happen. Also, I
wonder if Exchange is installed on the same box as the SharePoint server
as I know this is an unsupported configuration but there is a workaround
for this. But then again, if there are other sites that are working
just fine, then I don't believe this to be the case.

I have always had success making the accounts the same to get it to work

Answer #6    Answered By: Alice Chandler     Answered On: Mar 10

What Steve is referring to in his white paper is using the DMS (Directory
Management Service) to create the contact account in AD when you mail enable a
list or library. If you are using DMS to create the account, then yes, I have
had the same issue that unless the web application app pool and central admin
are using the same service account, then DMS does not work. However, if you are
simply trying to mail enable a library, without using DMS, then this is not an
issue. If DMS is not enabled in Central Administration, once you enable a list
or library  to receive  e-mail you need to then manually create a mail-enabled
contact in AD for the list or library. However, even without this contact, if
users know the address assigned to the list or library, they can e-mail it.

Answer #7    Answered By: Lynette Sawyer     Answered On: Mar 10

The incoming  e-mail works fine for us on our
other sites. It's just that when you try to configure  a workspace  library, the
option isn't even present.

As an update, I was able to speak to one of the MS Sharepoint evangelists on
this. While he could not provide any overall reason, he did indicate that this
was a direct design decision  rather than a bug. It's a little disappointing but
at least we got clarification on the issue.

Answer #8    Answered By: Shelton Dickson     Answered On: Mar 10

Directory Management Service:

As I recall, the content application pool is trying to contact the list
library on Central Administration so it can insert a record for
approval of the email  address. If it is not the same app pool, DMS
simply responds "Error in applicaton" with no further explanation in
Trace or Event logs.

I remember I got it working once (I think with web policy permission
settings) but I don't remember how.

Answer #9    Answered By: Gretchen Stokes     Answered On: Mar 10

DMS Directory Management Settings
Incoming email  Settings
Approve / Reject Distribution Groups

I remember having the problem when I enabled Directory Management
Settings I would always get "Error in Application" if the Central
Admin site had a different app pool account than the application I
was trying to set up an email for.

I posted oodles about it, and now I can't find it, I swore it had
something to do with cross-application permissions, and didn't end up
really having anything to do with Active Directory. (though you do
have to have permissions set correctly). The frustrating part was
there were no errors reported so I was sure the error was happening
outside of sharepoint, but I found out if you change the reporting
settings for "General" to "Informational & Verbose" you get the
following error code "8nca" for /_layouts/EmailSettings.aspx

09/18/2008 10:56:54.99 w3wp.exe (0x1218)
0x1018 Windows SharePoint Services
General 8nca Verbose
Application error when access /_layouts/EmailSettings.aspx,
Error=Error in the application. at
oldAlias, String newAlias) at Microsoft.SharePoint.SPList.Update
(Boolean bFromMigration) at Microsoft.SharePoint.SPList.Update
() at
lick(Object sender, EventArgs args) at
System.Web.UI.WebControls.Button.OnClick(EventArgs e) at
eventArgument) at
aisePostBackEvent(String eventArgument) at
sourceControl, String eventArgument) at System.Web.UI.P...

...age.RaisePostBackEvent(NameValueCollection postData) at
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)


Answer #10    Answered By: Angarika Shroff     Answered On: Mar 10

This has been driving me nuts on and off for a while but I never
had time to really mess with it and figure out where the issue is.

Answer #11    Answered By: Eliza Hutchinson     Answered On: Mar 10

This functionality doesn't seem fully-baked, for sure. Here is a common
workaround I use when all else fails:

Put the Web application pool idents into the farm admins group. I know it isn't
the most secure, but usually fixes the below problems.

Didn't find what you were looking for? Find more on Incoming Email with Meeting Workspace Or get search suggestion and latest updates.