Upgrade - Maintenance mode
Idea shared by Sabatino - Today at 9:11 AM
Proposed
Hi everyone.
Like all of you, I’m facing the need to update to version 9735.

I’ve never had issues with updates, but I always get a bit nervous doing them—naturally, I take snapshots, backups, etc., beforehand.

If something goes wrong, I can restore the system. However, restoring—even from a snapshot—isn't painless, because there’s inbound and outbound traffic on the server in the meantime.

I was thinking there might be a better way.
ST could provide a feature to put SM into maintenance mode. In this state, everything would still function, but it wouldn't accept any incoming or outgoing messages.
The delivery queue would also be suspended.

That way, if an update goes wrong, reverting from a snapshot would effectively come at zero cost.

This would apply to any type of update, including operating system updates.

What do you think?
Sabatino Traini
      Chief Information Officer
Genial s.r.l. 
Martinsicuro - Italy

I just block port 25. Not perfect but it does work.
Yes, it's an imperfect solution.
Users could still interact with the server, but the delivery queue would continue to function.

In maintenance mode, however, only one domain could be excluded from maintenance, which would also allow me to run my tests.
In practice, all incoming messages not addressed to that excluded domain would receive an RSP: 451.

All users would simply be unable to authenticate.


Of course, here too, the protection would apply to serious situations.
Services failing to restart and/or errors occurring immediately.
Sabatino Traini
      Chief Information Officer
Genial s.r.l. 
Martinsicuro - Italy

Reply to Thread

Enter the verification text