Posted by . (15 comments)

After installing April 2012 CU on my Search Server 2010 Express, the “Incoming E-Mail” feature stopped working.


E-Mails still land in the drop folder but don’t get picked up by the “Microsoft SharePoint Foundation Incoming E-Mail” timer job. (The default folder is “c:\inetpub\mailroot\drop” if you want to have a look.)

The document libraries / lists will not receive e-mails.

In the ULS log you will start seeing entries like this:

05/01/2012 13:17:12.71 OWSTIMER.EXE (0x14B78) 0x113C4 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Timer Job job-email-delivery) 0a9e5349-84ef-4669-9bba-2a3c9bd12a0a
05/01/2012 13:17:12.83 OWSTIMER.EXE (0x14B78) 0x113C4 SharePoint Foundation E-Mail 0000 High E-mail cannot be delivered because site is over quota or locked for editing. Site URL: 0a9e5349-84ef-4669-9bba-2a3c9bd12a0a
05/01/2012 13:17:12.83 OWSTIMER.EXE (0x14B78) 0x113C4 SharePoint Foundation E-Mail 6871 Information The Incoming E-Mail service has completed a batch. The elapsed time was 00:00:00.1130065. The service processed 1 message(s) in total. Errors occurred processing 1 message(s): Message ID: 0a9e5349-84ef-4669-9bba-2a3c9bd12a0a

This message occurs although no quota limit is set.

Outgoing e-mails still work.


Go to “SharePoint Central Admin > Application Management > Configure Quota and Locks“, set a limit via “Limit site storage to a maximum of:” and press “OK”.

No downtime necessary. No data loss. (E-mails will get collected in the drop folder until SharePoint starts picking them up again.)

Further information:

Looks like others are having the same problem: “Incoming Email stuck in Drop folder after SP/Hotfix installation

Update 14.05.2012:

Nintex LazyApproval also affected

Problem: LazyApproval uses the incoming e-mail functionality, but runs in Central Administration, for which you cannot set a quota limit via the browser UI.

Solution: Same as above, but via Windows PowerShell for SharePoint Server 2010:

Get the storagemaximumlevel for Central Administration using PowerShell (insert your Central Admin URL):

$ca = get-spsite -identity http://Servername:CAport

A numeric result will be returned.

Then set a bigger maximum for it using the same command but with a number bigger than the result.


No IISRESET is required after running the script.

(Source: Cameron McConnell, Support Manager for Nintex,

Update 25.05.2012:

April 2012 CU no longer available

Microsoft has now removed to hotfix from their website.

This hotfix package is no longer available due to a technical problem.

See: Description of the SharePoint Server 2010 cumulative update package (SharePoint server-package): April 24, 2012

(Source: Joel Oleson)

The reason seems to be a regression that may result in inaccessible list items, lists, webs and/or site collections.

(Source: Randell Hall)

Update 14.06.2012:

April 2012 CU available again

The identified issues have been fixed.

(Source: Stefan Goßner)

15 Responses to “April 2012 CU causing problems with incoming e-mails in SharePoint 2010”

  1. Gyorgy Homolya

    This is a result of a hotfix in the April Cu package which prevents email processing and losing emails when the site reached its quota
    •A list that has the Incoming Email feature enabled does not create a list item for an incoming email message. This issue occurs when the site collection that contains the list reaches the site quota limitation.

    • Christian Heindel

      Hello Gyorgy,

      the problem is, that the e-mails also do not come in if no quota limit has been set. This is a bug introduced by the April 2012 CU or the hotfix package KB2598304.

      How to reproduce the bug:

      Set up a new server
      Install SP1 and April 2012 CU
      Configure incoming e-mail in Central Administration

      Create a document library, configure incoming e-mail in the library settings
      E-mails will not land in document library
      Set site collection quota limit via Central Administration
      Now, e-mails will land in document library

  2. Gyorgy Homolya

    Yes, Microsoft Support is aware of the problem. Meantime the workaround documented here is the right thing to do.

  3. Stan

    Hello Christian, any idea, is it possible to fix it by installing the new version of April 2012 over the old version?

    • Christian Heindel

      Hi Stan,

      you should be able to install the new version of the April 2012 CU (Build 14.0.6120.5006) over the older version (Build 14.0.6120.5000), but I have not tested this.

      As far as I know, it does not fix the problem with the incoming e-mails, but it does fix the problem with the HTTP 500 error.

  4. Stan

    Hi Christian, thank for quick response. Yes, I could installed the newer version, but as you have supposed, it did not fix it? Any proposal? 🙂

  5. Jon

    I’m on the second April CU (14.0.6120.5006) and still have this problem. Do you know if this is supposed to have been fixed in the June 2012 CU? I am also using Nintex w/ Lazy approvals.

  6. Shruti Modak

    Hi Christian, I have also set up an announcement list which accepts incoming.
    I send emails to the sharepoint list with attachments, but not all the emails with attachment reach sharepoint. I get an exception saying “An error occurred while processing the incoming e-mail file d:\inetpub\mailroot\Drop\897c45b401cead5f00000023.eml. The error was: Illegal characters in path.” There is no regular pattern observed in the attachment names that donot reach sharepoint.
    Can you help me with the same? I am all clueless as there is no stack trace also.

    Thanks for your help


Leave a Reply

  • (will not be published)