similar to: FETCH for mailbox mailboxname UID #1 got too little data: #2 vs #3

Hi all, I can send myself a test message that causes Dovecot to crash when I open it in Alpine, with the following error: Jan 12 14:52:52 one-mail dovecot: imap(chris): Error: FETCH [1] for mailbox badbox UID 1 got too little data: 2 vs 4 Jan 12 14:52:52 one-mail dovecot: imap(chris): Error: Corrupted index cache file /home/chris/mail/.imap/badbox/dovecot.index.cache: Broken MIME parts

Hi there I keep getting the following errors scrolling in my dovecot logs. I am wondering how I can nail down what is creating that problem. dovecot: 2011-11-04 16:58:01 Error: IMAP(<usr>): FETCH for mailbox Trash UID 42022 got too little data: 90900 vs 1529791 also I have a trash folder with over 100k messages in mbox format. I am wondering if migrating to Maildir format would make

Hi all, Any thoughts about this error? Should I file a bug report somewhere? Cheers, Chris. On Wed, 12 Jan 2011, Chris Wilson wrote: > Hi all, > > I can send myself a test message that causes Dovecot to crash when I open > it in Alpine, with the following error: > > Jan 12 14:52:52 one-mail dovecot: imap(chris): Error: FETCH [1] for > mailbox badbox UID 1 got too

Whenever I try to access an e-mail in the middle (rather than at the end) of the mailbox, my mail-client (KMail) gets an error a message like this is logged in the maillog: IMAP(mi): FETCH for mailbox INBOX UID 39641 got too little data: 4823 vs 4825 IMAP(mi): Disconnected: Disconnected The actual numbers vary, but it is always X vs X+2 The problem started when I upgraded to 1.0.8.

Hi Timo, I am receiving the above error in dovecot's logs, here's how it looks like: dovecot: Aug 05 19:52:19 Info: imap-login: Login: user=<XXXXXXXXXXXX>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Aug 05 19:53:36 Error: IMAP(XXXXXXXXXXXX): FETCH for mailbox Bulk Mails UID 32 got too little data: 9199 vs 39532 dovecot: Aug 05 19:53:36 Info: IMAP(XXXXXXXXXXXX):

This happened a while back, I was running 1.1rc3 up until today so I have no idea if it would have an effect. Sorry if its something that has been fixed. The error below was repeated many many times, I deleted the index so the user would stop getting disconnected (although I didn't hear any complaints). I have not seen this happen repeatedly in this manner to any other user yet. Apr 15

Sorry, this time I've no core file, (I forgot to set ulimit -c unlimited before starting dovecot) Regards, Diego. --- dovecot: Dec 09 08:26:52 Panic: IMAP(user): file mbox-sync-rewrite.c: line 590 (mbox_sync_rewrite): assertion failed: (mails[idx].from_offset == start_offset) dovecot: Dec 09 08:26:52 Error: IMAP(user): Raw backtrace: /usr/libexec/dovecot/imap [0x80f739e] ->

Using 1.1.1. Got this error message in a tight loop, using both Tbird and Mulberry 3 as client: FETCH for mailbox INBOX UID 32994 got too little data: 1616 vs 1649 I get this repeatedly alternating with a login line. What does this mean? I stopped the server, zipped ~/mail/.imap/INBOX to hide it and let dovecot recreate it, and things seem to be working again. Is there a less destructive way

Hi, We are still getting, on a daily basis, users who cannot move messages to Trash or expunge Trash due to these errors: Mar 28 10:43:57 tm2 dovecot: [ID 107833 mail.error] IMAP(kss021): mbox sync: UID inserted in the middle of mailbox /home/kss021/Mail/Trash (3137 > 536, seq=2, idx_msgs=76) Our users have no other access to their mailbox other than Dovecot, and we are using mbox

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

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,

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

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

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

While trying to use imaptest (-20100922, from http://dovecot.org/nightly/imaptest/imaptest-latest.tar.gz) with the included tests directory, it assert-crashes after a suspicious connect() failure: $ ./imaptest user=foo pass=bar host=localhost test=tests Error: connect() failed: No route to host Panic: file test-exec.c: line 903 (test_send_lstate_commands): assertion failed:

http://www.imapwiki.org/ImapTest/ <http://www.imapwiki.org/ImapTest/> I am doing imap testing using imaptest scripts. But, i am unable to append message. APPEND INBOX "15-Jun-2015 05:30:05 -0700" "From:abc at gmail.com" "Subject: test. HI this is msg". This command i am using in my testing script. Command executed properly. But, it is not appending mail

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

Hello, I download and install it manual, this working now? waiting for next update to found out, yum is working correct again ;-) Thanks for answers, Am Sonntag, 31. M?rz 2019, 13:59:17 CEST schrieb Kostya Vasilyev via dovecot: > On Sun, Mar 31, 2019, at 2:30 PM, G?nther J. Niederwimmer via dovecot wrote: > > Hello, > > > > Am Samstag, 30. M?rz 2019, 21:36:12 CEST schrieb

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