What is Blacklisting
Blacklisting 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 blacklisted entry is present, everything else is deemed good.
Blacklisted entries can be either forwarded (to the forward user) or dropped silently. Of course, selecting drop will mean a badly constructed regular expression may cover addresses not intended. Testing is advised!
Who can do what
JEMHC Global Configuration has a Blacklisting section that applies to all email processing. Released in v1.2.191 (JUL 25th), Blacklisting is also available to Project Admins, where the configuration is scoped to the particular project, and is in addition to Global Blacklisting. When blacklisting rules apply, removing attachments or stopping the message from being processed, the JEMHC > Auditing > item > Report contains details as to why. Auditing is available through JEMH Global Configurtion (JEMHCloud > Auditing ) and through the Project Admin screen ( Project Admin > JEMHCloud > Auditing )
Why blacklist/who to blacklist?
Common reasons to blacklist include Postmaster addresses, e.g. informing you that the recipient cannot be found (a legacy user /email address that no longer resolves). Other automated senders are also good candidates. You may also want to blacklist file attachments, a common annoyance can be email signature images being attached to created issues, attachment blacklisting allows you to remove these unwanted attachments.