This is not a Virtualmin question. We don’t care how you sync your time. (And, I’m personally mostly using systemd-timesyncd on systems that don’t need to provide NTP services to other devices.)
The first question was not specifically related to Virtualmin, but to Virtualmin/Webmin. In the web interface, if you visit the Webmin > Hardware > System Time section, in the third tab "Time server sync", the settings related to time synchronization can be made. If you choose to change the configuration of the module, you will get the following page where reference is made to NTP
I’d rather we not go backward. I’m only aware of minor inconveniences from the switch to the journal (I think it’s just mail logins that we’re not showing?). Is there something else I don’t know about?
I’m not willing to recommend overhauling your logging just to get mail login times (which we’ll fix pretty soon, I’m sure).
Analyzing the situation better, I agree with your opinion, we cannot continue to swim in reverse. If you manage to make the changes by using journalctl information so that plain-text files are no longer needed for mail, then the issue is solved.
However, if you have information related to how the sending of information from journalctl in plain-text files could be implemented, it should be made public somewhere. What I pointed in that link is a solution, but it still depends on rsyslog installation, which I would like to avoid. Unfortunately, I did not find many resources when searching the Internet, journalctl is not very popular.
In the past the same section in Webmin was modified based on a discussion initiated by me. Then I showed that the ntpdate package is deprecated and we have to take a step forward. After so many years, it’s time for that module and the whole time synchronization part to adapt to the times. The Debian team makes us choose ntpsec.
PS - We should be happy that Debian 12 works with Webmin/Virtualmin since July of the year. In the past, it took until the end of the year to have something stable. There are some issues reported, but I think the people behind this wonderful control panel know what they have to do.
The purpose of the spamassassin-maintenance.timer is to periodically trigger the spamassassin-maintenance.service , to handle tasks like rule updates, bayesian database cleanup, expired token expiry and etc.
It’s been suggested, and I was already thinking it myself, that this could be a Debian 12 specific issue. I can see Debian 12 is listed as a grade A supported OS so I am querying whether this issue can be replicated on any Debian 12 test systems or if it really is a environment specific problem for me to deal with?
I see 12.0 is working for folks so just tried 12.2 it errors out 100 citing there is no release file for the repository. Not entirely sure is this like a version check that only allows 12.0 bookworm or is there something more to it? I just tried the GPL cause I’ll be danged if I’m trying to memorize and type in the installer info for the pro version I can always switch up down the line but wanna make sure it works before going too crazy.