If you want to run Mailcow on a VPS without providing ID or a phone number, you can — but it requires careful provider choice and strict configuration to keep deliverability and security intact. Pick a no‑KYC or anonymous VPS provider that offers a dedicated IPv4 address and allows custom DNS/PTR records; that combination gives you the technical foundation Mailcow needs to send reliable mail without exposing your identity.
You’ll also need to plan DNS, DKIM/DMARC/SPF, PTR setup, and ongoing IP reputation management before you deploy. The article VPS for Self-Hosting Mailcow Without Identity Verification or Phone Number walks through how to evaluate anonymous VPS options and how to configure Mailcow so your installation stays private, functional, and compliant with anti‑abuse requirements.
Choosing Anonymous VPS Providers
You need a provider that accepts privacy-preserving payments, avoids KYC, and sits in a jurisdiction with strong protections against data requests. Prioritize payment methods you can use without linking to your identity, clear signup policies that omit ID/phone checks, and countries with limited mandatory data retention or hostile legal reach.
Privacy-Focused Payment Methods
Use cryptocurrency options that you can spend without reconnecting to your identity. Bitcoin (on-chain) and Monero are common; Monero offers stronger on-chain privacy but fewer providers accept it. If you use Bitcoin, route funds through a reliable coin mixer or CoinJoin service, then transfer to the provider to reduce traceability.
Consider prepaid crypto gift cards, open-source custodial wallets, or non-custodial wallets where you control keys. Avoid using bank transfers, PayPal, Apple Pay, Google Pay, or credit cards for anonymous purchases because these create direct links to your real identity. Keep receipts minimal and avoid using the same payment channel for personal and anonymous spending.
No-KYC Signup Platforms
Look for vendors that explicitly advertise “no KYC” or “no ID required” in their terms of service. Check the signup flow before you pay: if the registration asks only for an email and a password, that’s a good sign. Use disposable email addresses (aliasing or burner mail) and avoid phone number fields entirely.
Read the provider’s acceptable-use policy and logging policy. Prefer hosts that state they keep minimal or no identifiable logs and that accept anonymous payment forms. Verify through third-party reviews and recent user reports that the provider hasn’t changed KYC policies; policies can shift when regulations tighten.
Country and Jurisdiction Considerations
Choose hosting locations where local law doesn’t force providers to retain subscriber identity or mandatory logs for long periods. Countries like Switzerland, Iceland, and some Baltic states often provide stronger privacy protections, but always check current local laws rather than assuming status remains static.
Avoid hosts based in countries with broad surveillance mandates, easy cross-border takedown obligations, or frequent cooperation with major intelligence alliances. Also consider physical risks: natural disasters, stable power and network infrastructure, and the provider’s data center resilience affect uptime and your mail server’s delivery reliability.
Setting Up Mailcow Securely
You will install Mailcow on a VPS with a static public IP, configure DNS and authentication records, and harden the server and Mailcow services. Focus on correct DNS, TLS, and regular backups to maintain deliverability and resilience.
Installing Mailcow on VPS
Choose a Debian/Ubuntu LTS VPS with at least 2 vCPU, 4 GB RAM, and 50 GB disk; increase resources for larger mailboxes. Assign a dedicated public IPv4 (Mailcow works best with one primary IP) and a stable hostname (mail.yourdomain.tld) that matches your certificates.
Update the OS, install Docker and Docker Compose from official repositories, then clone Mailcow’s repository and run the installer. During setup, provide your domain, admin email, and FQDN, and let Let’s Encrypt handle TLS or supply your own certificates. Configure a firewall (ufw/iptables): allow TCP 25, 80, 443, 587, 993 and drop unused ports.
After deployment, log into the admin UI, create mailboxes and domains, and enable DKIM signing in Mailcow’s config so outgoing mail is signed automatically. Monitor Docker container health and automate updates for Mailcow and the host OS.
Email Deliverability Best Practices
Set DNS records precisely: an A record for the mail host, MX pointing to that host, SPF allowing your VPS IP or outbound relay, DKIM public key TXT for each domain, and a DMARC TXT with a monitor policy (p=none) initially. Use a short TTL while testing, then increase it once stable.
Configure reverse DNS (PTR) for your VPS IP to match your mail hostname; many providers require a support ticket to set PTR. Limit simultaneous SMTP connections and enable rate limits to avoid blacklists. Watch blacklists and run regular deliverability tests with tools that check spam score, header alignment, and authentication.
Consider using a secondary SMTP relay provider if your IP has poor reputation or is on home/residential ranges. Maintain clean mailing lists: remove bounces, honor unsubscribe requests, and throttle bulk sends. Log and inspect mail queues and headers to debug delivery failures.
Data Protection and Backups
Encrypt Mailcow backups and store them offsite on a separate VPS, S3-compatible object storage, or encrypted external volumes. Include Docker volumes, Postfix queues, Dovecot maildirs, MariaDB, and LDAP in backup scripts to ensure full recovery.
Schedule daily incremental and weekly full backups. Test restores regularly on a staging VPS to verify integrity and restore procedures. Protect backups with access controls and rotate encryption keys when personnel changes occur.
Harden access: disable root SSH, use key-based auth, run fail2ban, and restrict admin UI access by IP or 2FA. Keep audit logs and monitor disk usage, mail queue size, and database growth to catch issues before they impact service.
