Re: Migration

> On 29 Dec 2018, at 23.49, Hans Brage wrote: > > Hi! > > I'm currently running an small imap-server on Dovecot 2.2.4 but will retire > that server. I've set up an new server with Dovecot 2.3.4 and will migrate > the mailboxes (maildir-format) from the old to the new server. I'm planning >

Re: Several problems on Solaris10

On 29/12/2018 13:49, Pierluigi Frullani wrote: 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

Re: BUG: cannot move messages to root mailfolder in namespace "There can be only one namespace with inbox=yes"

> On 30 December 2018 at 17:09 Marc Roos wrote: > > > > I can only move messages to a root namespace folder when specifying > inbox=yes. That is strange because it is not even the inbox. I don't > even get why it is not by default possible, maybe bug there? > This makes no sense.

BUG mailboxaliases, does not take into account namespaces

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.

BUG mailboxaliases plugin not working with subfolders

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

BUG: cannot move messages to root mailfolder in namespace "There can be only one namespace with inbox=yes"

I can only move messages to a root namespace folder when specifying inbox=yes. That is strange because it is not even the inbox. I don't even get why it is not by default possible, maybe bug there? You have made the mistake of overloading the use of a parameter inbox=yes (or not creating a

Re: Issue with LMTP proxying and port number

Hello Sami, yes, see below. We run Dovecot at a different versions, mainly 2.2.10 (CentOS), 2.2.22 (Ubuntu) and now 2.2.36 (CentOS).  The issue is weird, because it only happened after the update from 2.2.10->36.  Just to understand it would be great. I'm actually checking out the configs now

Re: Solr

On 12/29/2018 4:46 PM, Joan Moreau wrote: Hi Daniel, I am on Archlinux. Anyway, I adapted the scripts. 2 questions: 1 - It looks like we are not on the same version . I am on 7.5.0. Which version are you running ? Solr 7.5.0. 2 - Your conf shows that you let managed-schema but deleted

Re: Solr

On 12/29/2018 4:49 PM, Joan Moreau wrote: Also : - Java is 10.0.2 Same as me. - If i delete schema.xml but create only managed-schema, the solr refuses to start with a java error "schema.xml missing" Ok...so we need to do some more digging. How did you install Solr? (I downloaded a

Re: Issue with LMTP proxying and port number

> On 31 Dec 2018, at 0.43, Laz C. Peterson wrote: > > Hello there, > > Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but after > updating to version 2.2.36, our director servers are not able to proxy LMTP. > > We are sending mail from exim to the local Dovecot LMTP socket,

Re: Migration

Thanks! That was a really useful answer. // Hans Den 2018-12-30 kl. 10:53, skrev Sami Ketola: On 29 Dec 2018, at 23.49, Hans Brage wrote: Hi! I'm currently running an small imap-server on Dovecot 2.2.4 but will retire that server. I've set up an new server with Dovecot 2.3.4 and will

Issue with LMTP proxying and port number

Hello there, Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but after updating to version 2.2.36, our director servers are not able to proxy LMTP. We are sending mail from exim to the local Dovecot LMTP socket, which then used to send it to our internal mail servers on port 24.