User Tools

Site Tools


faq:email:global_mail_rules_configuration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
faq:email:global_mail_rules_configuration [2022/02/15 11:31] vikkifaq:email:global_mail_rules_configuration [2022/12/15 11:48] (current) – [Examples] vikki
Line 6: Line 6:
 The **Global Email Rules** is for the administrator to further refine their email traffic. It is applicable to incoming emails, where you can determine which sender's emails are always allowed and which sender's emails should be blocked. The **Global Email Rules** is for the administrator to further refine their email traffic. It is applicable to incoming emails, where you can determine which sender's emails are always allowed and which sender's emails should be blocked.
  
-1. You have to login as an Avomaster/VOadmin in order manage these mail rules.\\ +===== Accessing Global Email Rules ===== 
-2. Referring to the image below, go to **(1)Profile (icon on the top section) -> (2)Admin (rightmost icon) -> (3)Global Email Rules (left side under Admin Task) -> (4)Make any important edits on this section -> (5)Update button to save the edits**+ 
-{{faq:general:jmail1.png|}}\\ +1. You have to login as an Avomaster/VOadmin in order manage these mail rules. 
-{{faq:email:globmail.png|}}\\ + 
-==== Rules syntax ==== +2. Referring to the image below, go to **Profile** -> **Admin**. 
-  * Each line is a rule. A rule may contains wild card like those used by the Bourne shell.\\+ 
 +|{{:faq:email:global_mail_rules:1.png|}}| 
 + 
 +3. Click on **Global Email Rules** from the left panel. 
 + 
 +|{{:faq:email:global_mail_rules:2.png|}}| 
 + 
 +4. At the Mail Rules page, add in the required rules in the provided field and click **Update** to save the edits. 
 + 
 +|{{:faq:email:global_mail_rules:3.png|}}| 
 + 
 +5. The "Updated" message will be shown when the changes are successfully saved. 
 + 
 +|{{:faq:email:global_mail_rules:4.png|}}
 + 
 +-------- 
 + 
 +===== Rules Syntax ===== 
 +  * Each line is a rule. A rule may contains wild card like those used by the Bourne shell.
   * Each rule is prefix with an action, like this: **[//action//] [//space//] [//rule//] [//cr//]**   * Each rule is prefix with an action, like this: **[//action//] [//space//] [//rule//] [//cr//]**
  
-==== Examples ====+-------- 
 + 
 +===== Examples =====
 The following will allow all email from yahoo.com to get pass: The following will allow all email from yahoo.com to get pass:
    pass *@yahoo.com    pass *@yahoo.com
-Note that the "*" sign is very important here.\\+Note that the "*" sign is very important here.
  
 The following will mark all emails from somedomain.com as Junk: The following will mark all emails from somedomain.com as Junk:
Line 27: Line 47:
 The following will reject (stop delivery) of all email coming from hotmail domain. The following will reject (stop delivery) of all email coming from hotmail domain.
    block *@hotmail.*    block *@hotmail.*
-Note that the * at the end will basically block all hotmail domain including:\\ +Note that the * at the end will basically block all hotmail domain including: hotmail.com, hotmail.net or hotmail.cc
-hotmail.com, hotmail.net or hotmail.cc\\+
  
 The following will reject (stop delivery) incoming mails from the domain xyz.com, including its subdomain (like shop.xyz.com, alert.xyz.com): The following will reject (stop delivery) incoming mails from the domain xyz.com, including its subdomain (like shop.xyz.com, alert.xyz.com):
Line 37: Line 56:
    junk *@domain.com    junk *@domain.com
 This would basically block all other email from domain.com other than vip@domain.com.\\ This would basically block all other email from domain.com other than vip@domain.com.\\
-However, pay attention that the pass rule must place before the junk (or reject) rule, or else it will not work this way.\\+However, pay attention that the pass rule must place before the junk (or reject) rule, or else it will not work this way.
  
 Action tags available:\\ Action tags available:\\
-**pass** Let the email pass. The Junk ranking will set to 0.\\ +**pass**Let the email pass. The Junk ranking will set to 0.\\ 
-**reject** (or block) Reject the email, not going into the delivery system.\\ +**reject** (or block)Reject the email, not going into the delivery system.\\ 
-**junk** Deliver the email, with Junk rank set as 5 at least.+**junk**Deliver the email, with Junk rank set as 5 at least
 + 
 +**<color #ed1c24>Note:</color>**  
 +  * Global mail rules take priority over junk ranking and spam filtering system. So if an email passed the rules, it will not be scanned and tagged with junk ranking.\\ 
 +  * The rules are processed line by line, from top to bottom. E.g. if you want to block the entire .co top level domain but wish to pass emails from somedomain.co, the line //pass *@somedomain.co// must be inserted before the //block *.co// line. 
 + 
 +-------- 
 + 
 +===== Rules Testing ===== 
 +To check if the rule is correctly inserted, you can utilize the Test Rules Mail section to test it. Enter an email address that would respond to the rule, and click on the **Test** button. 
 + 
 +|{{:faq:email:global_mail_rules:5.png|}}| 
 + 
 +If the result is **"pass"**, it means incoming emails from this email address will be accepted and enter your Inbox.  
 + 
 +|{{:faq:email:global_mail_rules:6.png|}}| 
 + 
 +If the result is **"block"**, it means all emails that is sent from this email address will be rejected. 
 + 
 +|{{:faq:email:global_mail_rules:7.png|}}| 
 + 
 +Likewise, if the result is **"junk"**, it implies that incoming emails from this email address will be moved to the Junk folder.
  
-Mail rules take priority over junk ranking and spam filtering system. So if an email passed the rules, it will not be scanned and tagged with junk ranking.\\+|{{:faq:email:global_mail_rules:8.png|}}|
faq/email/global_mail_rules_configuration.1644895881.txt.gz · Last modified: 2022/02/15 11:31 by vikki