Troubleshooting Mail fetching problems
After you configure the mail server, test the settings by fetching a sample mail. To do so, click the Fetch a sample mail button.

If the settings are configured right and the connection is successful, the oldest mail from your mailbox will be fetched, along with its properties. If not, an error message will be displayed on the screen.
In ServiceDesk Plus, mail fetching problems can be categorized as follows:
Authentication failed for the given username and password
If there are no connectivity issues with third-party apps, and there are authentication issues only with ServiceDesk Plus, go here.
Configured mail host name is unknown or not reachable (or) Unable to connect to the mail server with the provided configurations
If you are able to connect to other third-party apps and unable to connect the mailbox through ServiceDesk Plus server, go here.
Could not find valid certification path to requested target, kindly configure to apply Trusted/Self Signed Certificate
Download the file from the link given below and extract it to the Service Desk Plus Home directory:
For Linux:
For Windows:
For Windows - gencert.bat <hostname>:<port>
E.g. cmd> gencert.bat sdpexchange.com:995
For Linux - sh gencert.sh <hostname>:<port>
E.g. sh gencert.sh sdpexchange.com:995
If you still face the issue after applying the certificate, click here.
Unable to open mailbox in READ/WRITE mode
Unable to connect to the mail server. Check server URL and try again.
Get to know your Exchange Web Services URL (Connect URL)
Troubleshooting Mail Sending problems
To check the mail server connectivity, send a sample email by entering a mail address and clicking on the Send a sample mail button in the outgoing tab.
.png)
If the settings are configured right and the connection is successful, a sample mail will be sent to given the email address. If not, an error message will be displayed on the screen.
The common exceptions that occur in ServiceDesk Plus while sending mails can be categorized as follows:
Incorrect username or password
Note: If you are using SMTP/STMPS, do not check your account configurations using Outlook Web Access as it works with the MAPI protocol. If you are using Exchange Web Services, open the connect URL in an incognito window.
If you are still unable to login with your credentials, click here to debug your email and send a log report for analysis.
If the error persists, click here to enable email debugging and send a log report for analysis.
Unable to connect to the mail server. Check connect URL and try again.
Get to know your Exchange Web Services URL (Connect URL)
If there are no connectivity issues with third-party apps, and there are authentication issues only with ServiceDesk Plus, enable email debugging and mail the logs for analysis:

Mail throttling limits are evaluated for each application ID and mailbox combination. ServiceDesk Plus prevents users from configuring the same Client ID and Reply Email for both Incoming and Outgoing Mail Server Settings in the same service desk instance or across instances.
To use the same mailbox in both Incoming and Outgoing Mail Server Settings, create a separate application (with different client ID).
Refer to microsoft documents for more details about throttling limits in Microsoft Graph API.

You may notice that emails in your Inbox are not being processed by ServiceDesk Plus (SDP) and instead keep accumulating. This happens when certain conditions prevent email processing, even though mail fetching itself does not stop.
Once the underlying issue is resolved, email processing will automatically resume.
Below are the common reasons for this issue and how to fix them.
1. Unsupported Email Encoding
Why this happens
Some emails may use unsupported encoding formats (for example, UTF-7). SDP cannot process such emails, which causes them to remain in the Inbox and block the processing of subsequent emails.
How to resolve
Check your Inbox for emails with unsupported encoding.
Remove these emails or move them to another folder.
In most cases, the oldest emails in the Inbox are affected.
If possible, configure your mail server to prevent such emails from reaching the Inbox.
2. Oversized Emails
Why this happens
Emails that exceed the configured processing size limit are not processed.
The default maximum email size (including attachments) is 30 MB.
Emails larger than this limit will remain unprocessed in the Inbox.
How to resolve
Remove oversized emails or move them to another folder.
Typically, the oldest emails in the Inbox are the affected ones.
Changing the email size limit (Advanced)
You can modify the maximum allowed email size using the following SQL query:
update mailconfig set paramvalue = <maximum allowed mail size in mb> where parameter = 'MAX_MAIL_SIZE' and helpdeskid = <helpdeskid of the portal>;
Example: Set the limit to 50 MB for helpdesk portal ID 1:
update mailconfig set paramvalue = 50 where parameter = 'MAX_MAIL_SIZE' and helpdeskid = 1;
To find out how to connect to the database, click here.
3. Recoverable Items Folder Quota Exceeded (Exchange Online)
Applicable only when an Exchange Online mailbox is configured in SDP’s Incoming Mail Settings.
Why this happens
When SDP processes emails, they are soft deleted and moved to the Recoverable Items folder in Exchange Online.
This folder has a default quota of 30 GB (can be increased up to 100 GB).
If the folder reaches its storage limit, SDP cannot delete processed emails.
As a result:
Processed emails remain in the Inbox
New emails are not fetched
Emails continue to accumulate in the Inbox
Once storage is freed, SDP will automatically resume email processing.
How to check Recoverable Items folder size
Step 1: Connect to Exchange Online
Connect-ExchangeOnline -UserPrincipalName <admin_account_login_name>
Step 2: Get Recoverable Items folder statistics
Get-EXOMailboxFolderStatistics -Identity "<helpdesk_mailbox_email>" -FolderScope RecoverableItems |
Format-Table Name, FolderPath, ItemsInFolder, FolderAndSubfolderSize

If the Recoverable Items folder exceeds the quota, free up space or increase the quota as required.
Notifications and Alerts
When any of the above conditions are detected:
An error message is displayed on the Incoming Mail Server Configuration page.
A bell notification is sent to all SDAdmins.
Email alerts are sent to technicians configured under the Application Error Notification rule.
Both the in-app notification and email alert are sent every 30 minutes until the issue is resolved.