| Table of Contents |
|---|
2024-23-2319
| Status | |
|---|---|
|
...
|
...
|
...
The new user center is now generally available. It allows end-users the ability to manage their allow, block, and graymail list from the new dashboard experience. It also allows Signatures customers to customize their personal signatures. Look out for new user center features coming soon!
...
Please reach out to support@inky.com if you experience any issues with the new User Center or feedback@inky.com with any thoughts!
| Status | ||||
|---|---|---|---|---|
|
Found on https://app.inkyphishfence.com/settings/analysis, you’re now able to add a custom message to the First-Time Sender threat category. This is similar to our Sensitive Content policies for money, password, and covid-19 but specifically for the First-Time Sender threat category.
Including any verbiage, you’d like, as well as optional policy URLs, gives your user more context on what they should do when receiving a First-Time Sender.
...
After inputting your desired text it’ll now appear in all new First-Time Sender banners.
...
| Status | ||||
|---|---|---|---|---|
|
...
Allow and Block List Overhaul
The core concepts of the Allow and Block List are remaining the same where an admin chooses an appropriate threat category and criteria to block or allow a particular message. However, there have been a few new additions added to provide more targeted entries when appropriate.
DMARC Authentication
Allow list entries can have “only if passing DMARC” and Block list entries can have an “only if failing DMARC” option.
Allow list entries now prompt you and pre-check “Apply only to messages that pass DMARC authentication (safer option)” when applying a new Allow Entry. This option gives admins more control in which messages apply to the new entries.
...
Given the entry above, with DMARC authentication check, we have two messages below that would be evaluated against it on future deliveries. The first one has an SPF pass for securitytides.com and the second one has no authentication passes. In the future, due to the new allow list entry, the top message, with authentication will not be marked as Spam Content, while the second one will because it has no authentication.
...
On the Block Listing side, admins now have the option to “Apply only to messages that fail DMARC authentication (useful for targeting Spoofing).” Think of this as an internal INKY DMARC failure control where if you receive a spoofed email from a particular sender, domain, or IP address you can have it set block if necessary.
For example, the below entry for google.com would apply the Phishing Content banner to all messages with a FROM header google.combut contains no passing authentication. Normally, individual companies are expected to control their DMARC records to perform this type delivery but having the flexibility within INKY gives you more control.
...
To learn more please review: https://inkyops.atlassian.net/wiki/spaces/AG2/pages/2139160585/Allow+and+Block+Listing#Authentication
Match Subdomains
When adding an Allow Entry against a specific domain admins are now prompted with an option to cover all subdomains for the given domain. The below example shows the option to “Never warn about Spam Content for mail from domain securitytides.com (and subdomains).”
You’ll also be able to add subdomain matching entries against domains added directly from https://app.inkyphishfence.com/settings/allow-list, there are two new additional options: “Blocked Sender Location” and “Do not warn about Any Threats”. You can now allow these two threat categories at any point using the Add new entry option.
| Note |
|---|
Using the “Do not warn about Any Threats” is a blanket allow option that will let any message that matches the criteria set pass through INKY. It should be used for very specific purposes. We’ve also restricted this option to Super Admin only for the time being. |
...
| Status | ||||
|---|---|---|---|---|
|
Previously, Block Sender Locations only worked on M365 deployments. Now Google Workspace and Smart Host deployments can take advantage of sender location blocking the same way. Just navigate to the bottom of list.
...
Editing Allow and Block List
Allow list and block list entries are now editable. These allow list options can be set when performing allow list message actions and also when manually adding via csv input, or via the More Info > Edit interface. This can be set when manually adding via csv input or via the More Info > Edit interface.
To learn more please review: Editing Allow and Block List
Add/Remove/Edit User Level Allow and Block List
Admins can now manually add (and edit) user-specific allow and block entries as well as manually add Blocked Sender entries (for specific users or at the team level) via the csv input option.
To learn more please review: Add/Remove/Edit User Level Allow and Block List
| Status | ||
|---|---|---|
|
Found on the https://app.inkyphishfence.com/settings/allow-list and https://app.inkyphishfence.com/settings/analysis, enter in the countries you wish to block, and you’re all set!
| Status | ||||
|---|---|---|---|---|
|
Customers asked for the ability to close all details at once on the Observation Page, instead of closing each one individually. The marked icon in the picture below will now close all open detail views.
...
| Status | ||||
|---|---|---|---|---|
|
You can now search any of the Mail Group selectors instead of scrolling through the complete list.
...
| Status | ||||
|---|---|---|---|---|
|
...
Fixed bug in custom dashboard that ignored set filter mode when determining total message count
...
Fix teamid filter bug that would ignore user input while the initial team id list was loading
...
-list pages you’ll now see an Alert column indicating if an entry added to either list is too permissive or restrictive.
For example, the below entry is an Allow List for First-Time Sender that has a “None” criteria meaning it will match on every new message received and never allow another First-Time Sender threat category. With First-Time Sender completely disabled this would be seen as a very permissive allow list entry that these new warnings are meant to highlight to admins.
...