Send reviewed email to people who opted in

Establish your own sender, record actual permission, review campaign content and follow safe submission and unsubscribe outcomes.

Send a reviewed message to people who asked to hear from you#

Confirm the workspace identity and sending purpose, establish your sender, record the actual audience permission, then prepare and review one campaign. Approve its exact revision before deliberately starting or scheduling submissions. Follow the individual outcomes and protect every stop request.

This release supports ordinary express-consent domestic sending within Australia or within New Zealand. Preparation remains useful elsewhere, but unavailable country cases cannot send. Your own SMTP provider accepts submissions; Emnaro does not infer delivery, opens, clicks or legal certification.

Set up the responsible business and working rules#

Use the actual shared business identity. Review the displayed controller name, postal and contact details, privacy notice, processing explanation, recipients and retention review. Correct a wrong shared identity through Business setup rather than inventing a different sender in this app.

Choose who may prepare work and whether approval belongs to the owner or a separately authorised reviewer. Settings never install another app, copy another profile’s audience or turn platform transactional SMTP into campaign infrastructure.

Separate useful preparation from sending requirements#

Lists, audience preparation and campaign drafts are standalone corporate work. CRM, Ecommerce, Events, Surveys and Customer Success do not grant audience access or marketing permission merely because they are installed.

Submission additionally needs the actual workspace SMTP entitlement, current sender/domain/mailbox facts, permitted country case, valid recipient permission, no suppression, an approved revision and available allowance. The current server explanation identifies what is missing.

Customer-owned SMTP is a shared workspace feature. It is included unless Emnaro publishes an optional one-time licence price. When a licence is required, the setup page opens the current price for owner review; no purchase happens automatically. A workspace already using its configured SMTP connection keeps its grandfathered access when a fee is first introduced.

Review the actual domestic country case#

The implemented sending cases are an ordinary Australian business to explicitly recorded Australian recipients and an ordinary New Zealand business to explicitly recorded New Zealand recipients, using express permission. These are separate domestic cases; an Australia-to-New-Zealand audience is not made supported by the presence of both countries.

Other countries, cross-border targeting and specialist purposes remain preparation or review only. Record the actual business and recipient facts; address suffixes, language, IP location, currency and DNS checks do not establish jurisdiction. Country controls support the stated workflow and do not certify your organisation or replace its actual legal review.

Official references: ACMA: Avoid sending spam ↗ · New Zealand DIA: Three steps ↗

Describe the message the person agreed to receive#

Use a clear purpose and the exact notice shown at collection. Permission for one purpose is not blanket permission for unrelated offers. Keep the source, collection time, language and notice reference meaningful enough to review later.

An ordinary purchase, ticket, customer relationship, survey response or old list membership is not recorded as express marketing permission by this workflow. Other possible legal bases are outside this first sending scope, rather than automatically being declared unlawful.

Review necessary contact use and retention#

Explain who is responsible, how the person can contact you, why contact details are used, the notice supplied, the actual processors/locations and the next retention review. Use ordinary contact details proportionate to this purpose; this scope is not for sensitive profiling or special-sector campaigns.

Current contact removal, consent evidence, original prepared messages, protective suppression and backup retention are different records. Review their consequences before redaction. An erased display copy does not authorise another send or promise that an earlier downloaded file was recalled.

Assign the responsibility without exposing the whole audience#

Campaign view/preparation, recipient read/management, suppression management, approval, sending and export are deliberate permissions. Workspace role, current membership, installation and scope remain ceilings. A viewer cannot become a writer through a grant, and list-scoped work does not imply access to every list.

Use the current availability reasons. Removing staff, changing a role, changing approval authority or reinstalling the app does not revive old authority. After rejoining or reinstalling, the owner must select the current member and deliberately save a fresh grant; retained old grants provide no access. A hidden count is unavailable, not zero. Table controls do not replace independent server export permission.

Connect your workspace’s SMTP account#

An owner enters the actual SMTP hostname and supported secure mode: implicit TLS on 465 or required STARTTLS on 587. Supply credentials from your own mail provider. On an existing connection, deliberately keep the stored credentials or replace them; a masked value is never submitted as a password.

Secrets are write-only and clear after dispatch. They are not stored in page history, browser storage or ordinary operation receipts. Platform transactional mail remains separate. Your provider’s sending policy and charges still apply; the app does not invent a new automatic email fee or choose a provider contract for you.

