Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Email analysis: X-Lastline header (900122)

Last Updated: 10/22/2020Categories: InformationalTotal Views: 1085Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

When a NSX Lastline Sensor is configured in full MTA mode, it will add a custom header with the outcome of the NSX Lastline analysis to every email.

The header is called X-Lastline and can contain the following keywords:

Keyword

Description

analysis-skipped

Analysis was skipped because of whitellist match reason as below.

* sender-whitelist
* recipient-whitelist
* subject-whitelist
* attachment-filename-whitelist
* attachment-md5-whitelist
* url-whitelist

analysis-incomplete=X

The analysis was not completed. This header is associated to a value that tells you the reason for the failure:

backend-unreachable: we do not seem to be able to connect to the backend

attachment-too-large: at least one attachment was over the maximum configured file size and was skipped

attachment-upload-error: we encountered an unexpected error when attempting to upload the attachment

url-upload-error: same for URL

queue-full: we failed open because the analysis queue is full

analysis-disabled

Analysis was disabled, usually in case of fail-open scenarios (analysis queue full)

analysis-timed-out

Reached maximum amount of time to attempt to analyse the artifacts and failed open

benign

No suspicious/malicious URL or attachment was found

max-malicious-attachment-score=X

Malicious/suspicious attachments were found, with maximum score of X

max-malicious-url-score=X

Malicious/suspicious URL's were found, with maximum score of X

attachment-blocked

At least one attachment was removed from the email

suspicious-url

Suspicious/malicious URLs were found

url-blocked

At least one URL was removed from the email

message-suspicious

Used when Lastline found reasons to consider the message suspicious that go beyond the analysis of artifacts or URLs. This includes the analysis of the headers, the text parts of the message, and other factors that may affect the reputation of the message as a whole.*

* these are static heuristic checks that influence the score of the message in the UI. Currently, it is not possible to define thresholds for these messages. For inline sensors deployments, a message matching exclusively on the static heuristics will not be blocked.

Examples:

X-Lastline: benign
X-Lastline: max-malicious-attachment-score=10
X-Lastline: max-malicious-attachment-score=90 attachment-blocked
X-Lastline: suspicious-url
X-Lastline: suspicious-url url-blocked
X-Lastline: max-malicious-attachment-score=90 attachment-blocked suspicious-url url-blocked

This feature is supported starting from sensor version 709.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
修改在 vSAN 数据存储中的快照上运行的虚拟机上的存储策略规则 (70797)

KB
•
Windows 10 Wi-Fi プロファイルがインストールされない (85058)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX Detonator

VMware NSX Defender

Related Versions:

Take Our Survey

Support Assistant