Powered by INKY

Axiom Customers
Not authorized
You cannot modify these settings.

Summary

Markup User Reporting

Analysis

Reporting Options
Delivery

INKY can put a "Report This Email" link in every email processed to allow users to provide feedback.
User Reporting
For the most effective reporting, INKY must store an unprocessed copy of incoming mail; we offer a
Phishing Awareness Training
method of doing so that stores the mail encrypted in a way that even INKY employees cannot
decrypt until a user explicitly reports the email.
Allow List
Save raw message data, encrypted at rest, to allow faster and more actionable response
Block List to feedback.

Advanced Block List

Enterprise 3 days

Tools
Always send raw messages (if available) to INKY for analysis (i.e., do not allow end
users to opt-out for specific messages)

Allow end users the option to authenticate on the Report This Email page to unlock
enhanced reporting capabilities. If signed in with Microsoft or Google as the recipient of
a reported message, a user can choose to have reported spam or phish automatically
deleted from their mailbox. They can also choose to automatically block (i.e., send to
quarantine) all future mail from unwanted senders. These Block Sender settings apply on
a per-user basis and can be viewed on the Block List by checking the "User-Specific" box.
A user can review their settings on the User Dashboard.

If a user is authenticated, allow end users to maintain a personal allow list for a
limited set of threat categories. If the user labels a message as safe, they will be
presented
Note: You with allow
are currently actions settings
configuring for the following categories:
for the entire AxiomSpam Content,
Customers Reported
organization,
Spam
which may (can be
affect up customized by request
to 1 descendant team. to INKY support). The actions apply on a per-
user basis and can be viewed on the Allow List by checking the "User-Specific" box.
A user can review their settings on the User Dashboard.
Revert Changes Save Changes

Require end users to authenticate on the Report This Email page in order to submit
reports.

Automatically attempt to authenticate end users using the platform for which
Directory API access is granted.

Replace the standard "Report This Email" link with multiple context-sensitive quick-
Back to Top
action links for more targeted reporting options.
 Automatically treat the user as authenticated when clicking a quick-action link in a
single-recipient message.

Custom Reporting Email Notifications

By default, user reports are sent to INKY for further analysis. These settings control where
notification emails for each type of report can optionally be sent for your own internal review. Note:
Each field can be a comma-separated list of email addresses (e.g., "user@[Link],
user2@[Link]"). Leave a field blank to not send any custom notifications about a specific type
of report.

Safe

Spam

Phish

Attach original raw message inside a .zip (application/zip) file. By default, the original
mail will be attached as an RFC822-formatted .txt (text/plain) file. This is due to the fact
that some mail systems automatically process/reformat incoming .eml attachments.

Attach original raw message as a .eml (message/rfc822) file. By default, the original mail
will be attached as an RFC822-formatted .txt (text/plain) file. This is due to the fact that
some mail systems automatically process/reformat incoming .eml attachments.

Set the From: header in the notification email to match the contact email address
specified on the report page (default is an INKY address). This option will cause INKY to
"spoof" mail from your reporting team member and should only be used if the
notifications are going into a system that expects this. Otherwise, the mail may get
blocked due to suspicion of phishing.

Use a unique subject in the notification email (identifies INKY result, user label, and a
unique report id).