The right delivery route
Rules based on purpose, sender and CRM outbound account determine the connection. Fallback routes must be authorised for the same identity.
Module · AgenticUltimateEvery important email in view.
Every important email in view.
Delivery under control.
Reliable email delivery in SuiteCRM 8: routing, delivery status, error handling and diagnostics — matched to your infrastructure.
SuiteSMTPThe workflow at a glance
- 01CRM delivery request
- 02Check sender & attachments
- 03Authorised delivery service
- 04Record transport acceptance
Schematic illustration · Part of the CRM process
✓ Intelligent routing✓ Controlled retries✓ Required attachment checks✓ Health Center integration
Turn the black box into a clear process.
Your team can see what has been sent, what is waiting and where a decision is needed.
A controlled queue
Persisted delivery requests and coordinated background processes reduce competing attempts. Uncertain handovers are handled separately.
Complete messages
A missing required attachment or an integrity issue blocks delivery. Operational logs contain sanitised information rather than credentials.
Connect a delivery service in five steps.
Set up under Administration → Email delivery.
Choose the purpose
System messages, workflows and business modules receive appropriate delivery rules.
Configure the service
Set up SMTP with TLS or a supported API adapter. The adapter architecture is designed for services such as Amazon SES, Postmark, Brevo and SendGrid; we clarify the exact scope in the demo.
Authorise senders
Define permitted From addresses, display names and Reply-To settings.
Diagnose the connection
Check configuration, networking, TLS and authentication separately. A test email confirms transport acceptance.
Activate and protect
Activate the tested connection and configure an authorised fallback with a limited retry budget.
A status that means something.
Transport acceptance, delivery and opening are different events. Delivery information depends on the feedback available from the provider.
| State | Meaning | Next step |
|---|---|---|
| Queued | Request saved in the outbox | Wait for processing |
| Sending | A background process is handling the request | Monitor the handover |
| Accepted | The mail server has accepted the message | Evaluate provider feedback |
| Retry scheduled | Temporary error | Retry after a delay |
| Unknown | Handover not conclusively confirmed after a timeout | Reconcile or review manually; do not resend blindly |
| Blocked | Required attachment, sender or approval missing | Resolve the cause |
| Failed | Permanent error or exhausted attempt budget | Review the error and decide the next action |
When something fails, the right decision matters.
A timeout does not prove that a message was never sent.
Reconcile uncertain handovers
Provider identifiers and available feedback help clarify the outcome. If it remains unresolved, the request stays on hold for review.
Preserve sender identity
Fallback routes use only previously authorised senders. DNS and provider configuration remain part of setup.
Protect confidential content
Credentials are protected, logs sanitised and temporary content removed according to defined rules. Previews are isolated.
A delivery foundation for your suite.
Delivery status remains separate from a document's business state.
Invoices & signatures
Send approved document versions and valid signature invitations. A delivery issue changes neither an invoice's finalisation nor its payment status.
SuiteOffload
Retrieve attachments from the file register. Deletion holds and integrity checks protect files during delivery.
Health Center
Monitor queues, background processes and connections. Administrators can see where attention is required.
Frequently asked questions
Good to know about SuiteSMTP.
Does SuiteSMTP replace our mailboxes?
No. It focuses on outbound SMTP and API delivery. Mailboxes and incoming email remain separate.
Can employees use personal senders?
Personal and group outbound accounts are planned for expansion stage R2. Usage follows CRM permissions.
Does transport acceptance guarantee delivery?
No. Acceptance by a mail server is a separate status. Delivery events are considered where the provider makes them available.
What happens if no fallback is available?
Depending on the error and retry budget, the request remains queued, blocked or held for clarification. Its state stays traceable.
Stronger together.
Explore the complementary areas of AgenticUltimate.
Help & documentation
SuiteSMTP documentation
Setup, routing and diagnostics — guides in the QOON Knowledge Base.
See SuiteSMTP
in your SuiteCRM?
In about 20 minutes we clarify delivery paths and failure cases and show setup, logs and diagnostics in SuiteCRM 8.
Request a personal demo ↗No obligation · Matched to your SuiteCRM environment