Recent content by MiloPesk

Just to add to what Sebahat suggested. We have the same setup on a few cluster nodes and the trick that worked for us was indeed creating mail.{domain} as a separate A record then repointing the MX. Took maybe 30 min per domain to migrate, mostly via the API. For the SPF, dont forget to update...

Supplementing Sebahat's loop script — if you're running this on a big Plesk setup, be aware that plesk bin dns --remove / --add can be slow when you have hundreds of domains (DNS zone file reload per operation). For 200+ domains I batch-edit the zone files directly with sed, then run plesk...

For anyone landing here later — the distinction is worth documenting because it's a real footgun on Plesk 18.0.7x+ : "Mail Server Settings" DNSBL : injected into Postfix smtpd_recipient_restrictions as reject_rbl_client zone.example.com. Blocks at SMTP transaction time, before the mail enters...

Same evaluation path here — tested all three over the last 18 months on different Plesk servers. Imunify360 (single user license) is the best bang for buck if your threat model is PHP webshells + backdoored WP sites. The ModSecurity ruleset + PHP callback hooks catch 90% of cryptominers on...

The 127.0.0.1 SPF flag on mxtoolbox is almost always a false positive on Plesk servers using postfix with smtp_bind_address. What happens : mxtoolbox injects a synthetic header from its own test transaction, the return-path shows the loopback because the submission was relayed through the local...