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 dictionaries 
(https://doc.dovecot.org/configuration_manual/shared_mailboxes/shared_mailboxes/#user-shared-mailboxes-shared-mailbox-listing), 
in particular the example for SQL dict. But obviously LDAP is different 
than SQL. The dictionaries page 
(https://doc.dovecot.org/configuration_manual/dict/) has  LDAP example 
but it looks like it does not contain all the bit and pieces I need.


Following the structure of the SQL example, I come to something like this:

map {
  pattern = shared/shared-boxes/user/$to/$from
  base_dn = ou=shared mailboxes,dc=example,dc=com
  filter = (&(objectClass=group)(mail=%{from})

  fields {
    from_user=$from
    to_user=$to
  }
}

The "to_user" / "$to" should be filled with the 'uid' or 'email' of a 
nested group lookup of the 'member' fields of the group.


What are the mechanics to get that done? Does anyone has an example or 
pointer to documentation or is a LDAP dict for shared-mailboxes not 
possible / supported? And in the latter case, suggestions about possible 
alternatives are welcome :-)


FYI. the LDAP implementation I am using is a recent Samba4 ad-dc.

- Kees.



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 
service/imap/executable="/usr/bin/nice -n 10 /usr/libexec/dovecot/imap"
from users for the throttled users.

Sami



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

>8
Quis custodiet ipsos custodes?
  /"\
  \ /  ASCII Ribbon Campaign
   X   against HTML e-mail
  / \
8<

On 01/11/2021 15:41, Aki Tuomi wrote:

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:



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 temporary solution I currently hashed out SSL in dovecot.conf and
receive e-mail again.
Can you tell how to fix? Thanks!

/elise




OpenPGP_0xAE3BF20B2187E63C.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


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 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 not sure, if
its part of the problem or the solution.


I'll do a complete reinstallation of the server, there are obviously
more problems. For example: I can ssh to both servers (and i can connect
from them to my server at home) but they refuse to talk to each other.
Same with telnet etc. No idea why, so I'll start over and recheck things.

Regards Hanns


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:
>
>
> > 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 temporary solution I currently hashed out SSL in dovecot.conf and 
>receive e-mail again.
>Can you tell how to fix? Thanks!
>
>/elise


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() to reduce 'current' works for large numbers, but 
does return error for low numbers.  On my hardware at least, it starts to 
return error around 419 GB.

Sean




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: WARNING: failed to start dovecot

As a temporary solution I currently hashed out SSL in dovecot.conf and 
receive e-mail again.

Can you tell how to fix? Thanks!

/elise


See this list from the last few days since the newest release.

Alexander




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 temporary solution I currently hashed out SSL in dovecot.conf and 
receive e-mail again.

Can you tell how to fix? Thanks!

/elise


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 Dovecot 
> for 10 years on MacOS with the same config, and only after upgrading to 12.0 
> did this issue surface.
> 
> > On Nov 1, 2021, at 8:47 AM, Aki Tuomi wrote:
> > 
> > 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, 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 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!
> > 
> > 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 me:
> >> 
> >> default_vsz_limi t = 0
> >> 
> >> 
> >> 
> >>> On Oct 28, 2021, at 12:12 PM, Don Feliciano wrote:
> >>> 
> >>> Same issue in 2.3.17
> >>> 
> >>> dovecot-2.3.17.tar.gz:
> >>> ./configure --prefix=/usr/local/Cellar/dovecot/ 2.3.17 
> >>> --libexecdir=/usr/local/Cellar/dovecot/2.3.17/libexec 
> >>> --sysconfdir=/usr/local/etc --localstatedir=/usr
> >>> make install
> >>> 
> >>> dovecot-2.3-pigeonhole-0.5.17.tar.gz:
> >>> ./configure 
> >>> --with-dovecot=/usr/local/Cellar/dovecot/2.3.17/lib/dovecot 
> >>> --prefix=/usr/local/Cellar/dovecot/2.3.17
> >>> make
> >>> make install
> >>> 
> >>> sudo /usr/local/opt/dovecot/sbin/dovecot -F
> >>> Warning: fd limit (ulimit -n) is lower than required under max. load 
> >>> (256 < 1000), because of default_client_limit
> >>> Oct 28 12:08:48 service(log): Fatal: setrlimit(RLIMIT_DATA, 
> >>> 268435456): Invalid argument
> >>> 
> >>> 
> >>> 
>  On Oct 27, 2021, at 11: 08 AM, Don Feliciano wrote:
>  
>  
>  I've been happily running Dovecot on my Mac for many years 
>  (installed via Homebrew). After upgrading to Monterey (MacOS 12.01), 
>  it no longer starts:
>  
>  $ sw_vers
>  ProductName: macOS
>  ProductVersion: 12.0.1
>  BuildVersion: 21A559
>  
>  $ uname -a
>  Darwin dfelicia-mac 21.1.0 Darwin Kernel Version 21.1.0: Wed Oct 13 
>  17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64 x86_64
>  
>  $ sudo dovecot -F
>  Oct 27 10:11:18 service(log): Fatal: setrlimit(RLIMIT_DATA, 
>  268435456): Invalid argument
>  
>  $ mount
>  /dev/disk1s2s1 on / (apfs, sealed, local, read-only, journaled)
>  devfs on /dev (devfs, local, nobrowse)
>  /dev/disk1s5 on /System/Volumes/VM (apfs, local, noexec, journaled, 
>  noatime, nobrowse)
>  /dev/disk1s3 on /System/Volumes/Pre boot (apfs, local, journaled, 
>  nobrowse)
>  /dev/disk1s6 on /System/Volumes/Update (apfs, local, jour naled, 
>  nobrowse)
>  /dev/disk1s1 on /System/Volumes/Data (apfs, local, journaled, 
>  nobrowse)
>  
>  $ sudo dovecot -n
>  # 2.3.16 (7e2e900c1a): /usr/local/etc/dovecot/dovecot.conf
>  # Pigeonhole version 0.5.16 (09c29328)
>  # OS: Darw in 21.1.0 x86_64 apfs
>  # Hostname: dfelicia-mac
>  default_internal_group = mail
>  default_internal_user = _dovecot
>  default_login_user = _dovenull
>  first_valid_uid = 100
>  listen = 127.0.0.1
>  log_path = /var/log/dovecot.log
>  mail_location = maildir:/usr/local/var/mail/%u
>  managesieve_notify_capability = mailto
>  managesieve_sieve_capability = fileinto reject envelope 
>  encoded-character vacation subaddress comparator-i;ascii-numeric 
>  relational regex imap4flags copy include variables body enotify 
>  

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 not sure, if
> its part of the problem or the solution.
> 

I'll do a complete reinstallation of the server, there are obviously
more problems. For example: I can ssh to both servers (and i can connect
from them to my server at home) but they refuse to talk to each other.
Same with telnet etc. No idea why, so I'll start over and recheck things.

Regards Hanns


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, 
> 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 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!
> > > > 
> > > > 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 me:
> > > > > 
> > > > > default_vsz_limit = 0
> > > > > 
> > > > > 
> > > > > 
> > > > > > On Oct 28, 2021, at 12:12 PM, Don Feliciano wrote:
> > > > > > 
> > > > > > Same issue in 2.3.17
> > > > > > 
> > > > > > dovecot-2.3.17.tar.gz:
> > > > > > ./configure --prefix=/usr/local/Cellar/dovecot/ 2.3.17 
> > > > > > --libexecdir=/usr/local/Cellar/dovecot/2.3.17/libexec 
> > > > > > --sysconfdir=/usr/local/etc --localstatedir=/usr
> > > > > > make install
> > > > > > 
> > > > > > dovecot-2.3-pigeonhole-0.5.17.tar.gz:
> > > > > > ./configure 
> > > > > > --with-dovecot=/usr/local/Cellar/dovecot/2.3.17/lib/dovecot 
> > > > > > --prefix=/usr/local/Cellar/dovecot/2.3.17
> > > > > > make
> > > > > > make install
> > > > > > 
> > > > > > sudo /usr/local/opt/dovecot/sbin/dovecot -F
> > > > > > Warning: fd limit (ulimit -n) is lower than required under max. 
> > > > > > load (256 < 1000), because of default_client_limit
> > > > > > Oct 28 12:08:48 service(log): Fatal: setrlimit(RLIMIT_DATA, 
> > > > > > 268435456): Invalid argument
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > > On Oct 27, 2021, at 11:08 AM, Don Feliciano wrote:
> > > > > > > 
> > > > > > > 
> > > > > > > I've been happily running Dovecot on my Mac for many years 
> > > > > > > (installed via Homebrew). After upgrading to Monterey (MacOS 
> > > > > > > 12.01), it no longer starts:
> > > > > > > 
> > > > > > > $ sw_vers
> > > > > > > ProductName: macOS
> > > > > > > ProductVersion: 12.0.1
> > > > > > > BuildVersion: 21A559
> > > > > > > 
> > > > > > > $ uname -a
> > > > > > > Darwin dfelicia-mac 21.1.0 Darwin Kernel Version 21.1.0: Wed Oct 
> > > > > > > 13 17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64 x86_64
> > > > > > > 
> > > > > > > $ sudo dovecot -F
> > > > > > > Oct 27 10:11:18 service(log): Fatal: setrlimit(RLIMIT_DATA, 
> > > > > > > 268435456): Invalid argument
> > > > > > > 
> > > > > > > $ mount
> > > > > > > /dev/disk1s2s1 on / (apfs, sealed, local, read-only, journaled)
> > > > > > > devfs on /dev (devfs, local, nobrowse)
> > > > > > > /dev/disk1s5 on /System/Volumes/VM (apfs, local, noexec, 
> > > > > > > journaled, noatime, nobrowse)
> > > > > > > /dev/disk1s3 on /System/Volumes/Preboot (apfs, local, journaled, 
> > > > > > > nobrowse)
> > > > > > > /dev/disk1s6 on /System/Volumes/Update (apfs, local, jour naled, 
> > > > > > > nobrowse)
> > > > > > > /dev/disk1s1 on /System/Volumes/Data (apfs, local, journaled, 
> > > > > > > nobrowse)
> > > > > > > 
> > > > > > > $ sudo dovecot -n
> > > > > > > # 2.3.16 (7e2e900c1a): /usr/local/etc/dovecot/dovecot.conf
> > > > > > > # Pigeonhole version 0.5.16 (09c29328)
> > > > > > > # OS: Darw in 21.1.0 x86_64 apfs
> > > > > > > # Hostname: dfelicia-mac
> > > > > > > default_internal_group = mail
> > > > > > > default_internal_user = _dovecot
> > > > > > > default_login_user = _dovenull
> > > > > > > first_valid_uid = 100
> > > > > > > listen = 127.0.0.1
> > > > > > > log_path = /var/log/dovecot.log
> > > > > > > mail_location = maildir:/usr/local/var/mail/%u
> > > > > > > managesieve_notify_capability = mailto
> > > > > > > managesieve_sieve_capability = fileinto reject envelope 
> > > > > > > encoded-character vacation subaddress comparator-i;ascii-numeric 
> > > > > > > relational regex imap4flags copy include variables body enotify 
> > > > > > > environment mailbox date index ihave duplicate mime foreverypart 
> > > > > > > extracttext
> > > > > > > namespace inbox {
> > > > > > > inbox = yes
> > > > > > > location =
> > > > > > > mailbox Drafts {
> > > > > > > special_use = \Drafts
> > > > > > > }
> > > > > > > mailbox Junk {
> > > > > > > special _use = \Junk
> > > > > > > }
> > > > > > > mailbox 

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 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!
>>>
>>> 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 me:

 default_vsz_limit = 0


> On Oct 28, 2021, at 12:12 PM, Don Feliciano wrote:
>
> Same issue in 2.3.17
>
> dovecot-2.3.17.tar.gz:
> ./configure --prefix=/usr/local/Cellar/dovecot/ 2.3.17 
> --libexecdir=/usr/local/Cellar/dovecot/2.3.17/libexec 
> --sysconfdir=/usr/local/etc --localstatedir=/usr
> make install
>
> dovecot-2.3-pigeonhole-0.5.17.tar.gz:
> ./configure --with-dovecot=/usr/local/Cellar/dovecot/2.3.17/lib/dovecot 
> --prefix=/usr/local/Cellar/dovecot/2.3.17
> make
> make install
>
> sudo /usr/local/opt/dovecot/sbin/dovecot -F
> Warning: fd limit (ulimit -n) is lower than required under max. load (256 
> < 1000), because of default_client_limit
> Oct 28 12:08:48 service(log): Fatal: setrlimit(RLIMIT_DATA, 268435456): 
> Invalid argument
>
>
>> On Oct 27, 2021, at 11:08 AM, Don Feliciano wrote:
>>
>>
>> I've been happily running Dovecot on my Mac for many years (installed 
>> via Homebrew). After upgrading to Monterey (MacOS 12.01), it no longer 
>> starts:
>>
>> $ sw_vers
>> ProductName: macOS
>> ProductVersion: 12.0.1
>> BuildVersion: 21A559
>>
>> $ uname -a
>> Darwin dfelicia-mac 21.1.0 Darwin Kernel Version 21.1.0: Wed Oct 13 
>> 17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64 x86_64
>>
>> $ sudo dovecot -F
>> Oct 27 10:11:18 service(log): Fatal: setrlimit(RLIMIT_DATA, 268435456): 
>> Invalid argument
>>
>> $ mount
>> /dev/disk1s2s1 on / (apfs, sealed, local, read-only, journaled)
>> devfs on /dev (devfs, local, nobrowse)
>> /dev/disk1s5 on /System/Volumes/VM (apfs, local, noexec, journaled, 
>> noatime, nobrowse)
>> /dev/disk1s3 on /System/Volumes/Preboot (apfs, local, journaled, 
>> nobrowse)
>> /dev/disk1s6 on /System/Volumes/Update (apfs, local, jour naled, 
>> nobrowse)
>> /dev/disk1s1 on /System/Volumes/Data (apfs, local, journaled, nobrowse)
>>
>> $ sudo dovecot -n
>> # 2.3.16 (7e2e900c1a): /usr/local/etc/dovecot/dovecot.conf
>> # Pigeonhole version 0.5.16 (09c29328)
>> # OS: Darw in 21.1.0 x86_64 apfs
>> # Hostname: dfelicia-mac
>> default_internal_group = mail
>> default_internal_user = _dovecot
>> default_login_user = _dovenull
>> first_valid_uid = 100
>> listen = 127.0.0.1
>> log_path = /var/log/dovecot.log
>> mail_location = maildir:/usr/local/var/mail/%u
>> managesieve_notify_capability = mailto
>> managesieve_sieve_capability = fileinto reject envelope 
>> encoded-character vacation subaddress comparator-i;ascii-numeric 
>> relational regex imap4flags copy include variables body enotify 
>> environment mailbox date index ihave duplicate mime foreverypart 
>> extracttext
>> namespace inbox {
>> inbox = yes
>> location =
>> mailbox Drafts {
>> special_use = \Drafts
>> }
>> mailbox Junk {
>> special _use = \Junk
>> }
>> mailbox Sent {
>> special_use = \Sent
>> }
>> mailbox "Sent Messages" {
>> special_use = \Sent
>> }
>> mailbox Trash {
>> special_use = \Trash
>> }
>> prefix =
>> }
>> passdb {
>> args = login
>> driver = pam
>> }
>> protocols = imap
>> service imap-login {
>> inet_listener imap {
>> address = 127.0.0.1
>> port = 143
>> }
>> inet_listener imaps {
>> address = 127.0.0.1
>> ssl = no
>> }
>> }
>> ssl = no
>> userdb {
>> driver = passwd
>> }
>>
>> $ ulimit -Ha
>> core file size (blocks, -c) unlimited
>> data seg size (kbytes, -d) unlimited
>> file size (blocks, -f) unlimited
>> max locked memory (kbytes, -l) unlimited
>> max memory size (kbytes, -m) unlimited
>> open files (-n) unlimited
>> pipe size (512 bytes, -p) 1
>> stack size (kbytes, -s) 65532
>> cpu time (seconds, -t) unlimited
>> max user processes (-u) 2784

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!
> > 
> > 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 me:
> >> 
> >> default_vsz_limit = 0
> >> 
> >> 
> >>> On Oct 28, 2021, at 12:12 PM, Don Feliciano wrote:
> >>> 
> >>> Same issue in 2.3.17
> >>> 
> >>> dovecot-2.3.17.tar.gz:
> >>> ./configure --prefix=/usr/local/Cellar/dovecot/ 2.3.17 
> >>> --libexecdir=/usr/local/Cellar/dovecot/2.3.17/libexec 
> >>> --sysconfdir=/usr/local/etc --localstatedir=/usr
> >>> make install
> >>> 
> >>> dovecot-2.3-pigeonhole-0.5.17.tar.gz:
> >>> ./configure --with-dovecot=/usr/local/Cellar/dovecot/2.3.17/lib/dovecot 
> >>> --prefix=/usr/local/Cellar/dovecot/2.3.17
> >>> make
> >>> make install
> >>> 
> >>> sudo /usr/local/opt/dovecot/sbin/dovecot -F
> >>> Warning: fd limit (ulimit -n) is lower than required under max. load (256 
> >>> < 1000), because of default_client_limit
> >>> Oct 28 12:08:48 service(log): Fatal: setrlimit(RLIMIT_DATA, 268435456): 
> >>> Invalid argument
> >>> 
> >>> 
>  On Oct 27, 2021, at 11:08 AM, Don Feliciano wrote:
>  
>  
>  I've been happily running Dovecot on my Mac for many years (installed 
>  via Homebrew). After upgrading to Monterey (MacOS 12.01), it no longer 
>  starts:
>  
>  $ sw_vers
>  ProductName: macOS
>  ProductVersion: 12.0.1
>  BuildVersion: 21A559
>  
>  $ uname -a
>  Darwin dfelicia-mac 21.1.0 Darwin Kernel Version 21.1.0: Wed Oct 13 
>  17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64 x86_64
>  
>  $ sudo dovecot -F
>  Oct 27 10:11:18 service(log): Fatal: setrlimit(RLIMIT_DATA, 268435456): 
>  Invalid argument
>  
>  $ mount
>  /dev/disk1s2s1 on / (apfs, sealed, local, read-only, journaled)
>  devfs on /dev (devfs, local, nobrowse)
>  /dev/disk1s5 on /System/Volumes/VM (apfs, local, noexec, journaled, 
>  noatime, nobrowse)
>  /dev/disk1s3 on /System/Volumes/Preboot (apfs, local, journaled, 
>  nobrowse)
>  /dev/disk1s6 on /System/Volumes/Update (apfs, local, jour naled, 
>  nobrowse)
>  /dev/disk1s1 on /System/Volumes/Data (apfs, local, journaled, nobrowse)
>  
>  $ sudo dovecot -n
>  # 2.3.16 (7e2e900c1a): /usr/local/etc/dovecot/dovecot.conf
>  # Pigeonhole version 0.5.16 (09c29328)
>  # OS: Darw in 21.1.0 x86_64 apfs
>  # Hostname: dfelicia-mac
>  default_internal_group = mail
>  default_internal_user = _dovecot
>  default_login_user = _dovenull
>  first_valid_uid = 100
>  listen = 127.0.0.1
>  log_path = /var/log/dovecot.log
>  mail_location = maildir:/usr/local/var/mail/%u
>  managesieve_notify_capability = mailto
>  managesieve_sieve_capability = fileinto reject envelope 
>  encoded-character vacation subaddress comparator-i;ascii-numeric 
>  relational regex imap4flags copy include variables body enotify 
>  environment mailbox date index ihave duplicate mime foreverypart 
>  extracttext
>  namespace inbox {
>  inbox = yes
>  location =
>  mailbox Drafts {
>  special_use = \Drafts
>  }
>  mailbox Junk {
>  special _use = \Junk
>  }
>  mailbox Sent {
>  special_use = \Sent
>  }
>  mailbox "Sent Messages" {
>  special_use = \Sent
>  }
> > >>> mailbox Trash {
>  special_use = \Trash
>  }
>  prefix =
>  }
>  passdb {
>  args = login
>  driver = pam
>  }
>  protocols = imap
>  service imap-login {
>  inet_listener imap {
>  address = 127.0.0.1
>  port = 143
>  }
>  inet_listener imaps {
>  address = 127.0.0.1
>  ssl = no
>  }
>  }
>  ssl = no
>  userdb {
>  driver = passwd
>  }
>  
>  $ ulimit -Ha
>  core file size (blocks, -c) unlimited
>  data seg size (kbytes, -d) unlimited
>  file size (blocks, -f) unlimited
>  max locked memory (kbytes, -l) unlimited
>  max memory size (kbytes, -m) unlimited
>  open files (-n) unlimited
>  pipe size (512 bytes, -p) 1
>  stack size (kbytes, -s) 65532
>  cpu time (seconds, -t) unlimited
>  max user processes (-u) 2784
>  virtual memory (kbytes, -v) unlimited
>  
>  
>  
> >>>


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 dumped -
> https://dovecot.org/bugreport.html#coredumps - set service doveadm {
> drop_priv_before_exec=yes })
>
> I (surely) may have missed something while upgrading (I've learned a lot
> about backup/snapshot-strategies with zfs, but to late to apply).
>
> How can I debug the erro?
>
> Regards Hanns
>

