4 {pmg} ships with a highly configurable mail filter. It’s an easy but
5 powerful way to define filter rules by user, domains, time frame,
6 content type and resulting action.
8 image::images/screenshot/pmg-gui-mail-filter-rules.png[]
10 Every rule has 5 categories ('FROM', 'TO', 'WHEN', 'WHAT' and
11 'ACTION'), and each category may contain several objects to match
16 Who is the sender or receiver of the e-mail? Those objects can be used
17 for the 'TO' and/or 'FROM' category.
20 Example: EMail-object - Who is the sender or receiver of the e-mail?
25 What is in the e-mail?
28 Example: Does the e-mail contain spam?
33 When is the e-mail received by {pmg}?
36 Example: Office Hours - Mail is received between 8:00 and 16:00.
41 Defines the final actions.
44 Example: Mark e-mail with “SPAM:” in the subject.
47 Rules are ordered by priority, so rules with higher priority are
48 executed first. It is also possible to set a processing direction:
50 'In':: Rule applies for all incoming e-mails
52 'Out':: Rule applies for all outgoing e-mails
54 'In & Out':: Rule applies for both directions
56 And you can also disable a rule completely, which is mostly useful for
57 testing and debugging. The 'Factory Defaults' button alows you to
58 reset the filter rules.
64 image::images/screenshot/pmg-gui-mail-filter-actions.png[]
66 Please note that some actions stops further rule precessing. We call
72 Accept mail for Delivery. This is a 'final' action.
78 Block mail. This is a 'final' action.
84 Move to quarantine (virus mails are moved to the “virus quarantine”,
85 other mails are moved to “spam quarantine”). This is also a 'final' action.
91 Send notifications. Please note that object configuration can use
92 xref:rule_system_macros[macros], so it is easy to include additional
93 information. For example, the default 'Notify Admin' object sends the
94 following information:
96 .Sample notification action body:
100 Receiver: __RECEIVERS__
103 Matching Rule: __RULE__
111 Notification can also include a copy of the original mail.
114 Blind Carbon Copy (BCC)
115 ~~~~~~~~~~~~~~~~~~~~~~~
117 The BCC object simply sends a copy to another target. It is possible to
118 send the original unmodified mail, or the processed result. Please
119 note that this can be quite different, i.e. when a previous rule
126 This object is able to add or modify mail header attributes. As notice above, you can use xref:rule_system_macros[macros], making this a very powerful object. For example, the 'Modify Spam Level' actions adds detailed infomation about detected Spam characteristics to the ` X-SPAM-LEVEL` header.
128 .'Modify Spam Level' Header Attribute
134 Another prominent example is the 'Modify Spam Subject' action. This
135 simply adds the 'SPAM:' prefix to the original mail subject:
137 .'Modify Spam Subject' Header Attribute
140 Value: SPAM: __SUBJECT__
147 Remove attachments can either remove all attachments, or only those
148 matched by the rules 'WHAT' object. You can also specify the
149 replacement text if you want.