...
Setting | Description |
|---|---|
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. | Reported messages will arrive to the specified recipient as an .EML inside a .ZIP file. |
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. | Reported messages will arrive to the specified recipient as an attached .EML. |
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. | The sending address for reported messages can be modified to any email address. By default, reports originate from: robot@verify.inky.com. |
Microsoft 365 Delivery through SecOps Mailbox
Microsoft’s secure by default feature may affect the way your organization whitelists INKY. Due to this change, you can whitelist INKY using Microsoft’s advanced delivery policies feature instead. Since INKY reports contain potentially malicious phishing emails that your users are reporting you must add your delivery mailbox to the advanced delivery settings.
Navigate to https://security.microsoft.com/advanceddelivery?viewid=SecOpsMailbox
Select Edit
Add the mailbox you’re delivering INKY reports to
It may take an hour or longer to fully propagate on the M365 side.
