Hello, we are using zammad 3.6 and sometimes we get e-mails from different “no-reply” addresses. That’t ok, we want to recive these mails and the new ticket.
But when zammad tries to send an email to one of these mails (Hello, your new Ticket … ) or when we close the ticket (Your Ticket was closed …) Zammad gets back en error message becuase the mail is undeliverable.
How can we define exceptions with e-mails addresses which must not recive any e-mails responses?
In the settings per trigger I can only write one single mail address … The behaviourwiht this setting is nice but there are more than one mail-addresses I want to except…
1 Like
Solution: using regex:
Using ing Zammad:
write in the field:
regex:mail1@online.de|mail2@online.de|mai3@online.de
awedor
July 19, 2021, 2:24pm
3
Thanks for sharing the solution, I’m sure many people are not aware that we can use regex in triggers now.
Ahh sorry but I found out that regex is only possible in the mail filter settings
Info here:
opened 12:31PM - 23 Sep 20 UTC
enhancement
trigger
verified
prioritised by payment
performance
specification required
### Infos:
* Used Zammad version: 3.5
* Installation method (source, package… , ..): any
* Operating system: any
* Database + version: any
* Elasticsearch version: any
* Browser + version: any
* Ticket-ID: #1079611
* Note: We regulary have this topic within support request - this also appears once in a while within the Community.
* This is not covered by Issue #2185 as it's technically a different approach and not relevant for AND/OR at all.
### Desired behavior:
If Triggers and Schedulers could make use of regular expressions (like postmaster filters do), this would also solve #2185 partly (for text fields) and allow several conditions of the same type.
But there's more: One could also use a regex to ensure that the checked string beings with a specific string.
This currently is not possible, because you can only check if a string is contained or not (`contains`, `contains not`).
Alternatively to regular expressions allowing the following matching on top of existing matching for text fields would be desirable:
* exact match
* begins with
* ends with
#### potential issues:
Regular expressions may bring potential issues in terms of performance, which is why I'd restrict them to
* postmaster filters
* triggers
* schedulers
I especially see issues if we have such a function within Overviews (even though it'd be cooleo).
### Actual behavior:
You currently neither can use regular expressions nor several conditions for triggers and schedulers.
awedor
July 20, 2021, 6:34am
5
I was wondering but I thought I just missed the change and believed you
1 Like
system
November 17, 2021, 6:35am
6
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.
