MBOX-Line: From lyndon at orthanc.ca  Mon Jun  6 10:47:33 2011
To: imap-protocol@u.washington.edu
From: Lyndon Nerenberg <lyndon@orthanc.ca>
Date: Fri Jun  8 12:34:46 2018
Subject: [Imap-protocol] Where to start?
In-Reply-To: <4DED0EDA.3030303@BusCom.net>
References: <4DEBB242.2090200@BusCom.net>
	<201106051924.p55JOwpG003543@mxout12.cac.washington.edu>
	<4DEBDFF5.9000301@BusCom.net>
	<4DEC1C93.24755.853F5AE5@David.Harris.pmail.gen.nz>
	<4DEC5CC4.5010507@BusCom.net>
	<201106060837.2YFKV00@c.mx.BCN-servers.us>
	<4DED0EDA.3030303@BusCom.net>
Message-ID: <alpine.OSX.2.00.1106061035540.68614@haldir.orthanc.ca>

> Testing with telnet is going to verify that my server works the way I think 
> it should. It doesn't validate my understanding of RFC-3501.

It could.  During the days of the IMAP interop meetings, telnet was my 
tool of destruction for many (many!) server implementations.  Look through 
the 3501 grammar for every instance of <number> and <nz-number>. Next, 
telnet to any IMAP server and hand craft a series of commands that 
exercise the edge cases of those two tokens.

For starters, send a command containing a <[nz-]number> token with the 
high bit set.  The results can be spectacular :-(

--lyndon

