Incoming Email Service Job Lock Type Change between SharePoint 2010 and 2013

EDIT: 12/12/2013: The LockJobType in SharePoint 2013 has been changed back to None in the December 2013 CU (, allowing the SharePoint Administrator to run the Incoming Email Service on more than one server!

In SharePoint 2010, the Incoming Email service timer job had an SPJobLockType of None, which means that the job ran on all servers in the farm, given the Incoming Email service was provisioned.

In SharePoint 2013, that SPJobLockType has changed to Job, which means it only runs on a single member in the farm.  This is a problem for those who wish to use round-robin MX records.  While in SharePoint 2010, you could have multiple SharePoint servers, using equally weighted MX records servicing Incoming Email requests, in 2013, you can only have a single server servicing Incoming Email requests.  Disable the Incoming Email service on all SharePoint 2013 servers except the one designated by the MX record.  This will prevent the Incoming Email service timer job from running on a server which does not contain any email to be picked up.

SharePoint 2010:

SharePoint 2013:

MSDN Reference: SPJobLockType enumeration


  1. Sorry I am little confused here… so now SharePoint 2013 can we run incoming emails on multiple servers in farm or not?

    I have SP1 installed and started incoming email service on more than 1 server but incoming timer jobs runs on only one server at a time.

  2. which file shows if my environment has .Job or .None … I am planning on installing the hotfix.

    but first i want to know where my status lies..

    • It is in Microsoft.SharePoint.dll, but you’ll see in that KB the specific fix:

      When more than one front-end server is set up to process incoming email messages on a SharePoint Server 2013 farm, only one of the servers can process email messages and cannot fail over to any other server.

  3. I have SP1 installed with 2 servers running incoming email service, but still incoming email timer job runs on only 1 server at a time… I also tried instaling installing patch ( but got message it’s already installed.

    Not sure how I can run incoming email timer job on more than 1 server.

  4. is it possible to make the drop folder a network share folder and then both front ends can grab emails from there? like the article below. will that make it deliver emails faster? right now our queue goes up and is always lagging behind.

  5. hello. i have the same issue as dpsingh. server says hotfix already installed but still only 1 smtp server is running incoming email timer job. has anyone found a workaround or resolution? thanks.

    • another note.. I checked the jobtype and it says the locktype is “Job” for job-email-delivery. shouldn’t this have changed to None with the hotfix and SP1 upgrade?

      get-sptimerjob | ? {$_.LockType -eq “Job”} | format-table -wrap -autosize

  6. Please share the solution if anyone finds… Thanks in advance!

  7. here is the response from MS Support…recreate the e-mail job:

    To fix your particular problem after applying the Dec 2013 CU go through the following steps:

    Delete the incoming E-mail Job and then re-create it. This will change Job lock type to None. Below steps needs to be followed to do that:

    1. Delete the Job:
    $job = Get-Sptimerjob | ? {$_.Name -eq “job-email-delivery”}

    2. Re-enable the “Incoming E-mail”, this will recreate the job
    – Central Admin->System Settings
    – Configure incoming e-mail settings
    – Configure all option as necessary

    3. Confirm the Locktype : None for job-email-delivery
    get-sptimerjob job-email-delivery | fl

    Timer job locktype gets set to none as expected from the CU.

    • Thanks Abdul, that worked….!!!

      Is “Microsoft SharePoint Foundation Update Distribution List Status” timer job will run on single server only?

  8. I believe it picks a server and just switches back and forth… however for me mails are not decreasing in the first front end server. MS said to restart the timer service on all servers.. so far that hasnt helped.

  9. yup got it working now… my mistake. didnt enable the service for the front end server in CA.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.