Secure Email
Secure Email
Breadcrumbs

Secure Email – Status & Delivery Stages

This document explains the lifecycle of a Secure Email record in Salesforce, including status updates, delivery outcomes, and batch processes.

Stages of Secure Email

  1. Created

    • The Secure Email record is created in Salesforce.

    • This stage represents that the request has been logged but not yet processed.

  1. Processing

    • An API call is made to Paubox to initiate email delivery.

    • A background process runs after 1 minute to check the delivery status of the email.

  1. Partially Delivered

    • If the email is successfully delivered to few of the recipients:

      • Email Status = Partially Delivered

      • Delivery Status = Partially Delivered

    • Individual Delivery Status for all the recipients will be stored on the Email Recipients record related to the Secure Email Message record.

  1. Delivered

    • If the email is successfully delivered:

      • Email Status = Delivered

      • Delivery Status = Delivered

    • If the recipient opens the email during this time:

      • Opened Status = Opened

      • Delivered Time and Opened Time fields are updated.

  1. Failed

    • Email delivery failed due to an error or bounce.

      • Delivery Status contains the failure reason.

    • Failure reasons may include:

      • Soft bounce (temporary delivery issue).

      • Hard bounce (permanent issue such as invalid email).

      • Internal error.

Scheduled Batch Process

  • A batch job runs every N minutes to monitor Secure Email records. Default is 2 and is configurable.

  • It checks for:

    • Emails stuck in Processing.

    • Emails Delivered but not opened for the past N days.

  • The value of N is configurable through Custom Settings, allowing organizations to fine-tune monitoring intervals.

Click here to find more details on the Batch.

Delivery Status Values

Secure Email can return one of the following delivery statuses:

Status

Meaning

processing

Email is in progress and being handled by the system.

TLS not offered, sending via Secure Portal

Recipient’s mail server does not support TLS; email sent via secure portal.

soft bounced

Temporary delivery failure (e.g., server unavailable).

soft bounced – mailbox full

Recipient’s mailbox is full; delivery could not be completed.

hard bounced

Permanent delivery failure (invalid email or domain issue).

Internal error. Please check back later.

Paubox encountered an internal issue; retry later.

delivered

Email successfully delivered to the recipient.

delivered via secure portal

Delivered securely via Paubox secure portal.

Summary

  • Secure Email follows a clear Created → Processing → Delivered/Failed lifecycle.

  • Statuses are auto-updated via background jobs and batch monitoring.

  • Delivery outcomes (Delivered, Bounced, Secure Portal) are tracked for compliance and auditing.

  • Organizations can configure retry/monitoring intervals using Custom Settings.

For assistance or troubleshooting, please contact:
📧 solutions@cloudmaveninc.com