Hello and thank you for your reply.
I tried what you suggested, I tried other actions as well, but nothing happened.
It seems that the problem relies on the filtering section (the Match header)
and not on the action Header.
However I see that your configuration is working, despite of mine.
Maybe you followed a different path??
I configured the new Content-Type header through the web interface, editing the
Ticket::Core::PostMaster::PostmasterX-Header section in SysConfig.
Then I configured the PostMaster filter as you did: I've placed it in first
position: it's not pocessed, while other filters are, and ther's no trace about
it in system log.
Maybe you have passed through some other config steps, or edited config file
manually, or what?! Can you provide more informations about your configuration?
Or maybe you have any idea why it's not working for me?
Thanks in advance
Gabriele
----- Original Message -----
From: Carlos G. Oyarzabal
To: 'User questions and discussions about OTRS.org'
Sent: Sunday, June 10, 2007 8:52 PM
Subject: RE: [otrs] Filtering Disposition Notifications
I filtere some notifications as follows:
Content-Type :: disposition
X-OTRS-queue :: Junk
I think all filter actions must to have a destination, with the previous
filter OTRS put the "disposition" notifications to Junk Queue, after that I
close tickets created into Junk queue.
Carlos
México
------------------------------------------------------------------------------
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de Gabriele D'Andrea
Enviado el: Viernes, 08 de Junio de 2007 04:50 a.m.
Para: User questions and discussions about OTRS.org
Asunto: [otrs] Filtering Disposition Notifications
Hello,
I'm trying to filter messages that are response to Disposition Notifications.
I've seen that this kind of messages contains the following header:
Content-Type: multipart/report;
report-type=disposition-notification;
boundary="----=_NextPart_000_015A_01C7A9BD.EA993250"
So I've tried to filter incoming messages by Content-Type header
1st, I've created a new PostMaster X-Header to be scanned for Content-Type
header
2nd, I've created the following PostMaster Filter rule, that is processed for
first
Corrispondenza: Intestazione (header) 1: - Body Cc Content-Type Delivered-To
Errors-To From Importance In-Reply-To List-Archive List-Id Mailing-List
Message-ID Message-Id Organization Precedence References Reply-To ReplyTo
Resent-From Resent-To Subject To User-Agent X-Loop X-Mailer X-No-Loop
X-OTRS-ArticleKey1 X-OTRS-ArticleKey2 X-OTRS-ArticleKey3 X-OTRS-ArticleType
X-OTRS-ArticleValue1 X-OTRS-ArticleValue2 X-OTRS-ArticleValue3
X-OTRS-CustomerNo X-OTRS-CustomerUser X-OTRS-FollowUp-ArticleKey1
X-OTRS-FollowUp-ArticleKey2 X-OTRS-FollowUp-ArticleKey3
X-OTRS-FollowUp-ArticleType X-OTRS-FollowUp-ArticleValue1
X-OTRS-FollowUp-ArticleValue2 X-OTRS-FollowUp-ArticleValue3
X-OTRS-FollowUp-Priority X-OTRS-FollowUp-Queue X-OTRS-FollowUp-SenderType
X-OTRS-FollowUp-State X-OTRS-FollowUp-TicketKey1 X-OTRS-FollowUp-TicketKey10
X-OTRS-FollowUp-TicketKey11 X-OTRS-FollowUp-TicketKey12
X-OTRS-FollowUp-TicketKey13 X-OTRS-FollowUp-TicketKey14
X-OTRS-FollowUp-TicketKey15 X-OTRS-FollowUp-TicketKey16
X-OTRS-FollowUp-TicketKey2 X-OTRS-FollowUp-TicketKey3
X-OTRS-FollowUp-TicketKey4 X-OTRS-FollowUp-TicketKey5
X-OTRS-FollowUp-TicketKey6 X-OTRS-FollowUp-TicketKey7
X-OTRS-FollowUp-TicketKey8 X-OTRS-FollowUp-TicketKey9
X-OTRS-FollowUp-TicketValue1 X-OTRS-FollowUp-TicketValue10
X-OTRS-FollowUp-TicketValue11 X-OTRS-FollowUp-TicketValue12
X-OTRS-FollowUp-TicketValue13 X-OTRS-FollowUp-TicketValue14
X-OTRS-FollowUp-TicketValue15 X-OTRS-FollowUp-TicketValue16
X-OTRS-FollowUp-TicketValue2 X-OTRS-FollowUp-TicketValue3
X-OTRS-FollowUp-TicketValue4 X-OTRS-FollowUp-TicketValue5
X-OTRS-FollowUp-TicketValue6 X-OTRS-FollowUp-TicketValue7
X-OTRS-FollowUp-TicketValue8 X-OTRS-FollowUp-TicketValue9 X-OTRS-Ignore
X-OTRS-Info X-OTRS-Loop X-OTRS-Priority X-OTRS-Queue X-OTRS-SenderType
X-OTRS-State X-OTRS-TicketKey1 X-OTRS-TicketKey10 X-OTRS-TicketKey11
X-OTRS-TicketKey12 X-OTRS-TicketKey13 X-OTRS-TicketKey14 X-OTRS-TicketKey15
X-OTRS-TicketKey16 X-OTRS-TicketKey2 X-OTRS-TicketKey3 X-OTRS-TicketKey4
X-OTRS-TicketKey5 X-OTRS-TicketKey6 X-OTRS-TicketKey7 X-OTRS-TicketKey8
X-OTRS-TicketKey9 X-OTRS-TicketValue1 X-OTRS-TicketValue10 X-OTRS-TicketValue11
X-OTRS-TicketValue12 X-OTRS-TicketValue13 X-OTRS-TicketValue14
X-OTRS-TicketValue15 X-OTRS-TicketValue16 X-OTRS-TicketValue2
X-OTRS-TicketValue3 X-OTRS-TicketValue4 X-OTRS-TicketValue5 X-OTRS-TicketValue6
X-OTRS-TicketValue7 X-OTRS-TicketValue8 X-OTRS-TicketValue9 X-Original-To
X-Priority X-Spam-Flag X-Spam-Level X-Spam-Status Valore:
Impostazione: Intestazione (header) 1: - X-OTRS-ArticleKey1
X-OTRS-ArticleKey2 X-OTRS-ArticleKey3 X-OTRS-ArticleType X-OTRS-ArticleValue1
X-OTRS-ArticleValue2 X-OTRS-ArticleValue3 X-OTRS-CustomerNo X-OTRS-CustomerUser
X-OTRS-FollowUp-ArticleKey1 X-OTRS-FollowUp-ArticleKey2
X-OTRS-FollowUp-ArticleKey3 X-OTRS-FollowUp-ArticleType
X-OTRS-FollowUp-ArticleValue1 X-OTRS-FollowUp-ArticleValue2
X-OTRS-FollowUp-ArticleValue3 X-OTRS-FollowUp-Priority X-OTRS-FollowUp-Queue
X-OTRS-FollowUp-SenderType X-OTRS-FollowUp-State X-OTRS-FollowUp-TicketKey1
X-OTRS-FollowUp-TicketKey10 X-OTRS-FollowUp-TicketKey11
X-OTRS-FollowUp-TicketKey12 X-OTRS-FollowUp-TicketKey13
X-OTRS-FollowUp-TicketKey14 X-OTRS-FollowUp-TicketKey15
X-OTRS-FollowUp-TicketKey16 X-OTRS-FollowUp-TicketKey2
X-OTRS-FollowUp-TicketKey3 X-OTRS-FollowUp-TicketKey4
X-OTRS-FollowUp-TicketKey5 X-OTRS-FollowUp-TicketKey6
X-OTRS-FollowUp-TicketKey7 X-OTRS-FollowUp-TicketKey8
X-OTRS-FollowUp-TicketKey9 X-OTRS-FollowUp-TicketValue1
X-OTRS-FollowUp-TicketValue10 X-OTRS-FollowUp-TicketValue11
X-OTRS-FollowUp-TicketValue12 X-OTRS-FollowUp-TicketValue13
X-OTRS-FollowUp-TicketValue14 X-OTRS-FollowUp-TicketValue15
X-OTRS-FollowUp-TicketValue16 X-OTRS-FollowUp-TicketValue2
X-OTRS-FollowUp-TicketValue3 X-OTRS-FollowUp-TicketValue4
X-OTRS-FollowUp-TicketValue5 X-OTRS-FollowUp-TicketValue6
X-OTRS-FollowUp-TicketValue7 X-OTRS-FollowUp-TicketValue8
X-OTRS-FollowUp-TicketValue9 X-OTRS-Ignore X-OTRS-Info X-OTRS-Loop
X-OTRS-Priority X-OTRS-Queue X-OTRS-SenderType X-OTRS-State X-OTRS-TicketKey1
X-OTRS-TicketKey10 X-OTRS-TicketKey11 X-OTRS-TicketKey12 X-OTRS-TicketKey13
X-OTRS-TicketKey14 X-OTRS-TicketKey15 X-OTRS-TicketKey16 X-OTRS-TicketKey2
X-OTRS-TicketKey3 X-OTRS-TicketKey4 X-OTRS-TicketKey5 X-OTRS-TicketKey6
X-OTRS-TicketKey7 X-OTRS-TicketKey8 X-OTRS-TicketKey9 X-OTRS-TicketValue1
X-OTRS-TicketValue10 X-OTRS-TicketValue11 X-OTRS-TicketValue12
X-OTRS-TicketValue13 X-OTRS-TicketValue14 X-OTRS-TicketValue15
X-OTRS-TicketValue16 X-OTRS-TicketValue2 X-OTRS-TicketValue3
X-OTRS-TicketValue4 X-OTRS-TicketValue5 X-OTRS-TicketValue6 X-OTRS-TicketValue7
X-OTRS-TicketValue8 X-OTRS-TicketValue9 Valore:
But I've got no result, the filter is not applied.
Can someone tell me why this is not working?
Or alternatively suggest a better method?
I need to filter and ignore messages that are replies to Disposition
notifications
Thank you for any help
--
Gabriele D'Andrea
------------------------------------------------------------------------------
_______________________________________________
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
Support or consulting for your OTRS system?
=> http://www.otrs.com/
_______________________________________________
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
Support or consulting for your OTRS system?
=> http://www.otrs.com/
