- dovecot - dovecot.org

Oauth2 MFA config
by Scott Q. 24 May '24

24 May '24

Anyone managed to get Dovecot working as smoothly with OAUTH2 as Gmail has with Outlook ? So that for example when you add the account up in Outlook it performs all the required steps for saving the device, getting tokens, etc. Ideally with a custom ID provider, not Google as described here: https://doc.dovecot.org/configuration_manual/authentication/oauth2/

2 1

I can't configure shared mailbox ACLs using LDAP information
by moso.mosoleu＠gmail.com 23 May '24

23 May '24

It shouldn't be impossible, but I've tried countless ways and not even ChatGPT 4o was able to help me! :D I use three LDIF files to get OpenLDAP ready for testing. In the first LDIF I just modify the schema to add the associatedDomain attributes (then I could configure the server to serve more than one domain). The second LDIF is to add 4 objects to the schema that I use to differentiate accounts that actually receive/send emails and have a password; another thing done in it is to add a "groupOfUniqueNamesWithMail" object that allows the "mail" and "mailEnabled" attributes that are then necessary to use in the entries created in the "shared-mailboxes" OU. Finally, the third LDIF populates the LDAP by creating OUs, user accounts and creating entries in "shared-mailboxes" that serve to say which user accounts have access to which other user accounts. When I start the email server, sending and receiving emails works perfectly. And mailbox shares work as expected if I manually use, for each share, the command: doveadm acl set -u admin(a)mydomain.com.br INBOX user=user.1(a)mydomain.com.br lookup read write write-seen write-deleted insert post expunge create delete But just as authentication works perfectly via LDAP, I believe there must be a way to configure Dovecot to dynamically adjust ACLs via LDAP. The configuration in principle would be this: acl_search_base = ou=shared-mailboxes,dc=mydomain,dc=com,dc=br acl_search_filter = (&(objectClass=groupOfUniqueNamesWithMail)(|(uniqueMember=mail=%u,ou=system-accounts,dc=mydomain,dc=com,dc=br)(uniqueMember=mail=%u,ou=department-accounts ,dc=mydomain,dc=com,dc=br)(uniqueMember=mail=%u,ou=mailing-accounts,dc=mydomain,dc=com,dc=br)(uniqueMember=mail=%u,ou=person -accounts,dc=mydomain,dc=com,dc=br))) acl_user = %u Testing this filter on the command line with "ldapsearch" the expected results are returned. I mean, I enter an email address from a user account and the result is all the other user account email addresses that the first one would have access to. Any charitable soul who is willing to help and needs more information, just say what you need and I will try to respond as quickly as possible. I will place the content of the three LDIFs below. [ 01-modify_domain.ldif ] dn: dc=mydomain,dc=com,dc=br changetype: modify add: objectClass objectClass: domainRelatedObject - add: associatedDomain associatedDomain: mydomain.com.br - add: associatedDomain associatedDomain: anotherdomain.com.br [ 02-add_my_object_classes_to_schema.ldif ] # Object class for system user accounts dn: cn=SystemAccount,cn=schema,cn=config objectClass: olcSchemaConfig cn: SystemAccount olcObjectClasses: ( 1.3.6.1.4.1.99999.1.1 NAME 'SystemAccount' DESC 'Object class for system accounts' SUP top AUXILIARY ) # Object class for department user accounts dn: cn=DepartmentAccount,cn=schema,cn=config objectClass: olcSchemaConfig cn: DepartmentAccount olcObjectClasses: ( 1.3.6.1.4.1.99999.1.2 NAME 'DepartmentAccount' DESC 'Object class for department accounts' SUP top AUXILIARY ) # Object class for mailing user accounts dn: cn=MailingAccount,cn=schema,cn=config objectClass: olcSchemaConfig cn: MailingAccount olcObjectClasses: ( 1.3.6.1.4.1.99999.1.3 NAME 'MailingAccount' DESC 'Object class for mailing accounts' SUP top AUXILIARY ) # Object class for person user accounts dn: cn=PersonAccount,cn=schema,cn=config objectClass: olcSchemaConfig cn: PersonAccount olcObjectClasses: ( 1.3.6.1.4.1.99999.1.4 NAME 'PersonAccount' DESC 'Object class for person accounts' SUP top AUXILIARY ) # Object class that allows groupOfUniqueNames to have a mail attribute dn: cn=groupOfUniqueNamesWithMail,cn=schema,cn=config objectClass: olcSchemaConfig cn: groupOfUniqueNamesWithMail olcObjectClasses: ( 1.3.6.1.4.1.99999.1.5 NAME 'groupOfUniqueNamesWithMail' SUP groupOfUniqueNames STRUCTURAL MAY ( mail $ mailEnabled ) ) [ 03-initialize_mydomain.com.br.ldif ] ### Create organizaitonal units dn: ou=system-accounts,dc=mydomain,dc=com,dc=br ou: system-accounts objectClass: organizaitonalUnit objectClass: top dn: ou=department-accounts,dc=mydomain,dc=com,dc=br ou: department-accounts objectClass: organizaitonalUnit objectClass: top dn: ou=mailing-accounts,dc=mydomain,dc=com,dc=br ou: mailing-accounts objectClass: organizaitonalUnit objectClass: top dn: ou=person-accounts,dc=mydomain,dc=com,dc=br ou: person-accounts objectClass: organizaitonalUnit objectClass: top dn: ou=shared-mailboxes,dc=mydomain,dc=com,dc=br ou: shared-mailboxes objectClass: organizaitonalUnit objectClass: top ################################################################################ ## Create System User Accounts # not related to a person # can be accessed directly or indirectly by more than one person dn: mail=admin(a)mydomain.com.br,ou=system-accounts,dc=mydomain,dc=com,dc=br uid: admin userPassword: {SSHA} displayName: My Domain - Admin givenName: System sn: Admin cn: System Admin mail: admin(a)mydomain.com.br mailAlias: root(a)mydomain.com.br mailAlias: postmaster(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/system-accounts/admin/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/system-accounts/admin/ descripiton: My Domain - Admin (root/postmaster) objectClass: PostfixBookMailAccount objectClass: SystemAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top dn: mail=smtp(a)mydomain.com.br,ou=system-accounts,dc=mydomain,dc=com,dc=br uid: smtp userPassword: {SSHA} displayName: My Domain - SMTP givenName: System sn: SMTP cn: System SMTP mail: smtp(a)mydomain.com.br mailAlias: no-reply(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/system-accounts/smtp/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/system-accounts/smtp/ descripiton: My Domain - System SMTP objectClass: PostfixBookMailAccount objectClass: SystemAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top dn: mail=smtp-auditor(a)mydomain.com.br,ou=system-accounts,dc=mydomain,dc=com,dc=br uid: smtp-auditor userPassword: {SSHA} displayName: My Domain - SMTP Auditor givenName: System sn: SMTP Auditor cn: System SMTP Auditor mail: smtp-auditor(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/system-accounts/smtp-auditor/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/system-accounts/smtp-auditor/ descripiton: My Domain - System SMTP Auditor objectClass: PostfixBookMailAccount objectClass: SystemAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top ################################################################################ ## Create Department User Accounts # not related to a person # can be accessed directly or indirectly by more than one person dn: mail=it(a)mydomain.com.br,ou=department-accounts,dc=mydomain,dc=com,dc=br uid: it userPassword: {SSHA} displayName: My Domain - Information Technology givenName: My Domain sn: IT cn: My Domain - IT mail: it(a)mydomain.com.br mailAlias: information.technology(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/department-accounts/it/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/department-accounts/it/ descripiton: My Domain - Information Technology (IT) objectClass: PostfixBookMailAccount objectClass: DepartmentAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top ################################################################################ ## Create Mailing User Accounts # not related to a person # can be accessed directly or indirectly by more than one person dn: mail=everyone(a)mydomain.com.br,ou=mailing-accounts,dc=mydomain,dc=com,dc=br uid: everyone userPassword: {SSHA} displayName: My Domain - Everyone givenName: My Domain sn: everyone cn: My Domain - Everyone mail: everyone(a)mydomain.com.br mailAlias: everyone(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/mailing-accounts/everyone/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/mailing-accounts/everyone/ descripiton: My Domain - Everyone mailing list objectClass: PostfixBookMailAccount objectClass: MailingAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top dn: mail=mailing.list.1(a)mydomain.com.br,ou=mailing-accounts,dc=mydomain,dc=com,dc=br uid: mailing.list.1 userPassword: {SSHA} displayName: My Domain - Mailing List 1 givenName: My Domain sn: Mailing List 1 cn: My Domain - Mailing List 1 mail: mailing.list.1(a)mydomain.com.br mailAlias: ml.1(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/mailing-accounts/mailing.list.1/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/mailing-accounts/mailing.list.1/ descripiton: My Domain - Mailing List 1 objectClass: PostfixBookMailAccount objectClass: MailingAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top dn: mail=mailing.list.2(a)mydomain.com.br,ou=mailing-accounts,dc=mydomain,dc=com,dc=br uid: mailing.list.2 userPassword: {SSHA} displayName: My Domain - Mailing List 2 givenName: My Domain sn: Mailing List 2 cn: My Domain - Mailing List 2 mail: mailing.list.2(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/mailing-accounts/mailing.list.2/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/mailing-accounts/mailing.list.2/ descripiton: My Domain - Mailing List 2 objectClass: PostfixBookMailAccount objectClass: MailingAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top ################################################################################ ## Create Person User Accounts dn: mail=user.1(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br uid: user.1 userPassword: {SSHA} displayName: User 1 givenName: User sn: 1 cn: User 1 mail: user.1(a)mydomain.com.br mailAlias: user.one(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/person-accounts/user.1/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/person-accounts/user.1/ descripiton: My Domain - User 1 objectClass: PostfixBookMailAccount objectClass: PersonAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top dn: mail=user.2(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br uid: user.2 userPassword: {SSHA} displayName: User 2 givenName: User sn: 2 cn: User 2 mail: user.2(a)mydomain.com.br mailAlias: user.two(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/person-accounts/user.2/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/person-accounts/user.2/ descripiton: My Domain - User 2 objectClass: PostfixBookMailAccount objectClass: PersonAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top dn: mail=user.3(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br uid: user.3 userPassword: {SSHA} displayName: User 3 givenName: User sn: 3 cn: User 3 mail: user.3(a)mydomain.com.br mailAlias: user.three(a)mydomain.com.br mailEnabled: TRUE mailUidNumber: 5000 mailGidNumber: 5000 mailHomeDirectory: /var/mail/mydomain.com.br/person-accounts/user.3/ mailStorageDirectory: maildir:/var/mail/mydomain.com.br/person-accounts/user.3/ descripiton: My Domain - User 3 objectClass: PostfixBookMailAccount objectClass: PersonAccount objectClass: inetOrgPerson objectClass: organizaitonalPerson objectClass: person objectClass: top ################################################################################ ## for Shared System User Accounts dn: cn=admin(a)mydomain.com.br,ou=shared-mailboxes,dc=mydomain,dc=com,dc=br mail: admin(a)mydomain.com.br mailEnabled: TRUE uniqueMember: mail=user.1(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br objectClass: groupOfUniqueNames objectClass: groupOfUniqueNamesWithMail objectClass: top ## for Shared Department User Accounts dn: cn=it(a)mydomain.com.br,ou=shared-mailboxes,dc=mydomain,dc=com,dc=br mail: it(a)mydomain.com.br mailEnabled: TRUE uniqueMember: mail=user.1(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br objectClass: groupOfUniqueNames objectClass: groupOfUniqueNamesWithMail objectClass: top ## for Shared Mailing User Accounts dn: cn=everyone(a)mydomain.com.br,ou=shared-mailboxes,dc=mydomain,dc=com,dc=br mail: everyone(a)mydomain.com.br mailEnabled: TRUE uniqueMember: mail=user.1(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br uniqueMember: mail=user.2(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br uniqueMember: mail=user.3(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br objectClass: groupOfUniqueNames objectClass: groupOfUniqueNamesWithMail objectClass: top dn: cn=mailing.list.1(a)mydomain.com.br,ou=shared-mailboxes,dc=mydomain,dc=com,dc=br mail: mailing.list.1(a)mydomain.com.br mailEnabled: TRUE uniqueMember: mail=user.2(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br uniqueMember: mail=user.3(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br objectClass: groupOfUniqueNames objectClass: groupOfUniqueNamesWithMail objectClass: top dn: cn=mailing.list.2(a)mydomain.com.br,ou=shared-mailboxes,dc=mydomain,dc=com,dc=br mail: mailing.list.2(a)mydomain.com.br mailEnabled: TRUE uniqueMember: mail=user.1(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br objectClass: groupOfUniqueNames objectClass: groupOfUniqueNamesWithMail objectClass: top ## for Shared User Accounts dn: cn=user.2(a)mydomain.com.br,ou=shared-mailboxes,dc=mydomain,dc=com,dc=br mail: user.2(a)mydomain.com.br mailEnabled: FALSE uniqueMember: mail=user.1(a)mydomain.com.br,ou=person-accounts,dc=mydomain,dc=com,dc=br objectClass: groupOfUniqueNames objectClass: groupOfUniqueNamesWithMail objectClass: top

3 3

Command "doveadm director kick ...." doesn't work
by g.carabella＠panservice.it 23 May '24

23 May '24

Hi, I have a Dovecot installation (version 2.3.16) with 3 directors and 4 backend servers. Three backend servers have the director_tag 'new', one has the director_tag 'old'. The users are on the DB, the director_tag is a table field. I want to migrate mailboxes from the old backend (Maildir format) to the new (mdbox format). For the migration I use the "doveadm backup" command and everything works fine. The problem I'm having is that I can't kick the user (if logged in). Once the migration is done (as indicated https://doc.dovecot.org/3.0/man/doveadm-sync.1/) I modify the user's home, mail_location and director_tag and then execute the command "doveadm director kick ..." but the connection on the directors is not killed. Why does this problem occur? Could it be due to the use of the director_tag and the fact that for the command "doveadm director kick ..." it is not possible to specify it? Even if I run the command "doveadm director move mailbox_account new_backend_server", the director adds a new connection but does not kill the previous one, with the result that there are two connections for the same user, one on the new backend and one on the old one. I also tried to configure the director_tag only for the 3 new servers, but the "director kick" still doesn't work.

1 0

Problems using non-libc memory allocators
by bl0v3 22 May '24

22 May '24

Hey I was trying to use dovecot2 with a not libc based memory allocation such as scudo or graphene-hardened or graphene-hardened-light but ran into the issues I described in https://github.com/NixOS/nixpkgs/issues/313721 I just wanted to mention this here as well as this behavior may suggest a flaw in the memory allocation mechanism of dovecot2/anvil. I haven't yet found the time to check the underlaying issue as I'm quite busy rn. So I thought id just mention what I came across in case this is actually unexpected or potentially even security relevant mis/behavior.

2 1

Dovecot calculating quota wrong or am I stupid?
by jarland＠mxroute.com 21 May '24

21 May '24

I'm currently running 2.3.21 on this system and here's what I'm seeing (a bit cut down for excess): # doveadm quota get -u emailuser(a)domain.net STORAGE 1052385 MESSAGE 2741 So the storage is roughly more than 1GB according to Dovecot. No change after quota recalc. But: root@arrow:/home/username/imap/domain.net# du -sh emailuser 692M emailuser There are no symlinks or anything like that. Quota config is pretty basic: root@arrow:/etc/dovecot# cat conf.d/90-quota.conf #add quota to end of line in: #/etc/dovecot/conf/mail_plugins.conf, eg: #mail_plugins = $mail_plugins quota #add imap_quota to end of line in: #/etc/dovecot/conf/imap_mail_plugins.conf, eg: #mail_plugins = $mail_plugins imap_quota plugin { quota = maildir } If anyone has advice I would greatly appreciate it.

1 1

Re: After user disconnect run the custom script
by Michael Slusarz 20 May '24

20 May '24

> On 05/20/2024 9:43 AM MDT Alexey Krylov via dovecot <dovecot(a)dovecot.org> wrote: > > Please, send me the link, where I can find the info about configuring > firing script after dovecot client is disconnected. > > I found post-login scripting. Than's cool, but... I need to fire script > a little bit later. See https://doc.dovecot.org/admin_manual/list_of_events/#mail-user-session-fini… You will need to build a event listener for this event, and then do your scripting in there. michael

1 0

After user disconnect run the custom script
by Alexey Krylov 20 May '24

20 May '24

Sirs, good day. Please, send me the link, where I can find the info about configuring firing script after dovecot client is disconnected. I found post-login scripting. Than's cool, but... I need to fire script a little bit later. May be I try to build crutches... But I wish with all my heart to do this. Thanks to everyone who responded. -- Это сообщение было проверено антивирусным ПО Avast на наличие вирусов. www.avast.com

1 0

Errors after enable add mail_attachment_detection_options
by Ricardo Machini 20 May '24

20 May '24

Hello, I got a lot of fatal errors on differents mailbox after I added the option: mail_attachment_detection_options = add-flags Rocky Linux release 8.9 (Green Obsidian) 2.3.21 (47349e2482) May 16 15:03:00 Panic: imap(user(a)domain.com.br)<1669762><cOqoC5YYQlq63CaF>: file imap-sieve-storage.c: line 317 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box) May 16 15:03:00 Error: imap(user(a)domain.com.br)<1669762><cOqoC5YYQlq63CaF>: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x41) [0x7f2c9d8b9761] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x22) [0x7f2c9d8b9882] -> /usr/lib64/dovecot/libdovecot.so.0(+0x10bb6b) [0x7f2c9d8c6b6b] -> /usr/lib64/dovecot/libdovecot.so.0(+0x10bc07) [0x7f2c9d8c6c07] -> /usr/lib64/dovecot/libdovecot.so.0(+0x5cec5) [0x7f2c9d817ec5] -> /usr/lib64/dovecot/lib95_imap_sieve_plugin.so(+0x7ebc) [0x7f2c9b011ebc] -> /usr/lib64/dovecot/lib95_imap_sieve_plugin.so(+0x815f) [0x7f2c9b01215f] -> /usr/lib64/dovecot/lib20_zlib_plugin.so(+0x4a37) [0x7f2c9c179a37] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_free+0x12) [0x7f2c9dc73982] -> /usr/lib64/dovecot/lib95_imap_sieve_plugin.so(+0x71be) [0x7f2c9b0111be] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_free+0x1e) [0x7f2c9dbef55e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf124f) [0x7f2c9dc8624f] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_transaction_commit_full+0x80) [0x7f2c9dc9f900] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_transaction_commit+0xf1) [0x7f2c9dc867e1] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xccb15) [0x7f2c9dc61b15] -> /usr/lib64/dovecot/lib95_imap_sieve_plugin.so(+0x885d) [0x7f2c9b01285d] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0x13de4) [0x7f2c9c79fde4] -> /usr/lib64/dovecot/lib15_notify_plugin.so(+0x240d) [0x7f2c9c9cf40d] -> /usr/lib64/dovecot/lib10_quota_plugin.so(+0xfcdf) [0x7f2c9cde5cdf] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x7a) [0x7f2c9dc000ba] -> dovecot/imap [user(a)domain.com.br 186.220.38.133 UID COPY](+0x153c2) [0x559668ce73c2] -> dovecot/imap [user(a)domain.com.br 186.220.38.133 UID COPY](command_exec+0x6c) [0x559668cf559c] -> dovecot/imap [user(a)domain.com.br 186.220.38.133 UID COPY](+0x215af) [0x559668cf35af] -> dovecot/imap [user(a)domain.com.br 186.220.38.133 UID COPY](+0x21661) [0x559668cf3661] -> dovecot/imap [user(a)domain.com.br 186.220.38.133 UID COPY](+0x21882) [0x559668cf3882] -> dovecot/imap [ user(a)domain.com.br 186.220.38.133 UID COPY](client_handle_input+0x1c5) [0x559668cf3a95] -> dovecot/imap [user(a)domain.com.br 186.220.38.133 UID COPY](client_input+0x76) [0x559668cf3f96] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x6d) [0x7f2c9d8dd84d] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x139) [0x7f2c9d8def09] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7f2c9d8dd8f0] May 16 15:03:00 Fatal: imap(user(a)domain.com.br)<1669762><cOqoC5YYQlq63CaF>: master: service(imap): child 1669762 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Regards, Ricardo

1 0

Change the default base_dir to /run from ${prefix}/var/run
by Дилян Палаузов 20 May '24

20 May '24

Hello, at 6b1bcf1bad1d7, calling ./configure && make install sets prefix=/usr/local, and thus the default base_dir = /usr/local/var/run/dovecot. Moreover it installs /usr/lib/systemd/system/dovecot.service with [Service] ProtectSystem=full. ProtectSystem=full mounts /usr as read-only, so no files can be written under the default base_dir. The Linux Hierachy Standard says for /usr/local - https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s09.html - directories bin, etc, games, include, lib, man, sbin, share, and src must be in /usr/local. No other directories, except those listed below, may be in /usr/local after first installing a FHS-compliant system. var is not listed below. (“below” means the citation above, not the next paragraph) For /var/run LSH contains - https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#varrunRuntimeVari… - This directory was once intended for system information data describing the system since it was booted. These functions have been moved to /run; this directory exists to ensure compatibility with systems and software using an older version of this specification. In general, the requirements for /run shall also apply to /var/run. It is valid to implement /var/run as a symlink to /run. . For /run LHS mentions “This directory contains system information data describing the system since it was booted. Files under this directory must be cleared (removed or truncated as appropriate) at the beginning of the boot process.” The defaults base_dir=/usr/local/var/run/dovecot and ProtectSystem=full present a non-working configuration. • Please consider changing the default (implicit) value of base_dir to /run. • When prefix is /usr/local, then dovecot.service should be installed in /usr/local/lib/systemd/system/. Kind regards Дилян

