
Hi,
Thanks Ralf for your prompt answer.
That's what I would think, too.
But OTRS didn't sort the mail into the specified queue, but took the queue defined in Postmaster Mail Account. :-(
Hmm. Wait.
Is this Postmaster Filter possible?
---8< ---
Match:
Header 1: Subject ---> (\D|^)123_Cust(\D|$)|(\D|^)123(\D).*(\D)Cust(\D|$)
Header 2: X-OTRS-Queue ---> defaultqueue as defined in Postmaster Mail Account
Set:
Header 1: X-OTRS-Queue --> another queue esp. for this filter
---8< ---
So, is X-OTRS-Queue set after receiving the mail (and before running through postmaster filter)? Postmaster Mail account is set to "Dispatching by selected Queue" ...
Regards,
Jan Dreyer
-----Original Message-----
From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Ralf Hildebrandt
Sent: Friday, June 24, 2011 3:02 PM
To: otrs@otrs.org
Subject: Re: [otrs] PostmasterFilter: Regexp not working
* Ralf Hildebrandt
* Jan.Dreyer@bertelsmann.de
: Hello,
we are using the postmaster filter very excessively (having more than 100). Some regexp are really not failure-proof.
But I thought this one (looking at subject line) is:
---8< ---
(\D|^)123_Cust(\D|$)|(\D|^)123(\D).*(\D)Cust(\D|$)
Damn, didn't see the other | So it's either: (\D|^)123_Cust(\D|$) or (\D|^)123(\D).*(\D)Cust(\D|$) The second part of the regexp should match! # echo "Subject: 123: GPW Cust Lieferung /UPS hat Pal. gezogen **CUT OFF RELEVANT**" | pcregrep "(\D|^)123(\D).*(\D)Cust(\D|$)" Subject: 123: GPW Cust Lieferung /UPS hat Pal. gezogen **CUT OFF RELEVANT** yup, it's matching! -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt@charite.de | http://www.charite.de --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs