SMTP Service Going End of Life: Instructions for System Configuration

In this article, you can find information about SMTP Service going end of life and instuctions on how to reconfigure the systems.

Created: September 2025

Permalink: https://wildix.atlassian.net/wiki/x/AYCpWg

The service w-smtp.wildix.com reaches End of Life on May 1, 2026. All systems using the service, e.g. in Dialplan and custom scripts and integrations, need to be reconfigured by May 1, 2026.

Wildix notifications about missed calls, voicemails, etc. are not affected and continue working as before.

1 Introduction
2 How to reconfigure your systems
- 2.1 Option 1: Use your own SMTP server
- 2.2 Option 2: Use the Wildix Notifications API
  - 2.2.1 Dialplan Integration Example

Introduction

The legacy SMTP service w-smtp.wildix.com will reach End of Life (EOL) on May 1, 2026. On the latest WMS versions, WMS 6/ WMS 7, the service has been replaced with a secure and API-based platform:notifications.wildix.com for sending email notifications.

The service has the following benefits:

Security: the notifications.wildix.com platform is API-based and offers improved security compared to the legacy SMTP relay.
Reliability: the service provides better scalability and higher delivery success rates.

Actions required:

Any custom scripts, dialplan logic, or third-party tools that are still using w-smtp.wildix.com (e.g., via mutt or other SMTP clients) will stop working after May 1, 2026. To continue sending emails or notifications, you need to update your integrations:

Review your existing Dialplan, scripts, and tools
Replace any usage of w-smtp.wildix.com or mutt with either:
- your own SMTP configuration, or
- /usr/sbin/sendemail.php (recommended option)

Failure to update integrations before May 1, 2026 will result in email delivery failures. See the detailed instructions below.

How to reconfigure your systems

Option 1: Use your own SMTP server

If you prefer to continue using traditional email clients such as mutt, you need to configure them with your own SMTP service by providing the correct configuration in WMS → System → SMTP client:

Option 2: Use the Wildix Notifications API

We strongly recommend to adopt /usr/sbin/sendemail.php rather than an SMTP service, to ensure compatibility with the Wildix ecosystem and long-term support.

Another option is to use Wildix Notifications API via sendemail.php. For dialplan and shell script integrations, Wildix provides a wrapper script:

Command syntax:

/usr/sbin/sendemail.php --body="Some text" --to="email@address"

Available options:

Option	Description

Option	Description
`--type`	Type of the mail template.
`--body`	Mail body (takes priority over `--body64`).
`--body64`	Mail body encoded in Base64.
`--to`	Recipient email address.
`--from`	Sender email address.
`--replyto`	Reply-to address.
`--cc`	Carbon-copy recipient(s).
`--bcc`	Blind carbon-copy recipient(s).
`--attach`	Path to a file to attach.
`--template`	Custom template name (default: `default`).
`--subject`	Email subject (takes priority over `--subject64`).
`--subject64`	Email subject encoded in Base64.
`--asrLanguage`	(for `voicemail` type) Language used for voicemail transcription (default: English).
`--asrFile`	(for `voicemail` type) File to send for transcription.
`--transcript`	(for `voicemail` type) Enable voicemail transcription. Values: `yes`.

Note: In case any assistance with the configuration is required, please contact Wildix Tech Support.

Dialplan Integration Example

On the screenshot below you can see an example of the configuration:

This ensures that all email notifications are routed through the notifications.wildix.com service.