MBOX-Line: From tss at iki.fi  Thu Feb 28 14:06:23 2008
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
Date: Fri Jun  8 12:34:41 2018
Subject: [Imap-protocol] imaptest update
In-Reply-To: <1204181407.11220.53.camel@hurina>
References: <1204181407.11220.53.camel@hurina>
Message-ID: <1204236384.11220.83.camel@hurina>

On Thu, 2008-02-28 at 08:50 +0200, Timo Sirainen wrote:
> A couple of examples to show what's possible:

I added a few more features to make it support pretty much any test I
can think of:

# $n maps to sequences at the beginning of a command:
connections: 2

1 ok store 1,3 +flags \deleted
1 ok expunge
* $1 expunge
* $3 expunge

2 ok uid fetch 2,4 uid
* $1 expunge
* $2 fetch (uid 2)
* $3 expunge
* $4 fetch (uid 4)

The second matches regardless of in what order server sends the
fetch/expunge replies.

# $!directives to specify ordering rules in lists:
ok status $mailbox (messages recent)
* status $mailbox ($!unordered=2 messages 2 recent 2)

The above matches any of:
* status mailbox (messages 2 recent 2)
* status mailbox (recent 2 messages 2)
* status mailbox (recent 2 extension () messages 2 more stuff)

# If the extra isn't wanted:
ok fetch 1 flags
* 1 fetch ($unordered=2 flags ($!unordered $noextra \seen \draft))

These $!directives aren't actually required for the above standard
untagged replies (fetch, fetch flags, status, list) because they're
added by default.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20080229/0b700a31/attachment.sig>
