similar to: UID inserted in the middle of mailbox errors

Hi All, Our webmail having an issue with the harddrive so I build new webmail on other machine (using Squirrelmail+dovecot+postfix). After copy all data/home folder from the backup, when this user want to access his Sent item, nothing's in it. I've checked the log and found the message as below. mailserver dovecot: IMAP(xxxxx): mbox sync: UID inserted in the middle of mailbox

Hi, We're getting a lot of errors like this: Mar 7 10:02:35 imapserver dovecot: imap(user1): mbox sync: UID inserted in the middle of mailbox /home/user1/mail/mail/INBOX.Trash (8 > 2, seq=2,idx_msgs=6) We have several hundred people using the server, and at least 22 have had this error in the past 24 hours. The numbers at the end change between each user, which I guess you'd

Hi. Just got this error (1.1.rc4), is it something to worry about? Corrupted index cache file /.../Maildir/.Sent/dovecot.index.cache: used_file_size too large This is a shared mailbox with concurrent access. In general, can that usage pattern mess up the index? I am guessing "no", which is why I worry slightly about the warning. Cheers, Anders.

dovecot: POP3(knute): mbox sync: Expunged message reappeared in mailbox /var/mail/knute (UID 585 < 379664, seq=2, idx_msgs=0): 1 Time(s) dovecot: POP3(knute): mbox sync: UID inserted in the middle of mailbox /var/mail/knute (379664 > 585, seq=2, idx_msgs=1): 1 Time(s) I've been getting these lately. Any idea what causes them? Should I worry about it? Thanks, --

I have a problem since a couple of hours: I manage several mboxes on a virtual server using Dovecot (over POP3). Until a few hours ago, it worked well, but since 11:50, the e-mail clients which access Dovecot's mailboxes, receive all e-mails new each time the mailbox is queried. For example: 15:40 fetches 22 new mails 15:41 fetches the same 22 mails again as new 15:42 fetches the same 22

Hi list! I have a problem with transfering mails from mbox to maildir format. On dovecot wiki I found a dsync tool, which looks good, but returns me an error: # dsync -u mail at example.com mirror mbox:~/mail:INBOX=/var/mail/virtuser_808 dsync(root): Fatal: Mail locations must use the same virtual mailbox hierarchy separator (specify separator for the default namespace) I found a solution with

Here's my configuration. dovecot -n # 1.0.7: /usr/local/etc/dovecot.conf protocols: pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock The above setting was just added in an attempt to resolve the issue.

Now that I have a working kvm setup, I thought I'd finally try how Zimbra works. This is mainly some microbenchmarking, so it may not have much to do with actual performance in real life. Setup: - 1GB memory given to kvm (from host's 2GB) - Intel Core 2 6600 (kvm uses only one CPU) - CentOS 5 - 15GB qcow2 image on XFS filesystem - Zimbra 5.0 RC2 RHEL5 x86_64 - Dovecot latest hg,

I've been doing some stress testing in the last few days and fixing all the errors I saw. I'm hoping that I've finally really fixed all the index/mbox problems. So, again I think the only thing left for v1.0 is the documentation. Please test this nightly snapshot before I'll release rc27 tomorrow: http://dovecot.org/nightly/dovecot-latest.tar.gz If you've seen any of the

imaptest host=mail04.local port=143 user=xxx pass=xxx mbox=test.mbox [Fri Jan 11 15:09:14 2019] imaptest[7634]: segfault at 1354ff0 ip 0000000001354ff0 sp 00007ffed5d8f558 error 15 [Fri Jan 11 15:09:22 2019] imaptest[7635]: segfault at 2267ff0 ip 0000000002267ff0 sp 00007ffee5890308 error 15 [Fri Jan 11 15:10:47 2019] imaptest[7648]: segfault at 10e6ff0 ip 00000000010e6ff0 sp 00007ffedbb19f98

