• Plugin version: v3.2.0
• Released on: 2021-12-06
• Changelog

For other versions, see theoverview list.

To learn more about Logstash, see theLogstash Reference.

For questions about the plugin, open a topic in theDiscuss forums. For bugs or feature requests, open an issue inGithub. For the list of Elastic supported plugins, please consult theElastic Support Matrix.

Read mails from IMAP server

Periodically scan an IMAP folder (INBOX by default) and move any read messages to the trash.

The plugin includes sensible defaults that change based onECS compatibility mode. When ECS compatibility is disabled, mail headers and attachments are targeted at the root level. When targeting an ECS version, headers and attachments target@metadata sub-fields unless configured otherwise in order to avoid conflict with ECS fields. Seeheaders_target, andattachments_target.

This plugin supports the following configuration options plus theCommon options described later.

Also seeCommon options for a list of options supported by all input plugins.

• Value type isstring

• Default value depends on whetherecs_compatibility is enabled:

  • ECS Compatibility disabled:"[attachments]"
  • ECS Compatibility enabled: `"[@metadata][input][imap][attachments]"

The name of the field under which mail attachments information will be added, ifsave_attachments is set.

• Value type isnumber
• Default value is300

• Value type isstring
• Default value is"text/plain"

For multipart messages, use the first part that has this content-type as the event message.

• Value type isboolean
• Default value isfalse

• Value type isstring

• Supported values are:

  • disabled: does not use ECS-compatible field names (for example,From header field is added to the event)
  • v1,v8: avoids field names that might conflict with Elastic Common Schema (for example, theFrom header is added as metadata)

• Default value depends on which version of Logstash is running:

  • When Logstash provides apipeline.ecs_compatibility setting, its value is used as the default
  • Otherwise, the default value isdisabled.

Controls this plugin’s compatibility with the [Elastic Common Schema (ECS)][Elastic Common Schema (ECS)](([^:]+)://reference/index.md)). The value of this setting affects thedefault value ofheaders_target andattachments_target.

• Value type isboolean
• Default value isfalse

• Value type isnumber
• Default value is50

• Value type isstring
• Default value is"INBOX"

• Value type isstring

• Default value depends on whetherecs_compatibility is enabled:

  • ECS Compatibility disabled: no default value (for example, the subject header is stored under the"subject" name)
  • ECS Compatibility enabled:"[@metadata][input][imap][headers]"

The name of the field under which mail headers will be added.

Settingheaders_target => '' skips headers processing and no header is added to the event. Except the date header, if present, which is always used as the event’s@timestamp.

• This is a required setting.
• Value type isstring
• There is no default value for this setting.

• Value type isboolean
• Default value istrue

• This is a required setting.
• Value type ispassword
• There is no default value for this setting.

• Value type isnumber
• There is no default value for this setting.

• Value type isboolean
• Default value isfalse

When set to true the content of attachments will be included in theattachments.data field.

• Value type isboolean
• Default value istrue

• Value type isstring
• There is no default value for this setting.

Path of the sincedb database file (keeps track of the UID of the last processed mail) that will be written to disk. The default will write sincedb file to<path.data>/plugins/inputs/imap directory. NOTE: it must be a file path and not a directory path.

• Value type isboolean
• Default value isfalse

• Value type isboolean
• Default value isfalse

When the IMAP input plugin connects to the mailbox for the first time and the UID of the last processed mail is not yet known, the unread mails are first downloaded and the UID of the last processed mail is saved. From this point on, ifuid_tracking is set totrue, all new mail will be downloaded regardless of whether they are marked as read or unread. This allows users or other services to use the mailbox simultaneously with the IMAP input plugin. UID of the last processed mail is always saved regardles of theuid_tracking value, so you can switch its value as needed. In transition from the previous IMAP input plugin version, first process at least one mail withuid_tracking set tofalse to save the UID of the last processed mail and then switchuid_tracking totrue.

• This is a required setting.
• Value type isstring
• There is no default value for this setting.

• Value type isboolean
• Default value istrue

These configuration options are supported by all input plugins:

• Value type ishash
• Default value is{}

Add a field to an event

• Value type iscodec
• Default value is"plain"

The codec used for input data. Input codecs are a convenient method for decoding your data before it enters the input, without needing a separate filter in your Logstash pipeline.

• Value type isboolean
• Default value istrue

Disable or enable metric logging for this specific plugin instance by default we record all the metrics we can, but you can disable metrics collection for a specific plugin.

• Value type isstring
• There is no default value for this setting.

Add a uniqueID to the plugin configuration. If no ID is specified, Logstash will generate one. It is strongly recommended to set this ID in your configuration. This is particularly useful when you have two or more plugins of the same type, for example, if you have 2 imap inputs. Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.

input {  imap {    id => "my_plugin_id"  }}

• Value type isarray
• There is no default value for this setting.

Add any number of arbitrary tags to your event.

This can help with processing later.

• Value type isstring
• There is no default value for this setting.

Add atype field to all events handled by this input.

Types are used mainly for filter activation.

The type is stored as part of the event itself, so you can also use the type to search for it in Kibana.

If you try to set a type on an event that already has one (for example when you send an event from a shipper to an indexer) then a new input will not override the existing type. A type set at the shipper stays with that event for its life even when sent to another Logstash server.