Can't find what you're looking for? Access our previous PDF-based library.
3 min read
️ Updated Jun 03, 2026Category | Email Alerts / SMTP Configuration |
Affected Area | Change Alerts / Scheduled Reports |
1. Issue Summary
Lepide alerts and scheduled reports were configured in the system, but emails were not being delivered to the intended recipients. The alerts appeared to be set up correctly in the Lepide console, but no emails were arriving in the mailbox.
2. Observations
Alerts are visible in the Lepide console under Change Alerts.
Scheduled reports show as configured, but recipients report never receiving them.
No error messages visible to the end user at first glance.
3. Root Cause
The sender email address configured in the Lepide alert settings was a placeholder or nonexistent email address (e.g., lepide@domain.com or noreply@domain.com). This address had no actual send permissions in the mail environment, causing all outbound alert emails to silently fail.
Note: In many organizations, no-reply or placeholder addresses are created as aliases without mailbox send permissions. Lepide requires a real, functional sender account to successfully relay alert emails.
4. Steps Followed
Step 1 – Identify the Faulty Email Configuration
Navigate to the Lepide console and go to:
Settings > Message Delivery Settings
Review the sender email address configured in the existing profile(s).
Step 2 – Run a Test Email
Click the Test Email button within the message delivery profile to confirm whether the current configuration can send emails.
If the test email is not received or an error is shown, the sender account is the likely cause.
Step 3 – Remove the Faulty Profile
Delete the old broken email delivery profile to avoid confusion and ensure only working profile is in use.
Step 4 – Add a New Working Email Account
Click Add Email Account in the Message Delivery Settings and configure using a real, functional sender email address that has permission to send emails in your environment.
Enter the correct SMTP server address.
Enter the correct SMTP port (typically 25, 587, or 465).
Enter the real sender email address with send permissions.
Enter the recipient email address or distribution group.
Step 5 – Send a Test Email
Click Test Email to verify the new configuration is working. Confirm the test email is received in the recipient inbox.
Step 6 – Update All Existing Alerts to Use the New Profile
Go to the Alerting section in the Lepide console and review each existing alert. Ensure all alerts are using the correct, working email delivery profile. Some alerts may still reference the old broken profile.
Step 7 – Verify via Failed Reports Log
To check which reports or alerts previously failed, navigate to:
Change Alerts > Failed Reports
The Subject column will show exactly which report failed and when. Cross-check with the alert configuration to ensure the correct email profile is now assigned.
5. Resolution
Replacing the non-functional placeholder sender email with a real, permissioned sender account resolved the issue. All test emails were confirmed delivered. Alerts began sending successfully after the configuration update.
6. Prevention
Always use a real, functional email account as the sender in Lepide email delivery settings.
Periodically check the Failed Reports section to catch any silently failing alerts early.