Automatic replies limit the options and filters available for sending specific responses to customers when new tickets are created. They are one size fits all. The setting SendNoAutoResponseRegExpTicket, is a blacklist option which needs to be replaced before moving away from auto-replies. Once this hurdle has been overcome, you can enhance your automatic replies with precise rules and notifications through ticket notifications.

Bad group name: Note.

Replicating the auto-reply while excluding the senders originally found in SendNoAutoResponseRegExpTicket.

Create the dynamic field (Checkbox) SendReply.
Create a new ticket notifcation to replace the automatic reply with the customer as the recipient.
Set the ticket filter on the notifaction to look for the SendReply check box, and optianlly the queue.
Disable the auto-reply for the desired queues.

Example Postmaster Filter.

Name: "send reply" - This is the name of the filter or rule being created or edited.

Match Header: This dropdown allows selecting different email headers to filter by.

From: This header specifies that the filter will check the "From" field of incoming emails.
for value: "shawn|roy" - This is the value that the "From" field must match for the rule to be applied. In this case, it is looking for emails including "shawn" or "roy" in from.

Note: Choose the not checkbox to negate the exepression.

Set Headers: This dropdown allows selecting different email headers to set.

X-OTRS-DynamicField-SendReply: This is a specific email header being checked by the filter.
with value: "1" - This is the value that the "X-OTRS-DynamicField-SendReply" header must have for the rule to be applied.

Recommendations:

Thorough Testing:

Conduct comprehensive testing of the new configuration in a controlled environment before full deployment.
Ensure all filters and dynamic fields work as intended to avoid disruptions in customer communication.
Training Programs:
.
By moving away from traditional automatic replies and adopting selective notifications, organizations can significantly improve the accuracy and relevance of their customer communications, enhancing overall service quality and efficiency.

Posts within the same category

Sep 19, 2025

When Mail Intake Breaks, CLI Saves the Day

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.

Sep 4, 2025

Turning Process Maps into Power Moves with Znuny

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.

View all

Selective notifications: level-up your automatic replies.