Unlimited email sending from your own server: what it really means
Unlimited email sending means no per-email fee and no sending cap set by the software. With a self-hosted MTA such as TurboMTA you pay once per server and send from your own IP addresses. Your real ceiling is your hardware, IP reputation, your provider's port 25 policy and whether recipients want your mail.
What "unlimited" does and does not mean
On a hosted email service you pay per email or per monthly volume tier, and the service can cap or throttle you. On your own server running TurboMTA there is no per-email fee and no daily cap in the software. You pay a one-time licence per PC or server plus whatever your VPS costs.
It does not mean mailbox providers will accept everything you send. Gmail, Outlook and Yahoo decide that from your reputation, authentication and recipient behaviour, not from your software. We never promise inbox placement.
- Does mean: no per-message licence fee, no monthly volume tier, no sending quota inside TurboMTA.
- Does not mean: no limits from your VPS provider, your IP reputation or the receiving mail servers.
- Does not mean: permission to send to people who did not ask for your mail. Our acceptable-use policy requires opt-in or another lawful basis.
The four limits that really decide how much you can send
| Limit | What decides it | What you control |
|---|---|---|
| Server resources | CPU, RAM, disk and network of your VPS or PC | Choose a bigger server; TurboMTA is built for modest hardware, we recommend at least 2 GB of RAM |
| IP reputation | How mailbox providers have seen mail from your IP and domain | Warm up gradually, send to engaged recipients, keep bounces and complaints low, use several IPs you own or rent |
| Provider policy | Whether your host allows outbound port 25 and how many messages per hour | Pick a host that allows port 25 or ask for it to be unblocked; set per-domain rate limits to match |
| Recipient consent | Complaint and bounce rates reported by Gmail, Yahoo and Microsoft | Only mail opted-in addresses, add one-click unsubscribe, remove bounces quickly |
These are the limits you actually manage when you run your own sending server. Most people hit the first two long before anything else.
A simple cost model: flat server cost versus per-email pricing
Hosted services price per email. Amazon SES, for example, has listed $0.10 per 1,000 emails; check current prices before you decide, and note that other services use monthly tiers that cost more per email at small volume.
Worked example: 1,000,000 emails a month at $0.10 per 1,000 is about $100 a month on a per-email plan. A self-hosted setup costs your VPS (often tens of dollars a month) plus a one-time $249 TurboMTA licence, and the monthly cost stays the same at 2,000,000 or 5,000,000 emails as long as the server and your reputation can carry it.
Be honest with yourself about the other side: self-hosting costs time for DNS, warm-up and monitoring, and at small volume a hosted service is usually cheaper and simpler. Independent comparisons put the break-even somewhere between roughly 500,000 and 5 million emails a month. Treat that as a rough guide, not a promise.
- Formula: monthly hosted cost = emails / 1,000 x price per 1,000. Monthly self-hosted cost = VPS cost + (licence / months you will use it).
- Free setup is included with every TurboMTA licence, which removes most of the one-off effort.
Who this is for, and who it is not for
- Good fit: newsletters and product updates to opted-in lists, transactional mail from your own apps, agencies and consultants running several client domains, teams leaving per-email billing, anyone who wants their sending data on their own server.
- Good fit: teams that need several IPs with per-domain rate limits and a dashboard they can read at a glance.
- Not a fit: cold email to bought or scraped lists, anything that breaks our acceptable-use policy, or senders who cannot spend a few weeks warming up new IPs.
- Not a fit: very small volumes where a hosted free tier already covers you.
How to start in four steps
- 1. Choose a VPS or PC with a public IP and outbound port 25 open (see our port 25 guide).
- 2. Buy a TurboMTA licence for Linux, Windows or the bundle, and open a free setup ticket.
- 3. Publish reverse DNS, SPF, DKIM and DMARC for your sending domain (we do it with you).
- 4. Warm the IP up gradually with our schedule, then raise the volume as bounces and complaints stay low.
Keep reading
- Turn a VPS into an email server: Step-by-step guide with the DNS records you need.
- IP warm-up schedule: A conservative schedule and the signals to watch.
- Self-hosted MTA vs SES, SendGrid and Mailgun: When each model wins.
- TurboMTA pricing: One-time licence: $249 Linux, $249 Windows, $299 bundle.
Frequently asked questions
Can I really send unlimited emails from my own VPS?
TurboMTA puts no per-email fee and no sending cap on you: you pay once per server. Your real limits are your server hardware, the reputation of your IP addresses, your provider's port 25 policy and whether recipients want your mail. Send only to people who opted in, and warm new IPs up gradually.
Is a self-hosted email server cheaper than SES, SendGrid or Mailgun?
At low volume usually not: hosted services cost little until you send a lot. At high, steady volume a flat server cost plus a one-time licence can be far cheaper, because there is no per-email price. Independent write-ups put break-even somewhere between roughly 500,000 and 5 million emails a month; treat that as a rough guide.
Do I need an SMTP relay or can I send directly from my VPS?
You can send directly if your VPS provider allows outbound port 25 and you set up reverse DNS, SPF, DKIM and DMARC. If port 25 is blocked and cannot be unblocked, you either change provider or relay through another service on port 587 or 465. TurboMTA works for both.
How long does IP warm-up take?
Plan on two to four weeks for a new IP. A conservative start is about 50 emails a day, roughly doubling every two to three days while bounces and complaints stay low, to the volume you need. Skipping warm-up is the most common reason a new sending IP gets blocked.