Hey Ralf, you need to build a PostMaster filter which recognizes the usual autoreplies (subject, content, whatever). Then you have two possibilities: - Set X-OTRS-Ignore to yes - Set a specially created dynamic field to a value and initialize all other mails with the opposite value
With the first one, no autoreply will reach the ticket system at all, which could be undesired. For the second one, you need to create a ticket notification by yourself, which filters for your queues and the value for "not an autoreply". In this one you'll put your text. Furthermore: if you create a ticket and send a mail to your customers/hospital users and they reply with an vacation response, doesn't it leave the original subject intact? Kind regards, Matthias T-SYSTEMS INTERNATIONAL GMBH Matthias Terlinde Bonner Talweg 100 53113 Bonn E-Mail: [email protected] Internet: www.t-systems.com Let's power higher performance You can find the compulsory statement on: www.t-systems.com/compulsory-statement > -----Ursprüngliche Nachricht----- > Von: otrs <[email protected]> Im Auftrag von otrs- > [email protected] > Gesendet: Samstag, 9. November 2019 15:57 > An: [email protected] > Betreff: otrs Digest, Vol 133, Issue 1 > > Send otrs mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.otrs.org/mailman/listinfo/otrs > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific than "Re: > Contents of otrs digest..." > > > Today's Topics: > > 1. User accidentally created more than 5000 tickets (Mathias Waack) > 2. Re: User accidentally created more than 5000 tickets > (Mathias Waack) > 3. Re: User accidentally created more than 5000 tickets > (Florian Edlhuber) > 4. Conditional autoreply possible? (Ralf Hildebrandt) > 5. Re: Conditional autoreply possible? (Florian Edlhuber) > 6. LDAP Lookup for Ticket Content (Anthony F McInerney) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 30 Oct 2019 10:20:11 +0100 > From: Mathias Waack <[email protected]> > To: [email protected] > Subject: [otrs] User accidentally created more than 5000 tickets > Message-ID: <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > An HTML attachment was scrubbed... > URL: > <http://lists.otrs.org/pipermail/otrs/attachments/20191030/ecfdc486/attach > ment-0001.html> > > ------------------------------ > > Message: 2 > Date: Sat, 2 Nov 2019 10:14:39 +0100 > From: Mathias Waack <[email protected]> > To: [email protected] > Subject: Re: [otrs] User accidentally created more than 5000 tickets > Message-ID: <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > An HTML attachment was scrubbed... > URL: > <http://lists.otrs.org/pipermail/otrs/attachments/20191102/a1215de9/attac > hment-0001.html> > > ------------------------------ > > Message: 3 > Date: Sat, 2 Nov 2019 22:26:05 +0100 > From: Florian Edlhuber <[email protected]> > To: "User questions and discussions about OTRS." <[email protected]> > Subject: Re: [otrs] User accidentally created more than 5000 tickets > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > > Hi, > > 30.10.2019 10:27 - Mathias Waack schrieb: > > > Finally I was able to delete these tickets using the generic agent. > > But since then our otrs does not send any email. The communication > > logs shows again more than 1000 open communications and the number is > > constantly growing. Why is otrs queuing these messages without sending > > it? Where can I start searching for the reason? > > Depending on your mail configuration, sending takes time. It needs a working > DNS and a good MTA. > > On specific (wrong!) Mail configuration OTRS tries to send mails to non- > existend users. Maybe you have this situation. > > Check your communication log and try to use the otrs.Console.pl command > to check the mail sending queue and/or delete it. > > Check your local syslog and mail log, too. > > regards > Florian > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.otrs.org/pipermail/otrs/attachments/20191102/557ec2fc/attach > ment-0001.html> > > ------------------------------ > > Message: 4 > Date: Wed, 6 Nov 2019 14:30:52 +0100 > From: Ralf Hildebrandt <[email protected]> > To: [email protected] > Subject: [otrs] Conditional autoreply possible? > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8 > > We have queues where autoreply is activated. > > But we don't want to reply to vacation autoresponders and the like. Is that > possible? > > > Ralf Hildebrandt > Charit? - Universit?tsmedizin Berlin > Gesch?ftsbereich IT | Abteilung Netzwerk > > Campus Benjamin Franklin (CBF) > Haus I | 1. OG | Raum 105 > Hindenburgdamm 30 | D-12203 Berlin > > Tel. +49 30 450 570 155 > [email protected] > https://www.charite.de > > > ------------------------------ > > Message: 5 > Date: Wed, 6 Nov 2019 22:10:34 +0100 > From: Florian Edlhuber <[email protected]> > To: "User questions and discussions about OTRS." <[email protected]> > Subject: Re: [otrs] Conditional autoreply possible? > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > > Hi, > > 06.11.2019 14:37 - Ralf Hildebrandt schrieb: > > We have queues where autoreply is activated. > > But we don't want to reply to vacation autoresponders and the like. > > Is that possible? > > you can try Postmaster Filter for subject and set X-OTRS-Ignore = YES but > then you'll lose the mail. This is the easy (but usually not the > preferred) way. > > To specifically filter for the autoresponse requires more deeper tweaking. I > think on specific header/subject handling, setting dynamic fields and trigger > a > ticket notification (not a auto response) on that. > > AFAIK not an easy one. > > -- > Florian > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.otrs.org/pipermail/otrs/attachments/20191106/8d60dc84/attach > ment-0001.html> > > ------------------------------ > > Message: 6 > Date: Sat, 9 Nov 2019 14:56:47 +0000 > From: Anthony F McInerney <[email protected]> > To: "User questions and discussions about OTRS." <[email protected]> > Subject: [otrs] LDAP Lookup for Ticket Content > Message-ID: > <CALoKiCrYr9VZdmWAmmThvAT4vxTShyguZ=2vA- > [email protected]> > Content-Type: text/plain; charset="utf-8" > > Hi All, > I am looking for a very specific feature/plugin for LDAP lookup. > > If I understand correctly OTRS is using something like > https://metacpan.org/pod/distribution/perl-ldap/lib/Net/LDAP.pod for the > LDAP auth ? > > Which seems to have the ability to meet my requirements. > > What I would like to do, is an ldap search to query the members of a Group. > (Much like it already does for Customer or Agent auth.) > > I would like to list those members in a ticket, somehow and send them out as > a notification. > > Would someone be able to help guide in me the right direction to solve this? > > Many thanks > Ant. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.otrs.org/pipermail/otrs/attachments/20191109/6bba6b06/attac > hment.html> > > ------------------------------ > > Subject: Digest Footer > > --------------------------------------------------------------------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs > > > ------------------------------ > > End of otrs Digest, Vol 133, Issue 1 > ************************************ --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs
