- dovecot - dovecot.org

dict: Error: Fatal error in defaults handling. Program aborted
by Hugo Manuel Ojendiz Lemus 10 Apr '19

10 Apr '19

Good day to everyone Currently, I'm trying to implement the sieve "vacation" plugin with the sieve "Extdata" plugin to lookup information from a MySQL remote server. I'm following the instructions in the documentation: https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/Extdata ===== I have the following error === Apr 09 13:46:51 mail dovecot[5512]: dict: Error: Fatal error in defaults handling. Program aborted Apr 09 13:46:51 mail dovecot[5512]: lmtp(usrx(a)themail.com)<5539><PNwlBJvorFyjFQAAYWwSRA:2>: Warning: sieve: before: line 18: extdata: failed to lookup value `reply_enabled': Connection closed (reply took 0.016 secs (0.017 in dict wait, 0.000 in other ioloops, 0.000 in locks, async-id reply 0.001 secs ago)) Apr 09 13:46:51 mail dovecot[5512]: dict: Fatal: master: service(dict): child 5542 killed with signal 11 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Apr 09 13:46:51 mail.halmex.com.mx dovecot[5512]: dict: Error: Fatal error in defaults handling. Program aborted ============================ ====== Dovecot Information ====== 2.3.5.1 (7ec6d0ade): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.5 (2483b085) # OS: Linux 3.10.0-514.16.1.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) xfs doveconf: Warning: please set ssl_dh=</etc/dovecot/dh.pem doveconf: Warning: You can generate it with: dd if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dhparam -inform der > /etc/dovecot/dh.pem dict { sieve = mysql:/etc/dovecot/pigeonhole-sieve.dict } log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/var/vmail/%d/%Ln 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 = prefix = separator = . type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { pop3_migration_mailbox = imapc: sieve_extdata_dict_uri = proxy::sieve sieve_global_extensions = +vnd.dovecot.extdata sieve_plugins = sieve_extdata sieve_vacation_send_from_recipient = yes sieve_before = /var/lib/dovecot/before.sieve } pop3c_host = mail.halmex.com.mx service auth-worker { user = root } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0600 user = vmail } user = root } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } userdb { args = uid=5000 gid=5000 home=/var/vmail/%d/%Ln allow_all_users=yes driver = static } protocol pop3 { disable_plaintext_auth = no } protocol doveadm { mail_plugins = " pop3_migration" } protocol lmtp { mail_plugins = " sieve" } ============================ An important bit of information it's that the dict service was trying to read the /etc/my.cnf file, but SELinux prevent it, and the sieve script worked fine, once I solved the SELinux access problem, the errors began to appear. This is a postfix server working great for years, with a local MariaDB. The remote MySQL server its in the same LAN and Its reachable by the mail server and other servers, the account has access, and like Ive mention, before I gave access to the local /etc/my.cnf the sieve script worked fine (just the SELinux warnings). Looks like the dict service has problems with the local MariaDB configuration file, but in this scenario its not required Any information or help you can provide me would be greatly appreciated. Hugo Manuel Ojendiz Lemus Desarrollo | Recursos Humanos | HALMEX ((°J°))

2 1

Where to report (potential) Dovecot bugs
by Mark Moseley 10 Apr '19

10 Apr '19

I'm curious if this is still the right place to report potential bugs with Dovecot. Is there a Dovecot bug tracker somewhere?

2 2

LMTP, PAM session and home directory autocreating
by Ivars Strazdins 09 Apr '19

09 Apr '19

Hi, mail is delivered by Dovecot's lmtp locally and I need user's home directory to be created if it doesn't exist yet. There is a setting in Dovecot's configuration, "session=yes", in /etc/Dovecot/conf.d/auth-system.conf.ext, which should do that. passdb { driver = pam args = session=yes dovecot } But I think it does not work in my setup because I do not see any PAM log entry for Dovecot when this error happens: Apr 9 13:01:55 mailhost dovecot: lmtp(2935): Connect from local Apr 9 13:01:55 mailhost dovecot: lmtp(2935, testuser): Error: User initialization failed: Namespace '': mkdir(/home/testuser/Maildir) failed: Permission denied (euid=174000327(testuser) egid=174000327(testuser ) missing +w perm: /home, dir owned by 0:0 mode=0755) Apr 9 13:01:55 mailhost dovecot: lmtp(2935): Disconnect from local: Successful quit The error above seems expected, because it is not lmtp agent's job to create user's home directory but pam_oddjob_mkhomedir.so module should do that. Right? And there are log entries every PAM user session: Apr 9 13:24:42 mailhost auth: pam_sss(dovecot:auth): authentication success; logname= uid=0 euid=0 tty=dovecot ruser=validuser rhost=::1 user= validuser Apr 9 13:24:42 mailhost auth: pam_unix(dovecot:session): session opened for user validuser by (uid=0) Apr 9 13:24:42 mailhost auth: pam_unix(dovecot:session): session closed for user validuser I ask for help how to debug this problem and find out why Dovecot does not open PAM session or - if I am wrong and it does, then what else is going wrong. Home directory autocreation is configured with command "authconfig --enablemkhomedir --update" and it works if user logs into system manually. I tried to enable "mail_debug" in Dovecot's settings, but it did not give me any more information on PAM session. Running on Centos 7.6, with Dovecot 2.2.36. I sort of remember this was working 2 years ago when I enabled "session=yes" but something has changed along the way with all the Centos updates. Thank you very much in advance for your time. Ivars /etc/pam.d/dovecot #%PAM-1.0 auth required pam_nologin.so auth include password-auth account include password-auth session include password-auth /etc/pam.d/password-auth #%PAM-1.0 # This file is auto-generated. # User changes will be destroyed the next time authconfig is run. auth required pam_env.so auth [default=1 success=ok] pam_localuser.so auth [success=done ignore=ignore default=die] pam_unix.so nullok try_first_pass auth requisite pam_succeed_if.so uid >= 1000 quiet_success auth sufficient pam_sss.so forward_pass auth required pam_deny.so account required pam_unix.so account sufficient pam_localuser.so account sufficient pam_succeed_if.so uid < 1000 quiet account [default=bad success=ok user_unknown=ignore] pam_sss.so account required pam_permit.so password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type= password sufficient pam_unix.so sha512 shadow nullok try_first_pass use_authtok password sufficient pam_sss.so use_authtok password required pam_deny.so session optional pam_keyinit.so revoke session required pam_limits.so -session optional pam_systemd.so session optional pam_oddjob_mkhomedir.so umask=0077 session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid session required pam_unix.so session optional pam_sss.so doveconf -n # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 3.10.0-957.10.1.el7.x86_64 x86_64 CentOS Linux release 7.6.1810 (Core) # Hostname: mailhost.example.com auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-master auth_username_format = %Ln auth_verbose = yes default_client_limit = 3500 default_process_limit = 500 disable_plaintext_auth = no first_valid_uid = 203 imap_client_workarounds = tb-lsub-flags tb-extra-mailbox-sep lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_save_to_detail_mailbox = yes mail_location = maildir:~/Maildir:INBOX=~/Maildir:LAYOUT=fs mail_plugins = " fts fts_lucene" mail_privileged_group = mail maildir_very_dirty_syncs = yes 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 imapsieve vnd.dovecot.imapsieve mbox_write_locks = fcntl namespace inbox { inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = session=yes dovecot driver = pam } plugin { autocreate = Junk autocreate2 = Sent autocreate3 = Drafts autocreate4 = Trash autosubscribe = Junk autosubscribe2 = Sent autosubscribe3 = Drafts autosubscribe4 = Trash fts = lucene fts_lucene = whitespace_chars=@. imapsieve_mailbox1_before = file:/usr/lib64/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/usr/lib64/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * sieve = file:~/sieve;active=~/roundcube.sieve sieve_before = /var/lib/sieve/junk.sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/lib64/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %v.%u protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = user mode = 0660 user = root } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/letsencrypt/live/webmail.example.com/fullchain.pem ssl_key = # hidden, use -P to show it syslog_facility = local0 userdb { driver = passwd } valid_chroot_dirs = /var/mail:/home protocol lmtp { mail_fsync = never mail_plugins = " fts fts_lucene sieve" postmaster_address = postmaster(a)example.com } protocol lda { mail_fsync = never mail_plugins = " fts fts_lucene sieve expire" } protocol imap { mail_max_userip_connections = 25 mail_plugins = " fts fts_lucene fts fts_squat expire imap_sieve" } protocol sieve { 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 } protocol pop3 { mail_max_userip_connections = 20 mail_plugins = " fts fts_lucene fts fts_squat expire" }

1 0

Problem with filter forwarded messages when using director proxy
by Ted 09 Apr '19

09 Apr '19

Hey there, I've been able to switch our mailservers over to using director to proxy logins and received email to the backend servers which store email on a shared NFS mount. Before I did this we were having trouble with the indexes running into errors because multiple servers accessing and modifying the dovecot.index files at the same time. I'm still seeing a small amount of this, and tracing it through it appears that when an account uses a filter to forward email to another address within our mail system, it recognises that it is a local email address it is responsible for and saves the message locally despite the fact that it is not the director specified server for the recipient address. As an example, lets say that test1(a)example.com is currently pointed to the 01 backend server by director, and test2(a)example.com to 02. If a filter at test1 forwards email to test2, then when an email for test1 comes in the director porxy will direct it to the 01 backend server, and when the message is saved the filter will run to forward it, and the 01 server will recognise that it is also responsible for test2 and so 01 will save the message for test2 rather than 02, as per director. This is causing a smallish number of clashes which I'd like to get cleaned up. I've tried getting the server to send through a relay but if it recognises the account as local it will not use the relay to send the email. Has anyone run into anything like this or have any ideas about how to approach the problem? Thank you Ted easyDNS Technologies

1 0

Editing fail2ban page?
by Mauricio Tavares 09 Apr '19

09 Apr '19

In https://wiki.dovecot.org/HowTo/Fail2Ban, for a current (I know for a fact in 2.2.36) I believe it should be filter = dovecot instead of filter = dovecot-pop3imap [root@mail ~]# ls -l /etc/fail2ban/filter.d/doveco* -rw-r--r-- 1 root root 1875 May 11 2017 /etc/fail2ban/filter.d/dovecot.conf [root@mail ~]#

2 1

dovecot[30008]: auth-worker: Fatal: master: service(auth-worker): child 31074 killed with signal 11
by Herbert 09 Apr '19

09 Apr '19

Hi Since a recent DNF update, I see many log file entries like the following: Apr 08 16:16:36 udoo.symmetrix.ch audit[31074]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=system_u:system_r:dovecot_auth_t:s0 pid=31074 comm="auth" exe="/usr/libexec/dovecot/auth" sig=11 res=1 Apr 08 16:16:36 udoo.symmetrix.ch kernel: traps: auth[31074] general protection fault ip:7ff45b5f98a7 sp:7fff0df96830 error:0 in libmariadb.so.3[7ff45b5d7000+46000] Apr 08 16:16:36 udoo.symmetrix.ch dovecot[30008]: auth-worker: Fatal: master: service(auth-worker): child 31074 killed with signal 11 (core not dumped - https://dovecot.org/bugreport.html#coredumps) Apr 08 16:16:38 udoo.symmetrix.ch abrt-dump-journal-oops[1139]: abrt-dump-journal-oops: Found oopses: 1 Apr 08 16:16:38 udoo.symmetrix.ch abrt-dump-journal-oops[1139]: abrt-dump-journal-oops: Creating problem directories Apr 08 16:16:39 udoo.symmetrix.ch abrt-dump-journal-oops[1139]: Reported 1 kernel oopses to Abrt Apr 08 16:16:39 udoo.symmetrix.ch abrt-server[31104]: Can't find a meaningful backtrace for hashing in '.' Apr 08 16:16:39 udoo.symmetrix.ch abrt-server[31104]: Option 'DropNotReportableOopses' is not configured Apr 08 16:16:39 udoo.symmetrix.ch abrt-server[31104]: Preserving oops '.' because DropNotReportableOopses is 'no' Apr 08 16:16:39 udoo.symmetrix.ch dbus-daemon[1022]: [system] Activating service name='org.freedesktop.problems' requested by ':1.779' (uid=0 pid=31122 comm="/usr/bin/python3 /usr/bin/abrt-action-notify -d /v" label="system_u:system_r:abrt_t:s0-s0:c0.c1023") (using servicehelper) Apr 08 16:16:40 udoo.symmetrix.ch dbus-daemon[1022]: [system] Successfully activated service 'org.freedesktop.problems' Apr 08 16:16:40 udoo.symmetrix.ch abrt-notification[31129]: System encountered a non-fatal error in ??() # uname -a Linux udoo.symmetrix.ch 5.0.5-100.fc28.x86_64 #1 SMP Wed Mar 27 22:16:29 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # dovecot --version 2.3.5 (513208660) # mysql --version mysql Ver 15.1 Distrib 10.2.22-MariaDB, for Linux (x86_64) using readline 5.1 Unfortunately I didn't manage to get a core dump, sorry. Kind regards, Herbert

2 1

Re: SMTPUTF8 support
by David Bürgin 08 Apr '19

08 Apr '19

André, are you quite sure you have it working? In this thread someone from Open-Xchange stated that no, Dovecot doesn’t have SMTPUTF8 support implemented, and the same response was given by another Dovecot developer last September (it ‘is being considered’ was the answer then, see https://dovecot.org/pipermail/dovecot/2018-September/112887.html) I am using LMTP to deliver mail to Dovecot from Postfix, and delivery fails with Postfix reporting: ‘SMTPUTF8 is required, but was not offered by host mail.my.org[private/dovecot-lmtp]’. I doubt that this can work without a change in Dovecot LMTP. Anyway, I am also interested in SMTPUTF8 support, so +1 from me! -- David

6 10

OpenFTS
by Cerebus 05 Apr '19

05 Apr '19

All the discussion on FTS reminds me, is there any plan to support OpenFTS in dovecot or is there a reason preventing that? -- This is my signature. There are many like it, but this one is mine.

2 1

SMTPUTF8 support
by sylvhem＠lepubdelobservateur.fr 05 Apr '19

05 Apr '19

Hi, I'm currently trying to set up SMTPUTF8 on my mail stack, but I can't find any information on Dovecot's RFC 6531 support. Has it been implemented yet? If so, does anyone know how to activate it? Regards. -- Sylvhem

4 5

Solr connection timeout hardwired to 60s
by Peter Mogensen 05 Apr '19

05 Apr '19

Hi, What's the recommended way to handling timeouts on large mailboxes given the hardwired request timeout of 60s in solr-connection.c: http_set.request_timeout_msecs = 60*1000; /Peter

5 5