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.

Derniers articles

Voir tous

Building Intelligent Voice Response Systems with Vodia's JavaScript IVR

JavaScript IVR transforms the way businesses handle incoming calls by enabling fully customizable, intelligent phone menu systems. Unlike static IVR setups with limited, pre-defined options, JavaScript IVR allows you to create dynamic call flows that adapt in real time based on caller input, business data, or even external API integrations. This means you can route calls more efficiently, automate complex processes, and offer highly personalized experiences to your customers. Whether you want to check customer records before transferring a call, adjust menu options based on time of day, or integrate with CRM systems for instant data access, JavaScript IVR gives you the flexibility and control to make it happen - all while improving efficiency and enhancing caller satisfaction.

August 11, 2025

Get The Support You Need Easily Through The Vodia Help Center On Jira

Vodia support is now easier to access through the Vodia Help Center on Jira, giving partners and customers a centralized platform to submit technical support tickets, ask sales or licensing questions, and suggest new features. With a valid license key, users can open detailed requests and track their status in one place. The portal also brings together Vodia documentation, the PBX API, and the Vodia forum, making it the go-to resource for everything Vodia. Whether you're troubleshooting, planning an upgrade, or just need guidance, the Help Center is designed to streamline your experience and connect you with the right support faster.

August 7, 2025

Vodia Attends ChannelCon 2025 in Nashville

At ChannelCon 2025 in Nashville, Vodia Sales Engineer Eric Altman engaged with MSPs and IT professionals to explore how AI is shaping the future of managed services. He emphasized that ChannelCon remains a valuable space for building strong vendor-partner relationships, especially as AI continues to dominate industry conversations. Altman noted how Vodia is helping MSPs unlock greater flexibility by combining powerful PBX features with AI-driven capabilities like dynamic call analytics, customized call flows, and automated performance reporting. He also highlighted Vodia’s recent launch of prepaid cloud instances on AWS, DigitalOcean, and Microsoft Azure, designed to streamline deployment for MSPs without infrastructure or licensing delays.

August 5, 2025