First steps with your managed email infrastructure
This guide is for new Cloud Server for Email infrastructure clients. It covers what happens after your service agreement is signed, what we configure on your behalf, and what you need to provide or configure on your side to begin sending.
Upon provisioning, you receive: SSH access credentials (key pair — we generate the key pair and provide the private key securely), server IP address, and access to your PowerMTA HTTP management interface (localhost access only by default for security).
# Connect to your server
ssh -i your-key.pem user@YOUR.SERVER.IP
# Check PowerMTA status
pmta show status
# View queue
pmta show queue
# View recent accounting log
tail -50 /var/log/pmta/acct.csvMailWizz is accessible at your server IP or custom domain. Initial credentials are provided in the onboarding email. Change the admin password immediately upon first login.
PowerMTA's HTTP management API runs on port 8080, restricted to localhost by default. Access via SSH tunnel:
# Create SSH tunnel to access PowerMTA API
ssh -L 8080:localhost:8080 user@YOUR.SERVER.IP
# Then access in browser or via curl:
curl http://localhost:8080/status.jsonSend a test email from MailWizz to a personal Gmail account. Check the received email headers for: Authentication-Results showing dkim=pass and spf=pass. This confirms DKIM signing and SPF are working correctly.
Add your sending domain to Google Postmaster Tools (postmaster.google.com). Verify domain ownership by adding a TXT record (we will provide the verification code). This gives you inbox placement data for Gmail.
Register your sending IPs at Microsoft's Smart Network Data Services (sendersupport.olc.protection.outlook.com). This provides IP reputation data for Outlook.com delivery.
In MailWizz, your first campaign should go only to subscribers who opened or clicked in the last 30 days. We configure PowerMTA to enforce volume limits during warming — do not attempt to bypass these limits.
Send to your 30-day active segment. Review Postmaster Tools the following morning for spam rate and domain reputation. Contact us at infrastructure@cloudserverforemail.com if any metric looks unexpected.
Before sending your first production campaign: (1) Authentication headers verified via test email, (2) Postmaster Tools domain verified, (3) SNDS registration submitted, (4) Warming schedule reviewed with Cloud Server for Email team, (5) Segment filtered to 30-day openers only.