I'm getting strange timeouts occasionally on Dovecot 1.0.rc15 on Debian 4.0, and haven't been able to figure out the cause. $ ./src/imaptest user=test%d at imaptest.com host=localhost pass=foo mbox=~/dovecot-crlf - select=0 Logi Logo 100% 100% 2 4 7/ 10 0 0 10/ 10 0 0 10/ 10 0 0 10/ 10 0 0 10/ 10 0 0 10/ 10 0 0 10/ 10 0 0

dovecot-1.1.beta16]# gcc imaptest.c -o imaptest -g -Wall -W -I. -Isrc/lib-mail -Isrc/lib -Isrc/lib-imap -Isrc/lib-storage/index/mbox -DHAVE_CONFIG_H src/lib-storage/index/mbox/mbox-from.o src/lib-imap/libimap.a src/lib-mail/libmail.a src/lib/liblib.a imaptest.c: In client_append function: imaptest.c:1492: error: too many arguments for i_stream_create_limit function

I thought I'd try benchmarking with dbmail (v2.2.4) to see how much slower a SQL backend could actually be. Skip to bottom for the conclusions. Originally I ran the tests with the databases being in XFS filesystem. MySQL's performance was horrible. It went 3-7x faster with ext3. MySQL 5.0.30 backend (innodb): ./imaptest clients=1 - append=100 seed=1 secs=30 msgs=1000000 logout=0

I upgraded one server to 1.0rc19 (from rc15) over the weekend, and have since received several reports of dovecot erroneously retrieving older messages as new mail. I've seen this myself intermittently on KMail, and users have reported it on Thunderbird, Squirrelmail, and Outlook. I see some things in the archives that suggest that this was a problem in older 1.0 release candidates, but

I have been testing with imaptest and getting 'stalls', I tried even building from source and static. Even running it on the same host. Anyone knows what I could doing wrong? [@~]# ./imaptest - append=100,0 logout=0 host=192.168.10.44 port=143 user=test2 pass=xxxxxxxx seed=100 secs=240 clients=1 mbox=64kb.mbox box=INBOX/test Logi Sele Appe 100% 100% 100% 1 1 5 1/ 1 0

Hi, I'm an Apache James committer and we are curious to use imaptest in order to validate our IMAP protocol implementation. I'm using the nightlybuild : imaptest-20170506 I follow the examples given in the /T/ /est IMAP server compliancy/ examples https://imapwiki.org/ImapTest/Examples. And I wanted to analyse the errors reported, here are some: Error: user1 at james.org[11]: seq too

Please, unsubscribe me. I really don't want to read this. 12.01.2019 22:47, Stephan Bosch ?????: > > Op 11/01/2019 om 15:13 schreef Marc Roos: >> imaptest host=mail04.local port=143 user=xxx pass=xxx mbox=test.mbox >> >> [Fri Jan 11 15:09:14 2019] imaptest[7634]: segfault at 1354ff0 ip >> 0000000001354ff0 sp 00007ffed5d8f558 error 15 >> [Fri Jan 11 15:09:22

Dear Folks, Using head of imaptest with dovecot 2.1, I am attempting to put a heavy load on the server, with insufficient success. I made 15000 user accounts, put them in to a file, one per line. Then I ran imaptest with ./imaptest userfile=../../imap-test-userlist-15001.txt clients=15001 pass=SECRETPASSWORD But CPU load is only reaching 20. I put an mbox containing 67 messages into

Yes dovecot is showing the inserted messages until the stall. Looks like it is an issue with imap test because I am able to empty the mailbox again via thunderbird. I am comparing write tests to different backends. -----Original Message----- From: Daniel Miller [mailto:dmiller at amfes.com] Sent: dinsdag 17 september 2019 22:06 To: Marc Roos; dovecot Subject: Re: Imaptest stall On 9/17/2019

Hey guys, Has anybody ever used imaptest to benchmark *ONLY* reads? I'm trying to run a battery of tests in my new cluster and apparently no combination of parameters works, because fetch instruction doesn't run. Below is the command I'm using and its partial output imaptest/src/imaptest host=$SERVER_IP port=143 user=teste%d at example%d.com pass=$TEST_PASS users=10 domains=10