semaf

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

Hi,

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
Tony

This 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
Mail cant be read/decrypt after restore

mailcow communityDiscussion

Mail cant be read/decrypt after restore

K KaiserN

Hi, i had to full restore my mailcow from backup. This has worked so far, but I no longer see the old emails. They are visible via IMAP/SOGo, but you can’t read/retrieve them anymore. IMAP imap(email@domain.tld)&lt;980230&gt;&lt;ubMlLwv1YKUAAAAAAAAAAAAAAAAAAAAB&gt;: Error: Mailbox Trash: UID=146:

4 3 Feb 20, 2023

Can't restore to a new server

mailcow communityDiscussion

Can't restore to a new server

R reed

Hi, I have an issue and I din’t know how to solve it… I have 2 dedicated VPS. The main one works well with Mailcow but I must change to another VPS server. First, I update Mailcow using update.sh, then, I follow the documentation and backup Mailcow

3 2 Jun 18, 2021

IMAP Issues

mailcow communityDiscussion

IMAP Issues

R rupertchandler

Hi, On latest update and having an odd issue with IMAP connections. Add a new account and the email client (Unibox/EMclient) downloads email from account without a problem, but from that point on is unable to update to see new mail. However Outlook works without an a problem. Very odd! Can’t see

7 2 Oct 9, 2020

Certain Emails No Longer Loading / Corrupted

mailcow communityDiscussion

Certain Emails No Longer Loading / Corrupted

UpperCenter

Hi All, I’ve recently discovered that a handful of emails from a few months ago have corrupted somehow, and are no longer loading in the WebUI or via 3rd party clients (Thunderbird) See above, I’m able to send and recieve mail just fine, but these emails just don’t load and I can’t seem to

5 2 Dec 11, 2022

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 https://docs.mailcow.email/en/i_u_m/i_u_m_migration/

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.