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. Initially, the email client used a single loop, which caused issues with stability and multi-tenant functionality, as 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, especially with fast, independent email delivery for each tenant. If you upgraded before June 28, we recommend reapplying the upgrade to ensure all fixes are in place.

Those who watched the 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 telephone systems. Many vendors use the term unified communications because of this. Honestly we never understood what that term stands for and 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 messages of the system. Every email reset the client, and let him start all over again. We had the email client run in its own thread, so that things like timeouts and connects could be programmed in an easy way.

However there were problems with this approach. 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. Anyway, that wasn’t even the biggest problem as we got the email client working pretty stable. What was a bigger problem was that in a multi-tenant environment, every domain may use their own email server. When that email server was down, all other domains were also affected by the problem. Email would still eventually go out; but it could take a long time before that happens. This was against the rule that every tenant should be working independent from anyone else.

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

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

Latest Articles

View All

Webinar | Real-Time Media Streaming in Vodia PBX: AI, Call Transcription, and Security in V69.5.6

Join Vodia Networks on April 8 for a live, in-depth webinar on how real-time media streaming is powering the future of voice communication. Discover how Vodia PBX version 69.5.6 enables seamless AI integration, live call transcription using the Whisper API, and secure voice data handling. Hosted by Sales Engineer Eric Altman and VoIP Engineer Hamlet Collado, this session will walk you through real-world use cases, including OpenAI and Google Speech-to-Text integrations, MS Teams support, and new security features. You’ll also get a first look at Vodia’s AI roadmap and have the opportunity to ask your questions during a live Q&A.

March 28, 2025

The Vodia PBX On-Premise Whisper AI Deployment​

Whisper, OpenAI’s Automatic Speech Recognition system, delivers multilingual, noise-tolerant, and technical-language-ready transcription through a streamlined encoder-decoder architecture. With Vodia PBX’s integration, organizations can choose between using OpenAI’s service or hosting Whisper AI locally for complete data sovereignty and control. This on-premise option ensures that sensitive call data stays within your infrastructure while still benefiting from powerful transcription capabilities. To explore deployment options, see our Whisper AI on-premise setup documentation, review a self-hosted integration example, or follow our cloud-based call transcription guide.

March 27, 2025

Vodia at Enterprise Connect 2025: Embracing AI and Advancing Communications

Vodia Sales Engineer Eric Altman attended Enterprise Connect 2025 on March 18 and 19, where he connected with partners and gained insight into the future of enterprise communications. AI was the clear focus of the event, with discussions centered on agentic systems, chatbots, and generative technologies. “It was certainly the main element in the atmosphere,” Eric noted. He also shared his excitement about Vodia PBX version 69.5.6, which includes real-time AI integration with OpenAI and call transcription using the Whisper API. The event confirmed that AI is rapidly becoming a core component of modern communication platforms—and Vodia is well-positioned to lead the way.

March 26, 2025