Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Thu, 10 Apr 2008 10:02:36 -0400,    group: microsoft.public.exchange.development        back       


Exhange 2007 IMAP4 Search and Charset   
It looks like they may have re-written the IMAP4 agent in 2007 because I am 
finding a lot of things that work differently.

For example the Search command no longer supports the Charset parameter.  Is 
this a known feature removal or is there a setting somewhere that enables 
this?

i.e.

102 SEARCH CHARSET US-ASCII SUBJECT Test
102 BAD Command Argument Error. 11

Remove the charset and it works...

102 SEARCH SUBJECT Read
* SEARCH 6 28 44 67 74
102 OK SEARCH completed.


I am testing with US-ASCII because the RFC says...

...US-ASCII MUST be supported; other [CHARSET]s MAY be supported....
date: Thu, 10 Apr 2008 10:02:36 -0400   author:   Bob Bins

Re: Exhange 2007 IMAP4 Search and Charset   
Found another bug/inconsistency.

You can create mailboxes in Outlook with a space on the end.  i.e.

"Test Folder "

Then try to select this mailbox using the IMAP4 protocol it will break the 
connection.

100 Select "Test Folder "

Thanks.


"Bob Bins"  wrote in message 
news:%23HR5ANxmIHA.536@TK2MSFTNGP06.phx.gbl...
> It looks like they may have re-written the IMAP4 agent in 2007 because I 
> am finding a lot of things that work differently.
>
> For example the Search command no longer supports the Charset parameter. 
> Is this a known feature removal or is there a setting somewhere that 
> enables this?
>
> i.e.
>
> 102 SEARCH CHARSET US-ASCII SUBJECT Test
> 102 BAD Command Argument Error. 11
>
> Remove the charset and it works...
>
> 102 SEARCH SUBJECT Read
> * SEARCH 6 28 44 67 74
> 102 OK SEARCH completed.
>
>
> I am testing with US-ASCII because the RFC says...
>
> ...US-ASCII MUST be supported; other [CHARSET]s MAY be supported....
>
>
date: Thu, 22 May 2008 11:50:39 -0400   author:   Bob Bins

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us