Skip to main content
--tail opens an interactive terminal UI on top of the log endpoints. Status updates in place as messages flow. 
jetemail outbound logs --tail
jetemail inbound logs --tail
jetemail inbound account logs --tail

​
Filters work in tail mode too

Anything you can filter the static log views by also works while tailing: 
jetemail outbound logs --tail --action BOUNCED_HARD --poll-secs 10
jetemail inbound logs --tail --logtype spam
jetemail inbound account logs --tail --logtype quarantine

​
Keyboard shortcuts

KeyAction
EnterOpen a structured detail view for the selected row
rShow the raw event JSON
SpacePause / resume
/Filter visible rows
qQuit

​
Buffer & polling

FlagDescription
--poll-secs <n>How often to fetch new entries. Default 5. Raise it for long sessions.
--buffer <n>Maximum entries kept in memory. Default 500.
jetemail outbound logs --tail --poll-secs 10 --buffer 2000

​
Look-back

By default only entries logged after you launched the command are shown. To include older entries that are already in the API’s buffer, pass --date-from: 
# include everything in the buffer
jetemail outbound logs --tail --date-from 0

# include the last hour
jetemail outbound logs --tail --date-from $(( $(date +%s) - 3600 ))

​
Three sources

CommandEndpointScope
jetemail outbound logs --tail/outbound/logsAll sends across your account.
jetemail inbound logs --tail/inbound/logsInbound mail (can scope with --uuid <domain>).
jetemail inbound account logs --tail/inbound/account/logsAccount-wide inbound activity, including allow/blocklist hits.
All three share the same keyboard shortcuts and buffer / poll flags.

​
When not to use tail

--tail is interactive and intended for a real terminal. For scripting, CI, or jq pipelines, drop --tail and use a one-shot jetemail outbound logs --limit N (paged) instead.