How Do You Troubleshoot Email Notification Problems in ServiceDesk Plus? - Solution for Guru

Skip to main content
Table of Contents
< All Topics
Print

How Do You Troubleshoot Email Notification Problems in ServiceDesk Plus?

What Should You Know First?

Here is the short version for admins who need a fix quickly.

  • Start with the outgoing mail settings. Most notification failures trace back to the server name, port, protocol or credentials.
  • Send a sample email first. ServiceDesk Plus includes a test option that shows whether the connection works.
  • Check notification rules next. A notification cannot leave the application if the rule behind it is off.
  • Look at the network and security layers. Firewalls, virus scanners and relay restrictions often block mail without a clear error.
  • Read the logs. Email debug mode and the application logs pinpoint the exact failure.
  • Check the links inside emails. A changed server address can break every request link in a notification.
  • Menu names vary by edition. Cloud editions use Setup, while on-premises editions use Admin.

Work through the steps in order, and you can usually find the fault within minutes.


What Is ManageEngine ServiceDesk Plus and How Do Notifications Fit In?

ManageEngine ServiceDesk Plus – ITSM Software is an IT service management platform. Teams use it to handle incidents, service requests, changes, assets and knowledge articles. Email notifications keep that work moving, because they tell requesters that someone received their ticket and tell technicians that a new assignment needs attention.

Why Do Notifications Matter So Much?

When notifications fail, the whole service desk slows down. Requesters assume nobody answered, technicians miss urgent tickets and approvers leave change requests waiting. ManageEngine ServiceDesk Plus – ITSM Software depends on email as its main communication channel, so a silent failure creates real business impact.

How Do Sending and Fetching Differ?

Two separate mail functions exist. The outgoing mail server sends notifications from the application. The incoming mail server fetches emails and turns them into requests. This article focuses on outgoing problems, although a few incoming settings also affect notifications. Keep the two apart when you diagnose an issue, because each has its own settings page.


How Do You Confirm That Outgoing Mail Settings Work?

Always begin with the outgoing mail configuration. It causes more notification failures than any other setting.

Where Do You Find the Outgoing Mail Settings?

On-premises editions use Admin > Mail Server Settings > Outgoing. Cloud editions use Setup > Mail Settings > Mail Server Settings, according to ManageEngine’s cloud documentation. ManageEngine’s help pages explain that you can send email through SMTP or SMTPS, Exchange Web Services, or Microsoft Graph, depending on your edition and version.

Which Fields Should You Verify?

Check each of these carefully:

SettingWhat to verify
Server name or IP addressSpelling, DNS resolution and reachability
PortThe port your mail server expects, such as 25, 465 or 587
Protocol and TLSWhether the server requires SMTP with TLS or SMTPS
AuthenticationCorrect username, password and account permissions
Reply-to addressA valid mailbox on your domain
ProxyProxy details, if your network requires a proxy

How Do You Send a Test Email?

ManageEngine’s troubleshooting guide recommends using the sample mail option. Enter an email address on the outgoing tab and click Send a sample mail. If the settings work, the sample arrives in that mailbox. If it fails, the error message points toward the cause. Run this test after every change, so you know exactly which adjustment fixed or broke the connection.


Why Does the Server Refuse to Send Mail?

Once the basic settings look right, connection and authentication errors come next. ManageEngine’s knowledge base lists several common causes.

What Does “Unknown SMTP Host” Mean?

This error means the application cannot resolve the mail server name. ManageEngine’s troubleshooting article shows a log entry with an unknown SMTP host and tells admins to verify the outgoing mail settings and check whether the email server relays messages to outside domains. Start by checking for typos. Then test whether the ServiceDesk Plus server can resolve the hostname through DNS.

What Do Relay and Authentication Errors Mean?

Mail servers often block relaying to protect against spam. If your server rejects messages with a “relaying denied” response, the mail server does not trust the application to send on behalf of your domain. Fix this by enabling authentication in ServiceDesk Plus, or by allowing the application server’s IP address to relay on the mail server.

