Mail logs

Mail logs is the record of every email Reynt actually sent to your customers and owners. When a guest says “I never got the confirmation,” this is where you check what happened. Open it from Settings → Mail Logs.

What’s recorded

Each row is one outgoing email, with:

• Date it was sent.
• Type — which email it was (booking confirmed, payment instructions, and so on).
• Recipient — the address it went to.
• Sender — whether it went through your own server or the platform mailer (Reynt’s fallback, used when you have no mail server configured).
• Subject.
• Status.
• Error message, when a send failed.

Filter the list by type or status to narrow things down.

Delivery statuses

• Sent — Reynt handed the email to the mail server.
• Delivered — the receiving server accepted it for the recipient.
• Bounced — the recipient’s server rejected it (bad address, mailbox full, blocked). It did not arrive.
• Failed — the send itself didn’t go through.

Delivery tracking depends on your mail transport. On the platform mailer it is always on. On your own Brevo or Mailjet account it needs a one-time setup step — see below. With SMTP there is nothing to observe: the protocol reports nothing back once the message is handed over, so those emails stay at Sent even when they arrive.

Turning on delivery tracking for your own mail account

If you send through your own Brevo or Mailjet account, that account has to tell Reynt what happened to each email. Setting it up takes a minute:

1. Go to Settings → Emails → Mail server and make sure your provider is configured and enabled.
2. Under Delivery tracking, click Enable delivery tracking and copy the URL that appears.
3. Paste it into your provider and select the events below.

Brevo

Settings → Webhooks → Add a webhook, paste the URL, and tick exactly these:

delivered · hard_bounce · soft_bounce · blocked · spam · invalid_email · deferred · error

delivered is what turns an email from Sent into Delivered; the rest are the ways a send can fail.

Mailjet

Account Settings → Event notifications (Event API). Mailjet takes one entry per event, so add four, each with the same URL:

sent · bounce · spam · blocked

sent is the one people leave out, and it is the important one. Mailjet has no separate delivered event — its sent (German: Gesendet) means the recipient’s server accepted the email, and that is what turns Sent into Delivered. Without it you would only ever see failures, never confirmations.

Also tick Group events (“Events zusammenfassen”). Mailjet then batches events instead of sending one request per event, which Reynt handles either way.

Both

Leave opens, clicks and unsubscribes switched off. Reynt discards them, so they only cost requests against your webhook.

From then on, mail logs show the real delivery status instead of stopping at Sent, and a bounce shows the reason the receiving server gave.

The URL contains a secret — treat it like a password. If it ever leaks, use Rotate secret to invalidate it, then paste the new URL into your provider. Tracking stays down in between, so do the two steps together.

Debugging delivery

A typical “missing email” check:

1. Find the email by recipient and date. No row at all means it was never sent — check whether the notification is turned off in Notifications, or whether it’s still waiting in the Mail Outbox.
2. Bounced or Failed — read the error message; usually a wrong address or a mailbox problem. Fix the customer’s email and resend from the booking.
3. Delivered but the guest can’t find it — it likely landed in spam; ask them to check.

If you’re testing against imported data, note that a redirected email shows the intended recipient as a [→ guest@example.com] prefix on the subject.

Relationship to the Inbox

Guest-facing emails also appear on the booking’s timeline in the Inbox, where each shows the same delivery badge (delivered, sent, failed, bounced). Mail logs is the complete technical record of every outgoing email; the inbox shows the guest-facing ones in the context of the conversation they belong to.