similar to: imaptest build problems

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:

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

* Found my error. I moved the dovecot source code after compiling it. Didn?t realize there were embedded/absolute URLS within the dovecot source tree. All I needed to do was make clean && make dovecot, then imaptest compiled no problem. [Brad Hein] From: <Hein>, Local Administrator <Brad_Hein at cable.comcast.com<mailto:Brad_Hein at cable.comcast.com>> Date:

I spent the last 5 hours or so updating my imaptest tool. It's beginning to become almost like a real IMAP client. http://dovecot.org/tools/imaptest10.c contains a version that compiles against Dovecot v1.0 (instead of against CVS HEAD). imaptest is this tool that I've been using for a few years to do stress testing. It can create a lot of dummy IMAP client connections which execute some

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

On 23 May 2017, at 12.10, aduprat <aduprat at linagora.com> wrote: > > 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

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 2019] imaptest[7635]: segfault at 2267ff0 ip > 0000000002267ff0 sp 00007ffee5890308 error 15 > [Fri Jan 11 15:10:47 2019]

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

On 4 Jul 2018, at 20.10, Jo?o Paulo Sacchetto Ribeiro Bastos <joaopaulosr95 at gmail.com> wrote: > > 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

I have had this imaptest[1] stall. I compared this command with what you have on the website and I was a bit surprised that what is on the website is working. What I have noticed is that if you remove this msgs argument, the imaptest stalls. I am not sure if this is according to design, but one might expect that specifying a secs, makes specifying msgs redundant? [1] imaptest - append=100,0

I've finally added support for "normal" command/reply tests for my imaptest program (http://imapwiki.org/ImapTest). My plan is that imaptest will include some generic IMAP compliancy tests and Dovecot will include some more strict Dovecot-specific checks. "make dist" will run all these tests before building a tarball, so in future I shouldn't be able to release

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

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

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

If you're just speed testing for writing probably sdbox or maildir would be the fastest. Daniel On 9/17/2019 1:09 PM, Marc Roos via dovecot wrote: > > 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. > >

Hello. My system is: Debian Lenny 2.6.26-2-amd64 I try to build Imaptest and follow http://www.imapwiki.org/ImapTest/Installation But get this: ./configure --with-dovecot=../dovecot-2.0.beta4 && make checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking

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

Hallo, today I tried to compile imaptest under solaris 10 with studio 11 compiler and got the following error: gmake[2]: Entering directory `/net/fileserv/export/sunsrc/src/imaptest-20111119/src' source='client.c' object='client.o' libtool=no \ DEPDIR=.deps depmode=none /bin/bash ../depcomp \ cc -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/local/include/dovecot

http://dovecot.org/tools/imaptest.c now keeps track of messages' metadata and complains if they change. It relies on Message-ID: header being unique in the source mailbox, otherwise it'll give bogus errors. I might fix that some day. I changed the code from using simple line-based parsing to Dovecot's imap-parser code. Unfortunately it looks like it's pretty slow. At least I'm