On a freshly provisioned Netcup server, nc -vz gmail-smtp-in.l.google.com 25 times out—not because AS197540 blocks SMTP at the hypervisor, but because Netcup attaches a user-editable firewall preset to new instances. For how other clouds handle outbound SMTP, see our 2026 Port 25 Open VPS Provider Matrix; this runbook focuses strictly on taking a Debian 12 Netcup node from blocked port to production-grade dual-stack delivery.
Step 1: Unlock Outbound Port 25 & Set Dual-Stack PTR in SCP
Before touching Postfix or Docker, establish Forward-Confirmed Reverse DNS (FCrDNS) and clear the SCP packet filter. Note that servercontrolpanel.de (SCP) uses separate technical credentials from your billing account in customercontrolpanel.de (covered in the 0% VAT registration guide).
- Create forward DNS first: In your authoritative DNS zone, create an
Arecord formail.example.compointing to your dedicated IPv4 (152.53.xxx.10) and anAAAArecord pointing to the first host address in your routed/64prefix (2a03:4000:xxxx::1). Leave any Cloudflare proxy cloud grey (DNS-only). - Set both PTR records (
SCP → Network): Open your server insideservercontrolpanel.de, click Network, and entermail.example.com(without a trailing dot) as the Reverse DNS hostname for both152.53.xxx.10and2a03:4000:xxxx::1. Click Save. - Remove the SMTP filter (
SCP → Firewall): Open Firewall in SCP. Locate the defaultnetcup Mail blockrule group—which drops outbound TCP25,465, and587—delete or detach that preset while preserving your inbound SSH/HTTPS/IMAPS rules, and click Save. Outbound Port 25 opens across IPv4 and IPv6 within 10–15 seconds.
Step 2: Pin Static IPv6 ::1 in Debian 12 (Preventing Gmail 550-5.7.25)
The single most common Netcup mail failure happens on IPv6. Netcup routes an entire /64 subnet (2a03:4000:xxxx::/64) to your interface over gateway fe80::1. If Debian 12 configures IPv6 via SLAAC (iface eth0 inet6 auto) or enables RFC 4941 temporary privacy addresses, outbound connections to gmail-smtp-in.l.google.com originate from an address like 2a03:4000:xxxx:0:5054:ff:fe12:3456—which has no PTR record, triggering an instant 550-5.7.25 bounce from Google.
Lock Debian 12 (eth0 or ens3—verify your NIC name with ip -br link) to 2a03:4000:xxxx::1/64 explicitly in /etc/network/interfaces:
# /etc/network/interfaces (Debian 12 Bookworm on Netcup KVM)
source /etc/network/interfaces.d/*
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
iface eth0 inet6 static
address 2a03:4000:xxxx::1/64
gateway fe80::1
accept_ra 0
autoconf 0
privext 0
Disable kernel temporary addresses persistently so container bridges or secondary interfaces never rotate outbound IPv6 source addresses:
cat <<'EOF' > /etc/sysctl.d/60-mail-ipv6-static.conf
net.ipv6.conf.all.use_tempaddr = 0
net.ipv6.conf.default.use_tempaddr = 0
EOF
sysctl --system
systemctl restart networking
ip -6 route get 2607:f8b0:4004:c0b::1a
# Verify "src 2a03:4000:xxxx::1" appears in output
Step 3: RAM Sizing & MTA Configuration (Postfix, Mailcow, Stalwart)
Choose your Netcup SKU around memory footprint before deploying containers. Full mailcow-dockerized (ClamAV + Rspamd + SOGo + Dovecot + Postfix + MariaDB) holds 3.8 GB to 4.5 GB of RAM idle because ClamAV loads signature databases into memory.
| Mail Stack Architecture | Target Netcup SKU | RAM & Disk | Year-1 Net (0% VAT) / Gross (19%) | Voucher |
|---|---|---|---|---|
| Managed Zero-Ops Mailboxes (Plesk Cluster) | Webhosting 2000 | 4 GB Guaranteed RAM · 75 GB Mail + 75 GB Web SSD | €2.37/mo net / €2.82 gross (Forever) | #w2 (30% Lifetime) |
Stalwart Mail (Rust) or Mailcow (SKIP_CLAMD=y) | VPS 500 G12.5 | 4 GB DDR5 ECC · 64 GB NVMe | €6.52/mo net / €7.76 gross | #5e (-€5 Net, New Users) |
| Full Mailcow (ClamAV + Rspamd + SOGo) | VPS 1000 G12.5 | 8 GB DDR5 ECC · 128 GB NVMe | €11.17/mo net / €13.29 gross | #vps1 (1 Mo Free) |
| Full Mailcow + Co-Hosted Web / DB Containers | RS 1000 G12.5 | 4 Ded. Zen 5 · 8 GB ECC · 128 GB | €15.22/mo net / €18.11 gross | #rs1 (2 Mo Free) |
Model multi-container RAM headroom in the Server Sizer.
Option A: Standalone Postfix (/etc/postfix/main.cf)
For transactional relays, Docker-Mailserver, or native Debian Postfix + Dovecot setups, explicitly bind both IPv4 and IPv6 outbound SMTP sockets and enable opportunistic TLS 1.2/1.3:
# /etc/postfix/main.cf — Dual-stack Netcup AS197540 production baseline
myhostname = mail.example.com
mydomain = example.com
myorigin = $mydomain
inet_interfaces = all
inet_protocols = all
# Crucial: force outbound SMTP to match exact SCP PTR records
smtp_bind_address = 152.53.xxx.10
smtp_bind_address6 = 2a03:4000:xxxx::1
smtp_helo_name = mail.example.com
# Outbound & inbound opportunistic STARTTLS + modern ciphers
smtp_tls_security_level = may
smtp_tls_mandatory_protocols = >=TLSv1.2
smtp_tls_loglevel = 1
smtpd_tls_security_level = may
smtpd_tls_cert_file = /etc/letsencrypt/live/mail.example.com/fullchain.pem
smtpd_tls_key_file = /etc/letsencrypt/live/mail.example.com/privkey.pem
Reload Postfix with postfix check && systemctl reload postfix.
Option B: Mailcow Dockerized (/opt/mailcow-dockerized/mailcow.conf)
Because Mailcow routes outbound container traffic through Docker’s NAT bridge, you must set SNAT_TO_SOURCE and SNAT6_TO_SOURCE in mailcow.conf so Docker rewrites outbound packets to your PTR-verified addresses. On a 4 GB VPS 500 G12.5, either run single-binary Rust Stalwart Mail Server (~180 MB idle RAM with built-in JMAP/IMAP/SMTP/DKIM/DMARC) or disable ClamAV:
# /opt/mailcow-dockerized/mailcow.conf
MAILCOW_HOSTNAME=mail.example.com
MAILCOW_TZ=Europe/Berlin
# Pin Docker NAT egress to exact SCP Network PTR addresses
SNAT_TO_SOURCE=152.53.xxx.10
SNAT6_TO_SOURCE=2a03:4000:xxxx::1
# Set SKIP_CLAMD=y on 4 GB RAM (VPS 500); keep SKIP_CLAMD=n on 8 GB+ (VPS 1000 / RS 1000)
SKIP_CLAMD=n
SKIP_SOLR=y
ENABLE_IPV6=true
Apply changes cleanly with docker compose up -d.
Step 4: Copy-Pasteable Production DNS Zone Block
Every major receiver in 2026 (Gmail, Yahoo, Microsoft 365, GMX/Web.de) enforces strict alignment across RFC 7208 SPF, 2048-bit RSA (or Ed25519) DKIM, and RFC 7489 DMARC. Adapt the zone block below for example.com (replace placeholder IPs and the public key generated by Mailcow UI, Stalwart, or opendkim-genkey -b 2048 -d example.com -s dkim):
; --- Forward & MX Records (Proxy OFF / DNS-Only) ---
mail.example.com. 300 IN A 152.53.xxx.10
mail.example.com. 300 IN AAAA 2a03:4000:xxxx::1
example.com. 3600 IN MX 10 mail.example.com.
; --- Strict Dual-Stack SPF (-all rejects unauthorized senders) ---
example.com. 3600 IN TXT "v=spf1 ip4:152.53.xxx.10 ip6:2a03:4000:xxxx::1 -all"
; --- 2048-bit RSA DKIM Public Key (selector: dkim) ---
dkim._domainkey.example.com. 3600 IN TXT ( "v=DKIM1; k=rsa; s=email; "
"p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAx..." )
; --- DMARC Policy (start with p=quarantine; promote to p=reject after 14 days clean RUA) ---
_dmarc.example.com. 3600 IN TXT "v=DMARC1; p=quarantine; adkim=s; aspf=s; pct=100; rua=mailto:dmarc@example.com"
; --- MTA-STS & SMTP TLS Reporting (RFC 8461 / RFC 8460) ---
mta-sts.example.com. 3600 IN A 152.53.xxx.10
mta-sts.example.com. 3600 IN AAAA 2a03:4000:xxxx::1
_mta-sts.example.com. 3600 IN TXT "v=STSv1; id=2026112101"
_smtp._tls.example.com. 3600 IN TXT "v=TLSRPTv1; rua=mailto:tlsrpt@example.com"
To complete MTA-STS, serve https://mta-sts.example.com/.well-known/mta-sts.txt over valid HTTPS containing version: STSv1, mode: enforce, mx: mail.example.com, and max_age: 604800 (Mailcow’s built-in Nginx container serves this endpoint automatically once DNS points to the host).
Step 5: CLI Verification Before Pointing Production Domains
Run all three diagnostic checks via SSH on your Netcup node before migrating live user mailboxes:
# 1. Confirm FCrDNS (PTR -> Hostname -> A/AAAA) on both IPv4 and IPv6
dig +short -x 152.53.xxx.10
dig +short -x 2a03:4000:xxxx::1
# Both commands MUST output: mail.example.com.
# 2. Verify outbound Port 25 STARTTLS & Banner over IPv4 and IPv6 to Gmail MX
openssl s_client -4 -starttls smtp -connect gmail-smtp-in.l.google.com:25 -crlf -brief </dev/null
openssl s_client -6 -starttls smtp -connect gmail-smtp-in.l.google.com:25 -crlf -brief </dev/null
# 3. End-to-end authenticated submission + DKIM/SPF/PTR echo test via swaks
apt-get update && apt-get install -y swaks dnsutils
swaks --to check-auth@verifier.port25.com \
--from postmaster@example.com \
--server mail.example.com \
--port 587 --tls \
--auth-user postmaster@example.com
Finally, register your IPv4 address in Microsoft SNDS and Google Postmaster Tools on Day 1 to monitor reputation during volume warm-up, and review renewal notice windows in our 1-Month Contract & Cancellation Guide.
VPS 1000 G12.5
1 Month Free · Best-Seller Entry Production VPS (12M Term)