Alternatively, you can log in to the user control panel using the respective link while logged to Webmail.<\/p>\n

After logging in and click on\u00a0Filtering<\/strong>, on the top bar.<\/p>\n

Change the\u00a0Detect Forged From<\/strong> the pull-down menu to Yes<\/strong>\u00a0and click on\u00a0Update settings<\/strong>.<\/p>\n

Afterward, click on Home<\/strong>\u00a0in the top bar, followed by the\u00a0Delivery Rules<\/strong>\u00a0icon.<\/p>\n

You will notice a new rule entitled “DetectForgedFrom”. Click on the\u00a0pencil icon<\/strong>\u00a0next to it, to edit it. This is what it looks like:<\/p>\n

\nWhat the rule does is check if the user did NOT authenticate using our SMTP (notice that the Negate column for the first condition is set to Yes) and uses your address as a FROM address and in such cases, it moves such e-mails to your spam folder.<\/p>\n

This rule can currently be created only on the user level, however, if you decide to implement it for all your users, contact us, and we will enable it automatically for everyone.<\/p>\n

One possibility is to change the folder where such e-mails are sent to. This will let you tweak the rule in an easier way. First of all, create a folder in WebMail or an e-mail client using IMAP, such as “Forged”. Then, simply click on the\u00a0minus sign icon<\/strong>\u00a0next to the Spam folder action (shown above), click on\u00a0Deliver to folder<\/strong>\u00a0button and choose your “Forged” folder.<\/p>\n

Notice that there’s another rule entitled “SpamDelivery”, responsible for moving spams to your spam folder and it comes before the Forged From rule. For that reason, forged e-mails detected as spam will be moved to your spam folder. If you decide to create a separate folder, such as the suggested “Forged folder”, consider clicking on the up arrow<\/strong>\u00a0next to the Forged From rule and moving this rule above the SpamDelivery rule. This way, all forged e-mails will be sent to your “Forged” folder, avoiding clutter in your spam folder.<\/p>\n

Besides catching forged e-mails, this rule may catch legitimate messages that were sent as being you, from some other SMTP server. For example, some website form or application that sends emails using your e-mail address in the From header.<\/p>\n

You can tweak the rule by denying such cases, so the filter does not catch such cases.<\/p>\n

For example, let’s say you receive legitimate e-mails that come From your email and to your e-mail address, sent from a remote server called otherhost.domain.com, which is the hostname of the system that sends our server the e-mail, shown in the e-mail header. What we do is click on\u00a0New And Condition<\/strong>. This new condition should have the\u00a0Match field<\/strong>\u00a0menu set to\u00a0Received<\/strong>\u00a0and\u00a0Negate Match<\/strong>\u00a0set to\u00a0Yes<\/strong>. In the\u00a0term<\/strong>\u00a0field, type in otherhost.domain.com and click on\u00a0Add Condition<\/strong>. Notice that rule is not set to Disabled. Click on the\u00a0Disabled<\/strong> button to enable the rule and click on the\u00a0Save rule<\/strong>. What we did, is inform the system to NOT run the rule for e-mails that come from otherhost.domain.com.<\/p>\n

This is how the rule now looks:<\/p>\n

\nLet’s consider one last scenario. Consider that you want to avoid forged e-mails coming from ANY account of your domain, not just your own account.<\/p>\n

In such case, click on the\u00a0minus sign icon<\/strong>\u00a0next to the FROM condition and add a\u00a0New And Condition<\/strong>\u00a0of the\u00a0type FROM,<\/strong>\u00a0and for\u00a0Term<\/strong>, type in\u00a0your domain<\/strong>, in this case, “emailarray.com” (without quotes).<\/p>\n

It might give you a bit of work to fine-tune the rule so that it is near perfect, but many customers and companies consider it a good idea.<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","format":"standard","manualknowledgebasecat":[549],"manual_kb_tag":[556],"_links":{"self":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb\/3460"}],"collection":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb"}],"about":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/types\/manual_kb"}],"author":[{"embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/comments?post=3460"}],"version-history":[{"count":1,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb\/3460\/revisions"}],"predecessor-version":[{"id":3463,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb\/3460\/revisions\/3463"}],"wp:attachment":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/media?parent=3460"}],"wp:term":[{"taxonomy":"manualknowledgebasecat","embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manualknowledgebasecat?post=3460"},{"taxonomy":"manual_kb_tag","embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb_tag?post=3460"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}