- dovecot - dovecot.org

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

BUG mailboxaliases, does not take into account namespaces
by Marc Roos 30 Dec '18

30 Dec '18

Does not honour namespaces. Should at least get the namespace location and link to that location and not just created a folder and link to it in the main/top? Namespace.

1 0

BUG mailboxaliases plugin not working with subfolders
by Marc Roos 30 Dec '18

30 Dec '18

The mailboxalias plugin is not working when subfolders are created, rendering its use quite useless. It should work of course something like this. (then I would be able eg. to put my archive mailboxes on different storage, by just creating one symlink on archive (get it??;)) If there is a new mailbox created And in its path there is a folder/path configured in aliases plugin Get the original folder location of that symlink Create a new file with the original name + new subfolder name, in the same location as the parent And then create a symlink to that created file with Thus not this mailbox_alias_old8 = Archive mailbox_alias_new8 = Archived messages -rw------- 1 xxx xxx 0 Dec 30 15:36 .Archive lrwxrwxrwx 1 xxx xxx 8 Dec 30 15:36 .Archived messages -> .Archive -rw------- 1 xxx xxx 0 Dec 30 15:40 .Archived messages.am-test But this: -rw------- 1 xxx xxx 0 Dec 30 15:36 .Archive lrwxrwxrwx 1 xxx xxx 8 Dec 30 15:36 .Archived messages -> .Archive -rw------- 1 xxx xxx 0 Dec 30 15:40 .Archive.am-test lrwxrwxrwx 1 xxx xxx 8 Dec 30 15:36 .Archived messages.am-test -> .Archive.am-test And then if you fix this, you might aswell take this into account. Thus in case I already have a symlink on .Archive -rw------- 1 xxx xxx 0 Dec 30 15:36 .Archive -> /home/mail-archive/userx/.Archive lrwxrwxrwx 1 xxx xxx 8 Dec 30 15:36 .Archived messages -> /home/mail-archive/userx/.Archive lrwxrwxrwx 1 xxx xxx 8 Dec 30 15:36 .Archived messages.am-test -> /home/mail-archive/userx/.Archive.am-test Then your mailboxaliases plugin starts to make sense a bit, now it is not consistent in its naming and is only creating a mess.

1 0

Archive namespace accepting messages to the main folder
by Marc Roos 29 Dec '18

29 Dec '18

I am struggling with an archive namespace. I am not sure if this is can solved. But if you right click in apple mail on a message and choose archive. It wants to move the message to the folder Archive folder (marked in the attached). If I set inbox=yes it is possible to move the mail in this folder, but then I get other problems (two namespaces with inbox=yes). When I leave it inbox=no, I get a complaint of apple mail that the mailbox is not selectable (attachment) namespace { type = private separator = / prefix = Archive/ location = mbox:/home/mail-archive/%u/Archive/:CONTROL=/home/mail-archive/%u/Archiv e/control:INDEX=/home/mail-archive/%u/Archive/index:LAYOUT=maildir++ inbox = no hidden = no list = yes subscriptions = yes } PS. I would like the archive to be located on different storage/mount -----Original Message----- From: Heinlein-Support Team [mailto:support@heinlein-support.de] Sent: 18 December 2018 19:46 To: Marc Roos Subject: Re: Are you still in business this +49 30 40 50 51 is not working [HPLS-Ticket#2018121810002908] Hallo Marc Roos, > I just talked with someone on this emergency number, they told me > someone would call me back. I think I have to wait for this still not? We have 0031203458804, but I'm not able to reach somebody there. Also we have received any more answer by mail. We'd be happy to help. You can reach me this evening at +49.176.23477024. Regards, Peer Heinlein Heinlein Support -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin https://www.heinlein-support.de Tel: 030 / 405051-0 Fax: 030 / 405051-19 Amtsgericht Berlin-Charlottenburg - HRB 93818 B Geschäftsführer: Peer Heinlein - Sitz: Berlin

1 0

Set ACL Error
by Qmail Dev 27 Dec '18

27 Dec '18

Hello, I run Dovecot 2.3.2.1 and I keep separate index / control files: mail_location = maildir:~/Maildir:INDEX=/liveindexes/indexes/%d/%n:CONTROL=/liveindexes/control/%d/%n When I try to set an ACL on a folder, I get this error: Dec 26 17:35:56 imap2 dovecot: imap(user(a)domain.com): Error: file_dotlock_open(/home/vpopmail/domains/domain.com/user/Maildir/.Test/dove… failed: Resource temporarily unavailable Dec 26 17:35:56 imap2 dovecot: Error: imap(user(a)domain.com): Mailbox Test: Failed to set ACL Is it normal for it to try opening the dotlock in the Maildir ? When I list that directory, the lock file did get created -rw------- 1 vpopmail vchkpw 0 Dec 26 17:35 dovecot-acl.lock Any help is appreciated!

2 5

Problem with different certificates
by Andreas Meyer 27 Dec '18

27 Dec '18

Hello! Dovecot manages different domains. Today I renewed the certifiactes from letsencrypt and since that time, dovecot does not recognized the certs for different domains anymore: This is part of my config: ssl = yes ssl_cert = < /etc/letsencrypt/live/bitcorner.de/fullchain.pem ssl_key = < /etc/letsencrypt/live/bitcorner.de/privkey.pem local 37.120.166.21 { # instead of IP you can also use hostname, which will be resolved protocol imap { ssl_cert = < /etc/letsencrypt/live/bitcorner.de/fullchain.pem ssl_key = < /etc/letsencrypt/live/bitcorner.de/privkey.pem } } local 46.38.231.143 { protocol imap { ssl_cert = < /etc/letsencrypt/live/nimmini.de/fullchain.pem ssl_key = < /etc/letsencrypt/live/nimmini.de/privkey.pem } } This worked for years and I don't know what's wrong now. It seems dovecot just takes the default certs into account and ignores the certs defined with "local" completly. Any help appreciated. Kind regards Andreas -- PGP-Fingerprint: F004 8EEE 5E54 F2EA 566E B939 22E5 85DD AA14 AC0A

2 2