Understand what the connection test proved#

Request the current connection test and follow its actual task. A successful result means the supported TLS and authenticated login checks passed for the observed connection. The test sends no campaign and does not establish mailbox control or inbox placement.

A failed or uncertain test has a safe reason. Review the actual configuration before a deliberate new test; credentials, raw SMTP replies and provider debug transcripts do not belong in notes or support exports. No unencrypted or unauthenticated relay fallback is offered.

Prove control of the exact sender domain#

Add the domain you actually control. Copy the generated record name, type and value to your DNS provider deliberately, then request verification. The app observes the required DNS facts; it does not modify your provider account or treat saving a form as verification.

Pending DNS can require a later check after your provider publishes the record. Use the exact displayed domain and selector. A public record check is a current observation, not a guarantee about the final recipient, relay signing behaviour or deliverability.

Publish the public signing record safely#

Publish the displayed DKIM public record for the exact current selector. The signing private key remains on the server and is never a DNS value or a downloadable UI field. Keep your actual provider’s SPF and DMARC instructions under review instead of guessing a universal DNS policy.

Key rotation is a reviewed change. It can invalidate a pending sender proof or campaign review, so read the current consequences first. Retained unsubscribe protection is not removed because a sender key, connection or installation changes.

Confirm the actual sender mailbox separately#

Choose a verified domain and enter the actual From name/address and Reply-To address. Domain control and a successful SMTP login do not replace confirmation of the particular sender mailbox.

A deliberate mailbox challenge is its own queued message task. Follow its actual state and complete the supported confirmation flow. A pending or unknown challenge is not shown as verified, and the app does not automatically send another copy.

To correct an existing From name or Reply-To address, open that mailbox’s sender details. Saving clears its mailbox proof and requires fresh confirmation before further use. The correction does not silently retain an older proof.

Pause or replace sender details with current review#

Read the current domain, connection, signing and mailbox facts separately. Editing a connection, replacing credentials, suspending a sender or rotating a key can make previously reviewed sending unavailable until the new facts are checked.

Pausing protects future starts; it cannot recall a message already in progress or retract an SMTP acceptance. Removing secrets does not delete the original attempt history or make old unsubscribe links stop working.

Add ordinary addresses without inventing permission#

Create the person’s actual email address, name, explicit country and relevant list membership. An address may remain pending when its permission is missing. Country is a supplied fact, not an inference from an email domain or a browser location.

Address normalisation and duplicate review preserve the supported identity rules. Do not assume that changing case, removing a contact or importing another copy clears an unsubscribe. Review the current record and its purpose-specific evidence.

Publish or pause the exact subscription form#

Choose the actual destination list, title, explanation, source language and notice/version. Review the frozen controller, purpose and exact proven confirmation sender shown before publication. The public URL is available only for the supported published source; viewing a draft never records a subscription.

Pause the form deliberately to prevent new signups through that source. This does not recall an already submitted confirmation, undo previously confirmed permission or disable existing protective unsubscribe links. Editing published content requires the current supported publication review; the recipient’s preferred email language does not silently translate the source notice.

Publish a clear form and distinguish requested from confirmed#

Prepare the signup form’s exact list, title, explanation, language, purposes and notice/version. Review the current controller and publication before sharing the resulting link. The person chooses explicit marketing permission and the supported actual domestic country; no checkbox is preselected for them.

A requested confirmation is separate from confirmed permission. Only the supported valid confirmation changes that state; viewing or prefetching a link does not. Do not create a cold campaign merely to ask strangers for permission, and do not claim the link establishes a person’s legal identity.

Stop future submissions when a person opts out#

Use the recipient’s unsubscribe, a recorded actual request, documented complaint or supported permanent-failure record. Confirm the actual reason/source. Current suppression is checked before each new submission, even when an older campaign was already approved.

The recipient does not need an Emnaro account or extra personal information to stop messages. Protective links remain supported for at least 90 days after the relevant started, accepted or unknown submission under this release’s design. Pause, uninstall, licence loss, sender rotation and contact removal do not create permission to send again.

Require separately supported new permission before a new subscription#

A new list, edited email copy or file import does not override an earlier protective stop. Review any separately supported person-initiated confirmation and current evidence before a recipient becomes eligible again.

An owner cannot use ordinary contact deletion, historical evidence or a campaign clone as a resubscription shortcut. If the current product does not offer a supported new confirmation for the case, keep sending unavailable.

Preview and commit an audience file deliberately#

Download the actual CSV sample and complete your own recipient and source facts. Each UTF-8 file accepts at most 1,000 data rows and 5 MiB; split larger sources into deliberately reviewed files. The sample includes an empty pending-contact row and an incomplete row carrying the current notice references. Neither row invents permission. Inspect valid, pending, suppressed and rejected rows before committing the exact preview.

Preview is pure and creates no permission, message or confirmation email. Row pages cover the complete bounded file rather than hiding records after the first page. Changes to the file, source, list, current authority or suppression can require a fresh preview; imports never unsuppress or queue confirmation automatically.

Download only the currently permitted records#

Use the app’s explicit export with current recipient/report authority. Files may be segmented; continue the displayed next segment until the server reports completion. A first segment is not presented as the complete audience when more records remain.

Current contact removal and scope still apply. Spreadsheet-active values are safely represented, but a download is a copy under your control and does not become a new source of consent. Keep it within your organisation’s actual access and retention arrangements.

Build useful content in an original email layout#

Choose an editorial, announcement, newsletter or offer starting structure, then write a meaningful subject/preheader, heading/text/button blocks and text alternative. Button destinations use actual supported HTTPS links. This release has no arbitrary HTML, scripts, image fetching or template execution.

Use the exact content language and direction; reviewed words are not automatically translated by interface preferences. The responsible controller/footer and unsubscribe presentation are part of the final message, not optional promotional blocks.

Review the same rendered content before approval#

Open the server-rendered safe preview and inspect both HTML and plain text. Check the From identity, subject, content, links, postal/contact details, purpose and unsubscribe presentation. The preview uses an inert protective-link placeholder and cannot unsubscribe a real person.

Previewing does not authenticate SMTP, queue a send, publish a form or change approval. The shared renderer applies the same supported content rules used for outgoing messages, while its isolated frame prevents scripts, forms, navigation and network activity.

Understand who was included and why others were excluded#

Select the exact lists, supported country cases and applicable tag rules. The current review explains missing permission, pending confirmation, withdrawal, suppression, unavailable country/source, duplicate or invalid addresses rather than silently forcing those records into the campaign.

Eligibility is reviewed again at the actual start of every recipient submission. An earlier included count is not a promise that all those people will still be eligible later; the attempt/report shows the actual disposition.

Approve the exact immutable revision#

Review the current sender identity/versions, complete content/footer, audience evidence and exclusions, country facts and allowance. Confirm the required approval separation before approving the exact revision.

In separate-approver mode, neither the original draft creator nor the latest content editor can approve it. Choose another currently authorised reviewer. The approved revision keeps the latest preparer and independent approver names separately, even after its status changes.

Approval and queueing are separate actions. Editing content or changing relevant sources requires a fresh deliberate review. A stale tab cannot silently substitute different text, a newer sender key or a repaired audience under an old approval.

Choose the actual time to start#

Queue the approved revision now or use the supported explicit local time, timezone and occurrence. Resolve repeated or nonexistent daylight-saving times deliberately rather than assuming the browser’s timezone is the business’s intended clock.

A scheduled start still checks current authority, sender, permission, suppression and allowance. Pauses, expiry or source changes can stop future work; the planned time does not bypass those checks or guarantee delivery at a particular minute.

Read reserved attempts and remaining capacity#

Inspect current contacts, lists, sender domains/mailboxes, daily attempts, campaign size, MIME size and storage limits. An owner can understand the current allowance before review; settings do not create a new unapproved charge.

A workspace can hold at most 10,000 messages that have not started, across its campaigns and confirmation tasks. Cancel unstarted work you no longer need or allow it to progress before queuing more. Original started and terminal history remain protected and do not consume this queue allowance.

Actual started and unknown submissions retain the protected attempt/budget disposition. A worker crash or uncertain response does not refund the budget automatically or create a fresh send allowance. Large work remains bounded and its actual progress stays visible.

Read real per-recipient submission outcomes#

Waiting, preparation and started describe local processing stages. Accepted by mail server requires the actual final SMTP acceptance. Rejected and not submitted are distinct known outcomes. Outcome unknown means the product cannot safely establish the original terminal result.

SMTP acceptance is not delivery or an open/click event. This scope does not invent delivery rates, tracking pixels or provider-authenticated bounce/complaint evidence. A documented manual failure remains labelled as such.

Preserve an uncertain original without sending another copy#

Keep the original attempt/request reference. A started submission that loses its acknowledgement remains unknown; do not guess that it failed or create a replacement campaign for that person. The unknown state is not automatically retried.

If the original worker later supplies authentic corroborating information, it is retained with that same attempt. It does not erase the terminal unknown, consume the allowance twice, count another accepted message or authorise a resend. Investigation adds actual evidence rather than rewriting provider truth.

Pause or cancel future starts without pretending to recall mail#

Review the exact pending work and current consequences, then pause or cancel deliberately. A pause can be followed only by the currently supported fresh resume review; cancellation does not remove original consent or attempt history.

The stop prevents new starts. A message that already crossed the actual started boundary can still receive its real acknowledgement, and an accepted message cannot be recalled through these controls. Preserve the original report and handle recipient requests promptly.

Follow actual decisions without duplicating private payloads#

Use original campaign revisions, consent events, current source references, task outcomes and guarded operation receipts to understand what happened. Staff attribution and current access matter; an audit reference is not permission to read someone’s address or evidence.

Passwords, signing keys, full MIME, private tokens, raw CSV and provider debug do not belong in ordinary history or errors. Current guarded content and metadata references are separate so contact correction does not leave a hidden duplicate body archive.

Remove a current contact copy while keeping protective stops#

Review the exact contact and actual retention consequences, then record the supported reason. Removal of the current displayed address is not deletion of a message already submitted or a recall of a file already downloaded.

Removing this contact copy also clears current temporary file previews; affected staff must review their original files again. Ordinary withdrawal preserves those previews and still blocks suppressed addresses from becoming eligible.

Minimal protected suppression and required unsubscribe lookup can remain so the same address is not silently reimported and sent another campaign. Contact-copy removal also clears current temporary file previews across the workspace; affected staff must prepare a new preview from their original files. It does not remove imported business records or recall downloaded files. Current records, retained evidence, encrypted message retention and platform backup policy have distinct purposes.

Protect existing recipients and attempts after disable#

Current owner recovery can stop future work, remove supported secrets and perform permitted suppression/privacy or scoped retrieval over retained records. Current membership and genuine demo expiry continue to apply.

Recovery cannot create a campaign, obtain new sending authority, bypass SMTP/licence requirements or revive old staff grants. The public protective opt-out remains independent of an active marketing installation; disable/reinstall does not remove an existing stop.

Retain entered values and check the original request#

Field errors preserve ordinary entered data and explain the exact current failure. A changed original or expired review requires another deliberate read/review. Switching workspace invalidates stale requests and selectors.

An uncertain ordinary request retains its exact original UUID/body in memory; check its receipt or deliberately retry only those unchanged original bytes. Secret forms clear their contents and never replay them automatically. Keep the tab/reference while resolving an outcome; memory-only data is not promised to survive a reload.

Practise with an isolated synthetic mail sink#

Demo follows the same permission, review, audience and outcome workflow under its genuine configured lifetime. External messages are routed only to an isolated synthetic sink; a demo outcome is never a production delivery or entitlement.

Where the current task permits it, open its actual neutral demo message to follow a mailbox or permission confirmation. This private inspection reads the synthetic message; it does not create another submission.

A permitted simulated campaign attempt also offers its original unsubscribe message. Open it in a new tab and confirm deliberately to test protective suppression. This does not send a real email or grant production sender authority.

No real recipient, SMTP provider or DNS record is modified by demonstration or QA. Normal expiry/purge remains effective, including pending tasks, and requesting an extension does not itself extend access or make an old sender live.

Review content, direction and accessible controls#

English, Arabic, Urdu, Hindi, Spanish, Turkish, Russian, French, Portuguese and Bengali are available interface/content choices within the supported source. Actual notice/campaign wording still needs its author’s review; selecting a language does not certify a translation.

Inspect mobile layout, keyboard access, visible labels, contrast and mixed-direction addresses/numbers. A dark-class check describes the current branded shell and does not claim a complete global dark theme, every email client or physical device certification.

Keep the active workspace, actual business requirements and current setup summary in view. A guide explains a choice; it does not make that choice for you.