Package: go-mmproxy Version: 2.2.1-2+b3 Severity: normal
Dear Maintainer, we have a problem with go-mmproxy that is fixed upstream. See: https://github.com/kzemek/go-mmproxy/issues/13 We are using go-mmproxy for our ldap/smtp loadbalancing and we are seeing a lot of RST packets (one for each closed connection), that might influence the stability of existing connections. This behavior was fixed in go-mmproxy 2.2.2: https://github.com/kzemek/go-mmproxy/pull/14/files If it is possible, please review the upstream bugfix. Regards, Johannes Kampmeyer -- System Information: Debian Release: 13.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.12.57+deb13-amd64 (SMP w/64 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages go-mmproxy depends on: ii libc6 2.41-12 go-mmproxy recommends no packages. go-mmproxy suggests no packages. -- no debconf information
smime.p7s
Description: S/MIME Cryptographic Signature
