Displaying 20 results from an estimated 1000 matches similar to: "errors while testing with imaptest"
2006 Apr 28
1
imaptest, with options!
I hacked some command line options into imaptest.
I dont think I broke it..
Place into dovecot-source root as usual and compile with:
gcc imaptest.c -o imaptest -Wall -W -I. -Isrc/lib -DHAVE_CONFIG_H
src/lib/liblib.a
As per Timo's instructions.
# imaptest -h imaptest [USER at IP:PORTNO] [pass=PASSWORD] [mbox=MBOX]
[clients=CC] [msgs=NMSG] [use_authenticate] [PORTNO]
USER = template for
2005 May 13
1
dovecot 1.0-test69 io hangs
I've been testing test69 with pop3 (under Linux and with mbox).
I began testing with a large inbox (11000 mails) and it seems the
communication between dovecot and the mailclient (evolution) stalls after
1000-2000 messages transferred.
I've looked in to the (non-trivial) io functionality of dovecot.
What I see is that io_loop_handler_run() in ioloop-poll.c does not
signal any more data
2005 May 20
1
pop3/commands.c query
Is this correct ?
cmd_rset()
if (mail_update_flags(mail, MAIL_SEEN,
MODIFY_REMOVE) < 0)
break;
Args seems to be switched.
/Jens
-----------------------------------------------------------------------
'This mail automatically becomes portable when carried.'
-----------------------------------------------------------------------
Jens L??s
2003 May 26
1
logging in POP3
I have begun testing dovecot as (primarly) a POP replacement.
So far the only lacking bit is the logging.
It would be great if pop3 could log a line at client exit with the
following info: (wishlist follows :)
o nr deleted mails + total bytes deletes
o nr mails left in spool + bytes left
o time spent
o indication if TLS was used or not
If you would lika generic logging API I have one you can
2005 Aug 24
0
thunderbird pop3 delete bug workaround
Following is patch that allows tbird to download and redelete the last
deleted message.
Not particularily nice but for "normal" usage the bug/workaround is not
triggered.
Tested with huge inbox.
--- src/pop3/client.h.orig 2005-08-23 15:00:48.000000000 +0200
+++ src/pop3/client.h 2005-08-23 15:02:18.000000000 +0200
@@ -35,6 +35,9 @@
unsigned int top_count;
unsigned int
2006 May 05
0
support for no modules, patch
--- src/lib/module-dir.c~ 2006-02-26 13:14:12.000000000 +0100
+++ src/lib/module-dir.c 2006-05-05 11:09:11.000000000 +0200
@@ -255,8 +255,8 @@
}
#else
-
struct module *module_dir_load(const char *dir __attr_unused__,
+ const char *module_names __attr_unused__,
bool require_init_funcs __attr_unused__)
{
2012 Nov 26
1
Heal not working
Hi,
I have a volume created of 12 bricks and with 3x replication (no stripe). We had to take one server (2 bricks per server, but configured such that first brick from every server, then second brick from every server so there should not be 1 server multiple times in any replica groups) for maintenance. The server was down for 40 minutes and after it came up I saw that gluster volume heal home0
2011 Mar 25
1
imaptest assertion failure
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:
2019 Jan 12
1
degfault imaptest
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
2014 Apr 23
0
ImapTest utility not compiling
* 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:
2007 Mar 11
1
imaptest updates
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
2014 Jun 26
1
Imaptest script testing
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
2017 May 24
0
[imaptest] Explaining errors
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
2019 Jan 12
0
degfault imaptest
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]
2019 Jan 11
3
degfault imaptest
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
2009 May 29
1
imaptest build problems
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:
2018 Jul 06
0
Benchmarks with imaptest
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
2020 Aug 30
0
Imaptest stalls when removing msgs argument
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
2008 Feb 28
1
imaptest update
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
2012 Mar 16
2
imaptest: performance testing
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