similar to: v2.3.5.1 released

Hi, Why didn?t you apply this patch to v2.3.5.1? commit df8addd41d87e61113de22a21a0e61506a8d74c2 Author: Stephan Bosch <stephan.bosch at dovecot.fi> Date: Tue Mar 12 03:18:33 2019 +0100 submission-login: client-authenticate - Fix crash occurring when client disconnects during authentication. diff --git a/src/submission-login/client-authenticate.c

Mandi! Rowland penny via samba In chel di` si favelave... > Even though your users may have the same username in AD as in the NT4-style > domain, they are different users, so a few thoughts. You have 'map to guest > = bad user', so I take it you must have 'guest ok = yes' set in the shares > (you haven't shown us the shares), so try changing 'bad user' to

Hello everybody, hope you?re all well! We have a really strange bug with our dovecot setup. After weeks and month of debugging we?re finally reached the point when we ask you for help. Our basic setup is quite simple: a single dovecot 2.3.10 (0da0eff44) install on Debian 10 with LDAP as user/passdb and sieve, imap_sieve and mail_crypt as mail_plugins. For the mail_crypt we have a special rule

On 29. Mar 2020, at 16:07, Timo Sirainen <timo at sirainen.com> wrote: > > On 29. Mar 2020, at 15.15, Andi Krischer <ak at michaelpelzer.de> wrote: >> We have a really strange bug with our dovecot setup. After weeks and month of debugging we?re finally reached the point when we ask you for help. >> >> Our basic setup is quite simple: a single dovecot 2.3.10

Marco Gaiarin via samba ha scritto il 25/08/20 alle 18:53: > [...] >> The only other thing I can think of at the moment is to remove >> 'winbind use default domain = yes' > > It was a try, i think in NT mode don't bother at all. on my samba server with 'winbind use default domain" set to yes dominioNT\ is removed from users and groups names... >

Hello, I had been running Samba 4.8 for a few years without any problems, and then upgraded to 4.10. Since then I?ve been having problems with some accounts connecting, while some connect fine still. I haven?t been able to figure out why. My server is a relatively simple standalone server, using the LDAP password backend. A failing user authenticates OK and ends up like this in the logs: