Ldap dict for shared mailboxes

2021-11-01 Thread Kees van Vloten
Hi everybody, I am trying to construct a LDAP dict for shared mailboxes. There is a lot of documentation available but nothing specific to this usecase. I could not find anything useful on Google nor in the mailinglist archives :-( The best start point seems to be the doc on shared mailbox

Re: limiting cpu time of dovecot/imap

2021-11-01 Thread Sami Ketola
> On 1. Nov 2021, at 19.25, Marc wrote: > > What would be the best way to 'throttle' dovecot/imap processes of specific > users? > Can you please elaborate a bit how you would like to ‘throttle’ the processes? Give it less CPU time? That you can probably achieve by returning

limiting cpu time of dovecot/imap

2021-11-01 Thread Marc
What would be the best way to 'throttle' dovecot/imap processes of specific users?

RE: dovecot: 2.3.16 -> 2.3.17_1

2021-11-01 Thread Marc
What about fixing the health check passthrough?

Re: dovecot: 2.3.16 -> 2.3.17_1

2021-11-01 Thread Goetz Schultz
Hi, I would assume that most people have only a cert signed by one ca? Would an appropriate method not be to single that ca-cert out into a singe file? The mail reception is usually not involving dovecot on a level where random CA certs are required? Thanks and regards Goetz R Schultz

Re: Auth-Trouble

2021-11-01 Thread infoomatic
please inform the mailing list if problems persist, thank you! I am about to migrate to FreeBSD ... On 01.11.21 13:53, Hanns Mattes wrote: Hi, Am 01.11.21 um 00:51 schrieb Hanns Mattes: Hi, Am 01.11.21 um 00:27 schrieb infoomatic: does 2.3.17_1 from ports fix the problem? I'm building

Re: dovecot: 2.3.16 -> 2.3.17_1

2021-11-01 Thread Aki Tuomi
This is caused by the ssl_ca setting. We are working on a fix. You can try commenting the setting out. Aki On 1 November 2021 15.32.55 UTC, Elise wrote: >Hi team, perhaps I do overlook something here, but after the update from >2.3.16 -> 2.3.17_1on startup Dovecot is generating error message:

Re: [EXT] SOLVED: Re: Dovecot does not start on MacOS 12.01

2021-11-01 Thread Sean McBride
On Mon, 1 Nov 2021 14:55:25 +0200, Aki Tuomi said: >I think this is happening because MacOS no longer supports RLIMIT_DATA. I just tried on macOS 12.1 beta and getrlimit(RLIMIT_DATA) gives RLIM_INFINITY for both current and max (and so does my macOS 10.14 box). On Monterey, using setrlimit()

Re: dovecot: 2.3.16 -> 2.3.17_1

2021-11-01 Thread Alexander Dalloz
Am 01.11.2021 um 16:32 schrieb Elise: Hi team, perhaps I do overlook something here, but after the update from 2.3.16 -> 2.3.17_1on startup Dovecot is generating error message: > doveconf: Fatal: execvp(/usr/local/sbin/dovecot) failed: Argument list too long > /usr/local/etc/rc.d/dovecot:

dovecot: 2.3.16 -> 2.3.17_1

2021-11-01 Thread Elise
Hi team, perhaps I do overlook something here, but after the update from 2.3.16 -> 2.3.17_1on startup Dovecot is generating error message: > doveconf: Fatal: execvp(/usr/local/sbin/dovecot) failed: Argument list too long > /usr/local/etc/rc.d/dovecot: WARNING: failed to start dovecot As a

Re: [EXT] SOLVED: Re: Dovecot does not start on MacOS 12.01

2021-11-01 Thread Aki Tuomi
I think this is happening because MacOS no longer supports RLIMIT_DATA. We'll try to look into this. default_vsz_limit = 0 seems good enough workaround. Aki > On 01/11/2021 14:53 Don Feliciano wrote: > > > 2G fails. > > This must be some change in MacOS 12 (Monterey). I have been running

Re: Auth-Trouble

2021-11-01 Thread Hanns Mattes
Hi, Am 01.11.21 um 00:51 schrieb Hanns Mattes: > Hi, > > Am 01.11.21 um 00:27 schrieb infoomatic: >> does 2.3.17_1 from ports fix the problem? > > I'm building own packages with poudriere and "pkg info dovecot" says > it's 2.3.17_1 > > Given the fact that this version is dated 2021-10-28 I'm

Re: [EXT] SOLVED: Re: Dovecot does not start on MacOS 12.01

2021-11-01 Thread Aki Tuomi
Ok... so for some reason the default_vsz_limit is too low for MacOS. Can you try default_vsz_limit = 2G? We don't recommend setting it to 0. Aki > On 01/11/2021 14:45 Don Feliciano wrote: > > > Different: > > Nov 01 08:44:36 master: Error: service(imap-login): command startup failed, >

Re: [EXT] SOLVED: Re: Dovecot does not start on MacOS 12.01

2021-11-01 Thread Don Feliciano
Different: Nov 01 08:44:36 master: Error: service(imap-login): command startup failed, throttling for 8.000 secs Nov 01 08:44:36 imap-login: Fatal: master: service(imap-login): child 17371 returned error 89 (Fatal failure) > On Nov 1, 2021, at 8:42 AM, Aki Tuomi wrote: > > Do you get exactly

Re: [EXT] Re: SOLVED: Re: Dovecot does not start on MacOS 12.01

2021-11-01 Thread Aki Tuomi
Do you get exactly same error message with that config or something else? Aki > On 01/11/2021 14:39 Don Feliciano wrote: > > > I just tried that solution, but it doesn't work. Only default_vsz_limit = 0 > seems to work. > > > On Nov 1, 2021, at 2:38 AM, Aki Tuomi wrote: > > > > Hi! > > >

Re: Errors after freebsd upgrade

2021-11-01 Thread Odhiambo Washington
On Sat, Oct 30, 2021 at 7:10 PM Hanns Mattes wrote: > Hi, > > after upgrading Freebsd from ports dovecot is throwing the following error > > Oct 30 18:04:15 freebsd dovecot[59232]: > doveadm(x...@example.com)<84061>: Fatal: master: > service(doveadm): child 84061 killed with signal 6 (core not

Re: 2.3.17 - breaks with fts-xapian.

2021-11-01 Thread Aki Tuomi
> On 31/10/2021 00:01 Juan Felipe Arjona wrote: > > > Hello: > > > I just upgraded my Debian server with dovecot 2.3.17, and it breaks when > using the plugin fts-xapian. > > Apparently is a bug in Dovecot, please see: > > > https://github.com/grosjo/fts-xapian/issues/99 > > >

Re: 2.3.17 broken on CentOS8 / bug

2021-11-01 Thread Aki Tuomi
Hi all! We are looking into this issue. Aki > On 30/10/2021 19:36 TG Servers wrote: > > > Thanks Robert, I read that. I will also wait for a patch and stay > > Cheers > > > On 30/10/2021 12:59, Robert Nowotny wrote: > > > the reason is : > > > > ssl_ca = > > > if

Re: SOLVED: Re: Dovecot does not start on MacOS 12.01

2021-11-01 Thread Aki Tuomi
Hi! That solution is bit overly broad way to solve this, I would instead recommend service log { vsz_limit = 0 } so that only service log is affected. Aki > On 31/10/2021 20:36 Don Feliciano wrote: > > > > A kind person who isn’t on the mailing list share the solution to this with >