POP3 integration
POP3 is supported through the Mach5 connector framework. This page lists every supported operation and where it can be used.
Connection
- Connector kind:
pop3 - Configuration:
host, optionalport,tls,username,password_secret_ref, andmax_message_bytes.
How to use this integration
For Axon concepts, safety classes, idempotency, and outcomes, see Axon workflows.
Axon
Axon is the controlled action path for connector reads, enrichments, and side effects. Use Axon when a workflow needs to call POP3 directly, enrich an investigation, or take an approved action. Invoke the connector kind pop3 with the operation name and JSON input.
connector: pop3
operation: list_messages
input: { ... }
Ingest Pipelines
Use ingest pipelines for operations exposed as sources. These operations can checkpoint and stream records into Mach5-managed data.
source.connector: pop3
source.operation: mailbox_source
source.config: { ... }
SQL
Use SQL for read operations exposed as table or scalar functions. Query the connector operation with JSON input and join the result with Mach5 data.
SELECT *
FROM connector_table('pop3', 'list_messages', JSON '{}');
Supported operations
| Operation | What it does | Axon | Ingest Pipelines | SQL |
|---|---|---|---|---|
validate | Validate POP3 server reachability and auth settings. | — | — | — |
list_messages | List POP3 message metadata. | Yes | — | Yes |
fetch_message | Fetch POP3 message raw/body with byte limits. | Yes | — | Yes |
delete_message | Delete a POP3 message explicitly. | Yes | — | — |
parse_message | Parse a raw RFC 5322/MIME message without network side effects. | Yes | — | Yes |
mailbox_source | Durable POP3 ingest source using UIDL entity tracking. | — | Yes | — |