Do you also check the Docker logs with Fail2ban? I tried to find information about it but unfortunately didn’t find much.
semaf

- 14 May
- Joined Jan 28, 2024
- 6 discussions
- 17 posts
- 0 best answers
- Post posted... wait what?
- Edited
- Best Answerset by semaf
Please check the docs, you have to create the ssh key at data/conf/borgmatic/ssh, that’s a directory inside your mailcow directory!
If you put it in /data/conf/borgmatic/ssh it won’t work
If the path you wrote above was just a typo, I guess the ssh key password is the problem. How exactly should the cronjob enter a password?
Create a key without a passwordHi,
don’t ask why, but I was on the impression that after announcing that arm support is now in the nightly build, I needed to switch to that. I have done that actually on the 19th of September and have now noticed that the private key is somehow missing for messages before that switch. All messages beginning from that point are readable, all the older messages are getting:
<849818><J5r6ZIIHksZQgmp5>: Error: Mailbox Archive: UID=131130: read() failed: read(/var/vmail/xy/xy/Maildir/.Archive/cur/1695152089.M340777P232.2c017e3a6c85,S=1649,W=1695:2,S) failed: Decryption error: no private key available (read reason=prefetch)Update was done through the documented way by ./update.sh –nightly and did not show any errors. Configuration was not changed at all.
Any change that someone can help with that? Where is the key and why did it somehow change as newer emails are accessible. I’m a little bit lost with this topic.
Looking forward to any suggestion / or help. Let me know if DM is needed.
Regards
TonyThis should be mentioned in the documentation!!!
I had too much faith in this and never checked the backup archives. Now a client asks for a mail folder he deleted by accident and I find out vmail has not been backing up for months (ever I set it up tbh)..
This seems to be an issue the mailcow community is not very keen on providing support for or is simply somewhat of uncharted territory.
I found numerous discussions online from the past 2 years similar to my problem and no clear resolution seems to exist.
Here are some of the other discussions:
mailcow/mailcow-dockerized2395
At this point there are 2 things I have to attempt with the hope of recovering my mail (2000+ messages).
1) Do a full backup of mailcow on existing host, restore it to a new temporary host, sync the restored mail from temp to existing host.
2) If 1) doesn’t work, will need to attempt the mailcow migration detailed in to a dummy server and then try to sync my mail from there.Anyways this seems to be a brutal PITA and am heavily disappointed it hasn’t been documented properly in the mailcow docs considering the amount of people who encountered this issue over the past 2 years.