Managed Servers (KVM VPS)

rspamd v4 has been brought to life (after determining the cause of it not filtering as the .spamassassin user folder not being given the correct perms on-restore into DA from cP). Incoming emails are now filtered!

SSL via Let’s Encrypt is mostly resolved. Our team will be going through domain-by-domain through this weekend to manually ensure every problem domain that isn’t suspended and does resolve, has automated SSL.

Backups are being finalised this week. We’ll be in contact again via this advisory when it’s visible in DA.

Re: AutoSSL Ordering Enablement

This has been manually fixed on all machines, aside from straggler domains. For stragglers, most of the time there’s a valid explanation - such as the account being suspended or DNS not pointing to your server. Please let us know if you encounter any domains with expired/broken SSL where DNS does point to your server, etc.

Re: SPF ip6 & include (365/Gmail) parts

We have fully processed all zone files (machine by machine) to rectify these common issues. Part of this has included working with DA to help them improve their conversion process. Fixed serials are 10/11 on the day.

Re: Backups & rspamd: On-going final work

With rspamd v3/v4, most machines are filtering nicely whereas there are some that are not yet filtering incoming emails. This is being investigated by senior staff now and we await their feedback shortly. With backups, the system integrates across all levels so we have been testing and are gradually deploying now.

Thank you for your patience. We’ll continue to finalise everything ASAP, taking care as we do.

Packages (DA) and Resource Allocations (LVE/CL) have been set & applied on all client machines.

Branding overrides including logos & icons have been deployed for clients where we have assets!

Next focuses which will allow us to close this out: Expose backups via GUI & configure rspamd.

Many thanks for your patience throughout. We’re very glad to have made the shift.

Packages are being deployed overnight into the morning, following successful testing this weekend.

There’s no longer a need to prefix the packages with your login username, so it’s now just level# for each, etc.

Nameservers (DNS) have all been cutover to run through DirectAdmin clustering. If you’re seeing a zone serial of 2026032001 or greater, then you’re seeing a zone that is being served by DA.

Our focus over the weekend is exposing backups via the GUI, and refining allocations & resources to suit each client’s packages better. This should help to bed down the new platform.

Spam Filtering is then being looked at, now that we have a better understanding of how the routing works with rspamd vs SpamAssassin. We’re excited for the benefits it brings.

Thank you again for your patience throughout.

Please find below the main documentation for DA, for both your usage and your end clients’.

1. https://evo.site-helper.com/ for end-user documentation
2. https://docs.directadmin.com/changelog/ for release info

Currently our focus is on leveraging the need to replace NS2 instances as a way to soft-cutover DNS (cP to DA).

Now we’ve almost finishing the tooling required to resolve some long-standing (SOA/NS), migration-caused (dupe v6) and now-irrelevant (cP/dav) issues and legacy across the zone files.

We’re taking the opportunity to resolve problems, sanitise zones and then process the cutovers. This lets us ensure NS2-DA takes over the role from NS2-cP, compare responses against NS1-cP, finalise NS2 wave, then do the same process again for all NS1 instances. We’re doing this by-client per-nameserver, all NS2 then all NS1.

Thank you for your continued patience. We’re now onto final action items before closing this out.

1. DNS has not been cutover as yet. We’re working through testing outcomes & fixes before progressing as we do not want to rush the cutover. There are duplicate IPv6 records to flatten beforehand as an example.
2. Full Domains (via Domain Setup) should replace Domain Pointers (“Parked Domains”) in your usage, as Pointers are not as functional as Parked Domains were in the old panel. Redirection/forwarding/etc needs full.
3. Backups are yet to be centrally exposed. These will be available in User and Reseller interfaces inside DA.
4. rspamd replaces SpamAssassin, and is yet to have inbound mail routing diverted through it at this stage.
5. Packages & Resource Limits are being gradually deployed to monitor behaviour, adjust and finalise.
6. AutoSSL is enabled globally however for any straggler domain names, please report them to us.

PHP options, extensions and versions have all been deployed at levels that make sense for agencies. From there you can use “Select PHP Version” (CloudLinux alt-PHP) to adjust options and extensions per-user as well. :-)

White-label branding has been partially applied to client servers where we have your logo (on-dark and on-light) on-file already. Please send your PNG/SVG files & brand colours across so we can improve your UX. Thanks!

We’ve resolved most quirks and curiosities, and are working through final odds and ends. Thank you.

