Editorial

What Happened to Email?

Published on:

June 28, 2014

In version 5.2.3 we made significant updates to the email client, addressing issues with Linux systems and multi-tenant environments. The email client initially used a single loop, which caused issues with stability and multi-tenant functionality - a problem with one email server affected all domains. The solution was to switch to a multi-threaded client, but this introduced its own challenges, especially with the STARTTLS command during the switch between unencrypted and encrypted traffic. After a second build to fix these issues, the email client is now more reliable, with fast, independent email delivery for each tenant. If you upgraded before June 28, we recommend reapplying the upgrade to ensure all the fixes are in place.

Those who watched release 5.2.3 closely might wonder what was going on with the email client. The first build had major problems with Linux operating systems. A second build was necessary to get it working again with popular email services.

Email has become an essential component in today's telephone systems. Many vendors use the term "unified communications" because of this. Honestly, we never understood what this term stands for, so we avoided the buzzword. Notwithstanding, the good old SMTP protocol delivers notifications and messages that are available on a telephone system, fast and reliably across a very large range of devices.

The old email client was using a single loop for all system messages. Every email reset the client, and he or she could start all over again. We had the email client run in its own thread, so things like timeouts and connects could be easily programmed.

There were problems with this approach, however. First of all, multithreaded tasks are always a source for trouble. If problems occur, they occur on a random basis; some of them occur only sometimes, and those are the hardest to fix. That wasn’t even the biggest problem, as we got the email client working pretty stable. A bigger problem was that in a multi-tenant environment, every domain might use its own email server. When that email server was down, all other domains were also affected. Email would still eventually go out, but it could take a long time before it happened. This was against the rule that every tenant should be working independently from anyone else.

When we changed the client to multi-tenant we of course tried to preserve the proven logic from the single loop client. Because most email servers support a dynamic switching from unencrypted to encrypted traffic using the STARTTLS command, however, our new client got into trouble when the second email was sent out right after the first. The TLS context was still the same, and what the PBX essentially did was a CONTINUETLS command. Unfortunately, no email server supports this, so we needed to come up with another build that also fixes that problem.

If you upgraded to 5.2.3 before June 28, we recommend you repeat the upgrade to make sure you got those last-minute email patches. Then you can enjoy fast and reliable email like never before.

Latest Articles

View All

The Vodia - Fanvil Hospitality Communications Webinar | Presentation Slides and Recording Now Available

This webinar demonstrates how integrating Fanvil’s IP Hotel Devices with the Vodia PBX delivers smart, guest-focused communication solutions that enhance operational efficiency and personalize guest experiences. It covers practical strategies for easy deployment and highlights Vodia’s AI-powered features that automate hotel workflows and streamline communication. With real-world applications and best practices, this session showcases how Vodia and Fanvil are advancing hospitality technology.

July 2, 2025

Announcing the Vodia Prepaid Offer on AWS Marketplace

Vodia has launched a new prepaid PBX offering on AWS Marketplace, enabling businesses of all sizes to quickly and easily deploy a secure, feature-rich phone system in the cloud. Building on the success of our prepaid solutions for Microsoft Azure and DigitalOcean, this new AWS package offers a cost-effective, scalable, and reliable way to integrate enterprise-grade telephony into your existing infrastructure. Whether you're connecting SIP devices with Microsoft Teams via our certified SBC or establishing a standalone PBX, the deployment process is streamlined, flexible, and built for growth.

June 30, 2025

Mastering Vodia PBX Installation on Linux: A Complete Guide for System Administrators

Installing Vodia PBX on Linux offers system administrators a powerful, enterprise-grade communication solution with built-in monitoring, automated backups, and disaster recovery features. This guide walks through supported Linux distributions, pre-installation requirements, and step-by-step instructions using a universal install script. With options for service monitoring, backup scheduling, and cloud deployment, it ensures a scalable and secure setup. Post-installation, standard Linux tools manage service status, updates, and logs, making ongoing maintenance simple.

June 26, 2025