CLOUD SERVER FOR EMAIL

Infrastructure Specifications

Technical Specifications for Managed Email Infrastructure

Technical senders evaluating email infrastructure need specific, verifiable specifications — not marketing language. This page documents the exact software versions, hardware configurations, datacenter specifications, and configuration parameters available in Cloud Server for Email's managed infrastructure environments.

Specifications are current as of April 2026. Software versions are updated regularly; contact infrastructure@cloudserverforemail.com to confirm current versions for a specific engagement.

Software Stack

ComponentSoftwareCurrent VersionUpdate Policy
Mail Transfer AgentPowerMTA (Port25/Zeta)5.5.x (current release)Minor updates within 30 days of release; major versions tested before deployment
Campaign PlatformMailWizz EMS2.x (current stable)Quarterly major updates; security patches within 7 days
Operating SystemAlmaLinux 9 / Ubuntu 24.04 LTSCurrent LTSSecurity patches automated (kernel monthly)
Web Server (MailWizz)Nginx + PHP-FPMNginx 1.24+, PHP 8.2+Security patches within 7 days
DatabaseMySQL 8.0 / MariaDB 10.11Current stableMinor: automated; major: tested 30 days
DNS/PTR ManagementRIPE NCC allocationN/APTR records updated same-day upon request
SSL/TLS (tracking domains)Let's Encrypt / custom certTLS 1.2 minimum, TLS 1.3 preferredAuto-renewal 30 days before expiry
Firewallnftables / UFWCurrent OS releaseRules updated as required for security

Hardware Specifications by Plan

SpecificationFoundationProductionEnterprise
CPU4 cores / 2.8 GHz+8 cores / 3.0 GHz+16+ cores / 3.2 GHz+
RAM16 GB ECC32 GB ECC64 GB ECC
Storage (OS + App)240 GB NVMe SSD480 GB NVMe SSD960 GB NVMe SSD RAID-1
Storage (PowerMTA Spool)240 GB NVMe (dedicated partition)480 GB NVMe (dedicated)960 GB NVMe RAID-1 (dedicated)
Network uplink1 Gbps dedicated1 Gbps dedicated10 Gbps dedicated
Network redundancySingle uplinkSingle uplinkDual uplink (BGP failover)
Power redundancyN+1 datacenter UPSN+1 datacenter UPS2N datacenter UPS
Hardware generationCurrent gen (< 2 years)Current gen (< 2 years)Current gen (< 1 year)

Datacenter Specifications

SpecificationDetails
Locationwith EU and global infrastructure, European Union
Tier classificationTier III (concurrent maintainability)
Power availability99.982% per datacenter SLA
CoolingN+1 precision cooling
Physical security24/7 on-site security, biometric access, CCTV, mantrap entry
Fire suppressionGaseous suppression (FM-200 / Novec 1230)
Network carriersTelia, Elisa, local IXP (TLL-IX) with DE-CIX Frankfurt peering
IP jurisdictionRIPE NCC (European Internet Registry) — the EUn allocation
Legal jurisdictionRepublic of the EU (EU member state)
Data protection lawGDPR (EU Regulation 2016/679) — applies directly

Network and IP Infrastructure

IP Address Allocation

ParameterStandardNotes
IP registryRIPE NCCEuropean allocation — verifiable via whois
IP assignment typeStatic dedicatedIPs assigned exclusively to client for contract duration
Minimum IP allocation1 IPFoundation plan includes 2 IPs
Maximum IPs per serverUnlimited (practical limit: 16–20)Subject to routing table size
IPv4 availabilityYesAll sending IPs are IPv4
IPv6 availabilityYes (optional)Available for sending but not required
rDNS (PTR record)Configured for all IPsMatches PowerMTA EHLO hostname; same-day update capability
FBL enrollmentYahoo, ComcastRegistered per client domain/IP combination

Connectivity

  • Direct peering at TLL-IX (Tallinn Internet Exchange) — low-latency access to Baltic and Nordic ISPs
  • DE-CIX Frankfurt peering via carrier — low-latency access to German ISPs (GMX, T-Online, Web.de)
  • AMS-IX Amsterdam peering via carrier — access to Dutch and Western European ISPs
  • Transit connections: Telia Carrier (AS1299), providing global IPv4 and IPv6 reach
  • Average latency to Gmail (Google): 18–22ms; Outlook (Microsoft): 20–25ms; Yahoo: 95–110ms (US-hosted)
  • Average latency to European ISPs: GMX/Web.de: 12–18ms; Orange.fr: 22–28ms; T-Online: 18–24ms

PowerMTA Configuration Parameters

Default Per-ISP Domain Block Configuration (Production)

The following parameters represent the default starting configuration for new infrastructure deployments. These are adjusted based on IP reputation data within the first 30 days of operation:

ISPmax-smtp-outmax-msg-rateretry-aftermax-msg-per-conn
Gmail (gmail.com)8 (HIGH rep)3,500/h15m100
Microsoft (outlook.com)52,000/h25m50
Yahoo (yahoo.com)62,500/h20m100
GMX / Web.de41,500/h30m50
T-Online (telekom.de)31,200/h30m50
Orange.fr31,000/h30m30
Default (all others)3800/h30m30
These are starting values for HIGH IP reputation. Production values are adjusted based on observed deferral rates and Postmaster Tools/SNDS data. Lower values are used during IP warming and for IPs at MEDIUM or LOW reputation.

Authentication Configuration

AuthenticationStandardImplementation
SPFPASS requiredSPF record includes all sending IPs; SoftFail (~all) minimum; Fail (-all) where possible
DKIM2048-bit RSA, per-domain keysSeparate key per sending domain; rotation every 12 months minimum; PowerMTA native signing
DMARCp=reject target (p=none initially)Start at p=none with rua reporting; advance to p=quarantine within 60 days; p=reject within 90 days
BIMIOptional (VMC required)Configured upon client request; requires DMARC at enforcement and Verified Mark Certificate
PTR/rDNSRequired for all IPsForward-confirmed reverse DNS for every sending IP; matches PowerMTA EHLO hostname
TLS (outbound)Opportunistic TLS (STARTTLS)TLS 1.2 minimum; TLS 1.3 where supported by receiving server
TLS (MailWizz tracking)RequiredLet's Encrypt or custom certificate; HTTPS enforced for tracking domains

Monitoring Infrastructure

Automated Monitoring Systems

  • PowerMTA accounting log real-time streaming: each delivery event logged to accounting CSV with 200ms maximum write latency
  • Automated deferral rate calculation: hourly per-ISP deferral rate from accounting log; alert triggers at 8% sustained for 2 hours
  • Google Postmaster Tools API integration: domain reputation and spam rate checked daily at 08:00 CET
  • Microsoft SNDS API: IP status checked daily at 08:30 CET; immediate alert on Red status
  • Blacklist monitoring: all sending IPs checked against 50+ lists every 6 hours; immediate alert on new listing
  • MailWizz cron job monitoring: execution confirmed every 5 minutes; alert if cron job fails to run within 10 minutes of schedule
  • Server health monitoring: CPU, RAM, disk utilization, network throughput checked every 60 seconds
  • SSL certificate expiry monitoring: alert at 30 days, 14 days, 7 days before expiry

Backup and Recovery

WhatFrequencyRetentionRecovery Time Target
PowerMTA configuration filesDaily30 days< 1 hour
MailWizz application + configDaily30 days< 2 hours
Subscriber database (MySQL)Daily incremental, weekly full90 days< 4 hours
DKIM private keysImmediately on creationIndefinite (encrypted)< 30 minutes
PowerMTA accounting logsNot backed up (ephemeral operational data)N/AN/A
Server snapshotsWeekly4 weeks< 30 minutes (full server restore)
Custom Specifications Available

Enterprise clients with specific requirements — different server locations within the EU, custom hardware configurations, specific software versions, or dedicated network segments — can discuss custom specifications during the technical assessment process. Contact infrastructure@cloudserverforemail.com for custom infrastructure requirements.

Discuss Infrastructure Requirements

Cloud Server for Email operates managed PowerMTA + MailWizz infrastructure from EU servers.
Dedicated IPs, daily monitoring, GDPR compliance by design.

Managed Infrastructure

PowerMTA + MailWizz. EU servers. Daily monitoring. GDPR by design.

Request Assessment