Help Center / Settings and administration /
Email log
The email log records every outgoing email sent from your workspace: invoice emails, proposal notifications, contract links, task reminders, scheduler confirmations, digest emails, and automation emails. Each entry shows who it went to, whether it was delivered, whether the recipient opened it, and any delivery errors that came back. Log entries are kept for six months.
Opening the email log
Go to Settings > Management > Email logs. The page lists every email sent from your workspace in reverse chronological order, with columns for recipient, status, type, sender, send method, errors, opens, and sent time.
If no emails have been sent yet, the page shows "No emails sent yet". That state is expected in a fresh workspace or when the log has just been cleaned past its retention window.
What each entry shows
| Column | What it shows |
|---|---|
| Recipient | The email address the message was addressed to. |
| Status | Where the email is in the delivery lifecycle: Sent, Delivered, Opened, Clicked, Bounced, Complained, Send failed, or Failed. |
| Type | What kind of email it was (invoice, proposal, contract, task notification, digest, automation email, etc.). |
| From | The address the email was sent from. Either a Plutio-managed address or your own connected email. |
| Error | The error message returned by the mail server when delivery fails. Empty for successful sends. |
| Send method | Plutio (Plutio's managed sending), Custom email (your own connected email or SMTP), or Test (test sends from the settings page). |
| Opened at | The first time the recipient opened the email (tracked via the open-tracking pixel). Empty if not opened. |
| Sent at | When the email left Plutio. |
Status values
Status is the most important column when something has gone wrong. Each status reflects a real webhook event from the mail server.
| Status | What it means |
|---|---|
| Sent | Plutio handed the email to the sending provider. No delivery confirmation yet. |
| Delivered | The recipient's mail server accepted the message. |
| Opened | The recipient opened the email (tracked with an invisible pixel). |
| Clicked | The recipient clicked a tracked link inside the email. |
| Bounced | The recipient's server rejected the email. Usually an invalid address, a full mailbox, or a blocked domain. |
| Complained | The recipient marked the email as spam. Keep an eye on this, because repeated complaints affect sender reputation. |
| Send failed | Plutio couldn't hand the email off to the sending provider. Check the Error column. |
| Failed | A downstream failure reported by the mail server after send. |
Send methods
Plutio supports three sending paths. Each row in the log makes clear which one was used.
- Plutio: Plutio's managed email sending. Used by default and for any notification where you haven't connected a custom address.
- Custom email: your own connected email (Google, Outlook, or SMTP). Set this up in Settings > Email > Sending email. Emails sent this way leave your mailbox, not Plutio's, so delivery depends entirely on your provider. Plutio does not see what happens after the hand-off, only the initial send or error.
- Test: the test button in the email settings page, used to verify that a sending configuration actually works.
When a custom email is connected, you'll see a banner in the log reminding you that outgoing emails go through your own provider, and that SPF and DKIM on your domain determine whether they reach your clients.
Resending an email
Any email in the log can be re-sent with one click.
- Open Settings > Management > Email logs.
- Find the email and click Resend.
- Plutio generates a fresh send with the same content and recipient, and records a new entry in the log.
Resending is the quickest fix for transient errors (temporary connection refused, timeouts). For persistent errors, you'll need to fix the underlying cause first. See the troubleshooting section below.
Troubleshooting delivery errors
When a send fails with a custom email, Plutio surfaces the SMTP error code in the Error column. The table below translates the common codes into what to check.
| Error code | What to check |
|---|---|
| ENOTFOUND | The recipient's email address has an invalid domain. Double-check the email address for typos. |
| ECONNREFUSED | Your email server refused the connection. Check that your SMTP host and port are correct in your email settings. |
| ETIMEDOUT | Your email server took too long to respond. Usually temporary, so try resending. If it keeps happening, check your SMTP settings. |
| ECONNRESET | The connection to your email server was interrupted. Usually temporary, so try resending. |
| EAUTH | Your email login details were rejected. Go to Settings > Email > Sending email and update your username or password. |
| ESOCKET | Could not connect to your email server. Check that your SMTP host, port, and SSL settings are correct. |
For Plutio-sent emails, hard bounces usually mean the address is invalid or the recipient's mail server blocked the domain. Spam complaints usually mean the recipient didn't expect the email, so check that you're using the right template and the right address.
Retention: six months
Email log entries are kept for six months. A daily cleanup job runs at 03:00 UTC and permanently removes anything older than that. Resends, open events, and click events update the original entry while it's still within the retention window.
The email log lives on Plutio's logs database, the same separate database that stores the activity log. That keeps large log scans away from the main workspace database.
