IMAP Mailbox

Configure IMAP email ingestion as a Outpost source

Achtung

Nur für Enterprise Outpost: IMAP-Postfach-Quellen sind ausschließlich für Kunden verfügbar, die eine eigene Outpost-Instanz betreiben. Die Konfiguration erfolgt über YAML-Dateien auf dem Outpost-Server - nicht über die meinGPT-Oberfläche. Cloud-Kunden ohne eigene Outpost-Instanz können diesen Source-Typ nicht nutzen.

Runtime-Konfiguration

data_pools:
  - id: support-mailbox
    type: imap
    imap_server: "imap.example.com"
    imap_user: $IMAP_USER
    imap_password: $IMAP_PASSWORD
    imap_port: 993
    imap_use_ssl: true
    folders: "INBOX,Support"
    exclude_folders: "Spam,Trash"

Configuration Options

Field	Type	Default	Required	Description
`id`	string	-	✅	Unique identifier for the data pool
`type`	string	-	✅	Must be `imap`
`imap_server`	string	-	✅	IMAP server hostname
`imap_user`	string	-	✅	IMAP username
`imap_password`	string	-	✅	IMAP password
`imap_port`	integer	`993`	❌	IMAP port
`imap_use_ssl`	boolean	`true`	❌	Enable SSL/TLS
`imap_timeout`	integer	`60`	❌	Connection timeout in seconds
`folders`	string	null	❌	Comma-separated include folders
`exclude_folders`	string	null	❌	Comma-separated exclude folders
`overwrite_existing`	boolean	`false`	❌	Reprocess already synced emails
`strip_attachments`	boolean	`false`	❌	Keep attachment metadata only
`max_messages`	integer	null	❌	Maximum messages per run
`ssl_key_file`	string	null	❌	Optional client key file
`ssl_cert_file`	string	null	❌	Optional client cert file

Synchronization

Outpost reads messages from configured folders and stores them as local sync files.
Next sync runs continue incrementally; overwrite_existing controls reprocessing behavior.
You can cap run size via max_messages for controlled rollouts.

Setup

Create a read-only mailbox/service account
Restrict folder scope (folders and exclude_folders)
Start with a low max_messages limit
Validate sync results, then increase limits

War diese Seite hilfreich?