Email logs
Audit outbound email sends and SMTP errors.
Open Channel → Email → Logs.
What this page is for
Paginated outbound send history for email only: log ID, sender, recipient address, subject and body preview, delivery status, and timestamp.
This is the same data as Logs → History, filtered to the email channel. Use it when you need to trace a specific email send without mixing in WhatsApp or Telegram rows.
Sample data shown.
Search and filter
Search is field-based — click the search area first, pick which column to search, then type your query.
| Step | What happens |
|---|---|
| 1. Click search | A Search in popup opens — you must choose a field before typing |
| 2. Pick a field | Recipient, Log ID, or Message |
| 3. Type | After a short debounce, Kirisan sends the query to the server and reloads matching rows |
After you pick a field, the search bar shows the field name on the left (for example Recipient ▼). Click it to switch fields — changing the field clears the query and reloads the list.
On the same row as search (to the right):
| Filter | What it does |
|---|---|
| Sender | Limits rows to one configured email sender — pick All senders or a specific from address |
| Status | All statuses, Sent, or Failed |
Sender and Status apply together and also apply to Recipient / Message window search and Continue search steps.
Sender filter
Open the Sender dropdown to pick a sending address. The list shows each sender as from name · from address (same labels as on Emails).
When you have many senders, use the search box inside the dropdown — it matches the display name, from address, or token. All senders stays pinned at the top.
| Situation | What you see in Sender column |
|---|---|
| Send logged after sender tracking shipped | From name + address (two lines — name on top, address below) |
| Older send before sender was stored | — (empty) — use recipient, message, or date instead |
Search fields
| Search field | Matches | Minimum length |
|---|---|---|
| Recipient | Email addresses that contain your query (for example acme.com matches budi@acme.com) | 3 characters |
| Log ID | The full, exact numeric ID from the ID column — not a partial match (for example 91842, not 918) | Full ID only |
| Message | Subject or plain-text body that contains your query (HTML is stripped for matching) | 3 characters |
Recipient and Message search scan the most recent 1,000 sends per step (respecting your Sender and Status filters). When older sends remain, Kirisan shows Continue search — same behavior for both fields.
Log ID is different: enter the complete ID exactly as shown in the table. Kirisan does not match prefixes or fragments.
If you type fewer than three characters for Recipient or Message, Kirisan waits until the minimum is met and shows a short hint under the search bar.
Window search and Continue search
Recipient and Message search do not scan your entire log at once. Each step the server reads the most recent 1,000 sends (respecting Sender, Status, and the active search field), then returns rows that contain your query.
When Kirisan finishes a step and older sends still exist, a bar appears below the table with Continue search:
| Situation | What you see |
|---|---|
| Matches in this 1,000 | Matching rows in the table; bar explains how many were found and offers Continue search if more history remains |
| No matches, older rows exist | Empty table message for that batch; Continue search scans the next 1,000 |
| No matches, end of log | No messages found. — nothing left to scan |
Click Continue search as many times as you need. New matches from later steps are added to the table. You decide when to stop.
Log ID search uses an index and returns results immediately — it does not use Continue search.
Log table
Each row is one outbound email send:
| Column | Meaning |
|---|---|
| ID | Unique send row ID — copy the full number for Log ID search (exact match only) |
| Sender | Which email sender sent the message (from name + from address when configured on Emails) |
| Recipient | Destination email address |
| Preview | Subject line (bold) and a truncated plain-text snippet from the HTML body (envelope icon) — no markup in the list |
| Status | sent (green) or failed (red) |
| Date | When the send was recorded |
Rows are clickable — Kirisan opens a full Email preview with subject and rendered HTML.
Email preview
Click any row to open the preview popup. The HTML body renders at full width inside a wide dialog (scroll vertically for long templates):
Close the preview with the × button, by clicking outside the dialog, or with Escape.
Pagination
When you are not using Recipient or Message window search, pagination below the table appears for long lists (for example Showing 1–25 of 248 · Page 1 / 10 with Previous and Next).
During Recipient or Message search, results from each Continue search step accumulate in the table instead of using page numbers.
Tips
- Run multiple from addresses? Filter Sender first, then search Recipient or Message — you only scan sends from that sender.
- Start with Recipient when a customer asks “did you email my address?” — use at least three characters anywhere in the address (for example
@acme.comorbudi). - Use Log ID when you have the full send ID from the table, an API response, or support — partial IDs do not work.
- Use Message when you remember part of the subject or body text — click Continue search to look further back in time.
- Filter Failed and pair with Sender or Recipient search to find failed sends for a specific campaign or address.
- Cross-channel history lives under Logs → History — see Message logs.
- For deliverability rates and bounced vs failed, see Statistics and Suppression.
Related
- Message logs — History, per-channel logs, webhooks
- Emails — configured from addresses used in the Sender filter
- Statistics — deliverability rates and domain breakdown
- Suppression — blocked recipient addresses
- Templates — reusable HTML used in sends