similar to: Random issue on mailbox "assertion failed"

Exactly - I removed then with find . -name "dovecot.index*" -type f -delete There is no need to restart dovecot. IMAP client will be forced to resync all the emails from the server. > Le 28 nov. 2018 ? 23:20, JCA <1.41421 at gmail.com <mailto:1.41421 at gmail.com>> a ?crit : > > Thanks. Assuming that the IMAP mail directory for the account affected is under

Thanks. Unfortunately, that made no difference. On Fri, Nov 30, 2018 at 1:20 PM Thomas Durand <tom at rezoo.org> wrote: > Exactly - I removed then with > *find* . -name "dovecot.index*" -type f -delete > > There is no need to restart dovecot. IMAP client will be forced to resync > all the emails from the server. > > > Le 28 nov. 2018 ? 23:20, JCA

Hi, I have update today dovecot and dovecot pigeonhole to the latest version available on my centos 7. It?s a small email servers with postfix/amavisd/clamav/spamasssin. I had dovecot for IMAP/POP3 with spam plugins to store spam message automatically into the spam folder. After the upgrade, I was noticed by some of my users that they have in their message the same message appearing 2,3 even 10

Thanks. Assuming that the IMAP mail directory for the account affected is under /home/xyz/mail, are you talking about the contents of the index directory, excluding the log file therein? On Wed, Nov 28, 2018 at 2:29 PM Thomas Durand <tom at rezoo.org> wrote: > Hi, > > I had the similar messages after an upgrade then downgrade. I was able to > fix by removing all indexes files.

This happening when my Thunderbird client is trying to establish a connection with a Dovecot server. Some background first: 1) I am running Thunderbird 6.20.1 from a Linux client. 2) Other clients (e.g. Maildroid in my Android phone) do not have any issues. 3) The Dovecot software is version 2.2.9, running in a Linux server. 4) This may be the root of the problem: at some point, the

Hello, we have a problem with pxelinux and a specific hardware. In short: PXE starts, get and start the pxelinux.0 but can't get the configuration file. This problem belongs only to one new client. Other clients work in this environment with out any problem. The client is a HP xw4300 with the networkcard: ------------ vendor = "Broadcom Corporation" name = "NetXtreme BCM5752

Hiya! Samba 2.0.7 on HP-UX 11.0. When a user tries to map a drive, the smb.log shows the following: NOTE: the stanza ending in PANIC repeats 3 times, snipped here for brevity ===================================== [2002/02/28 11:12:43, 1] smbd/server.c:(641) smbd version 2.0.7 started. Copyright Andrew Tridgell 1992-1998 [2002/02/28 11:12:43, 1] smbd/files.c:(215) file_init: Information

Several people already reported this at linux-kernel and elsewhere with no answers, I thought perhaps this would be a more adequate forum... [1.] One line summary of the problem: After I/O, journal is aborted and filesystems made read-only. [2.] Full description of the problem/report: One can't anymore write to the affected file systems. Upon investigation, ext3fs journal was aborted

Target: FreeBSD 6.2-STABLE on i386 autoconf says: configure:2122: checking build system type configure:2140: result: i386-unknown-freebsd6.2 [...] configure:2721: gcc -v >&5 Using built-in specs. Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 3.4.6 [FreeBSD] 20060305 [...] objdir != srcdir, for both llvm and gcc. Release build. llvm-gcc 4.2 from source.

Hi, I had the similar messages after an upgrade then downgrade. I was able to fix by removing all indexes files. Thomas > Le 28 nov. 2018 ? 22:02, JCA <1.41421 at gmail.com> a ?crit : > > This happening when my Thunderbird client is trying to establish a connection with a Dovecot server. Some background first: > > 1) I am running Thunderbird 6.20.1 from a Linux

Hello, I have to migrate my dovecot box to a new one. I would like to know if it?s possible to do this migration with the replication process. My plan is to activate replication between 2.2.10 server and the 2.3.4 new server. Then I will update the DNS to redirect the name to new box. Users will then connect either on the new or the old box depending on the dns upgrade. Does anyone have already