<< Click to Display Table of Contents >> Navigation:  Event and Object Analysis > Capture Results Filtering > Filtration Basics > Rules > Actions > JUMP action

Continue message processing in another table.

Description

This actions continues processing of the message in another table.

Format

<action name="jump" value="<table name>" />

<action name="jump" value="<table name>" />

The "name" attribute:

The name attribute specifies the name of the action: name="jump".

The "value" attribute:

The value="..." attribute specifies the name of the table to jump to for further processing of the message.

Please note:
Remember that jumps to the main table are prohibited.

Jumps which can result in an explicit or implicit recursion are also prohibited.

Example:

From the main table, jump to the yandex table to process messages from mail.ru and yandex.ru. The yandex table: the only rule destroys all messages larger than 100 KB. After that, jump back to the main table.

<?xml version="1.0" encoding="utf-8"?>
<filter name="Message filter" version="1.0">
 <comment>Message filter.</comment>
 
 <table name="main">
   <rule enabled="1">
     <comment>
       Processing of messages from the mail.ru,
       yandex.ru detectors in the yandex table.
     </comment>
     <match>
       <c name="detector" value="mail.ru, yandex.ru" />
     </match>
     <action name="jump" value="yandex"/>
   </rule>
 
   <rule enabled="1">
     <action name="drop" />
   </rule>
 </table>
 
 <table name="yandex">
   <comment>
     The table processes messages from the mail.ru,
     yandex.ru detectors.
   </comment>
 
   <rule enabled="1">
     <comment>
       Discard messages larger than 100 Kb.
     </comment>
     <match>
       <c name="size" op=">" value="100K"/>
     </match>
     <action name="drop" />
   </rule>
 
   <rule enabled="1">
     <comment>
       Returning to the main table for further processing.
     </comment>
     <action name="return" />
   </rule>
 </table>
 
</filter>