HI,
We are facing an issue with connections from SOGo to ManageSieve.
Our dovecot is configured as the following:
protocol sieve {
mail_max_userip_connections = 3
}
And SOGo with:
SOGoSieveServer =
"sieve://127.0.0.1:4190/?tls=YES&tlsVerifyMode=allowInsecureLocalhost";
SOGoVacationEnabled = YES;
SOGoForwardEnabled = YES;
SOGoSieveScriptsEnabled = YES;
When a filter/vacation filter is applied at webmail, the following happens:
* *if there is a free connection*, SOGo communicates with Dovecot and
applies the filter
- the filter is correctly applied and the user receives a response
- the connections to Dovecot/ManageSieve (on port 4190) are not freed.
* *if there are no available connections*, SOGo communicates with
Dovecot and do not apply the filter
- the filter is not applied
- an error is logged:
Apr 05 09:47:59 sogod [2033]: <0x0x55d9298ffa40[SOGoSieveManager]> Could not login 'u...@examle.org' on Sieve
server: <0x0x55d922d155b0[NGSieveClient]: socket=<NGActiveSSLSocket[0x0x55d9298d55b0]: mode=rw
address=(null)>>: {RawResponse = "{code = TRYLATER; ok = 0; reason = \"Maximum number of connections
from user+IP exceeded (mail_max_userip_connections=3)\"; }"; result = 0; }
Is there any way to prevent the connections from being opened/stale
after the changes?
Software versions:
OS: CentOS Linux release 7.9.2009
SOGo: 5.10.0
Dovecot version: 2.2.36
Best regards,
Bruno Costa
