Same problem. I had to backup. I don’t recommand to install this last upgrade !
I have problems too with this version:
I think that I missed the 2.29.1~ynh1 update, but I’m now running the 2.29.1~ynh2 with no problem. Maybe it was fixed in that version ?
Yes, now i can access snappymail user interface with 2.29.1~ynh2 version, but still not login admin panel.
I can now login by restoring the old /var/www/snappymail/app/data/data/default/configs/application.ini file.
Finally i keep the new application.ini file:
Disallowed Sec-Fetch Dest: document Mode: navigate Site: same-site User: true
looks like having the mail in a subdomain generates this
disabling mail for that subdomain
The configuration file '/var/www/.well-known/xxxxx/autoconfig/mail/config-v1.1.xml' has been manually modified and will not be updated
Configuration updated for 'postfix'
Configuration updated for 'dovecot'
postmap: fatal: open /etc/postfix/sni: No such file or directory
Could not run script: /usr/share/yunohost/hooks/conf_regen/19-postfix
Config updated as expected
Hi,
I’m having the same issue. Did you manage to solve it?
I noticed after refresh it works but is not convenient.
It can be configured in the admin area via the “Config” section:
Search for parameter secfetch_allow and enter value mode=navigate,dest=document,site=same-site for proper configuration.
Since 2.29.1~ynh1 , my var/www/snappymail/app/data/data/default/configs/application.ini is replaced by a new one. Is this the normal behaviour?
I lose my settings and i need to copy my couple login/password from the old file to access the admin page and then, reactivate SSL and STARTTLS on imap/smtp. I need to copy again all my settings, add access to my nextcloud contacts, etc…
Before this version, i don’t remember needing to do it.
Is it possible to keep personal/admin settings like my Nextcloud do? Nextcloud can be upgrade without loosing its settings.
Should be fixed in testing fix path to config file by ericgaspar · Pull Request #180 · YunoHost-Apps/snappymail_ynh · GitHub
I raised this a couple of days ago. I’m staying with the previous version as I have 5 accounts and a long list of filters that I’d like to keep.
Dj
I also encountered this problem again today with the latest update. Is this likely to be a recurring problem with SnappyMail? In which case I’ll consider switching to another client…
which is weird since the configuration file is not regenerated if i’m not mistaken
I upgrade Snappymail 2.37.3~ynh1 to Snappymail 2.38.2~ynh1.
No error or warning and i have the message :
Success! snappymail upgraded
Success! Upgrade complete
But when i log on Snappymail, i have a blank screen with this message :
I try to reinstall a second time but i got the same error. What’s wrong with this version?
Edit: the owner of /var/www/snappymail/app (and all sub-folders/files) is root.
With a chown -R snappymail:www-data /var/www/snappymail/app , snappymail works now but i need again to modify the config file and my preferences.
I don’t know if rights are correct, i don’t have the same before and after the upgrade.
Am I the only one concerned by this problem?
Hi,
Delete /var/www/snappymail/app/data/_data_/_default_/storage/domain.tld/user and login again.
Replace domain.tld/user by yours.
Find on github page , it’s not a yunohost app bug but a snappymail error.
Perharps only one file in this folder is corrupt, so you can keep a copy of them and try with only change one after one and logout/login between these changes.
For info i’m not concerned by this problem.
Thank you for that suggestion @metyun
However, the folder “/var/www/snappymail/app/data/_data_/_default_/storage/” is empty on my instance.
I finally switched to Roundcube.
FYI, the latest version of Snappymail was released in October 2024; this software no longer appears to be active. There is an active fork called Tachyon, not yet available in Yunohost. More informations in the wishlist (links of website and Github page) :
Living in the future 
This looks interesting, but in their installation guide :
Best practice would be to install webmail on a separate server, rather than on the mailserver. This creates service isolation and segmentation and tremendously benefits security. Despite the more hardened approach of this RainLoop fork, PHP doesn’t have a perfect track record; hence, decreasing the attack surface through isolation/segmentation is considered best practice. Furthermore, this helps by increasing scalability and stability.
We already have isolation in YunoHost app management using system user created for each app with restricted permissions.
Oh yes! I hadn’t read it! It’s writen “Coming soon in yunohost app store” , but i can’t wait, i’m going “Back to the future”
In the installation guide, it is only a recommendation, not a mandatory requirement, isn’t it? (if i understand correctly, because i’m not familiar with english to understand the subtleties of langage) So, if that is the case, the isolation in Yunohost app is a really good alternative.