Fix PTR & Webmail on Hetzner
Budget: $30 – $250 USD
I run a Linux server on Hetzner with CyberPanel and need an email-centric tune-up to stop Gmail rejections and smooth out daily use.
What’s happening now
• Gmail bounces my messages with “550-5.7.25 … no PTR record” even though reverse DNS was set in Hetzner. I have not yet verified that the PTR actually resolves or matches the forward record.
• Outlook on Windows 11 won’t connect reliably—accounts time-out or prompt for passwords in a loop.
• I would like webmail to load through a clean URL such as webmail.example.com instead of :8090 or any other port, and I’d like it running on the Snappy webmail client.
What I need from you
1. Audit and correct DNS: be sure the PTR, A, SPF, DKIM and DMARC work together so Gmail accepts mail.
2. Test and confirm end-to-end delivery to Gmail with proper headers (no 550 errors, passes Google Postmaster tools).
3. Diagnose and resolve the Outlook-Win 11 connection problem, ensuring IMAP/SMTP/SSL settings work without repeated prompts.
4. Deploy Snappy webmail under its own sub-domain with valid SSL so users simply visit https://webmail.example.com.
5. Hand over a brief summary of changes plus any commands or panel paths so I can repeat the steps later.
6. I’m open to occasional future maintenance, so keep the configuration clean and document anything custom.
CyberPanel, Postfix, Dovecot, Let’s Encrypt, and Hetzner’s DNS console are already in place; feel free to bring whatever tools—dig, nslookup, mail-tester, OpenSSL—you prefer.
I consider the job complete when a test message lands in Gmail’s inbox without warning, Outlook syncs flawlessly, and webmail opens over HTTPS from the new sub-domain.
What’s happening now
• Gmail bounces my messages with “550-5.7.25 … no PTR record” even though reverse DNS was set in Hetzner. I have not yet verified that the PTR actually resolves or matches the forward record.
• Outlook on Windows 11 won’t connect reliably—accounts time-out or prompt for passwords in a loop.
• I would like webmail to load through a clean URL such as webmail.example.com instead of :8090 or any other port, and I’d like it running on the Snappy webmail client.
What I need from you
1. Audit and correct DNS: be sure the PTR, A, SPF, DKIM and DMARC work together so Gmail accepts mail.
2. Test and confirm end-to-end delivery to Gmail with proper headers (no 550 errors, passes Google Postmaster tools).
3. Diagnose and resolve the Outlook-Win 11 connection problem, ensuring IMAP/SMTP/SSL settings work without repeated prompts.
4. Deploy Snappy webmail under its own sub-domain with valid SSL so users simply visit https://webmail.example.com.
5. Hand over a brief summary of changes plus any commands or panel paths so I can repeat the steps later.
6. I’m open to occasional future maintenance, so keep the configuration clean and document anything custom.
CyberPanel, Postfix, Dovecot, Let’s Encrypt, and Hetzner’s DNS console are already in place; feel free to bring whatever tools—dig, nslookup, mail-tester, OpenSSL—you prefer.
I consider the job complete when a test message lands in Gmail’s inbox without warning, Outlook syncs flawlessly, and webmail opens over HTTPS from the new sub-domain.