Tuesday, July 31, 2012

E-mail service cannot deliver e-mail - Event6873 (SharePoint 2010)


The Microsoft SharePoint 2010 Products e-mail service processes e-mail destined for insertion into SharePoint lists. The service processes mail that the Windows Simple Mail Transfer Protocol (SMTP) service added to a drop folder.





One or more of the following symptoms might appear:

  • SharePoint lists do not receive e-mail.
  • This event appears in the event log: Event ID: 6599 Description: an error occurred while processing incoming email

One or more of the following might be the cause:

  • There is no corresponding SharePoint list for the recipient of an e-mail.
  •  The sender does not have sufficient permissions to add content to the SharePoint list.

Troubleshooting:

  • Verify that the list is configured to receive e-mail:
  • In the list provided in the event details, on the List menu, click List Settings.
  • On the List Settings page, under Communications, click Incoming e-mail settings.
  • Verify the following:
  • The correct e-mail address is entered in the E-mail address box.
  • The Yes option is selected under Allow this document library to receive e-mail?

Grant the sender the appropriate permissions to the recipient list:

  • In the list provided in the event details, on the List menu, click List Settings.
  • On the List Settings page, under Permissions and Management, click Permissions for this list.
  • Verify that the user account provided in the event details has at least Contributor permissions to the list.

No comments:

Popular Posts

Disclaimer

The opinions expressed on this blog are the personal views of Pratik's SharePoint Blog, and do not represent or reflect the viewpoints or policies of any past, present, or future employer, colleague, or customer, or any other entity. The posts on this blog are provided ‘as is’ with no warranties, express or implied, and confer no rights. Use of information contained within this blog, including specific technical steps mentioned herein, is at your own risk. References to specific software products, processes, resources, or companies do not imply any endorsement.