Re: panic when using dovecot master account

2018-11-08 Thread André Rodier
On 2018-11-09 05:25, Aki Tuomi wrote: This seems to have nothing to do with master account or not. Does this happen if you try to open the virtual mailbox again? Aki On 09 November 2018 at 00:13 André Rodier wrote: Hello, I am running dovecot 2.2.34 (874deae), on Debian stable, from

Re: panic when using dovecot master account

2018-11-08 Thread Aki Tuomi
This seems to have nothing to do with master account or not. Does this happen if you try to open the virtual mailbox again? Aki > On 09 November 2018 at 00:13 André Rodier wrote: > > > Hello, > > I am running dovecot 2.2.34 (874deae), on Debian stable, from backports. > > I just tried the

panic when using dovecot master account

2018-11-08 Thread André Rodier
Hello, I am running dovecot 2.2.34 (874deae), on Debian stable, from backports. I just tried the master account, and although everything worked in the email client, I had logs in the error logs: imap(mirina): Panic: file mail-index-sync.c: line 413 (mail_index_sync_begin_to2): assertion

Re: doveconf: Fatal: open(/etc/dovecot/dovecot/dovecot.conf) failed: No such file or directory

2018-11-08 Thread Mart Pirita
Hi, You are right, recompiled with correct path. Hajo Locke wrote: > Hello, > > > > Am 07.11.2018 um 14:04 schrieb Mart Pirita: >> Hi, >> >> >> >> Build options - --sysconfdir=/etc/dovecot > you should use --sysconfdir=/etc > sysconfig is path to sysconfig, not dovecotconfig. >> doveconf -Pn

Re: after reboot listen(*, 995) failed: Address already in use/listen(*, 993) failed: Address already in use

2018-11-08 Thread Håkon Alstadheim
Den 08.11.2018 17:52, skrev Robert Kudyba: This is still happening after a reboot, Fedora 28. Restarting dovecot fixes the problem. Does anyone know if it could be related to this bug report? *https://bugzilla.redhat.com/show_bug.cgi?id=103401#c130 * and suggested work around to add ports to

after reboot listen(*, 995) failed: Address already in use/listen(*, 993) failed: Address already in use

2018-11-08 Thread Robert Kudyba
This is still happening after a reboot, Fedora 28. Restarting dovecot fixes the problem. Does anyone know if it could be related to this bug report? *https://bugzilla.redhat.com/show_bug.cgi?id=103401#c130 * and suggested work around to add

Strange log message with dovecot-2.3.3

2018-11-08 Thread Christian Pélissier
Hi, # dovecot --version 2.3.3 (dcead646b) # doveinfo Nombre d'utilisateurs : 1151 Sockets IMAP : 4356 Process dovecot/imap : 4357 Process dovecot/imap-login : 1339 Process dovecot/pop3 : 0 Process dovecot/pop3-login : 0 Process dovecot/auth