January 2019 - dovecot

Sieve script unable to file into public folder after dovecot upgrade to version 2.3.4
by Andreas Oster 03 Jan '19

03 Jan '19

Hi all, Wishing you and your families a Happy New Year 2019. I am currently struggling with an odd sieve issue after upgrading dovecot from 2.2.32 to the latest 2.3.4 version. OS is Ubuntu 18.04. For one of our users I have a sieve rule in place which should copy (keep + fileinto) incoming mails from the INBOX to a public namespace folder. Unfortunately this does not work anymore. In the sieve log file of the user I get error messages like this: sieve: info: started log at Jan 02 12:41:31. error: msgid=<dc6bdcb2-7efb-0f0a-3a6d-c1133233c11f(a)novanetwork.de>: failed to store into mailbox 'Public/Verteiler': Permission denied. This is the content of the sieve script : require ["fileinto"]; keep; fileinto "Public/Verteiler"; stop; At first I thought it might be caused by a faulty IMAP ACL but this does not seem to be the case. When I do a manual copy in Thunderbird from the INBOX to this public folder there are no problems at all. Does anybody have an idea what could be the cause of the issue ? Thank you very much for your kind help. Best regards Andreas

1 1

dovecot-uidlist path
by Christos Chatzaras 02 Jan '19

02 Jan '19

When I use this: mail_location = maildir:/home/mail/%d/%n the dovecot-uidlist file is located in: /home/mail/example.com/user/dovecot-uidlist But when I change it to: mail_location = maildir:/home/mail/%d/%n:CONTROL=/var/mail/%d/%n then it's stored in: /var/mail/example.com/user/.INBOX/dovecot-uidlist Any idea why is not stored in: /var/mail/example.com/user/dovecot-uidlist ?

1 0

Error with virtual index "Broken mailbox_count header"
by Tobias Kirchhofer 02 Jan '19

02 Jan '19

Hi, we experience trouble with one of our virtual mailboxes. dovecot-virtual: ` * -INBOX/Trash -INBOX/Spam all ` Error log: ```Error: virtual index /var/vmail/mailboxes/kirchhofer.net/tobias/virtual/all: Broken mailbox_count header``` This happens only with the filter form above. All other virtual mailboxes works fine. Jakobus Schürz experienced something similar: https://www.dovecot.org/list/dovecot/2018-January/110656.html We do not have the panic message. Is this probably something on our side or is this Dovecot? ``` namespace virtual { prefix = Virtual/ separator = / location = virtual:~/virtual } -- collect(a)shift.agency

2 4

Re: Several problems on Solaris10
by Pierluigi Frullani 02 Jan '19

02 Jan '19

On Tue, Jan 1, 2019 at 7:26 PM Sami Ketola <Sami.Ketola(a)open-xchange.com> wrote: > Believe me it does. I used to work for Sun Microsystems for 14 years in > Solaris support and sustaining and I can guarantee you that it does. > > You problem is that Solaris has concept of Secure Runtime Linker, and for > trusted applications most of LD_CONFIG and LD_LIBRARY_PATH is ignored for > security reasons. > > For secure applications LD_LIBRARY_PATH components are ignored for > non-secure directories. > > Your dovecot is probably setuid or setgid and considered as secure > application and secure runtime linker rules are triggered for it. Then > /usr/local is completely ignored from LD_LIBRARY_PATH. > That's rather strange. I too work with solaris ( and for sun in the past ) from sunos 4.1 onwards. I had this previous installation working, with LD_LIBRARY_PATH configured, on solaris 10 u8 since 2014. During this relativelly calm period I did a LiveUpgrade to latest solaris 10 ( u11 ) and the only application that stopped working is dovecot. This mean that ( obviously ) solaris changed something on security. No binary is setuid or setgid in dovecot dir: ls -l /usr/local/dovecot/sbin/dovecot -rwxr-xr-x 1 root root 259452 Dec 29 14:59 /usr/local/dovecot/sbin/dovecot root@puma find . -perm 4000 root@puma find . -perm 2000 root@puma find . -perm 1000 but yes, I agree that eventually the SRL stuffs could make them job. Probably is not tied to the setuid/setgid but with the fork of a binary from inside another one with the LD_LIBRARY_PATH in use. Thus the option is ( could be ) to use the R[UN]PATH feature or the wrapper with the new LD_LIBRARY_PATH ( as I'm doing now altough less secure ) or recompile with the -R option passed to linker, as suggested by James ( and verified to be working at least with the "dump" ). Thanks to all Pigi

2 1

Several problems on Solaris10
by Pierluigi Frullani 01 Jan '19

01 Jan '19

Hi all, I've just upgraded my old Solaris 10 update 8 to Solaris 10 update 11 with the latest patches, but after the reboot with the new update I'm having a lot of problems with dovecot. My version is 2.2.13 ( it was the last one, at the time of the first server setup ). I have seen that ( it seems ) the new solaris don't honour the LD_LIBRARY_PATH. The first error was a relocation error: relocation error: file /usr/local/dovecot/lib/dovecot/libdovecot-login.so.0: symbol EVP_PKEY_get1_EC_KEY: referenced symbol not found Just to bypass this phase I have linked the openssl-1.0.1e in /usr/local/lib ( libssl and libcrypto ) but then I got a new relocation error: imap: Error: dlopen(/usr/local/dovecot/lib/dovecot/lib20_fts_plugin.so) failed: ld.so.1: imap: fatal: relocation error: file /usr/local/dovecot/lib/dovecot/lib20_fts_plugin.so: symbol http_url_parse: referenced symbol not found Did someone has some idea on how to bypass those troubles ? Thanks in advance Pierluigi

4 5

dsync connection issue
by Subscription 01 Jan '19

01 Jan '19

I'm trying to move from my exising server to a new site. In preparation for this I've set up the new server as per the first attachment. I've added additional (temporary) setting to the new site as per these instructions https://wiki2.dovecot.org/Migration/Dsync but when I try to do a backup with the following command from the old to the new site sudo doveadm -D -o imapc_user=user1@oldserver -o imapc_password=pw-oldserver backup -R -u user1@newserver imapc: I get ----------------------- Error: User initialization failed: imapc: Login to 'oldserver' failed: Disconnected from server ---------------------- I can connect to both sites without any issues openssl s_client -crlf -connect newserver:993 openssl s_client -crlf -connect oldserver:993 Not sure what I'm missing. Have also included the config for the old site Thanks, Leo

4 4