The "service doveadm { drop_priv_before_exec=yes }" bit should go into
/usr/local/etc/dovecot/conf.d/10-master.conf.
Append the bit I have quoted into that file and then restart dovecot.

What command is it that you are running with doveadm?

The also run the following commands (as root):

sysctl -w kern.sugid_coredump=1
sysctl -w kern.corefile=/var/coredumps/%U.%N.core

mkdir /var/coredumps
chown -R 1777 /var/coredumps

The next time  you get that fatal error, you'll probably find a file in
/var/coredumps/

You can then obtain a backtrace from it:

gdb /usr/local/bin/doveadm /var/coredumps/FILENAME 
bt full 

Present the output, together with that from 'doveconf -n'.

HTH


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' :-)


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
> 
> 
> Thanks,
> 
> 
> Juan

Hi!

This issue is due to a bug in fts-xapian. The plugin does not call 
fts_mail_user_init, causing the crash.

Aki


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 "ca-bundle.crt"is too big, You will get that error.
> >  this should be fixed, but as a workaround You might pull out the 
> > certificates You need.
> >  I personally wait for the patch and stay at 2.3.16 for the time beeing.
> >  
> >  yours sincerely
> >  Robert
> > 
> >  
> > 
> > Am 30.10.2021 um 10:34 schrieb TG Servers:
> > 
> > > Hello,
> > >  
> > >  tonight my dovecot upgraded to 2.3.17 and completely broke on recent 
> > > CentOS 8 installation.
> > >  
> > >  I found the service in status 
> > >  
> > >  [root@riot ~]# systemctl status dovecot
> > >  ● dovecot.service - Dovecot IMAP/POP3 email server
> > >  Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled; vendor 
> > > preset: disabled)
> > >  Active: failed (Result: exit-code) since Sat 2021-10-30 09:59:11 CEST; 
> > > 58s ago
> > >  Docs: man:dovecot(1)
> > >  https://doc.dovecot.org/
> > >  Process: 1515 ExecStart=/usr/sbin/dovecot -F (code=exited, status=89)
> > >  Process: 1429 ExecStartPre=/usr/libexec/dovecot/prestartscript 
> > > (code=exited, status=0/SUCCESS)
> > >  Main PID: 1515 (code=exited, status=89)
> > >  
> > >  Oct 30 09:59:10 riot..com systemd[1]: Starting Dovecot IMAP/POP3 
> > > email server...
> > >  Oct 30 09:59:11 riot..com dovecot[1515]: doveconf: Fatal: 
> > > execvp(/usr/libexec/dovecot/managesieve) failed: Argument list too long
> > >  Oct 30 09:59:11 riot..com dovecot[1515]: doveconf: Error: 
> > > managesieve-login: dump-capability process returned 89
> > >  Oct 30 09:59:11 riot..com dovecot[1515]: doveconf: Fatal: 
> > > execvp(/usr/sbin/dovecot) failed: Argument list too long
> > >  Oct 30 09:59:11 riot..com systemd[1]: dovecot.service: Main 
> > > process exited, code=exited, status=89/n/a
> > >  Oct 30 09:59:11 riot..com systemd[1]: dovecot.service: Failed 
> > > with result 'exit-code'.
> > >  Oct 30 09:59:11 riot..com systemd[1]: Failed to start Dovecot 
> > > IMAP/POP3 email server.
> > >  
> > >  This seems to be like a bug as no configuration was changed by me in the 
> > > middle of the night.
> > >  I recall there were similar errors/bug reports in the past were it 
> > > seemed it was managesieve but wasn't, people had some misconfigurations 
> > > in the dovecot.conf. I did not change my dovecot.conf since April.
> > >  But maybe here it is a pigeonhole issue.
> > >  
> > >  As I did not find any reason for it I changed the repo and downgraded to 
> > > 2.3.16-2 now and it runs without any flaws, like all the time before. I 
> > > had no time to investigate this any longer thand 2 hours with 2.3.17 
> > > installed as this is a production server and I need the email access. I 
> > > also did not find anything adressable in the logs.
> > >  
> > >  [root@riot dovecot]# systemctl status dovecot
> > >  ● dovecot.service - Dovecot IMAP/POP3 email server
> > >  Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled; vendor 
> > > preset: disabled)
> > >  Active: active (running) since Sat 2021-10-30 10:18:11 CEST; 2s ago
> > >  Docs: man:dovecot(1)
> > >  https://doc.dovecot.org/
> > >  Process: 32398 ExecStartPre=/usr/libexec/dovecot/prestartscript 
> > > (code=exited, status=0/SUCCESS)
> > >  Main PID: 32452 (dovecot)
> > >  Status: "v2.3.16 (7e2e900c1a) running"
> > >  Tasks: 4 (limit: 99912)
> > >  Memory: 4.4M
> > >  CGroup: /system.slice/dovecot.service
> > >  ├─32452 /usr/sbin/dovecot -F
> > >  ├─32507 dovecot/anvil
> > >  ├─32508 dovecot/log
> > >  └─32513 dovecot/config
> > >  
> > >  Oct 30 10:18:11 riot..com systemd[1]: Starting Dovecot IMAP/POP3 
> > > email server...
> > >  Oct 30 10:18:11 riot..com dovecot[32452]: Warning: Corrected 
> > > permissions for login directory /var/run/dovecot/token-login
> > >  Oct 30 10:18:11 riot..com dovecot[32452]: master: Warning: 
> > > Corrected permissions for login directory /var/run/dovecot/token-login
> > >  Oct 30 10:18:11 riot..com dovecot[32452]: master: Dovecot 
> > > v2.3.16 (7e2e900c1a) starting up for imap, lmtp, sieve
> > >  Oct 30 10:18:11 riot..com systemd[1]: Started Dovecot IMAP/POP3 
> > > email server.
> > >  
> > >  
> > >  This is the configuration
> > >  # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf
> > >  # Pigeonhole version 0.5.16 (09c29328)
> > >  # OS: Linux 4.18.0-305.19.1.el8_4.x86_64 x86_64 AlmaLinux release 8.4 
> > > (Electric Cheetah)
> > >  # Hostname: riot..com
> > >  auth_mechanisms = plain login
> > >  auth_verbose = yes
> > >  listen = *
> > >  mail_gid = vmail
> > >  mail_home = /var/vmail/mailboxes/%d/%n
> > >  mail_location = maildir:~/mail:LAYOUT=fs
> > >  mail_plugins = " quota fts fts_solr"
> > >  mail_privileged_group = vmail
> > >  mail_uid = vmail
> > >  managesieve_notify_capability = mailto
> > >  

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 
> me:
> 
> default_vsz_limit = 0
> 
> 
> > On Oct 28, 2021, at 12:12 PM, Don Feliciano  
> > wrote:
> > 
> > Same issue in 2.3.17
> > 
> > dovecot-2.3.17.tar.gz:
> > ./configure --prefix=/usr/local/Cellar/dovecot/2.3.17 
> > --libexecdir=/usr/local/Cellar/dovecot/2.3.17/libexec 
> > --sysconfdir=/usr/local/etc --localstatedir=/usr
> > make install
> > 
> > dovecot-2.3-pigeonhole-0.5.17.tar.gz:
> > ./configure --with-dovecot=/usr/local/Cellar/dovecot/2.3.17/lib/dovecot 
> > --prefix=/usr/local/Cellar/dovecot/2.3.17
> > make
> > make install
> > 
> > sudo /usr/local/opt/dovecot/sbin/dovecot -F
> > Warning: fd limit (ulimit -n) is lower than required under max. load (256 < 
> > 1000), because of default_client_limit
> > Oct 28 12:08:48 service(log): Fatal: setrlimit(RLIMIT_DATA, 268435456): 
> > Invalid argument
> > 
> > 
> > > On Oct 27, 2021, at 11:08 AM, Don Feliciano  
> > > wrote:
> > > 
> > > 
> > > I've been happily running Dovecot on my Mac for many years (installed via 
> > > Homebrew). After upgrading to Monterey (MacOS 12.01), it no longer starts:
> > > 
> > > $ sw_vers
> > > ProductName: macOS
> > > ProductVersion: 12.0.1
> > > BuildVersion: 21A559
> > > 
> > > $ uname -a
> > > Darwin dfelicia-mac 21.1.0 Darwin Kernel Version 21.1.0: Wed Oct 13 
> > > 17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64 x86_64
> > > 
> > > $ sudo dovecot -F
> > > Oct 27 10:11:18 service(log): Fatal: setrlimit(RLIMIT_DATA, 268435456): 
> > > Invalid argument
> > > 
> > > $ mount
> > > /dev/disk1s2s1 on / (apfs, sealed, local, read-only, journaled)
> > > devfs on /dev (devfs, local, nobrowse)
> > > /dev/disk1s5 on /System/Volumes/VM (apfs, local, noexec, journaled, 
> > > noatime, nobrowse)
> > > /dev/disk1s3 on /System/Volumes/Preboot (apfs, local, journaled, nobrowse)
> > > /dev/disk1s6 on /System/Volumes/Update (apfs, local, jour naled, nobrowse)
> > > /dev/disk1s1 on /System/Volumes/Data (apfs, local, journaled, nobrowse)
> > > 
> > > $ sudo dovecot -n
> > > # 2.3.16 (7e2e900c1a): /usr/local/etc/dovecot/dovecot.conf
> > > # Pigeonhole version 0.5.16 (09c29328)
> > > # OS: Darwin 21.1.0 x86_64 apfs
> > > # Hostname: dfelicia-mac
> > > default_internal_group = mail
> > > default_internal_user = _dovecot
> > > default_login_user = _dovenull
> > > first_valid_uid = 100
> > > listen = 127.0.0.1
> > > log_path = /var/log/dovecot.log
> > > mail_location = maildir:/usr/local/var/mail/%u
> > > managesieve_notify_capability = mailto
> > > managesieve_sieve_capability = fileinto reject envelope encoded-character 
> > > vacation subaddress comparator-i;ascii-numeric relational regex 
> > > imap4flags copy include variables body enotify environment mailbox date 
> > > index ihave duplicate mime foreverypart extracttext
> > > namespace inbox {
> > >  inbox = yes
> > >  location =
> > >  mailbox Drafts {
> > >  special_use = \Drafts
> > >  }
> > >  mailbox Junk {
> > >  special _use = \Junk
> > >  }
> > >  mailbox Sent {
> > >  special_use = \Sent
> > >  }
> > >  mailbox "Sent Messages" {
> > >  special_use = \Sent
> > >  }
> > >  mailbox Trash {
> > >  special_use = \Trash
> > >  }
> > >  prefix =
> > > }
> > > passdb {
> > >  args = login
> > >  driver = pam
> > > }
> > > protocols = imap
> > > service imap-login {
> > >  inet_listener imap {
> > >  address = 127.0.0.1
> > >  port = 143
> > >  }
> > >  inet_listener imaps {
> > >  address = 127.0.0.1
> > >  ssl = no
> > >  }
> > > }
> > > ssl = no
> > > userdb {
> > >  driver = passwd
> > > }
> > > 
> > > $ ulimit -Ha
> > > core file size (blocks, -c) unlimited
> > > data seg size (kbytes, -d) unlimited
> > > file size (blocks, -f) unlimited
> > > max locked memory (kbytes, -l) unlimited
> > > max memory size (kbytes, -m) unlimited
> > > open files (-n) unlimited
> > > pipe size (512 bytes, -p) 1
> > > stack size (kbytes, -s) 65532
> > > cpu time (seconds, -t) unlimited
> > > max user processes (-u) 2784
> > > virtual memory (kbytes, -v) unlimited
> > > 
> > > 
> > > 
> >