Hardware: AMD64
YunoHost version: 11.2.3 (stable).
I have access to my server: Yes.
Description of the Issue
Hello,
I am encountering an issue with my YunoHost server. Postfix is reporting errors related to missing files, despite not having made any manual file alterations. It’s important to note that all other aspects of the server are functioning properly, and there is no unauthorized access, as the admin interface ports are secured against external connections. I ran the mailq command and observed that there are pending emails (approximately 12xx). I attempted to resolve the issue by executing postsuper -d ALL, followed by a server restart. However, I am still unable to send or receive emails.
Below is a portion of the log messages I retrieved:
journalctl
-- Journal begins at Wed 2023-07-26 16:49:02 CEST, ends at Fri 2023-08-04 17:28:49 CEST. --
aug 04 17:28:05 postfix/cleanup[5672]: warning: hash:/var/virtual is unavailable. open database /var/virtual.db: No such file or directory
aug 04 17:28:05 postfix/cleanup[5672]: warning: hash:/var/virtual lookup error for "root@serverdomain.ltd"
aug 04 17:28:05 postfix/cleanup[5672]: warning: 4402D18055E0: virtual_alias_maps map lookup problem for root@serverdomain.ltd -- message not accepted, try again later
aug 04 17:28:05 postfix/pickup[1707]: 442DD18055E0: uid=0 from=<root>
aug 04 17:28:05 postfix/cleanup[5672]: warning: hash:/var/virtual is unavailable. open database /var/virtual.db: No such file or directory
...
/var/log/mail.err
Aug 4 16:43:45 ECZ-SRV-01 postfix/cleanup[2451461]: error: open database /var/virtual.db: No such file or directory
Aug 4 16:43:45 ECZ-SRV-01 postfix/cleanup[2451464]: error: open database /var/virtual.db: No such file or directory
...
/var/log/mail.log
Aug 4 17:28:05 ECZ-SRV-01 postfix/pickup[1707]: 4483A18055E0: uid=0 from=<root>
Aug 4 17:28:05 ECZ-SRV-01 postsrsd[5673]: srs_forward: <root@serverdomain.ltd> not rewritten: Domain excluded by policy
...
It appears that the error is related to database files, specifically /var/virtual.db. I have not manually modified any configuration files, and the error persists even after attempting the mentioned actions.
Your guidance in resolving this matter would be greatly appreciated.
Thank you.
[Please note that this text retains the original format while ensuring privacy and security considerations.]
The next day
2023-08-04T22:00:00Z
I’ve tried to regenerate the config, but it’s all going wrong?!
yunohost tools regen-conf postfix
Warning: Traceback (most recent call last):
Warning: File "<stdin>", line 5, in <module>
Warning: AssertionError: Setting file /etc/yunohost/apps/:/settings.yml does not exists ?
Warning: Traceback (most recent call last):
Warning: File "<stdin>", line 5, in <module>
Warning: AssertionError: Setting file /etc/yunohost/apps/:/settings.yml does not exists ?
Also, what is with the /etc/yunohost/apps/:/settings.yml?
It should not have /:/
The correct path is:/etc/yunohost/settings.yml I can see the file there at least, it has correct values and rights and doesn’t seem to be corrupted.
Any help would mean the world to me… If only, @tituspijean, @Aleks, or @Mamie, you could lend your brilliant minds to my plight with YunoHost. My frustration has escalated to the point where I’m practically tearing my hair out in utter despair 
. To make matters worse, I’m being bombarded by complaints from other users about the complete breakdown of our email services. Strangely, I’ve hardly made any changes apart from what should have been routine – installing updates through the admin panel. The only other action I took was a bit of cleaning – merely deleting a handful of old, unused domains to bring the count-down from around 62 to a seemingly modest 32. Even this was advised by the knowledgeable Aleks in a previous discussion. Yet, here I am, drowning in this sea of email turmoil…