PowerMTA is the production-grade MTA used by every serious sending operation that doesn't outsource to an ESP. Receiver- aware throttling, VMTA pool architecture, DKIM signing at wire speed, FBL handling built in, configuration that scales from one IP to hundreds. Postfix and exim work for low volume; PowerMTA is what you switch to when serious sending starts.
Direct licensing from Port25/Bird starts at $5,000+ per year with annual maintenance fees. Our license is one-time €1,499, permanent, with no recurring costs. License delivered within 24 hours. Setup support optional and bundled cheaply with our PowerMTA + MailWizz Setup (€299).
Most operators start with Postfix because it's free, ubiquitous, and works. For low-volume sending (under 10K daily, single domain, single IP), Postfix is genuinely fine. The features PowerMTA adds don't matter at that scale because you can't generate enough volume to need them.
PowerMTA earns its place when sending volume hits a threshold where receiver-side dynamics start to matter. Around 20K-50K daily, individual receivers begin throttling per-IP based on observed sending rates. Postfix can't see this and doesn't adapt; it just keeps trying at its configured rate, accumulating deferrals. PowerMTA observes per-receiver SMTP responses, learns throttling patterns per host, and adapts send rates per receiver per IP per hour. The same volume that would generate 30% deferrals on Postfix sees 2-3% deferrals on PowerMTA because PowerMTA backs off on the right receivers at the right times.
Operationally, the gap widens further. PowerMTA's VMTA pools let you assign different IPs to different sending streams so marketing volume doesn't damage transactional reputation. DKIM signing happens at wire speed (Postfix needs OpenDKIM as a milter, which adds latency and a failure point). FBL handling is built into the MTA configuration directly. Pickup directories let you queue from any application without SMTP submission overhead. The configuration file format is verbose but thorough, including syntax for things Postfix simply can't express.
The honest comparison: for opt-in transactional mail under 10K daily, Postfix is the right choice. For cold outreach at any serious volume, for marketing automation past 50K daily, for multi-brand or multi-tenant infrastructure, for any case where per-receiver throttling discipline matters, PowerMTA earns its license cost within 6-18 months purely through reduced deferral rates and improved deliverability outcomes. We've seen customers switch back to Postfix after trying PowerMTA only when they decided the volume wasn't there to justify the operational complexity.
We also offer PowerMTA License Rental at €99/month if you don't want the upfront commitment. Adjust the slider to see when lifetime pays off versus rental. Crossover point is around 15-16 months of usage.
Typical sending operation runs 3-5 years. New ventures might commit to only 6-12 months initially.
No expiration. License survives infrastructure migrations, business pivots, scaling decisions. Compounding value over time.
Includes ongoing support and software updates. Cancel anytime. Lower commitment for new ventures or short-term campaigns.
For 24 months of operation, lifetime is the better choice. Most senders operate 3+ years, where the savings widen substantially.
Math: lifetime cost stays at €1,499; rental cost = €99 × months. Crossover at ~15.1 months (€1,499 ÷ €99). For operations running 15+ months, lifetime wins. For shorter pilots or contract work, rental makes sense. We sell both because the choice depends on your specific situation.
Toggle the criteria to highlight what matters for your case. Most sending operations care about throughput, throttling, or DKIM. The differences across these dimensions are operationally significant.
| us PowerMTA | Postfix (open source) | Halon MTA | Exim (open source) | |
|---|---|---|---|---|
| Sustained throughput per server | 300-1,000+ msg/sec | 50-200 msg/sec | 200-800 msg/sec | 30-100 msg/sec |
| Concurrent connections handled | Unlimited (config-bound) | Limited (process-per-connection) | Unlimited (config-bound) | Limited |
| Receiver-aware adaptive throttling | ✓ Built-in, learns per-host | ✗ Requires policy daemon | ✓ Built-in, scriptable | Limited via ACLs |
| VMTA (virtual MTA) pools | ✓ First-class concept | ✗ Workaround via transports | ✓ First-class concept | Workaround via routers |
| Per-receiver per-VMTA per-hour limits | ✓ Native syntax | ✗ | ✓ Scriptable | ✗ |
| DKIM signing speed | Wire speed (built-in) | OpenDKIM milter (latency) | Wire speed (built-in) | OpenDKIM milter |
| Multiple DKIM keys per domain | ✓ Per-VMTA | Workaround via OpenDKIM | ✓ Per-policy | Workaround |
| FBL handling | ✓ Built-in parsing | External tooling required | ✓ Scriptable | External tooling |
| Pickup directories (queue from filesystem) | ✓ Native | Workaround via maildrop | ✓ Native | Workaround |
| Bounce categorisation | ✓ Detailed (50+ categories) | Basic (4-5 categories) | ✓ Scriptable | Basic |
| Configuration learning curve | Steep but documented | Moderate | Steep, scripting required | Steep, idiosyncratic |
| License model | €1,499 one-time (us) | Free / open source | Subscription, quote-based | Free / open source |
Throughput numbers are sustained typical, not peak. Postfix can burst higher than 200 msg/sec on bare metal but doesn't sustain it under realistic conditions (DKIM signing, bounce processing, receiver throttling responses). PowerMTA's throughput advantage widens at scale. For most sending operations, the throttling and operational tooling features matter more than raw throughput. Halon is genuinely competitive but its scripting-required model and quote-based pricing fit a different operator profile.
Adjust your IP count and VMTA configuration. The visualizer estimates sustained throughput under realistic conditions (DKIM signing, FBL handling, mixed-receiver throttling). Useful for capacity planning before purchase.
More IPs = more parallel sending channels = higher sustained throughput. Past 32 IPs, network bandwidth becomes the bottleneck before MTA performance does.
Different sending streams (transactional vs marketing vs cold) get separate VMTA pools. Each pool has its own throttling configuration.
Load profile affects per-message overhead. Heavy profiles do more per-receiver throttling lookups and DKIM operations per message.
PowerMTA's throughput per server reduces hardware needed for equivalent volume. The license cost often pays back through hardware savings alone.
Estimates calibrated against production deployments. Real-world throughput varies with content size (larger messages = lower msg/sec), receiver mix, network bandwidth, disk I/O for logging. The visualizer assumes typical 30-80KB messages with mixed receiver distribution. For specific capacity planning before purchase, book a 1-hour consulting session (€199) for tailored estimates.
License file tied to your server hardware identifier (typically primary network interface MAC address or hardware UUID, depending on platform). License doesn't expire and includes all current PowerMTA features.
Single-server license. For multi-server operations, you order multiple licenses. We discount past 5 licenses (€1,299 each) and past 10 (€1,099 each); contact us for fleet quotes.
Current stable release (5.1+ as of early 2026) provided as RPM, DEB, and tarball. Compatible with AlmaLinux 8/9, RHEL 8/9, Rocky Linux 8/9, Debian 11/12, Ubuntu 22/24. We don't officially support older OS versions but have customers running on CentOS 7 with EOL caveats.
Step-by-step guide for the supported operating systems. Common pitfalls flagged: SELinux, AppArmor, firewall rules, sendmail-binary conflicts, log rotation. About 20-30 pages depending on OS.
Sample config.cf with VMTA pool template (3 pools: marketing, transactional, cold), receiver-aware throttling for the major receivers (Gmail, Outlook, Yahoo, Apple, AOL), DKIM signing block with key reference, FBL handling configuration, bounce categorisation tuning, log rotation setup.
About 800-1200 lines of config to start from. Customers customise from there. The starter config alone saves 20-40 hours of "what does this directive even mean" research that would otherwise be required for a from-scratch setup.
If migrating from Postfix, exim, or another MTA, we provide translation guidance for common configuration patterns. Not full migration management (that's our SaaS Migration product at €199); just translation reference for self-execution.
Telegram support during the installation period for license activation issues, configuration questions, and troubleshooting. One round of clarification questions on the configuration. Beyond 30 days, ongoing support bills at consulting rates (€199/hour) or via our managed services.
Hardware migrations happen. Server replaced, datacentre switched, infrastructure consolidated. We re-issue the license at no charge twice per lifetime. Beyond two re-issues, we charge €99 per re-issue to discourage license- sharing across multiple production servers.
License doesn't transfer between owners without our consent. If you sell your business, the license transfers with it (we update the licensee record); if you sell the license separately, we don't honour the sale.
Server hosting, OS installation, MailWizz frontend, ongoing operational management, 24/7 monitoring, FBL inbox setup, DNS records publication, blacklist removal, audit work. Those are separate products in our catalog. The license is the license.
For full setup including all ancillary work, our PowerMTA + MailWizz Setup (€299) bundles infrastructure setup with the license at a small discount. Common path: order both together for €1,749 and have working production infrastructure within 48 hours.
Direct enterprise licensing from Port25 / Bird (now part of Bird, formerly MessageBird) starts at $5,000+ per year with annual maintenance contracts. Their licensing model targets enterprise customers with 7-figure email programs. We offer the same software at one-time €1,499 through volume licensing arrangements that make per-license economics work for mid-market operators.
License is identical software, identical capabilities. The difference is the licensing path, not the product itself. Updates and patches available; support comes from us rather than from Port25 directly.
Postfix is free and works fine for low-to-medium volume (under 20K daily, single domain or simple multi-domain). PowerMTA outclasses it on receiver-aware throttling, VMTA pools, DKIM at wire speed, and operational tooling for serious sending. The feature matrix on this page details specifics.
Halon is closer to PowerMTA in capability. It's scripting- heavy (Lua-based) and quote-based pricing. Good fit for teams that want to write custom message-flow logic; PowerMTA is more declarative and configuration-driven. Both are production-grade.
Exim is widely deployed but has idiosyncratic configuration and limited modern receiver-aware features. Mostly seen in cPanel-style hosting. Not the right tool for serious commercial sending.
No. Single-server license tied to specific hardware identifier. For multi-server operations, you order multiple licenses. Discounts apply: past 5 licenses €1,299 each, past 10 licenses €1,099 each, fleet pricing available on quote past 25.
License re-issue is supported. We re-issue at no charge twice per lifetime. Beyond two, €99 per re-issue. Most customers don't reach the limit; common pattern is one re-issue every 2-3 years for hardware refresh, well within the included re-issues.
Yes. Software updates and patches available throughout the license lifetime. We mirror Port25's release cadence (typically quarterly minor releases, annual major releases). Security patches delivered as soon as available.
Updates delivered via Telegram or email when significant. Self-service download path for users who prefer to pull updates themselves.
Beyond the 30-day install support window, ongoing support bills at consulting rates (€199/hour). For ongoing operational support, our PowerMTA + MailWizz Managed (€49/mo) handles routine ops at fixed monthly cost.
For 24/7 enterprise support, Port25 / Bird's enterprise licensing tier remains the only option; we don't replicate that. Customers who need 24/7 phone-pickup support typically buy direct from Port25 or use a SaaS ESP rather than self-hosted.
Not in the traditional sense, but we offer a 14-day refund if the license doesn't work for your case. The conditions: you've installed it, configured it, run it under realistic conditions for at least 7 days, and can articulate why it doesn't fit. We've had this happen 3 times across hundreds of license sales; mostly when customer expectations didn't match what PowerMTA actually does.
For deeper evaluation, our PowerMTA License Rental (€99/mo) is the trial path. Pay one month, evaluate properly, decide whether to commit to lifetime. The rental fee can be credited toward lifetime purchase within 60 days.
Standard process: full payment on order (€1,499). Payable in any of our 11 supported cryptocurrencies. Self-hosted BTCPay, no third-party processor, no KYC. License delivered within 24 hours of payment confirmation.
For multi-license orders (5+), we accept staged payment: 50% on order, 50% on delivery of all licenses. Larger fleet orders negotiable. Contact via Telegram for fleet quotes.
Operators evaluating PowerMTA licensing can purchase directly from MessageBird (the current owner of PowerMTA, having acquired SparkPost which acquired Port25 which created PowerMTA originally). Direct licensing produces standard commercial terms with annual maintenance commitments and the support relationship managed directly with the vendor. Indirect licensing through us produces operational differences worth understanding.
Our licensing model bundles the PowerMTA license cost with operational support: deployment assistance during initial setup, ongoing configuration tuning, integration with our broader infrastructure stack, escalation path for vendor support when issues require it. The bundling produces lower total cost than separate direct licensing plus separate operational support, with the tradeoff that the licensing flows through us as the intermediary rather than directly to MessageBird.
The structural reasons operators choose indirect licensing through us include: simpler total billing without separate vendor relationships to manage, lower entry cost than direct licensing minimums for smaller operations, integration with our managed services that produce better outcomes than uncoordinated direct relationships, alignment with cryptocurrency payment that direct licensing does not support.
The structural reasons operators choose direct licensing include: existing relationships with MessageBird that have operational value beyond licensing, requirement for direct vendor support contracts that compliance frameworks impose, preference for separating infrastructure operations from licensing relationships, scale that justifies dedicated MessageBird account management which we cannot reproduce.
PowerMTA licensing through us follows volume tiers that match the operational requirements of different sender scales. The pricing structure reflects the underlying licensing cost plus operational support overhead.
Standard tier (EUR 299 monthly): covers single-instance PowerMTA deployment up to 5M monthly volume. Suitable for senders building dedicated infrastructure at moderate scale. Includes operational support for configuration tuning and integration with our broader infrastructure stack.
Professional tier (EUR 799 monthly): covers multi-instance PowerMTA deployment up to 50M monthly volume with multi-pool configuration. Suitable for ESP operations or large senders with diversified sending categories. Includes priority support and quarterly configuration reviews.
Enterprise tier (EUR 1,999 monthly): covers high-volume operations above 50M monthly with custom configuration requirements. Suitable for large ESPs or senders with complex multi-region operations. Includes dedicated technical contact and ongoing optimization work.
All tiers include the underlying PowerMTA license, MessageBird vendor support escalation when needed, our operational support for deployment and ongoing tuning. The pricing is fully inclusive; there are no additional charges for typical operational requirements.
Initial deployment runs 2-4 weeks from licensing agreement to production sending operation. The phases: requirements assessment to determine configuration needs, infrastructure provisioning with appropriate hardware allocation, PowerMTA installation and base configuration, integration with customer ESP control plane (MailWizz, Acelle, custom), validation testing through controlled sending, production cutover with monitoring.
Customer involvement during deployment is concentrated in requirements assessment and validation phases. The infrastructure and configuration work happens primarily on our side; customer-side coordination is required for DNS configuration, ESP integration parameters, and validation acceptance criteria. Total customer time during deployment typically runs 6-12 hours across the deployment window.
Ongoing operations require modest customer involvement. Monthly check-ins to review operational metrics and identify optimization opportunities, quarterly configuration reviews to ensure setup remains aligned with operational evolution, ad-hoc engagement for incidents or planned changes. Most months require under 2 hours of customer time beyond responding to automated alerts.
The transition from initial deployment to steady-state operations typically completes within 60-90 days. Operations during this transition involve more frequent tuning as the infrastructure adapts to actual customer sending patterns; operations after the transition stabilize with minimal ongoing configuration changes.
Customer support for PowerMTA licensing through us operates as a primary tier with vendor escalation rather than as a thin reseller passing requests to MessageBird. The structural difference matters because most operational issues resolve faster through our primary support than through vendor escalation, while issues genuinely requiring vendor involvement still escalate appropriately.
Primary support handles configuration questions, integration guidance, performance tuning, deliverability incident response, deployment assistance, version compatibility questions. The coverage matches what most customers actually need from PowerMTA support; vendor escalation typically applies only to license-related questions or specific software defects requiring MessageBird engineering involvement.
Response time commitments vary by tier: standard tier responds within 4 hours during business hours, professional tier responds within 1-2 hours during business hours, enterprise tier responds within 30 minutes any time. The commitments are operational rather than contractual SLAs; we treat them as performance targets that we measure and report on rather than legal obligations with associated penalties.
Escalation to MessageBird happens through our existing vendor relationships rather than requiring customers to establish their own MessageBird support channels. The escalation produces faster response than direct customer-vendor relationships in most cases because we have the institutional context and the vendor relationship history that direct customer requests would need to establish from scratch.
Telegram order takes 10 minutes. License delivered within 24 hours. Setup support available bundled at €299. For most senders past 50K daily volume, the license amortises within 6-18 months and keeps paying back over years of operation.
# Median Telegram response: 12 minutes during operating hours