Please let us know as you stumble upon anything, however our testing pass rates are increasing to near-100%.

2nd half was larger, and is now fully transitioned with 100% of machines now converted from cP to DA.

We’re now stepping up our testing, adjustment and tuning works - systematically working through it all.
Please continue to let us know of any quirks you’re seeing - we will work through every single report.

Thank you for your continued patience. Clients are already enjoying the positive changes, like:

• NGINX to OpenLiteSpeed
• SpamAssassin to rspamd
• Mailman to Majordomo
• MariaDB v10.6 to v10.11
• by-domain public_html
• ea-PHP to CL’s alt-PHP
• White-label branding!

1st half of servers have now been successfully transitioned to DirectAdmin. Testing continues.

2nd half of servers are now exiting from configuration into data migration phase.

We appreciate your continued patience. Thank you!

Thank you for your patience, we’re very nearly there! Very excited for you to realise the benefits.

• 1st half servers are migrated to, and will be cutover to before start-of-business in the morning.
• 2nd half servers are deployed, and will be fine-tuned then migrated to in the afternoon.

Half the remaining servers are close to finalised now. The second half will be later today/tonight.
From there we have testing rounds to iterate through, exceptions to resolve, tickets with clients, etc.

Thank you so much for your patience. We’re looking forward to the new platform to serve you from.
Client feedback so far has been positive, especially with regard to website performance - worth the change.

Many thanks once again for your continued patience.

We’ve launched a server-agnostic Webmail here: https://webmail.au

Our email auth patch is now deploying across all client machines. Please let us know if email issues persist.

Machines will be overhauled over the weekend, with testing and updates being sent through as we go. Thanks.

Final adjustments are being made to our deployment systems for the new platform based on learning from testing & our pilot client on-boarding, and we expect to start transitioning clients this afternoon.

Thank you for your patience. We’re working to ensure the best outcomes for our clients, and are excited to finalise this - especially considering the performance gains that we’ve confirmed thanks to OpenLiteSpeed.

Machines running on our normal Web Stack will be upgraded to the new platform this week.
This system leverages OpenLiteSpeed and has been shown to improve website performance nicely.

If you need help resolving caching or other issues in the interim, please continue to request support.
We appreciate your patience and are approaching this work in stages (by client) to minimise impact.

If you’re having problems with email, please ticket with logs/screenshots/etc so we can assist/prioritise you.

5 years of planning & 10 years of desire are coming together here. Sadly though, it’s sudden & unexpected.
Thank you for your patience throughout this impact as we work towards the best outcomes for our clients.

Thank you again for your continued patience. We’ve made headway over the weekend.

• We are in the final stages of testing a fix to both sides of the problem with a pilot client.
• Separately we’re finalising a drop-in patch for the email authentication problem only.

Work continues on ensuring we’ve got you back to normal operations ASAP.

Please let us know what else we can be doing for you. Thanks.

We appreciate your continued patience as we work through these problems. Thank you.

The email issue for a small subset of machines is related to the Dovecot v2.4 upgrade, and cPanel proxying auth via their internal cpauthd/cpsrvd binaries instead of “as usual” via passwd/shadow files and so on. There is a caching fault within cpauthd which leads to spurious “user unknown” errors for perfectly valid mailbox users - exploring the code responsible shows that it was AI-made without proper understanding by cP’s product team.

The access problem we’re now re-focusing on, targeting normal service by/on Monday at this time.

Many thanks for your patience today. We’re still working on this problem with cPanel+WHM.

There is a new security update that has been pushed out to all release tiers.

Changelog for cPanel+WHM 132.0.25:

- Security Case SEC-67580: Fix cPanel File Download Endpoint IDOR Vulnerability (CVSS Score: 6.5)
- Implemented CPANEL-47921: Added a new tweak setting to control web server log archive retention and a script to perform automated cleanup.

There may also be intermittent email issues, potentially due to the newly forced update to CSF (firewall).

ConfigServer Security & Firewall (CSF) 16.08-1:

"As of August 31, 2025, the developers of CSF (Way to the Web Limited) no longer maintain or support it. They have released CSF under the GPLv3 license.

On supported cPanel & WHM versions, WebPros International, LLC maintains its own version of CSF for security and stability updates only. WebPros do not provide help with CSF configuration or troubleshooting."

Engineers will continue investigating, with most focus on the email component which has just been raised.