I am using MiaB for a year or so now and I am extremely satisfied with the project.
I am hosting it on a minimal DO droplet (512MB / 20 GB / 1 core) and it runs smoothly enough for <10 users.
Recently, I started to notice that my storage space is declining.
Even status page shows a warning.
Since I do not use NextCloud (or whatever cloud it is), I assume all space is occupied by mail (in particular, attachments).
OS installation should not (significantly) grow with time, only mail should.
I have looked through the users’ mailboxes’ sizes (on an admin page) and realized that they barely occupy 1 GB all together.
The question is, how it may have happened that I have 4/20 GB left (and this number is decreasing) given that all mailboxes take up 1 GB? And how do I fix it?
Actually, I have accidentially figured out the problem.
I am sure, other users will appreciate the fix (and MiaB maintainers may find it reasonable to implement it).
By default that’s your responsibility to run ‘apt-get autoremove’ right after every ‘apt-get update && apt-get upgrade’ and/or ‘apt-get dist-upgrade’ as linux updating / upgrading/ cleanup is not a decision directly related to MiaB itself.
The box should fix any problems that it creates itself, but not fix problems created by manual changes made by the end user. Do kernels tend to build up normally / on a vanilla Mail-in-a-Box install? I haven’t noticed it on mine.
Probably depends on the hosting arrangement. For example, Linode uses its own kernel so linux-image… is not installed. But I imagine for other setups using kernels from the Ubuntu repo, they can start piling up.
At the very least we could run autoremove during Mail-in-a-Box setups so that when upgrading versions we take care of it. I’ll push a fix for that soon. Presumably people upgrade a few times a year.
I’m not sure if running it in additionally periodically would be necessary, but I’m open to adding it.
is probably the best thing to do. If anyone would open up a pull request to add it (and preferably also include some comments in the script about why and add a CHANGELOG entry), I’d be glad to merge.
@JoshData I wouldn’t add it in, but instead maybe make a script / button for the web interface to run it if needed (As an example some times autoremove removes something a compiled application(not installed via apt) needs and will break things. Albeit not very frequently, but has happened to me before)
As long as MiaB is the only entity responsible for packages, we can make sure that we don’t have such compiled binaries. I believe, it is strongly discouraged to do anything on the server except upgrading MiaB itself.