How Do You Troubleshoot Email Fetching Issues in ManageEngine ServiceDesk Plus?
Quick Summary
- Problem: ServiceDesk Plus stops turning emails into requests, or it fetches them late, partially, or with errors.
- Common causes: Wrong credentials, blocked ports, expired OAuth tokens, certificate trust problems, mailbox limits, and oversized or malformed emails.
- Fastest first step: Open the mail server settings and use the “Fetch a sample mail” test. It shows a clear error message.
- Best cross-check: Connect to the same mailbox with a desktop client such as Outlook or Thunderbird, using the same settings.
- Modern authentication: Microsoft 365 and Google mailboxes rely on OAuth, so token and redirect issues cause many failures.
- Time needed: Most fixes take 15 to 45 minutes once you find the category of failure.
- Note: Menu names and options vary by build, so confirm details in ManageEngine’s current help documentation.
What Is ManageEngine ServiceDesk Plus and How Does Email Fetching Work?
ManageEngine ServiceDesk Plus – ITSM Software is an IT service management platform that turns incoming emails into requests, and it sends notifications back to users and technicians. Email fetching powers that first step. This article shows you how to find and fix the most common fetching problems.
How does the platform fetch email?
According to ManageEngine’s help guide, ServiceDesk Plus connects to a mailbox through POP, IMAP, POPS, or IMAPS, through Exchange Web Services (EWS), or through Microsoft Graph. It checks the mailbox at an interval you set, reads new messages, and creates requests or adds replies to existing ones. Therefore, any break between the server, the network, or the mailbox stops the flow of tickets.
Why should you act quickly?
Missed emails mean missed requests. Users assume that IT received their message, so silent failures damage trust and service levels. Consequently, monitor fetching actively, and fix problems as soon as they appear.
How Do You Confirm That Email Fetching Actually Failed?
Before you change anything, verify the symptoms. Many “fetching problems” turn out to be filters, rules, or delays.
Which signs point to a fetching failure?
- New emails do not create requests, and the mailbox unread count keeps growing.
- The mail fetching status shows an error or stays paused.
- Requesters report replies that never appear in tickets.
- Logs show authentication, connection, or certificate exceptions.
Which quick checks rule out simple causes?
| Check | What to look for |
|---|---|
| Mail fetching status | Confirm the process runs and is not paused |
| Fetch interval | Confirm the “Fetch mails every” value suits your volume |
| Mailbox contents | Confirm that new emails actually reach the mailbox |
| Rules and filters | Confirm that no rule moves or discards mail before fetching |
| Error folder | Check whether ServiceDesk Plus moved emails there |
| Server time and service | Confirm the application service runs normally |
How do you run the built-in test?
Open Admin > Mail Server Settings, review the incoming settings, and click the sample fetch option. ManageEngine’s troubleshooting guide says that a successful test fetches the oldest mail with its properties, while a failed test shows an error. Use that message to pick the right section below.
How Do You Fix Authentication Failures in Mail Fetching?
Authentication errors rank among the most frequent causes. They usually show messages such as “Bad login” or “authentication failed.”
What should you check for username and password logins?
ManageEngine’s troubleshooting guide lists the configured username or password as a leading cause of “Bad login” errors. Work through this list:
- Re-enter the username and password in the incoming mail settings, and save.
- Confirm that the mailbox account is active and not locked.
- Check whether the password contains characters or length that the mail server rejects.
- Confirm that the mail server allows the authentication method you chose.
- Test the same credentials in a desktop mail client.
Can too many IMAP connections cause failures?
Yes. ManageEngine’s MSP troubleshooting page notes that open IMAP connections can run out, which triggers intermittent authentication failures. Fetching resumes when a connection frees up. To reduce the risk, close unused sessions from other clients, and avoid several tools that poll the same mailbox.
What if the account uses multi-factor authentication?
Basic username and password logins often fail when the account enforces multi-factor authentication. Use an app password if your provider supports it, or switch to OAuth, as the next section explains.
How Do You Troubleshoot OAuth Problems With Microsoft 365 and Google?
Modern authentication now dominates cloud mailboxes. ManageEngine states that basic authentication no longer works for Microsoft 365 connections, so OAuth failures now cause many fetching outages.
Which OAuth errors appear most often?
| Symptom | Likely cause | Fix |
|---|---|---|
| “Access token not found” | You saved settings but never completed the sign-in | Save again, and sign in through the OAuth pop-up |
| Consent page never appears | Redirect or browser problem | Check the redirect URL, and try another browser or a private window |
| Fetching worked, then stopped | Refresh token expired or was revoked | Re-authorize the mailbox |
| Sign-in succeeds but fetching fails | Signed in with a different account than the settings | Use the same mailbox account in both places |
| Security error in the OAuth dialog | Host name or alias mismatch | Access ServiceDesk Plus with the same host as the redirect URL |
What requirements does OAuth impose?
ManageEngine’s OAuth FAQ says that Microsoft Outlook configurations require the application to run over HTTPS. It also says that ServiceDesk Plus supports Microsoft Azure and Google Workspace for OAuth, and that an expired refresh token makes fetching and sending fail until you re-authorize. Additionally, the redirect URL and the address you use to open the application must match. If the application server needs a proxy to reach the internet, configure the proxy in the application and enable it in the mail server settings.
How do you re-authorize a mailbox?
Open the mail server settings, pause fetching if the prompt asks you to, save the OAuth settings, and sign in with the mailbox credentials in the pop-up. Then resume fetching and run the sample test.
How Do You Resolve Connection, Port, and Certificate Errors?
Network problems block the connection before authentication even starts. They usually show timeouts, “connection refused,” or certificate messages.
Which network checks should you run?
- Firewall and antivirus. ManageEngine lists blocked ports as a common cause. Confirm that the firewall allows the ports for your protocol, such as 993 for IMAPS or 995 for POPS.
- DNS. Confirm that the application server resolves the mail server name correctly.
- Proxy settings. Confirm that proxy rules do not block mail traffic.
- Server time. Correct clock drift, because it breaks token and certificate validation.
- Direct test. Run a telnet or similar port test from the application server to the mail server.
How do certificate problems appear?
Secure connections require the application to trust the mail server’s certificate. If it does not, you see SSL or handshake errors. ManageEngine’s guide describes importing the certificate into the Java trust store, for example through a generated jssecacerts file that you copy into the JRE security folder before you restart the application. Follow the current instructions for your build, since certificate handling changes between versions.
Should you disable certificate validation?
Avoid it in production. Instead, install the correct certificate chain. If a temporary test helps you confirm the cause, re-enable validation immediately afterward.
How Do You Fix Problems With Specific Emails or Mailbox Conditions?
Sometimes the connection works, yet certain emails never become requests. Look at the messages themselves.
Which email conditions cause skips?
| Condition | Result | Action |
|---|---|---|
| Message larger than the size limit | Skipped or moved to the error folder | Ask the sender to reduce attachments |
| Malformed or corrupt message | Fetch error for that item | Remove it from the mailbox, and review the log |
| Hidden or restricted mailbox | Cannot connect to the mailbox | Confirm permissions for the service account |
| Duplicate or auto-reply loops | Ticket floods or blocks | Add rules to ignore automated senders |
| Blocked sender or domain | Email ignored | Review your allow and block lists |
ManageEngine’s help guide notes that emails larger than 50 MB are skipped or moved to the error folder during fetching, and that POP-based fetching skips them entirely. Check the error folder regularly, and process those emails manually.
How do you handle a stuck message?
Move the problem email out of the inbox into another folder, then restart fetching. If the process continues normally, examine the moved message for unusual encoding or size.
How Do You Fix Fetching Delays and Throttling?
If emails arrive, but late, look at intervals, limits, and provider throttling.
Which settings affect timing?
- Fetch interval. Lower the “Fetch mails every” value for faster ticket creation, but avoid extremes that trigger provider limits.
- Mailbox size. Very large inboxes slow the process, so archive old mail.
- Provider limits. Microsoft Graph applies throttling per application ID and mailbox combination, according to ManageEngine’s MSP guidance.
- Shared credentials. Do not reuse the same client ID and reply email for both incoming and outgoing settings where the product blocks it.
How can you reduce delays?
Use one dedicated mailbox per queue, and keep it clean. In addition, avoid running other tools that poll the same mailbox aggressively. Finally, monitor the fetch history for slow cycles.
How Do You Read Logs and Escalate to Support Effectively?
When quick fixes fail, evidence speeds up resolution.
Which logs matter most?
Check the application logs for exceptions that mention mail, authentication, SSL, or timeouts. ManageEngine’s guide names messages such as “AuthenticationFailedException: Bad login” and points to the support file tool for deeper analysis. Search the logs by the time of the failure to find the first error, because later errors often repeat the cause.
What should you send to support?
- Your ServiceDesk Plus build number and edition
- The protocol and provider (for example, IMAP with Microsoft 365)
- The exact error message and its timestamp
- A support file generated from the application
- Steps you already tried, including desktop client tests
- A screenshot of the mail server settings with the password hidden
How do you prevent repeat incidents?
Document the fix in your knowledge base. Additionally, set a reminder to review OAuth tokens and certificates before they expire, and monitor the fetching status daily.
Conclusions: What Should You Remember About Email Fetching Troubleshooting?
Email fetching failures follow patterns. Start with the sample fetch test, then work through authentication, OAuth, network, certificate, and message-level checks in order. ManageEngine ServiceDesk Plus – ITSM Software offers several connection methods and clear error messages, so most problems reveal their cause quickly.
To recap, verify that the failure is real, and test with a desktop mail client. Fix credentials and OAuth tokens, open the right ports, and trust the mail server’s certificate. Then check for oversized or corrupt emails and for throttling. Finally, collect logs and a support file when you need help. With these habits, your service desk will capture every request, and your users will trust that their emails reach IT.
Frequently Asked Questions
The most common reasons include an expired or revoked OAuth token, a changed mailbox password, a certificate renewal, or a firewall change. Run the sample fetch test to see the exact error, and then re-authorize or update the settings that match it.
ManageEngine’s documentation states that basic authentication no longer works for connecting to Microsoft 365 mailboxes. Configure OAuth or Microsoft Graph instead, and make sure your build supports the option you choose. Confirm the current requirements in the official help guide.
Depending on the cause and your version, the application may skip them or move them to an error folder. ManageEngine notes that oversized emails fall into this group. Review the error folder regularly, and handle those messages manually or fix the underlying cause.
