Hi.
At out company we were using OTRS version 3.0.11, but I decided that it's time to make an update and switched to the newest version. And some Postmaster filters stopped working. Basically, we have two types of filters. One based on the receiver's email:
Delivered-To: otrs@*
X-OTRS-Queue: Some Queue
Stop after Match: No
And another one based on subject:
Subject: STOP
X-OTRS-Queue: Other Queue
Stop after Match: Yes
Basically, as I understand, second filter should be used always, when subject is "STOP", because of "Stop after Match" set to "yes", but all the emails, after the update, go to the queue defined by the first rule. This makes no sense to me, but I couldn't find any more info, because there is no so much documentation on this particular subject(I mean PostMaster filters). Could please someone explain to me, what am I doing wrong?
[SOLVED] Postmaster filter stopped working after update
Moderator: crythias
[SOLVED] Postmaster filter stopped working after update
Last edited by TDO on 04 Oct 2012, 11:41, edited 1 time in total.
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Postmaster filter stopped working after update
Delivered-To: otrs@*
X-OTRS-Queue: Some Queue
Stop after Match: No
Why are you using this? The Postmaster mail accounts dispatching can handle this.
X-OTRS-Queue: Some Queue
Stop after Match: No
Why are you using this? The Postmaster mail accounts dispatching can handle this.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: Postmaster filter stopped working after update
how are they listed in the postmaster screen? They are run in the order they apear there
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
Re: Postmaster filter stopped working after update
Well, it's difficult to remember our reasoning, when we implemented this some years ago. But this worked quite good for us until the recent update. Maybe it's not the most elegant solution, but it should still work. Am I wrong?crythias wrote:Delivered-To: otrs@*
X-OTRS-Queue: Some Queue
Stop after Match: No
Why are you using this? The Postmaster mail accounts dispatching can handle this.
I thought so too, so I experimented with the names. In the beginning second rule was almost the last, but I renamed and it became the first. It made no difference. Result is always the same. I am trying to solve this problem for almost the whole day and I have an impression that "Subject" rules are just ignored.jojo wrote:how are they listed in the postmaster screen? They are run in the order they apear there
Re: Postmaster filter stopped working after update
Ok, looks like that after update PostMaster filters stopped working completely. When Email Address is defined in System Email Addresses, then emails are delivered to the queue associated with that email address(or the last queue associated, if there are more than one defined). If there is no address defined in System Email Addresses, emails always go to RAW Queue, even if there are some rules defined in PostMaster filters. Now I need to find out, why is this so.
Re: Postmaster filter stopped working after update
Finally I was able to solve this problem.
In filters queue were in UPPERCASE, when they should be lowercase(as defined in the system). I don't know why it worked before and why it has stopped to work after update. Maybe otrs.PostMaster.pl became case-sensitive or update went wrong and names were changed to a different case in one place, but not in the other. Anyway, to fix a problem I just needed to review all our PostMaster filters and rename all the queues.
In filters queue were in UPPERCASE, when they should be lowercase(as defined in the system). I don't know why it worked before and why it has stopped to work after update. Maybe otrs.PostMaster.pl became case-sensitive or update went wrong and names were changed to a different case in one place, but not in the other. Anyway, to fix a problem I just needed to review all our PostMaster filters and rename all the queues.