Dedicated SMTP Node
Zero server administration, a 100% email-focused dedicated engine: an IP allocated to you alone and outbound port 25 open. We install, update and harden the Postfix, Dovecot and Rspamd stack behind it; you install nothing. At delivery you receive your SMTP/IMAP connection details and your SPF, DKIM, DMARC and MX records ready to paste into your DNS, and you connect Mailwizz, Mautic, WordPress or your CRM directly. Smart rate distribution (throttling) that protects your IP reputation is included; no daily send volume is promised. After handover IP reputation and blacklist monitoring are yours, and we accept no liability if the IP is blacklisted.
Managed SMTP infrastructure — Postfix + Dovecot + Rspamd run by us · DKIM, TLS and rDNS/PTR ready · port 25 open — permission-based lists only.
Dedicated SMTP Node Packages
The plans differ in resources, not in send volume: CPU cores, RAM, disk space and mailbox capacity. Every one of them has port 25 open, an IP allocated to you alone and the same managed SMTP infrastructure; no plan puts a quota on your daily send volume.
Package | Processor | RAM | Disk | Traffic | Price |
|---|---|---|---|---|---|
SMTP-Lite | 2 Core Intel CPUPlatinum 8260 / E5-2690 v4 | 4 GB DDR4 | 40 GB NVMe | Unlimited 10 Gbit | ₺499.90/mo |
PopularSMTP-Pro | 4 Core Intel CPUPlatinum 8260 / E5-2690 v4 | 8 GB DDR4 | 80 GB NVMe | Unlimited 10 Gbit | ₺899.90/mo |
SMTP-Business | 6 Core Intel CPUPlatinum 8260 / E5-2690 v4 | 16 GB DDR4 | 150 GB NVMe | Unlimited 10 Gbit | ₺1.599.90/mo |
SMTP-Enterprise | 8 Core Intel CPUPlatinum 8260 / E5-2690 v4 | 32 GB DDR4 | 300 GB NVMe | Unlimited 10 Gbit | ₺2.999.90/mo |
SMTP-Lite
SMTP-Pro
PopularSMTP-Business
SMTP-Enterprise
NVMe disks are allocated based on stock availability. If NVMe stock is depleted, an SSD of equivalent capacity may be provided with your plan.
We Run the SMTP Engine
The Dedicated SMTP Node is a managed sending engine: we install, patch and keep running the operating system and the mail stack (Postfix, Dovecot, Rspamd) — DKIM signed, TLS certified and hardened against bans. Your SMTP/IMAP credentials and your ready-to-paste DNS records are delivered the moment the node is provisioned. We manage the infrastructure; you own the sending reputation: sending behaviour, list hygiene, IP reputation and blacklist monitoring are your responsibility.
What we run
Running the node is on us — setup, patching, certificates and hardening included, all free.
- We run the mail stack
Postfix (SMTP), Dovecot (IMAP/LMTP), Rspamd and Redis are installed, configured and kept running on Ubuntu 24.04. You install nothing — the node is ready to send on day one.
- DKIM key + SPF/DMARC records
A 2048-bit DKIM key is generated and signing is switched on; the SPF, DKIM and DMARC records you need are handed to you ready to paste (you add them to your DNS).
- TLS certificate and ports
A Let's Encrypt certificate is issued and auto-renewed. Outbound 25 is open; 587 (submission/STARTTLS), 465 (SMTPS) and 993 (IMAPS) are ready with authentication required.
- Hardening, patching and updates
Open relay closed, RBL checks on, the Rspamd filter plus a rule that files spam into Junk, Fail2ban and UFW. We track and apply the security updates for the operating system and the mail stack ourselves.
- Smart rate distribution (throttling)
We pace delivery per destination domain, so providers such as Gmail and Outlook never meet a sudden burst, and both your dedicated IP's reputation and our network's overall deliverability are protected. This is not an account quota — we impose no artificial daily sending limit; mail is queued, never refused (AUP Article 6.3).
- rDNS / PTR record
You tell us the hostname you want when ordering and we set the record — a PTR lives with the owner of the IP block and cannot be changed from your own DNS panel.
- SMTP/IMAP credentials
Your first mailbox is created; the host name, ports 587/465/993, the username and the passwords — plus your DNS records ready to paste — are delivered immediately. Enter the SMTP details you receive into Mailwizz, Mautic, WordPress or your CRM and start sending right away.
Yours on the sending side
Managing the infrastructure is not managing your sending reputation — we do not monitor your sending for you.
- Adding the DNS records
We hand you the SPF, DKIM, DMARC and MX records ready to paste; the domain is under your control, so adding them to DNS is on your side.
- IP reputation and blacklist monitoring
Checking lists such as Spamhaus, Barracuda and SORBS — and filing the delisting request when you are listed — is your responsibility.
- Warm-up, list hygiene, bounce/FBL
Ramping volume gradually (we do not run warm-up on your behalf), keeping the list opt-in only, handling bounces and complaints, processing unsubscribes — all yours.
- Your campaign software and your data
It does not matter where your campaign software (Mailwizz, Mautic, Sendy and the like) is installed. Without touching our infrastructure, enter the SMTP host, port and password we give you into your own panel and start sending over this engine straight away. Managing that software and backing up your data are yours; we do not monitor your sending on your behalf.
We accept no liability if your IP is blacklisted
Running the infrastructure correctly is half the job and that half is ours; the other half is how you send, and that is not in our hands. If your IP is listed on Spamhaus, Barracuda, SORBS or any other list, if your mail lands in spam, or if a receiving provider throttles you, the provider accepts no liability whatsoever. No refund, extension or free IP replacement can be claimed in that case, and the delisting request is filed by you.
Binding text: Acceptable Use Policy, Article 6.9.
Abuse Policy
It applies from the first day of service and is an integral part of the contract. Because a single abuse incident damages the IP reputation of every customer on the same network, enforcement is staged but firm.
- 01First breachWarning
A written warning is sent to your registered email address, naming the source of the breach and what you must fix. Sending may be throttled temporarily.
- 02Second breachSuspension
The service is suspended without prior notice. The suspension lasts until you document that the breach has been resolved.
- 03Third breachTermination
The service is terminated permanently, the node and all data on it are deleted and the contract is dissolved. No refund is issued.
Phishing, identity or brand impersonation, fraud, malware distribution, use of purchased or scraped lists, and content contrary to Turkish law are grounds for termination on first detection.
Breaches accumulate over the life of the service; renewal does not reset the counter. After 12 months with no new breach, the level drops by one. You may only send to your own opt-in list. Failing to answer an abuse notice within 24 hours is on its own grounds for stage 2 (suspension) as well (AUP Article 6.8).
Included on Every SMTP Node
Powerful Processors
Intel Xeon
DDoS Protection
Advanced security
NVMe SSD
Ultra-fast disks
Managed Infrastructure
Patching is on us
24/7 Support
Turkish expert team
99.9% SLA
Network availability
Pure SMTP/IMAP Access
No administration overhead
Turkey Location
Low ping latency
Easy Payment Options!
Up to 12 installmentsOn all credit cards
Secure payment with 3-D Secure. You can also pay by bank transfer. The number of installments may vary by your bank and card program.
Dedicated SMTP Node — Managed, Dedicated Bulk Email Infrastructure
A Dedicated SMTP Node is a managed sending engine with an IP dedicated to you alone and port 25 open, running Postfix (SMTP), Dovecot (IMAP/LMTP) and Rspamd (DKIM signing + spam filtering) behind the scenes: zero server administration, a 100% email-focused dedicated engine. Installing, updating and patching that stack on Ubuntu 24.04 and keeping its services up is ours; the Let's Encrypt certificate auto-renews, a 2048-bit DKIM key is generated and signing switched on, the rDNS/PTR record is set on your behalf, open relay stays closed, RBL checks run and the node is hardened with Fail2ban and UFW, with smart rate distribution (throttling) that protects your IP reputation included. At delivery you receive your SMTP/IMAP connection details (host, ports, username, password) and the SPF, DKIM, DMARC and MX records ready to add to your DNS. The rule is one sentence: we manage the infrastructure, you own the sending reputation — sending behaviour, list quality, warm-up, IP reputation and blacklist monitoring are your responsibility, and the provider cannot be held responsible if the IP is blacklisted.
Managed Engine, SMTP Ready
Postfix + Dovecot + Rspamd are installed, patched and kept running on your behalf; you take your SMTP/IMAP connection details and start sending with no system administration at all.
DKIM, TLS, PTR and Port 25
The DKIM key is generated, the Let's Encrypt certificate auto-renews and rDNS/PTR is set on your behalf; outbound port 25 is open, while 587 / 465 / 993 require authentication.
Hardened, With a Clear Line
Open relay closed, RBL, Fail2ban and the spam filter on at our end, with reputation-protecting rate distribution included. In return, IP reputation, blacklist monitoring and delisting are yours; blacklisting is not our liability.
Why Isn't Sending SMTP from Standard Hosting Enough?
On shared hosting the hourly send limit is 100-300 per account, and exceeding it automatically blacklists the IP and affects all accounts. Major services like Gmail, Outlook and Yahoo treat sudden high-volume sends from unknown IPs as a 'spam burst' — no matter how good the content, the emails go to the spam folder. An SMTP node dedicated to you alone — with its own IP, its own rDNS/PTR record, port 25 open and SPF/DKIM/DMARC configured — solves these problems at source. On top of that, the engine runs smart rate distribution (throttling) that paces delivery per destination domain: instead of dumping a sudden volume on one provider, mail goes out at a rate that provider accepts, so your IP reputation is not burned on the first campaign. We still do not promise a daily send volume: what determines throughput is your IP reputation, your warm-up stage and your list quality — not the hardware.
What Runs on Your Node, and What Do We Manage?
Your node is not run as a bare Ubuntu box but operated on your behalf as a working sending engine. Setup covers, in order: pinning the hostname and the /etc/hosts entry to the real IP (get this wrong and Postfix's forward-confirmed reverse DNS check fails), closing every unnecessary port with UFW — the ones open to you are outbound 25, submission 587, SMTPS 465, IMAPS 993 and Sieve 4190, with 80/443 used only for certificate validation and renewal, obtaining the Let's Encrypt certificate and installing the renewal hook, configuring Postfix with a TLS 1.2 floor plus authenticated submission (587) and SMTPS (465), enabling RBL checks on inbound mail, installing Dovecot with IMAPS (993), LMTP and Sieve, adding the rule that files spam straight into Junk, installing Rspamd + Redis, generating a 2048-bit DKIM key and switching signing on, creating the RFC-required postmaster / abuse / dmarc addresses, enabling Fail2ban for Postfix and Dovecot, turning on automatic security updates and creating your first mailbox. Additional mailboxes and a second sending domain (with its own DKIM key) are created by us on request, free of charge; the plan's disk space is what bounds their total capacity. We then run and report an open-relay test, the PTR match, the Spamhaus status and whether outbound port 25 is open, and hand you your SMTP/IMAP connection details plus the SPF, DKIM, DMARC and MX records to add to your DNS. Everything after that point stays with us as well: package updates, security patches, keeping the services up and auto-renewing the TLS certificate are our job — sending is yours.
What Managed Does NOT Mean
Managed means the INFRASTRUCTURE is managed — not your sending. That line is drawn deliberately: the operating system, the mail stack, security patches, TLS renewal, hardening, rDNS/PTR and service uptime are ours; the whole of your sending activity is yours. What stays with you: adding the SPF, DKIM, DMARC and MX records to your own DNS, ramping volume gradually (warm-up), keeping your list opt-in, handling bounces and complaints (FBL), processing unsubscribes, watching IP reputation and blacklist status, filing a delisting request when needed, and the campaign software you use plus backing up your data. In short: we manage the infrastructure, you own the sending reputation. We do not watch your campaigns on your behalf — we learn of a problem when you report it or when an abuse notice reaches us.
What Happens If the IP Is Blacklisted?
Sending reputation is set by how you send — not by the node's hardware or by our maintenance of the stack: a non-opt-in or stale list, a high bounce rate, sudden volume without warm-up, a rising complaint rate or a spam-trap hit. So the provider cannot be held responsible if your IP is listed on Spamhaus, Barracuda, SORBS or elsewhere, if your mail lands in spam, or if a receiving provider throttles you — and no refund, extension or free IP replacement can be claimed on those grounds. A listing is usually not a technical fault but the outcome of a sending policy, and the fix lives in the same place: clean the list, lower the volume and file that list's own delisting form; the delisting request is the customer's to file. The rule is written into Article 6.9 of the Acceptable Use Policy, an integral part of the contract.
Can You Use Campaign Software (Mautic, Mailwizz)?
Yes. It does not matter where your campaign software (Mailwizz, Mautic, Sendy and the like) is installed. Without touching our infrastructure, enter the SMTP host, port and password we give you into your own panel and start sending over this engine straight away. Tools such as Acelle Mail and Listmonk work the same way: they all send over SMTP, so you run the software on your own hosting, on an office machine or anywhere else and connect on port 587 (STARTTLS) or 465 (SMTPS). Mail still leaves from this node's dedicated IP with its DKIM signature, so the receiving side sees no difference. We do not take on installing, updating or licensing third-party software (Mailwizz Pro and the like); we provide and manage only the SMTP engine those tools connect to.
Why Clou.TR?
Frequently Asked Questions
Still Undecided?
Our expert team is ready to find the right Dedicated SMTP Node solution for you. Get in touch now for a free consultation.



