Closed kcastner closed 2 years ago
I can confirm this Issue. I think it is a problem between dovecot and sogo.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
I can also confirm this issue
I also experience this problem.
The cow has 16 GB and 6 cores , solr set to use 6 GB.
Mailboxes have been test imported with the cow syncjob , copy paste with trough thunderbird imap , PST outlook import in imap to try and exclude issues there.
A second test cow also has this issue, and to exclude the hostingprovider/platform i tested locally in a kvm , same issue.
mailcowdockerized-sogo-mailcow-1 | Mar 15 17:43:10 26b5a76e4b8f sogod [168309]: [ERROR] <0x0x55628a0bb580[NGImap4Connection]> could not select URL: imap://user%40user.tld@172.22.1.250/INBOX/Tender/?tls=NO&tlsVerifyMode=none: {RawResponse = "{ResponseResult = {description = \"Mailbox doesn't exist: INBOXTender (0.002 + 0.001 + 0.001 secs).\"; result = no; tagId = 4; }; }"; reason = "Mailbox doesn't exist: INBOXTender (0.002 + 0.001 + 0.001 secs)."; result = 0; }
Running search again a few times may result in completing correct. Sometimes a search that runs correct being executed a second time fails with above error.
The mentioned Mailbox, that does not exist actually DOES exist. But it seems to quit randomly blurting out a random folder where it is searching at that moment so the mentioned mailbox is different each time.
root@vmi1110516:~# docker -v Docker version 23.0.1, build a5ee5b1 root@vmi1110516:~# docker-compose -v Docker Compose version v2.13.0 root@vmi1110516:~# Cow version 2023-03 (but having the issue also on previous versions.
I also confirm this issue, it should not be marked as stale.
Maybe we have to open it at sogo side too?
@nicolaspernoud: Would you like to open it at sogo, please? A reference to this issue should be fine.
@kcastner : Hello, I did : https://bugs.sogo.nu/view.php?id=5912 . I wrote it in french since SoGO is now maintained by a french company. In the meantime, it would be nice to reopen the issue @andryyy or @FreddleSpl0it...
Also happening to us in version 2024-02. Did not happen in Version 2022-something we used before.
@FreddleSpl0it Search fails at random points. Does not seem related to resource conditions or timeouts (happens sometimes in the first 10 seconds of search, sometimes much later)
Prior to placing the issue, please check following: (fill out each checkbox with an
X
once done)Summary
Logs
Reproduction
System information
docker version
)docker-compose version
)Output of
git diff origin/master
, any other changes to the code? If so, please post them.+myhostname = sub.example.tld
diff --git a/docker-compose.yml b/docker-compose.yml index d706d2dc..a0c7ca1e 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -80,7 +80,7 @@ services: environment:
- IPV6_NETWORK=${IPV6_NETWORK:-fd4d:6169:6c63:6f77::/64}
volumes: @@ -434,7 +434,7 @@ services: environment:
- IPV6_NETWORK=${IPV6_NETWORK:-fd4d:6169:6c63:6f77::/64}
@@ -549,7 +549,7 @@ services:
ipv6nat-mailcow:
depends_on:
environment:
image: robbertkl/ipv6nat
security_opt:
restart: always
privileged: true
network_mode: "host"
volumes:
networks: mailcow-network: driver: bridge
All third-party firewalls and custom iptables rules are unsupported. Please check the Docker docs about how to use Docker with your own ruleset. Nevertheless, iptabels output can help us to help you:
iptables -L -vn
,ip6tables -L -vn
,iptables -L -vn -t nat
andip6tables -L -vn -t nat
.ALL default
DNS problems? Please run
docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254
(set the IP accordingly, if you changed the internal mailcow network) and post the output.