Stay updated and informed

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.

Effective communication is critical in today's fast-paced business environment. Whether you're reaching out to clients, colleagues, or team members, having a streamlined, straightforward, and informative communication process can significantly boost productivity. That's where multi-category templates come into play.

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.

Have you ever experienced the frustration of multiple agents working on the same ticket? In today's post, I explain the ticket lock feature in Znuny, which is designed to streamline workflows and prevent task duplication. Learn how this simple but powerful tool can enhance collaboration, assign clear ownership, and ensure smooth ticket management. Don’t miss out on optimizing your support process—read the full post now!

Providing excellent customer service is crucial for any organization. Znuny, the open-source service management software, has always been at the forefront of innovation, making the lives of IT support teams and service agents easier. Among its new features in Znuny 7.1 is the ability to unwatch multiple tickets simultaneously.

One critical component of ITIL (Information Technology Infrastructure Library) is the use of closure codes. These codes play a significant role in categorizing and analyzing the reasons behind resolving incidents and service requests. In this article, we will delve into the purpose of closure codes and provide practical insights on implementing them in your ITIL processes.