Operations

Security updates in practice: our email system

Coflnet β€’
#operations#security-updates#php#maintenance
Mail server with an envelope, shield and wrench illustrating security maintenance.

You want to get work done with your application. Reviewing security warnings, identifying affected components and installing updates takes additional time. When we operate your platform, we handle these tasks within the scope we agree with you.

Our email system: temporarily offline, upgraded within four hours

Following the recent PHP security warning, we took our own email system temporarily offline and completed the upgrade within four hours. Taking it offline was a deliberate protective step during the upgrade.

The PHP security advisory of 21 October 2026 explains the background: two critical vulnerabilities could allow attackers to execute code on a server without logging in. The PHP team released fixes and urged users to update immediately.

On 23 October, PHP published a follow-up notice about session upload progress. Mailcow had already disabled this unused feature in its October update. Checking our running installation confirmed session.upload_progress.enabled = Off, so this notice required no additional change. That check is part of maintaining a service: what matters is whether new guidance affects the configuration actually in use.

What we handle in ongoing operations

For the systems we maintain, an update involves more than changing a version number:

  • Check exposure: Which components are affected, and how urgently is a change needed?
  • Choose the response: Can the update wait for a maintenance window, or is immediate action, potentially including a temporary shutdown, needed?
  • Update and verify: Roll out the change, test important functions and continue monitoring the service afterwards.

That saves you from tracking security warnings and technical dependencies yourself. We coordinate decisions affecting your work according to the responsibilities agreed with you.

What the monthly retainer covers

Our operations and support agreement sets out the systems, security updates and support work included. It also defines responsibilities, response times and how maintenance interruptions are handled. Four hours describes this particular response; we agree binding times for your platform separately.

If you want us to take over operations, start by telling us which application you use and when an interruption would be most disruptive. That gives us a basis for agreeing the scope of operations and maintenance.

Next step: a one-hour consultation for €150

60 minutes with one of our managing directors about your project – our regular hourly rate, credited against a follow-up project. For businesses and founders.