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

Why Fax Still Matters in 2025 and How Vodia Makes It Easy

Although many consider fax outdated, it continues to play a crucial role in sectors where compliance, confidentiality, and legal proof of delivery are non-negotiable. Healthcare providers rely on fax to meet HIPAA requirements, while industries such as finance, law, and real estate depend on it for contracts and documents that require signatures or legally verifiable transmission. Unlike email, fax offers confirmation reports that serve as proof of receipt, along with time-stamped records that hold up in legal proceedings. With Vodia’s PBX, digital fax becomes faster, easier, and more accessible than ever before, enabling users to drag and drop documents, monitor transmission progress, and receive immediate confirmations.

September 5, 2025

The Vodia PBX and SAML Integration

Vodia PBX now supports SAML integration, offering a secure and standards-based method for enterprise users to access their phone system through single sign-on. SAML, or Security Assertion Markup Language, allows employees to authenticate in one system and access other systems without managing multiple passwords, improving both security and user experience. By exchanging digitally signed SAML Assertions between Identity Providers and Service Providers, Vodia ensures seamless authentication across internal and external applications. With this integration, IT teams can simplify user management, reduce login complexity, and maintain strong security controls for business communications.

September 2, 2025

Rethinking Communication in Education: Vodia Smart School

Digital communication is now woven into daily school life, from classroom platforms to how parents and teachers connect. Vodia Smart School takes this further with a VoIP-powered system that provides fast, secure, and documented communication for consent forms, sick notes, and routine notifications. In urgent situations, it enables automated alerts to staff, parents, and first responders, ensuring rapid responses when time is critical. Fully GDPR-compliant and offering features such as caller ID masking, MS Teams integration, and control of bells, announcements, and school systems, Smart School gives schools a modern, reliable alternative to legacy systems while improving both safety and everyday operations.

August 28, 2025