similar to: Imaptest script testing

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

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

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'm trying to use this to test an IMAP server I'm developing (I picked the nightly up from the link on the wiki page at http://www.imapwiki.org/ImapTest/Installation). With one client using the mailbox dovecot-crlf (http://www.dovecot.org/tmp/dovecot-crlf) I get messages like: Error: test at npsl.co.uk[67]: 1035253882.5041.34.camel at hurina: Header From changed 'Timo Sirainen

On this page http://imapwiki.org/ImapTest/Running It gives command line parameters to define. One of them is "password=pass" but this resulted in an "Unknown arg" response for me on a fresh install. I then looked at some examples and they give the argument as "pass=pass" which works for me. Was the argument name changed recently or something?

Hi, I've been trying some benchmarks to compare 1.0 vs 1.1 -this is the easiest way to explain the move to my boss-, so I've compiled dovecot 1.1 and imaptest-20080627 in my secondary machine running RHEL4, with homes in NFS, indeces in local files and control files also in NFS. Then I've created 100 new users imaptest001-imaptest100, and set the password paquitoelchocolatero to

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

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

Hey, We recently announced Gluon (https://github.com/ProtonMail/gluon/) our IMAP server library we are using in Proton Bridge(https://github.com/ProtonMail/proton-bridge). We would love to have it have it listed in the IMAP Server Compliancy Status wiki page (https://imapwiki.org/ImapTest/ServerStatus). What do we need to do or whom do we need to contact to make this happen? Additionally, We

On 23. Feb 2023, at 16.13, Leander Beernaert <leander.beernaert at proton.ch> wrote: > > Hey, > > We recently announced Gluon (https://github.com/ProtonMail/gluon/) our IMAP server library we are using in Proton Bridge(https://github.com/ProtonMail/proton-bridge). We would love to have it have it listed in the IMAP Server Compliancy Status wiki page

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

Hey Timo, Thanks for the quick turnaround, once we have the test results I'll contact you again. Should I also include instructions on how to run the a self contained server with a dummy backend so you can independently verify our results? Leander Beernaert Proton AG ------- Original Message ------- On Thursday, February 23rd, 2023 at 8:59 PM, Timo Sirainen <timo at sirainen.com>

* 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:

Something I can't quite place finger on here. Altogether too much Mafia, in the bulk email business generally, and I know Switzerland borders on Italy ... This sounds, (albeit vaguely,) altogether too much like the thieves I seem to have fallen amongst lately. Two stolen trucks, three stolen laptops, another one wrecked, three or four stolen cell phones, passwords GPG keys, city hall hookers

I am not sure this is the correct list, please forgive if it is not, and point me in the right direction. I downloaded the latest http://www.imapwiki.org/ImapTest/Installation from http://dovecot.org/nightly/imaptest/imaptest-latest.tar.gz cd imaptest-20090401 $./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... configure:

Hello, been lurking a while, about to move over to Dovecot soon. I have a nice test machine up and running. My previous email server when talking IMAP to Apple Mail, will eventually go "deaf" and new messages will not make it to the Inbox of Apple Mail Client. A restart of the desktop application is required. I am told that the reason for this is that my current email server

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

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:

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