Closed saytamkenorh closed 1 month ago
Thank you for the workaround.
Maybe related but not fully sure. I have had complaints that even after disabling vacation messages they will randomly auto respond to senders
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
? not fixing a bug is considered as stale? This bug still occurs in 2023-11. The auto-reply just triggered although it is set for beginning 2023-12-23.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This bug is still current... could you please fix it in some way? Thanks
Same here, dates are shifting anytime we use SoGo vacation messages. We are going to test above workaround and let you know here if it fixes date shifting
After my message I've tested the workaround and it's working. Still, it would be better to fix it at the source ;)
Thanks, we'll give it a try ASAP and post results here
A quick question: $TZ is an ENV var of SoGo?
$TZ is an ENV var that should be already defined within your docker-compose file (sourced from .env/mailcow.conf file) . And so it should be already available within SoGO container.
Contribution guidelines
I've found a bug and checked that ...
Description
By default the "/etc/timezone" file in the sogo-mailcow container contains "Etc/UTC".
Steps to reproduce:
Which branch are you using?
master
Operating System:
Fedora Linux 38 (Server Edition)
Server/VM specifications:
16 GB RAM, 2 CPU cores
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
none
Docker version:
24.0.5
docker-compose version or docker compose version:
v2.20.2
mailcow version:
2023-08
Reverse proxy:
Nginx
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check: