Mail-In-A-Box Back Up to Beget S3
Mailinabox supports S3 compatible storages. Below are the settings for the combination.
For some reason when I put all the correct settings, I was getting a 'Contents' error which is a truncated KeyError: 'Contents' error from backup.py. I fixed it with adding a file to the root of the S3 bucket in Beget. After I added the file, the error went away.
So, settings:
| Parameter | Value | Note |
| Backup to: | S3 (Amazon or compatible) | |
| S3 Region: | <empty> | |
| S3 Host / Endpoint: | <your value, e.g. s3.ru45.storage.beget.cloud> | No "https://" here! |
| S3 Region Name (if required): | <empty> | |
| S3 Bucket & Path: | <bucket-name from Beget>/ | Add "/" to the bucket name as it will be used in backup.py |
| S3 Access Key: | <your value> | |
| S3 Secret Access Key: | <your value> | |
| Retention Days: | <whatever you prefer> |
With these settings my backup is working.
Update: after one month running I see that MIAB has difficulties with accessing the data to delete old full backups and to display size of the backups.
I will be switching to S3FS mount (see NextCloud: Borg Backup to an Auto Mount Non-AWS s3fs on Debian 13) and monitoring the performance:
sudo mv /var/mailinabox/backup/encrypted /var/mailinabox/backup/encryptedd
sudo ln -s /mnt/beget-s3 /var/mailinabox/backup/encrypted