Archive for May 2008


Incoming eMail Settings

Sure, we'd like to have inbound eMail working because it can do alot for corporate communications.  Our friend, Joel, has a great outline of these capabilities here

When I try to enable inbound eMail for a document library, I click on the link on the list settings.

You can set the inbound mail to sort into folders depending on subject or sender and you can tell it to overwrite files.  I presume, if the library is set for versioning, overwrites will create a new version.

I can't tell because, when I click OK on the Inbound Email Settings page, I get one of those ugly SharePoint errors that says:

The request failed with HTTP status 401: Unauthorized.

Troubleshoot issues with Windows SharePoint Services.

I always wonder if we'll ever see those people again that click on that bottom link because, once you do, you are in Hell.

So, digging around, we find this.  Seems to be perfectly on point.  It says:

To enable or configure incoming e-mail support for a list or library, you must have the Manage Lists permission on the list or library. The Manage Lists permission is granted by default to the Site name owners SharePoint group.

I don't see a Manage Lists permission on the doc library.  All I see is Full Control. And, otherwise this page doesn't help.  Even though I have the "full control" permission, I get the unauthorized error.

At this point, I tried a new blank team site and created an discussion board.  During the creation process, I checked the Enable email option and gave it an email address.  When I clicked OK, I get an Operation Completed page that says:

The list was created successfully, but could not be assigned an e-mail alias because of the following error: The request failed with HTTP status 401: Unauthorized.

So I check the Windows Event Logs and I see I have some number of these:

The Execute method of job definition Microsoft.SharePoint.Administration.SPIncomingEmailJobDefinition (ID f940c454-b2f0-4bb0-bdec-fa034f5e6ee7) threw an exception. More information is included below.

Value cannot be null.
Parameter name: path

On MSDN, I see that someone else has the exact same problem.

I've seen several references to this from our new best friend Steve in the UK.