Authentication errors, such as “user not authenticated,” usually point to wrong credentials or a disabled authentication option. Confirm the username format and reset the password if needed.

How Do You Handle Microsoft 365 Environments?

Many organisations send notifications through Microsoft 365. An older ManageEngine community answer suggested SMTP with port 587, TLS enabled and authentication turned on, followed by a service restart. Microsoft has tightened authentication rules for Exchange Online in recent years, so check Microsoft’s current documentation and your ServiceDesk Plus version’s supported methods. Newer builds offer options such as Microsoft Graph, so review which method suits your setup.


How Do Network and Security Tools Block Notifications?

Sometimes the settings are perfect, and mail still fails. Network controls often cause these stubborn cases.

Could a Firewall or Virus Scanner Block the Connection?

Yes. ManageEngine’s troubleshooting article explains that a virus scanner may block the port used for notifications. It suggests running a telnet command from the ServiceDesk Plus server to the mail server on the relevant port. If the command succeeds but the application still cannot send mail, the article points to virus scanners that block requests from the java.exe process.

How Do You Test Connectivity?

  1. Open a command prompt on the ServiceDesk Plus server.
  2. Run telnet <mailserver> <port>, for example port 25 or 587.
  3. Watch the response. A connection banner means the port is open.
  4. If the connection fails, check the firewall, proxy and security software.
  5. If the connection works but the application fails, review scanner exclusions for the application’s Java process.

What About TLS Certificates?

ManageEngine’s MSP troubleshooting guide describes a certificate step for servers that require it. The process generates a jssecacerts file in the application’s home directory, and you copy it into the Java security folder before you restart the application. Follow the current instructions for your version, because certificate handling changes between releases.

Should You Use a Secondary Mail Server?

Consider it. ManageEngine’s documentation describes a secondary outgoing mail server. If the primary server fails, the application connects to the alternate server and continues sending. This feature adds resilience, so configure it if your edition supports it.


How Do Notification Rules Affect Delivery?

Perfect connectivity does not help if the rule that triggers the email is off. Notification rules decide who receives which message and when.

Where Do You Check Notification Rules?

On-premises editions use Admin > Notification Rules. Cloud editions place them under Setup > Automation > Notification Rules. Each rule covers an event, such as a new request, a technician assignment or a status change.

What Should You Look For?

Review these points for the missing notification:

  • The rule for that event is enabled.
  • The right recipients appear in the rule, for example the requester, technician or group.
  • The technician or requester has a valid email address in their profile.
  • Any conditions in the rule match the request.
  • Custom business rules do not suppress the notification.

Do Rejected Emails Trigger Notifications?

Yes, in some cases. The cloud documentation explains that the application sends an automatic notification to the requester when it rejects an email, and you can customise that message under the request notification rules. If requesters complain that they never received a confirmation, check whether the application rejected their email in the first place.

Who Receives Error Notifications?

ManageEngine’s documentation says the application sends error notifications to the technicians you configure under the notification rules. Add at least one active administrator there, so you learn about mail problems before your users do.


How Do You Read Logs and Enable Email Debug?

When the cause stays hidden, turn to the logs. They show what the application tried and how the server responded.

How Do You Enable Email Debug?

ManageEngine’s troubleshooting guide describes the steps: open the outgoing mail settings, tick Enable Email Debug and save. The application then writes debug output for later emails into its logs folder. On a Windows installation, the guide gives the default path as the logs folder inside the ManageEngine ServiceDesk directory. Reproduce the problem, then open the newest log file.

Which Errors Should You Search For?

Log messageLikely meaningFirst action
Mail sending failedGeneral send failureRead the nested exception below it
Unknown SMTP hostThe server name does not resolveCheck the name and DNS
User not authenticatedWrong credentials or authentication offRecheck login details
Relaying deniedServer blocks relayAllow relay or enable authentication
Connection timed outNetwork path blockedTest with telnet and check firewalls
Syntactically invalid HELOHostname contains unsupported charactersReview the server hostname

