Contents
Make sure “Microsoft SharePoint Foundation Incoming E-Mail” timer job is running on the server where SMTP confgiured. From Central admin, Incoming email setting > advance setting, make sure drop folder path added here. Make sure Timer Services having the correct permission on drop folder.
Incoming E-Mail works in SharePoint 2013 Farm in general. I have 2 sitecollections with E-Mail activated document libraries. I promoted the aliases to the new farm by deactivating and re-activating the incoming E-Mail Setting in the document library Settings.
Why are my incoming e-mails stuck in drop folder?
Now to provide the exact scenario where the incoming e-mail is affected by the Microsoft software bug part of November 2014. The document library where the incoming e-mail is enabled has no SharePoint quota defined, or the defined quota template applied doesn’t have defined the sandbox usage quota points.
Where does Microsoft SharePoint Foundation incoming e-mail go?
On a multi-server farm, be sure the “Microsoft SharePoint Foundation Incoming E-Mail” service is running on the same server you’re using for the SMTP service, presumably one of your front end servers. Check this in Central Admin-System Settings-Manage Services on Server and cycle through your servers on the top-right.
You can install the SMTP service on one or more servers in the farm, or administrators can provide an email drop folder for email that is forwarded from the service on another server. For more information about the email drop folder option, see Plan incoming email for a SharePoint Server farm.
In Central Administration, select System Settings, and in the E-Mail and Text Messages (SMS) section, select Configure incoming e-mail settings. To enable sites on this server to receive email, on the Configure Incoming E-Mail Settings page, in the Enable Incoming E-Mail section, select Yes. Select the Automatic settings mode.