1 1

example/config misses required section names for passdb{} and userdb{}
by Дилян Палаузов 20 May '24

20 May '24

Hello, I installed Dovecot from git 6b1bcf1bad1d78e, copied /usr/local/share/doc/dovecot/example/config to /usr/local/etc/dovecot and called dovecot -F . The system reported doveconf: Fatal: Error in configuration file /usr/local/etc/dovecot/conf.d/auth-system.conf.ext line 11: passdb { } is missing section name The problem remains, if I delete dovecot-dict-auth.conf.ext dovecot-ldap.conf.ext dovecot-oauth2.conf.ext dovecot-sql.conf.ext conf.d/auth-deny.conf.ext conf.d/auth-ldap.conf.ext conf.d/auth-passwdfile.conf.ext conf.d/auth-static.conf.ext conf.d/auth-dict.conf.ext conf.d/auth-master.conf.ext conf.d/auth-sql.conf.ext thus leaving passdb {} and userdb {} defined on a single place. Indeed, auth-system.conf.ext contains the sections passdb and userdb without the optional name, as described at https://doc.dovecot.org/configuration_manual/config_file/#sections . The problem report is that the example configuration does not contain for sections userdb and passdb a section name, and at the same time the as optional described section name is mandatory in Dovecot on these places. Kind regards Dilyan

2 1