Email delivery is a critical part of JD Edwards EnterpriseOne (JDE) for workflows, UBE reports, notifications, and system alerts. When emails fail, the root cause is often SMTP configuration or network connectivity.
This blog provides a step-by-step SMTP validation approach using PowerShell and JDE configuration checks to ensure end-to-end email delivery is working correctly.
1. Verify SMTP Server Connectivity
Before checking JDE or email configuration, ensure the SMTP server is reachable from the Enterprise Server.
PowerShell Command:
Test-NetConnection smtp.server.com -Port 25
What This Checks:
- Network connectivity to SMTP server
- Port availability (typically 25, 587, or 465)
- Basic firewall or routing issues
Expected Output:
TcpTestSucceeded : True→ SMTP reachableFalse→ Network/firewall issue
2. JDE INI SMTP Configuration
JDE uses the Enterprise Server INI file to define email routing rules and system email identities.
Sample Configuration:
Rule1=90|OPT|MAILSERVER=smtp.server.com
Rule2=100|DEFAULT|OWMON=OWMON@domain.com
Rule3=110|DEFAULT|PSFT_SYSTEM=PSFT_System@domain.com
Rule4=120|DEFAULT|JDE_SYSTEM=JDE_System@domain.com
Rule5=DEFAULT|WORKFLOW_SYSTEM=Workflow@domain.com
SMTPPort=25
Explanation:
| Setting | Purpose |
|---|---|
| MAILSERVER | Defines SMTP host |
| SMTPPort | SMTP port (usually 25) |
| OWMON | System monitoring email |
| PSFT_SYSTEM | Default PeopleSoft/JDE system sender |
| JDE_SYSTEM | JDE system-generated emails |
| WORKFLOW_SYSTEM | Workflow email sender |
Key Insight:
These rules determine which sender email is used depending on functionality inside JDE.
3. PowerShell SMTP Email Test (Enterprise Server)
Once network and configuration are validated, test actual email delivery using PowerShell.
Script:
Send-MailMessage `
-From "JDE_System@domain.com" `
-To "xxxxxx@domain.com" `
-Subject "SMTP Test" `
-Body "This is a test email from JDE Enterprise Server" `
-SmtpServer smtp.server.com `
-Port 25
What This Validates:
- SMTP authentication (if required)
- Email relay permissions
- Network path from Enterprise Server
- Basic email delivery capability
If This Fails:
Check:
- SMTP relay permissions
- Firewall rules
- Authentication requirements (anonymous relay vs credentials)
- TLS requirements (port 587 instead of 25)
4. JDE Functional Email Validation
After SMTP validation, confirm JDE configuration and functional email behavior.
Step 1: Enable Email on Job Completion
Ensure the following INI setting is enabled:
- “Send Email on Job Completion” option in UBE configuration
Step 2: Configure Who’s Who Email
In JDE:
- Go to Address Book → Who’s Who
- Add valid email address for user
Step 3: Assign Address Number
- Ensure User Profile is linked to correct Address Number
- Without this mapping, email routing may fail or fallback to system sender
Step 4: Run Test UBE
- Execute a sample batch job (UBE)
- Enable email notification on completion
- Verify email delivery
6. Common Issues and Fixes
❌ Email Not Sending
- SMTP server unreachable
✔ Fix: Check firewall / port 25 access
❌ Email Sent but From Address Wrong
- Missing Who’s Who email
✔ Fix: Update Address Book email
❌ Emails Failing Only from JDE
- INI misconfiguration
✔ Fix: Validate MAILSERVER and RULES
❌ UBE Email Not Triggering
- Notification not enabled
✔ Fix: Enable “Send Email on Completion”
7. Best Practices
✔ Always use system sender fallback
Example:
- PSFT_SYSTEM@domain.com as default
✔ Standardize SMTP relay
- Avoid multiple SMTP servers unless required
✔ Maintain Who’s Who emails
- Critical for correct sender identity
✔ Monitor failed email logs
- JDE logs + SMTP logs together provide full visibility
Final Thoughts
SMTP validation in JD Edwards is not just a network test—it is a three-layer validation process:
- Network layer (SMTP reachability)
- System layer (INI configuration)
- Application layer (JDE functional behavior)
Using PowerShell along with JDE configuration checks ensures end-to-end email reliability across workflows, UBEs, and system processes.
