How can we help?

After you create the records at your DNS provider, click Verify DNS. Postal keeps checking on its own for up to 72 hours, and DNS can take anywhere from minutes to a few hours to propagate. The dashboard shows the status of each record and, when something is wrong, the reason: a different value, a duplicate record. The most common mistake is a duplicated name: if your provider reports postal.seudominio.com.br.seudominio.com.br, remove the domain from the name. If the records are not found after 72 hours, verification fails; fix them and verify again. See the verification statuses.

No service can guarantee the inbox, but there are things to check. First, the domain: DKIM and SPF verified and, preferably, DMARC, which Gmail, Outlook and Yahoo require from anyone sending volume. The diagnostics for each email warn you when it is missing and point out what to improve, such as the text version, images with alt text and an all-caps subject. Then, the list: send only to people who asked and validate the addresses before a big campaign. See also deliverability.

Postal pauses the team's sending when permanent bounces exceed the limit of the account reputation level (3% to 5%), spam complaints exceed 0.3% or content rejected by the providers exceeds 5% of the emails sent. Before the pause, owners and administrators get an email warning, and each pause takes points off the reputation. To lift it, request a review in the dashboard or through the contact form; meanwhile, the API answers 403 sending_paused. Validate the addresses and handle the bounces before sending in volume again. Read the reputation rules.

If the bounce is permanent, meaning the address no longer exists, Postal adds the address to the suppression list automatically and it stops receiving your sends. Temporary bounces, such as a full mailbox, do not go on the list. If the person fixed their email, you can remove the address in the dashboard, under Suppressions, or through the API. Avoid removing anyone who complained or asked to leave without new consent. See the suppression list.

The URL must be HTTPS and public, and your server must respond with a 2xx status within 15 seconds. If it fails, Postal retries up to 8 times over about 27 hours. An endpoint with no successful delivery for 5 days is disabled, and owners and admins get an email. In the dashboard you can see the attempts, send a test event, resend events and reactivate the webhook. See the retries.

On the sign-in screen, click Forgot my password and enter the account email: we send a link to create a new password, which may land in your spam folder. If you sign in with Google or with a code sent by email, your account may not even have a password; sign in the same way you always do.

On the verification screen, choose Use a recovery code and enter one of the codes the dashboard showed when you turned on verification. Each code works once. After you sign in, generate new codes under My profile, Security. If you no longer have the codes, talk to us through the contact form.

The possible causes are the plan quota and a reputation pause. If the quota ran out, the campaign is paused and continues on its own when the quota renews (the day and the month are counted in UTC). On plans that allow it, you can turn on sending beyond the quota under Billing, and the overage is charged per thousand emails. If the team's sending was paused for reputation, the campaign only continues after it is restored. See the quotas.