Should You Turn Debug Off Afterwards?

Yes. Debug output grows quickly and can slow the system. Disable it once you fix the problem.


Why Do Notification Links and Delays Cause Trouble?

Sometimes emails arrive, but they contain broken links or show up late. These issues look different, so they need different fixes.

Why Does the Request Link in the Email Not Work?

ManageEngine’s knowledge base explains the usual cause. If you move the ServiceDesk Plus server or change the alias URL in the self-service portal settings, the notification links can still point to the old address. Update the URL settings, then send a new notification and test the link.

Why Do Emails Arrive Late?

Volume and protocol choice both matter. ManageEngine’s outgoing mail documentation notes that the application sends emails through multiple threads, including replies, forwards and system notifications, so delays can occur. It also presents test scenarios in which a burst of 200 requests per minute produced a delay of up to about ten minutes with Microsoft Graph. As a result, ManageEngine advises against choosing Microsoft Graph for high-volume environments. If your desk handles heavy traffic, consider SMTP or another supported method.

Why Do Some Emails Land in Spam?

Deliverability depends on your domain’s email authentication. Publish correct SPF, DKIM and DMARC records for the domain that ServiceDesk Plus uses as the sender. The SPF standard appears in RFC 7208, and your mail provider’s documentation explains DKIM and DMARC setup. Also avoid sending from a generic address that no mailbox owns.


How Do You Prevent Notification Problems in the Future?

Prevention costs less than emergency repairs. A few simple habits keep mail flowing.

Which Routine Checks Help Most?

TaskSuggested frequency
Send a sample mail from the outgoing settingsMonthly
Review notification rules for key eventsQuarterly
Check the sender account password expiryBefore each expiry date
Verify the secondary mail serverQuarterly
Review error notification recipientsQuarterly
Recheck settings after any server or URL changeAfter each change

What Should You Document?

Record your mail server name, port, protocol, sender account and the person who owns the mailbox. Note any firewall exceptions and certificate steps. When someone new takes over administration, that record saves hours.

Who Should Own the Mail Integration?

Assign one clear owner, usually a service desk administrator working with the mail administrator. Shared ownership prevents the classic problem in which the mail team changes a policy and the service desk learns about it from angry users.

What Are the Key Takeaways?

Troubleshooting email notification problems in ServiceDesk Plus follows a clear sequence. Confirm the outgoing mail settings and send a sample mail. Check authentication, relay rules and network access. Verify that the notification rules for the affected event work. Then read the logs with email debug enabled, and fix any broken links or delays.

ManageEngine ServiceDesk Plus – ITSM Software supplies the tools you need for each step, including a sample mail test, debug logging, notification rules, error notifications and a secondary mail server. Yet the tool cannot see your firewall, your mail server policy or your domain’s DNS records, so you must check those yourself.

Because menu names, supported protocols and mail platform requirements change over time, confirm the details in ManageEngine‘s current help pages and your mail provider’s documentation. Fix the problem, document what you learned and schedule a monthly test, so the next failure shows up in a test and not in an angry ticket.


What Questions Do Admins Ask Most About ServiceDesk Plus Email Notifications?

Why Does the Sample Mail Work but Real Notifications Do Not Arrive?

The connection works, so look at the notification rules and recipients. Check that the rule for the event is enabled, that the recipient has a valid email address and that no condition blocks the message. Then check spam folders and your mail server’s message trace.

Why Do Notification Links Open the Wrong Page?

The links likely use an outdated server address. ManageEngine’s knowledge base says that moving the server or changing the alias URL in the self-service portal settings can leave notifications pointing at the old address. Update the URL settings and send a fresh test notification.

Should I Use Microsoft Graph or SMTP for Outgoing Mail?

It depends on your volume and your mail platform. ManageEngine’s documentation lists Microsoft Graph as an option but advises against it for environments with high email flow, because of possible sending delays. Test both methods in a pilot, compare delivery times and choose the one that fits your traffic and security requirements.


Recommended: