Messaging with accountable consent
A planning guide for compliant outreach infrastructure and reputation management.
Content revised · English
- Architecture to evaluate
- Lawful basis / authentication / feedback
- Prepared starting points
- 3 plans
- Responsibilities
- Application, rights and recovery
A fit shortlist, not installed software or live inventory.
Keep these in view.
- Lawful basis / authentication / feedback.
- Set domain and sender signals before volume.
- Measure delivery quality instead of evading it.
Lawful basis / authentication / feedback
A campaign needs opt-in or another documented lawful basis appropriate to the recipients and jurisdiction. Purchased or harvested lists and reputation evasion are outside the proposed AUP. The server is only one part of a responsible sender’s process.
Set domain and sender signals before volume
Configure SPF, DKIM, DMARC and the relevant reverse DNS, then verify alignment. Supply a working unsubscribe path, suppress bounces and complaints, and increase volume only from observed legitimate engagement. A four-to-six-week ramp is an indicative planning range, not a guarantee of placement.
Measure delivery quality instead of evading it
The proposed review trigger is hard bounces above 5%. The SMTP tiers specify one, five or 25 sending domains according to the exact plan. Any warm-up tool or sending application is separately operated; rotating IPs to hide reputation problems is excluded. No inbox placement is promised.
Permission and relevance
Legitimate outreach needs a lawful basis, accurate identity, relevant recipients and a workable opt-out. Buying a larger sending allowance does not make unsolicited or deceptive campaigns acceptable.
Infrastructure is one layer
Authentication records, dedicated credentials and consistent sender identity matter. Separate outreach traffic from transactional mail so reputation problems do not interrupt essential account messages.
Respect feedback
Track bounces, complaints and suppression requests. Stop sending to invalid or opted-out addresses and review applicable rules before increasing volume.
Capacity to consider.
Match these starting points to the representative application. Software installation and live inventory are not connected; the exact specification and period total come from the catalogue.
Signal 1K
Send up to 1,000 messages per day through a relay configuration with one dedicated IPv4 address and PowerMTA or Postfix tooling. A prepared IP is available separately, making this a starting point for permission-based or transactional mail with domain authentication and sender reputation managed deliberately.
- Transfer
- Unmetered
billed monthly
Signal 10K
Scale permission-based or transactional delivery to 10,000 messages per day across three dedicated IPv4 addresses. The configuration includes IP rotation tooling and SPF, DKIM and DMARC setup, while successful delivery still depends on consent, content, recipient policies and the reputation of your sending domains.
- Transfer
- Unmetered
billed monthly
Signal 50K
Build a larger sending configuration with a daily allowance of 50,000 messages, ten dedicated IPv4 addresses and support for multiple domains. Delivery monitoring tooling is part of the service specification, with authentication, consent and reputation controls remaining essential at this volume.
- Transfer
- Unmetered
billed monthly
Before this workload goes live.
- Check the exact plan’s CPU, memory, disk, transfer and port.
- Choose a listed region and verify the workload’s permitted use.
- Test the representative application and an independent restore.
Questions, answered.
How long does a sender ramp take?
Four to six weeks is an indicative planning range from the audited workflow, not a fixed rule or delivery guarantee. Increase from observed legitimate engagement and feedback, not an automated volume target alone.
Will messages reach the inbox?
No inbox placement can be guaranteed. Authentication, consent, content, recipient filtering, bounces and complaints all influence delivery.
Can a sending application connect over SMTP?
A standards-compatible application such as the tools you evaluate can use a correctly configured live SMTP service. No third-party sending tool or authenticated SMTP endpoint is connected.
What happens to bad addresses or a blacklist?
Suppress hard bounces and complaints, investigate the cause and reduce harmful traffic. The proposed hard-bounce review trigger is above 5%; rotating addresses to evade reputation is excluded.
How many domains are prepared?
The exact SMTP tiers list one, five or 25 sending domains. Configure authentication and feedback handling for each; the count is not permission to use purchased lists.
What is kept in my account workspace?
Your configuration, selected plan, image, location and billing term are kept with the order and payment request references. Quotes, payment-state reads and support conversations remain linked to your account. Read fulfilment details separately from payment status.