doveadm index crash/assert

2018-12-31 Thread Larry Rosenman
I got the following crash whilst looking at my logs and seeing some indexer-worker crashes. doveadm(ler): Panic: file http-client-request.c: line 1108 (http_client_request_send_more): assertion failed: (req->payload_input != NULL) Abort trap (core dumped) bt full at:

Re: Several problems on Solaris10

2018-12-31 Thread Joseph Tam
On Mon, 31 Dec 2018, Pierluigi Frullani wrote: 5. When linking use -R to point to the installed location of the libraries. That's fine with me, ( and eventually I will try to modify all the makefiles, but I hoped it would have already been done by configure ( wich obviously has not :) One

Issue with LMTP proxying and port number

2018-12-31 Thread Steven Craig
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.

Re: Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1 (fwd)

2018-12-31 Thread Aki Tuomi
We are working on fixing this. Aki > On 31 December 2018 at 23:45 Chris BL wrote: > > > Hi Aki, > > Bingo! Putting that line in dovecot.conf rather than my custom file, and > then using my old custom file, unchanged, from Alpine works perfectly. > > My only remaining question, then, would

Re: Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1 (fwd)

2018-12-31 Thread Chris BL
Hi Aki, Bingo! Putting that line in dovecot.conf rather than my custom file, and then using my old custom file, unchanged, from Alpine works perfectly. My only remaining question, then, would be ... what was this (change) about / or is there any documentation that I should/could have read to

Re: Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1 (fwd)

2018-12-31 Thread Aki Tuomi
If your client directly executes imap binary, it is not mandatory for dovecot to be running, but you need to put the service section into /etc/dovecot/dovecot.conf and restart the dovecot service. Putting it to your local config file does not affect the global service. Aki > On 31 December

Re: Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1 (fwd)

2018-12-31 Thread Chris BL
Hi Aki, I am not 100% sure. I do not really know what my OS does. "ps -A" says dovecot is running, but if I say "sudo service dovecot stop", my email client works fine still (that is, assuming the old version of dovecot is installed). ie the on-demand instances of dovecot-imapd that Alpine

Re: Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1 (fwd)

2018-12-31 Thread Aki Tuomi
Am I assuming correctly that you are not, in fact, running anything but imap process from Dovecot? Aki > On 31 December 2018 at 18:35 Chris BL wrote: > > > > Hi Aki, > > Oops; I did not think carefully enough about your instructions. Here is the > output from > > $ dovecot -n -c

Re: Several problems on Solaris10

2018-12-31 Thread Pierluigi Frullani
Answer inline. On Sun, Dec 30, 2018 at 12:59 PM James wrote: > On 29/12/2018 13:49, Pierluigi Frullani wrote: > > > My version is 2.2.13 ( it was the last one, at the time of the first > > server setup ). > > 2.2.13 is from around May 2014. It worked but I can't see why you > wouldn't switch

Re: Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1

2018-12-31 Thread Chris Barrington-Leigh
Hi Aki, (This message might not make it to the list; I have to switch back to the other dovecot to be able to send from that address) Oops; I did not think carefully enough about your instructions. Here is the output from $ dovecot -n -c /home/meuser/dotfiles/auto-stanford-dovecot.conf #

Re: Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1 (fwd)

2018-12-31 Thread Chris BL
Hi Aki, Oops; I did not think carefully enough about your instructions. Here is the output from $ dovecot -n -c /home/meuser/dotfiles/auto-stanford-dovecot.conf # 2.3.2.1 (0719df592): /home/meuser/dotfiles/auto-stanford-dovecot.conf # Pigeonhole version 0.5.2 () # OS: Linux 4.18.0-13-generic

Re: Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1

2018-12-31 Thread Aki Tuomi
Did you remove the service section before taking doveconf -n? 'cos I can't see it here.. Also, did you restart dovecot after config change? Aki > On 31 December 2018 at 16:54 Chris BL wrote: > > > Hi Aki, > > Yes, the same connect error: imap(meuser,)Error: >

Re: Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1

2018-12-31 Thread Chris BL
Hi Aki, Yes, the same connect error: imap(meuser,)Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied The mail location in "doveconf -n" (belo) does not reflect my preferences. In Alpine, if I acknowledge the error I get, which tells me to add novalidate-cert in

Re: Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1

2018-12-31 Thread Aki Tuomi
You are still getting the connect error? Can you share your doveconf -n? Aki > On 31 December 2018 at 16:42 cpblpublic+dove...@gmail.com wrote: > > > Hi Aki, > > Thanks. I put that in the .conf file I mentioned, and it made no > difference. > > Chris > > > Hi! > > > > In your case it's

Re: Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1

2018-12-31 Thread cpblpublic+dovecot
Hi Aki, Thanks. I put that in the .conf file I mentioned, and it made no difference. Chris > Hi! > > In your case it's probably easiest to change > > service stats { > unix_listener stats-writer { > mode = 0666 > } > } > > Aki > > > On 31 December 2018 at 16:05

Re: Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1

2018-12-31 Thread Aki Tuomi
Hi! In your case it's probably easiest to change service stats { unix_listener stats-writer { mode = 0666 } } Aki > On 31 December 2018 at 16:05 cpblpublic+dove...@gmail.com wrote: > > > > I use a localhost dovecot imap server in order to access maildir folders from > Alpine (see

Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1

2018-12-31 Thread cpblpublic+dovecot
I use a localhost dovecot imap server in order to access maildir folders from Alpine (see 2009 instructions for my set up here https://cpbl.wordpress.com/2009/11/07/alpine-offlineimap-and-gmail-under-ubuntu/ ) My configuration has worked nicely since 2009, but failed after a recent upgrade

Moving Alternate Storage to another disk.

2018-12-31 Thread bOnK
Hello, Dovecot 2.3.4_3 on FreeBSD 11.2. I am using mdbox Alternate Storage since about two years without any problems. However, the disk containing this storage is almost full and I have to move this data to another disk, probably zpool. Would it be okay to do the following? 1) Shut down

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

2018-12-31 Thread Aki Tuomi
> On 31 December 2018 at 15:47 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? > >> >

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

2018-12-31 Thread Marc Roos
> >> >> 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. inbox=yes namespace means the namespace which

Re: Migration

2018-12-31 Thread Sami Ketola
> On 31 Dec 2018, at 12.22, Ignacio García wrote: > > A totally different approach (that is imap-server agnostic), providing that > you're setting up those new accounts with temporary passwords (which you > know), before users change their passwords to their liking: you could also > use

Re: Migration

2018-12-31 Thread Ignacio García
A totally different approach (that is imap-server agnostic), providing that you're setting up those new accounts with temporary passwords (which you know), before users change their passwords to their liking: you could also use imapsync ( https://github.com/imapsync/imapsync) . We here use it