Mailboxes that work in Outlook, on the same domain as everything else.
Real IMAP and SMTP mailboxes on your own domain, from €2.99 a month. Outlook, Apple Mail, Thunderbird and mobile configure themselves, and migration from Google Workspace or Microsoft 365 cannot break the mail you already have.
- #IMAP
- #SMTP
- #MX
- #Autodiscover
- #Migration
- #EU-hosted
Real IMAP, not a web-only inbox
IMAP on 993, submission on 587 and 465, MX inbound on 25. Whatever mail client your team already uses keeps working, including the one on their phone.
Configures itself
Autodiscover for Outlook, autoconfig for Thunderbird, and SRV records for the rest. Where a client cannot discover, the setup is two fields: the address and the password.
Migration that cannot lose mail
Every mailbox exists here before anything moves, the sync runs while your old MX is still live, and a seven-day dual-delivery window catches whatever arrived at the old server during propagation. Cut-over is never automatic.
Compromise detection
Sudden volume, an unusual mix of recipient domains, or a send from a country that does not match the login history freezes that mailbox's outbound, invalidates every session and app password, and holds the queued messages for 24 hours so a false positive is recoverable.
Storage that is actually yours
10, 25 or 50 GB per mailbox. Bodies and attachments are envelope-encrypted before they touch object storage, with a key per workspace — so a storage breach yields ciphertext.
Aliases, forwarding, app passwords
Unlimited aliases, catch-all, forwarding rules and sieve filtering. App passwords for clients that cannot do modern auth, revocable one at a time.
Moving your mail without a bad afternoon.
Changing MX is the one destructive step in onboarding. The wizard is built so the destructive step comes last, and only after everything else is verified.
- [01]
Read the current state
We look up your existing MX, SPF, DMARC and DKIM first and identify your current provider before suggesting anything.
- [02]
Create and sync
Every mailbox is created here with the same address, then synced over IMAP while your old provider keeps handling live mail.
- [03]
Cut over
Lower the TTL a day ahead, then switch MX. You press the button; nothing happens automatically.
- [04]
Dual-delivery, then verify
Seven days of pulling from the source, a delta sync, and a per-folder message count you can check against the old system.
Eight steps, in this order, every time.
The most damaging thing an email platform can do is tell a small business to add an MX record and take down the mailboxes they already use. So the wizard reads your DNS before it says anything, and the irreversible step is step five of eight.
- [01]Create every mailbox here first, with the same addresses as the source
- [02]Full IMAP sync from the source provider while the old MX is still live
- [03]You keep using the old provider throughout — nothing has moved yet
- [04]Lower the source MX TTL to 300 seconds, 24 hours in advance
- [05]Cut MX over to mx1 and mx2.mailhaap.com
- [06]Seven-day dual-delivery window: we keep pulling from the source to catch anything that arrived during propagation
- [07]Delta sync, then a verification report with message counts per folder per mailbox
- [08]Decommission checklist for the old provider
Client settings
For anything that cannot discover its own configuration, these are the only values needed. The dashboard shows them with copy buttons per field.
IMAP
host imap.mailhaap.com
port 993
security SSL/TLS
username [email protected]
SMTP (submission)
host smtp.mailhaap.com
port 587 (STARTTLS, required)
465 (implicit TLS)
username [email protected]
Authentication normal password, or an app password- Protocols
- IMAP 993, submission 587 / 465, MX 25
- IMAP latency, p50 / p99
- 15 ms / 100 ms
- Inbound, MX accept to mailbox
- 1 s p50, 5 s p99
- Storage per mailbox
- 10 / 25 / 50 GB
- Price per mailbox / month
- €2.99 / €4.99 / €6.99
- Fair-use sending
- 2,000 recipients per mailbox per day
- Recipients per message
- 100 by default
- Encryption at rest
- AES-256-GCM, per-workspace key, per-object derivation
- Inbound authentication
- SPF, DKIM, DMARC and ARC verified on every message
- Spam and virus scanning
- Built in, with the attachment pipeline from the API plane
- TLS
- Mandatory for submission and IMAP; opportunistic inbound with MTA-STS offered
- Data location
- EU — Falkenstein and Helsinki
One domain identity for your team, your app and your marketing.
Your mailboxes, your transactional email and your campaigns share one DNS setup, one suppression policy and one reputation view — while staying three isolated sending planes, so a compromised mailbox blasting spam cannot take your API down with it.