How to prevent e2a from processing spam emails?


Spam Emails

Email-to-Anything (e2a) creates and updates Target objects from the emails received in Salesforce. At the backend, there is a redirection set up at the customer mailboxes from where emails are getting redirected to Salesforce. At times marketing emails or social media emails get caught in the redirection and are sent to Salesforce. Such emails are termed as spam emails which should not be processed by e2a. 

e2a Action Rules 

To prevent e2a from processing such spam emails, there is a functionality in e2a emails rules named Action Rules that can be used. In the Action Rules certain email addresses, domains or keywords can be configured so when they are found in any email, such emails can be discarded.

Scenario

The requirement is that whenever an email is received and it is from marketing@test.com, it should be dropped and should not be processed for creation or update of the Target Object. 

Setting up the Action Rules

To set up an Action Rule to discard emails from marketing@test.com please follow the steps below: 

 

  1. Go to the e2a email rules tab and click on the e2a email rule you would like to set up the Action Rule in 
  2. Scroll down to the Action Rules - Pre-process section and click on the New button
  3. Add Processing Order (a number greater than 0) 
  4. Select Pattern Matched from the Trigger When drop-down
  5. Add the Pattern you need to detect in the email [e.g. marketing@test.com] in the Match pattern field
  6. Select the part of the email where you are looking for the pattern [e.g. From Address] from the Search In drop-down
  7. Select what action you would like to perform when a pattern is matched in the email [e.g. Drop Email] from the Action Type drop-down
  8. Click on Save button

 

Please contact us at support@ortooapps.com for any questions.

Was this information helpful?

The page cannot be found

The page you are looking for might have been removed, had its name changed, or is temporarily unavailable. Please make sure you spelled the page name correctly or use the search box.

Support