Permitted messages
Every message sent through Adionexus must be triggered by a specific event on a specific customer's account or order. Permitted message types are:
| Message | Triggering event |
|---|---|
| Account verification | account.verification_requested |
| Account activation | account.verified |
| Password reset | password.reset_requested |
| Security alert (new sign-in, credential change) | security.* |
| Order confirmation | order.created |
| Payment receipt | payment.confirmed |
| Payment failure notice | payment.failed |
| Invoice notification | invoice.created |
| Shipping update | order.shipped |
| Order completion | order.completed |
Message content must relate to the event that triggered it. Templates may include the order, invoice or account details needed to understand that event, and nothing unrelated to it.
Recipients
- A message may only be sent to the customer the event belongs to, or to a billing contact that customer has designated on their account.
- Recipient addresses must come from your own customer records, supplied by the customer when they registered, ordered or updated their account.
- Each API event produces at most one message per recipient. There is no endpoint for sending a message to a list of addresses.
Prohibited use
The following are not permitted on Adionexus and will result in suspension of sending:
- Promotional, marketing or advertising content, including promotional content added to transactional templates.
- Sending to purchased, rented, scraped or shared address lists.
- Sending to addresses that have no existing relationship with your business.
- Creating synthetic events to deliver messages that are not tied to a real order, payment or account action.
- Phishing, impersonation, malware, or any content that is illegal in the sender's or recipient's jurisdiction.
- Hiding or falsifying the sender identity, headers or the origin of a message.
Sender authentication
Before a workspace can switch to live mode, its sending domain must pass verification:
- DKIM — signing records published on the sending domain.
- SPF — a custom MAIL FROM subdomain authorized for Adionexus's sending infrastructure.
- DMARC — a published policy on the sending domain, aligned with DKIM.
Adionexus's own account emails are sent from notifications@adionexus.web.id with the same records in place.
Bounces and complaints
Adionexus processes delivery feedback automatically for every message:
- Hard bounces — the address is added to the workspace suppression list immediately. Later events for that address are logged but not delivered.
- Soft bounces — delivery is retried. An address that soft-bounces repeatedly is suppressed.
- Complaints — when a recipient marks a message as spam, the address is suppressed for all non-essential notifications from that workspace.
Bounce and complaint rates are monitored per workspace. Workspaces with a bounce rate above 5% or a complaint rate above 0.1% are reviewed, and live sending may be paused until the cause is resolved.
Recipient preferences
Messages required to operate an account or complete a transaction — verification, password reset, security alerts, receipts and payment failures — are always delivered. Recipients can turn off optional updates, such as shipping and order-completion notices, using the preferences link in the footer of those messages.
Enforcement
If a workspace breaks this policy, Adionexus may pause live sending, require changes to templates or recipient data, or close the workspace under the Terms of Service. Where possible, we contact the workspace owner before taking action.
Reporting abuse
If you received a message sent through Adionexus that you believe breaks this policy, forward it with full headers to abuse@adionexus.web.id. Every report is reviewed.
For other questions, contact help@adionexus.web.id.