Non-Suspend SMTP

The term describes a dedicated sending service marketed around operational control and continuity. It is not a promise that an account can never be suspended. Our managed plans include defined sending limits and management; misuse, security incidents, or provider restrictions can still require intervention.

It is a marketing term used for email infrastructure promoted as flexible or resilient, not a technical guarantee of delivery, anonymity, or immunity from complaints. Our offering is dedicated SMTP infrastructure with published capacity, MailWizz, and PowerMTA. It is not permission to host illegal content or send abusive messages.

You can compare three managed plans with clear monthly, daily, and hourly limits, see which domains and management are included, and submit your requirements before activation. We confirm the scope, domain arrangements, access, and payment terms with you rather than asking you to purchase an unexplained configuration.

They are intended for businesses, agencies, and marketing teams that need campaign infrastructure or managed sending. Share your audience source, message type, volume, and existing setup so we can assess the fit. Critical transactional messages need a separate discussion about routing and operating requirements.

Tell us which server or application tasks you want to control. We confirm the access level and responsibility split before provisioning. Do not assume unrestricted root access is included in every managed plan; application access and server-administration rights are different. Avoid sharing access credentials through the enquiry form.

Start with a plan enquiry. We provide the available payment methods and instructions when confirming your order. The website does not currently take payment or automatically activate subscriptions. If you need a particular payment method, mention it in your request so we can confirm availability before you commit.

Cancellation and refund eligibility are confirmed in the written order terms before activation. Ask for those terms before paying, particularly if your project depends on a specific setup date or service requirement. If an issue occurs, contact us with the affected service and timing so it can be reviewed against the agreed terms.

Yes. Tell us your new monthly volume and peak sending rate. We confirm availability, the revised price, and whether migration or configuration changes are needed. If a change requires downtime or moving data, the backup and change window should be agreed before work starts.

No. Sending capacity and successful server submission are not guarantees of inbox placement, opens, replies, or sales. We configure and test the agreed infrastructure, but recipient systems and campaign conditions affect the outcome. We do not promise to bypass filtering or remove complaint-handling obligations.

We reply to enquiries within 24 hours. Installation timing is agreed after reviewing the plan, domain arrangements, access, and any migration requirements. The reply window is not an installation deadline. We confirm a provisioning schedule before activation rather than promising an unverified instant setup.

Every stated limit applies together. For example, Non-Suspend 1 has a 100,000-email monthly allowance even though its daily ceiling is 24,000. You cannot send 24,000 every day for the entire month under that allowance. We confirm the billing-cycle dates and counting rules before activation.

Non-Suspend 1, 2, and 3 include 2, 4, and 10 domains respectively. Before activation, we confirm domain selection, registration arrangements, renewal costs, ownership, and access. The number of domains does not multiply the plan’s overall monthly, daily, or hourly allowance.

These Managed SMTP plans include MailWizz, PowerMTA, SMTP access, and management. We document application access, licence arrangements, and the division of operational responsibilities during onboarding so you know what you can manage and what our team handles.

Tell us about these messages before ordering. We review critical transactional traffic separately from bulk campaigns and agree suitable routing, capacity, and support responsibilities. A campaign plan should not be assumed to provide an uptime or delivery commitment for business-critical notifications.