These fall under the "soft bounce" category and usually resolve automatically. Raklet will retry delivery for up to 24 hours.

These indicate the message cannot be delivered and won't be retried. Raklet marks the address as a hard bounce and removes it from future sends.

Raklet supports authentication standards like SPF, DKIM, and DMARC to prevent spoofing and improve deliverability.

Failures in these records may result in delivery errors.

Since all Raklet emails are sent via Amazon SES, you must add include:amazonses.com to your SPF record. Example: v=spf1 include:amazonses.com ~all

DMARC – Aligns SPF/DKIM with the sender domain
Use mxtoolbox.com or your DNS provider to check records.
​If your DMARC policy is set to quarantine, you must configure Verify Your Email from Domain in Raklet to ensure proper delivery.

To make sure you receive all important Raklet communications, including membership updates, announcements, password reset emails, and event confirmations, we recommend adding Raklet’s sending email addresses to your email account’s whitelist (safe senders list).

Whitelisting helps prevent legitimate messages from being delayed, filtered, or marked as spam by your email provider and can reduce both soft and hard bounce issues caused by strict server or spam policies.

Using a custom email sender name helps recipients instantly recognize your organization and increases trust in your emails. Messages sent from a familiar sender are less likely to be ignored, marked as spam, or rejected by recipient servers.

A clearly identifiable sender name also improves deliverability for important communications such as membership notifications, event confirmations, and password reset emails.

We recommend configuring a custom email sender name alongside proper domain authentication (SPF, DKIM, and DMARC) for the best delivery results.

💬 Contact support if you’re repeatedly seeing the same errors.