Console operations

This page covers only the pages visible in the Email product customer console. Platform-managed domain authorization, domain approval, campaign approval, Webhook configuration, and quota changes are not customer self-service features.

Page overview

Domains and sender mailboxes

Set up a sending domain before creating a mailbox. The platform generates or enters the records shown in the domain detail; customers configure them at their DNS provider. Platform operations or AI support handle domain authorization; platform operations perform any required manual review. See Sending domains and identity verification.

A mailbox requires an approved domain. Reply-To supports one address. An explicit API replyTo takes precedence over the mailbox default.

Templates and campaigns

Templates

1. Create a marketing or transactional template and preview its HTML.
2. Save the draft and submit it for review.
3. Confirm that the current version is approved, enabled, and validation passed before using it in a campaign or API request.

The category cannot change after creation, and edited content must be reviewed again. See Templates and variables.

Campaigns

1. Create a campaign and select an approved sender mailbox plus a template or custom content.
2. Select an available API Key owned by the account, a reply address, and recipients.
3. Build the audience from tags, groups, or the campaign recipient list, then send a test.
4. Save the draft and click Submit for Review. Choose immediate sending after approval, a relative delay, or an absolute date, time, and timezone.
5. The platform must approve the campaign before dispatch. Submission alone does not mean messages were sent.

A campaign already in the sending flow cannot be recalled. Cancellation applies only to unexecuted pending-review or scheduled campaigns. Deletion applies only to campaigns that never executed and no longer have an active sending plan. The detail page can refresh delivery statistics and retry only currently failed recipients, preserving separate attempts.

Send records

• The default range is the last 7 days, and each query can span at most 7 days.
• Filter by exact recipient, full Message ID, subject, status, and message category.
• List status is a message-level summary, not a separate result for every recipient.
• Details include Request ID, batch number, retry count, template ID, key event times, and available text/HTML snapshots.
• The timeline shows only the first open and click, not every action.

See Send records and statuses.

SMTP settings

1. Open SMTP Settings, select an existing API Key, and enable SMTP.
2. Select the default purpose: TRANSACTIONAL or MARKETING.
3. Configure the client with the displayed connection details: host smtp.innomails.com, port 587, and STARTTLS.
4. Use the full API Key as the username and its API Secret as the password. There is no separate SMTP password or SMTP-only reset. Rotating the API credential affects both HTTP and SMTP clients.
5. Clients can specify purpose through X-Innomail-Message-Type; marketing messages still require one recipient per message.

SMTP TPS is a platform policy and is read-only here. Saved configuration can take a short time to take effect.

Unsubscribe page settings

From Suppressions, open Unsubscribe Page Settings to edit branding, logo, layout, colors, copy in three languages, website, and support email, and to preview different states. Saving or publishing this configuration does not enable automatic unsubscribe for the API Key; platform operators control that switch. See Marketing email and unsubscribe.

When to contact platform operators

The customer console does not currently provide inbound email, IMAP/POP3 mailboxes, or email forwarding.

FAQ

Can a submitted campaign be recalled?

A pending or scheduled campaign may be cancellable in the console. Once sending begins, messages cannot be recalled.

Related resources