Hidden Jewels in Znuny's Frontend: The Art of Ellipses and Configuration

In the world of ticketing systems, clarity and brevity are everything. Znuny quietly excels at this—especially in how it handles long strings in the frontend. Ever noticed how customer info, dynamic fields, or agent lists get gracefully truncated with ellipses (...)?

Single Sign-On has long been a requirement for enterprise deployments of Znuny. Until now, making it work meant configuring an external Apache module — typically mod_auth_mellon or mod_auth_kerb — correctly wiring it to your Identity Provider, and then connecting the result to Znuny's auth pipeline. It worked, but the setup was sometimes fragile, hard to document, and entirely outside Znuny itself.

One System, Many Senders: Introducing Outbound Email Profiles in Znuny 7.3

If your organization uses Znuny with multiple sender addresses — think support@, sales@, noreply@ — you've probably run into a familiar challenge: all outgoing emails go through a single, shared mail configuration. That works fine when everyone sends the same way. But in reality, different teams, domains, or compliance requirements often call for different transport settings, credentials, or even entirely different sending methods.

Znuny 7.3 solves this cleanly with Outbound Email Profiles without require 3rd party add-ons.

Sie warten sicher schon gespannt auf die Veröffentlichung von Znuny 7.3 – wir auch. Während der Entwicklungsphase von Version 7.3 haben wir eine wichtige Entscheidung getroffen, um diese und alle zukünftigen Versionen zu verbessern: Wir haben den Zeitplan für die Verfügbarkeit unserer Add-ons für neue Versionen geändert.

Recovering from Procmail misconfigurations and spool file buildup is simple with Znuny and formail.

In a perfect world, incoming emails flow seamlessly into your Znuny ticketing system and are processed without delay. But in reality, even a small misconfiguration — especially when direct delivery is done via procmail — can quietly derail your mail intake.

Instead of creating tickets, Znuny’s expected mail accumulates messages in the local spool file (e.g., /var/spool/mail/znuny). No alerts. No tickets. Just a growing backlog of unprocessed mail.

Managing change requests can feel like herding cats — multiple stakeholders, shifting priorities, and the constant risk of something slipping through the cracks. That’s where a well‑designed workflow becomes your secret weapon. In this guide, we’ll take a clean, visual BPMN process map and bring it to life inside Znuny, the open‑source ticketing powerhouse. You’ll see exactly how to turn decision points into automated transitions, keep every step accountable, and make sure no request dies in someone’s inbox. By the end, you’ll have a repeatable, auditable process that your team can follow without missing a beat.

⚠️ Attention Znuny Admins: Important Changes to Exchange Online Limits ⚠️

Microsoft has updated the sending limits for Exchange Online, which may impact your Znuny environment.

Default Znuny Cron Maintenance Tasks

Cron Maintenance Tasks carry the weight of system health and relevant maintenance tasks. By stating and modifying these settings according to your needs, tasks such as unlocking tickets after a timeout can be handled seamlessly, enabling smooth collaboration and improved customer service.

Many new users have yet to fully explore Znuny's vast capabilities, missing out on features that can transform their service desk into a powerhouse of efficiency and customer satisfaction. With the right configurations, Znuny can streamline communication, improve ticket management, and offer a highly customized user experience. To unlock the full potential of Znuny and take your service desk operations to the next level, here are some essential features you should review and activate today.