Znuny/Znuny LTS is a fork of the ((OTRS)) Community Edition, one of the most flexible web-based ticketing systems used for Customer Service, Help Desk, IT Service Management.
No errors in procmail.log on saving bonce reponse.
Actual behaviour
When bounce is stored in Znuny, ArticleCreateTransmissionError event is thrown in /opt/otrs/Kernel/System/Ticket/Article/Backend/Email.pm > ArticleCreateTransmissionError() and this makes also all handlers listening for ArticleCreate (regexp comparison in /opt/otrs/Kernel/System/EventHandler.pm) to run; one of them (TriggerEscalationStopEvents) requires OldTicketData parameter not provided by ArticleCreateTransmissionError and this throws an error like
In Znuny with procmail feeding e-mails to Znuny, send outbound e-mail ticket to non existing mailbox in valid domain and wait for mail bounce to return. See error like above in procmail log when storing bounce in Znuny.
Safest solution would be to avoid regexp matching and treat Event param as list of literals separated by | but some of Event definitions are regexps already so this would be braking change.
Environment
Expected behaviour
No errors in procmail.log on saving bonce reponse.
Actual behaviour
When bounce is stored in Znuny,
ArticleCreateTransmissionError
event is thrown in/opt/otrs/Kernel/System/Ticket/Article/Backend/Email.pm > ArticleCreateTransmissionError()
and this makes also all handlers listening forArticleCreate
(regexp comparison in/opt/otrs/Kernel/System/EventHandler.pm
) to run; one of them (TriggerEscalationStopEvents
) requiresOldTicketData
parameter not provided byArticleCreateTransmissionError
and this throws an error likeHow to reproduce
In Znuny with procmail feeding e-mails to Znuny, send outbound e-mail ticket to non existing mailbox in valid domain and wait for mail bounce to return. See error like above in procmail log when storing bounce in Znuny.
Additional information
New event names introduced in https://github.com/znuny/Znuny/commit/e59690ba9ddff11c39685bd7ca3b042330779fdd problaby conflict now with
Ticket::EventModulePost###4300-EscalationStopEvents > Event
regexp and should be renamed or regexp should be narrowed down if possible to something likeSafest solution would be to avoid regexp matching and treat Event param as list of literals separated by | but some of Event definitions are regexps already so this would be braking change.