Postly Email includes safeguards that help customers send authenticated, expected email and respond to delivery problems. These protections reduce avoidable sending risks. They do not guarantee delivery, inbox placement or Gmail Primary-tab placement: the receiving provider makes those decisions.
For example, if someone unsubscribes after you schedule a newsletter, Postly checks their current subscription status before dispatching their message. Reimporting an older subscriber file must not silently subscribe them again. Keep your subscriber choices current and review sending alerts before expanding a campaign.
Protections in managed Postly Email
| Protection | What it does for you | Your responsibility |
|---|---|---|
| Domain ownership and DKIM | Requires proof of domain control and verified, enabled DKIM signing for sender verification. Signing readiness is rechecked during dispatch using a short-lived provider check. | Maintain the requested DNS records, keep signing enabled and use a recognizable sender on your verified domain. |
| Authentication diagnostics | Shows DKIM signing, a DMARC lookup at the submitted domain and the configured return-path state when you check verification. Lookup failures and possible parent-domain policies are distinguished. | Confirm the effective DMARC policy and received-message alignment with your DNS administrator. Diagnostics are a setup snapshot, not an inbox score. |
| Subscriber exclusions | Checks subscription eligibility again before dispatch. Imports cannot overwrite previous unsubscribes, bounce or complaint exclusions. | Collect permission and migrate old exclusions as well as active contacts. |
| Easy unsubscribe | Adds a visible unsubscribe link and one-click unsubscribe headers to managed campaigns. Merely loading the preference page does not change a subscription; the confirmation or one-click POST performs the opt-out. | Keep the unsubscribe controls intact and respect subscriber choices. |
| Bounce and complaint handling | Processes available provider feedback, suppresses affected addresses for permanent bounces and complaints, and can hold unhealthy sending for review. | Investigate alerts and fix list quality problems rather than trying to bypass a hold. |
| Capacity and sender controls | Applies provider capacity and approved sender controls separately from your subscription allowance. | Review current capacity and use a measured ramp instead of assuming unlimited sends means unlimited speed. |
| Feedback health checks | Holds outbound work when required feedback processing cannot establish a healthy state. | Review the displayed alert and contact support when recovery requires investigation. |
| Duplicate-send precautions | Retains sending claims and does not automatically retry an ambiguous provider result. | Keep the original campaign for investigation. Do not create a duplicate as a recovery shortcut. |
| Reporting with limits | Separates provider acceptance, reported delivery and tracked engagement. | Interpret each measure correctly and verify actual placement with controlled received-message tests. |
These controls are implemented for managed Postly Email. Availability and sending capacity still depend on your sender's setup, provider approval and current service health. Domain checks reflect their last verification; use Check DNS after changing records. Provider checks may lag a DNS or signing change.
What the reports can establish
Accepted means the sending provider accepted a request. Delivered means the receiving server accepted the message according to available feedback. Neither proves that a person saw it or that it reached their inbox.
Opens and clicks are approximate engagement signals. Privacy tools can inflate opens, blocked tracking can hide readers, and link scanners can create clicks. Gmail does not provide individual spam complaints to Amazon SES, so a zero provider-complaint count does not establish zero Gmail complaints. AWS explains this limitation.
Use your domain's mailbox-provider reputation tools and controlled inbox tests alongside Postly's reports. Postly does not claim universal inbox-placement measurement, a guaranteed delivery rate or an independently certified delivery benchmark. See sending limits and metric definitions.
What customers must do
Authenticate a domain you control, obtain permission, preserve exclusions, send useful content at an expected frequency, monitor results and respond to complaints. A correct DNS setup cannot make an unsolicited list acceptable. Follow the inbox-delivery setup and troubleshooting guide before launching or increasing a campaign.
Connected email providers
When you connect another email provider, that provider manages its sending infrastructure, audience and available reports. Postly's managed-sending protections should not be assumed to replace the connected provider's rules, suppression settings or authentication requirements. Review its documentation and verify which results it exposes through the connection.
Get help safely
Open Email Settings and review your sender checks and alerts. When contacting support, share a campaign reference, approximate send time and timezone, mailbox provider and the displayed error. Use a redacted test-message authentication result where helpful. Never share credentials or an audience export.