Page Comparison

...

The Allowlisting section of JEMH looks like below:Image Removed

...

What is Blocklisting

Blocklisting is when you provide an email address or regular expression that, if the sender (from: address) matches, will be prevented from being processed.  If a blocklisted entry is present, everything else is deemed good.

...

JEMH applies Blocklisting/Allowlisting checks through a Message Filter, a pluggable component.

1. If the email has a matching global blocklisted subject, the message is marked 'bad'.

2. If there are allowlisting entries (CSV), the sender is checked against each.  A failure to match indicates 'bad'.

3. If there were no allowlisting entries, or the sender passed the allowlisting check, the blocklisting field, if present, is then used to check the sender against.  Any matches indicate 'bad'.

4. If the email has been tagged as 'bad', the JEMH Profile Configuration is consulted to determine whether the email should be dropped or forwarded to the 'forward' user.

Examples

In the screenshot above, the following have been listed as blocklist entries, meaning all others are good:

• mail-daemon@googlemail.com

• postmaster@.*

  Info

  The address field is regular expression sensitive. Note that the '*' character has special meaning in regexp, it means zero or more of the preceding character, not any character.  The dot '.' means any character except line, hence match all is '.*'. Therefore, it is best to escape dots with a backslash '\.', otherwise if left as a dot there is the chance that an unexpected address matches the regexp. For example: "jira@company.co.uk" would also allow the address "jira@companyaco.uk".

  
  

Restrict to an internal organisation only

Allowlisting to restrict inbound messages to only senders within an organisation can be achived with a simple regexp:

• .*@yourco.net

 Remember to set a catchEmail / jemhAddresseeRegexp value to match your expected 'incoming' addresses to discount them from notifications/user creation.

Related articles

...