About site: Internet/RFCs/1701 - 1800 - RFC 1732
Return to Computers also Computers
  About site: http://tools.ietf.org/html/rfc1732

Title: Internet/RFCs/1701 - 1800 - RFC 1732 IMAP4 Compatibility with IMAP2 and IMAP2bis. M. Crispin. December 1994.
RFC_2301 File format for internet fax.

RFC_2773 Encryption Using KEA and SKIPJACK. R. Housley, P. Yee, W. Nace. February 2000.

Four-fold_Increase_in_Productivity_and_Quality Published internal study, of Ericsson AXD 301 ATM switch project, using Erlang, C, C++, Java. Results: programmer productivity, code error rates, roughly proportional to source code size. [PDF]

Sony_E-Book_to_be_Written_in_Electronic_Ink "The consumer electronics maker is using electronic ink in its new e-book, marking one of the first applications of the next-generation display technology." [CNet] (March 24, 2004)

arTekWeb Offers site design, graphics, redesign, domain name registration and maintenance. Located in Larchmont, New York.

Next5_Interactive Design, DHTML, JavaScript, PERL, PHP, database development, e-commerce, search engine optimization, and hosting. Based in State College, Pennsylvania, United States.

  Alexa statistic for http://tools.ietf.org/html/rfc1732





Get your Google PageRank






Please visit: http://tools.ietf.org/html/rfc1732
  Related sites for http://tools.ietf.org/html/rfc1732
    Hello_World_Program COBOL source code for this traditional, beginner's programming exercise.
    Moscato,___Pablo Universidade Estadual de Campinas.
    ArtUproar Artwork, skins for Winamp, Windowblinds, and other applications, as well as wallpapers and a strong community.
    Clark_Consulting_Group Software consulting and development corporation specializing in network, firmware, robotic and device driver development.
    Innostream_org Provides free cellular phones wallpapers, themes and mflash for Nokia, Samsung, Ericsson, Motorola and Innostream.
    PC_Magazine Complete guide to PCs, peripherals and upgrades. Labs-based reviews of computer- and Internet-related products and services, technology news and trends, shopping advice, and price comparisons.
    Pardain_Design Christian PowerPoint Backgrounds and templates.
    Test_Track_Learning_Management_System Learning and Content Management developer and hosting services.
    The_Kiev_Elephant Video Player WarpVision, video accelerator HW EnDIVE and TV card driver TVShow are available here.
    Thejesh_AP About. Articles. Jazmyn OS completely written in C++ and a bit of 8086 assembly. Some tricky, funny programs. Jokes.
    Photolocator_Digital_Image_Software A database that manages and prints your digital images. Designed for appraisers and inspectors, you can find pictures by address, street, and city. Print forms include single family, and custom report
    Impression_Technology Designs, integrates, and delivers large-scale, image-assisted data capture solutions that generate measurable value for our customers in the automated forms processing market.
    FreewarePalm Extensive list of freeware games for the Palm.
    MagicNIC Domain registration, web design and hosting in Chinese and English language.
    Winsoft Developers of WinText, a multilingual creation tool with spell checking, text editing and publication functionality.
    Mac_Citadel A home for nostalgic Mac users of the BBS era; also tries to welcome a younger generation by offering a Java gateway to those who might have difficulties with the telnet protocol.
    GlowRed_com Provides web design, Flash animation, domain registration, hosting, and promotion.
    Resort_Online_Webring Residents' personal websites from the Resort Online.
    MV_Tracker Provides free realtime website statistics, page tracking, referrer tracking, and button exchange codes.
    Constraint_Satisfaction_Problems Research group in the Computing Laboratory, Oxford University.
This is websites2007.org cache of m/ as retrieved on 2008.10.10 websites2007.org's cache is the snapshot that we took of the page as we crawled the web. The page may have changed since that time.
RFC 1732 - IMAP4 COMPATIBILITY WITH IMAP2 AND IMAP2BIS body { margin: 0px 8px; font-size: 1em; } h1, h2, h3, h4, h5, h6, .h1, .h2, .h3, .h4, .h5, .h6 { font-weight: bold; line-height: 0pt; display: inline; white-space: pre; font-family: monospace; font-size: 1em; font-weight: bold; } pre { font-size: 1em; } .pre { white-space: pre; font-family: monospace; } .header{ font-weight: bold; } .invisible { text-decoration: none; color: white; } @media print { body { font-size: 10.5pt; } h1, h2, h3, h4, h5, h6 { font-size: 10.5pt; } a:link, a:visited { color: inherit; text-decoration: none; } .break { page-break-before: always; } .noprint { display: none; } } @media screen { .grey, .grey a:link, .grey a:visited { color: #777; } .docinfo { background-color: #EEE; } .top { border-top: 7px solid #EEE; } .bgwhite { background-color: white; } .bgred { background-color: #F44; } .bggrey { background-color: #666; } .bgbrown { background-color: #840; } .bgorange { background-color: #FA0; } .bgyellow { background-color: #EE0; } .bgmagenta{ background-color: #F4F; } .bgblue { background-color: #66F; } .bgcyan { background-color: #4DD; } .bggreen { background-color: #4F4; } .legend { font-size: 90%; } .cplate { font-size: 70%; border: solid grey 1px; } } [RFCs/IDs] [Plain Text] [From draft-ietf-imap-compat] INFORMATIONAL Network Working Group M. CrispinRequest for Comments: 1732 University of WashingtonCategory: Informational December 1994 IMAP4 COMPATIBILITY WITH IMAP2 AND IMAP2BISStatus of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited.Introduction This is a summary of hints and recommendations to enable an IMAP4 implementation to interoperate with implementations that conform to earlier specifications. None of these hints and recommendations are required by the IMAP4 specification; implementors must decide for themselves whether they want their implementation to fail if it encounters old software. IMAP4 has been designed to be upwards compatible with earlier specifications. For the most part, IMAP4 facilities that were not in earlier specifications should be invisible to clients unless the client asks for the facility. In some cases, older servers may support some of the capabilities listed as being "new in IMAP4" as experimental extensions to the IMAP2 protocol described in RFC 1176. This information may not be complete; it reflects current knowledge of server and client implementations as well as "folklore" acquired in the evolution of the protocol.Crispin [Page 1] RFC 1732 IMAP4 - Compatibility December 1994IMAP4 client interoperability with old servers In general, a client should be able to discover whether an IMAP2 server supports a facility by trial-and-error; if an attempt to use a facility generates a BAD response, the client can assume that the server does not support the facility. A quick way to check whether a server implementation supports the IMAP4 specification is to try the CAPABILITY command. An OK response that includes the IMAP4 capability value indicates a server that supports IMAP4; a BAD response or one without the IMAP4 capability value indicates an older server. The following is a list of facilities that are only in IMAP4, and suggestions for how new clients might interoperate with old servers: CAPABILITY command A BAD response to this command indicates that the server implements IMAP2 (or IMAP2bis) and not IMAP4. AUTHENTICATE command. Use the LOGIN command. LSUB and LIST commands Try the RFC 1176 FIND command. * in a sequence Use the number of messages in the mailbox from the EXISTS unsolicited response. SEARCH extensions (character set, additional criteria) Reformulate the search request using only the searching options listed in search_old in the IMAP4 grammar. This may entail doing multiple searches to achieve the desired results. BODYSTRUCTURE fetch data item Try to fetch the non-extensible BODY data item. body section number 0 Fetch the entire message and extract the header. RFC822.HEADER.LINES and RFC822.HEADER.LINES.NOT fetch data items Use RFC822.HEADER and remove the unwanted information. BODY.PEEK[section], RFC822.PEEK, and RFC822.TEXT.PEEK fetch data items Use the corresponding non-PEEK versions and manually clear the \Seen flag as necessary.Crispin [Page 2] RFC 1732 IMAP4 - Compatibility December 1994 UID fetch data item and the UID commands No equivalent capabilitity exists in older servers. FLAGS.SILENT, +FLAGS.SILENT, and -FLAGS.SILENT store data items Use the corresponding non-SILENT versions and ignore the untagged FETCH responses which com eback. The following IMAP4 facilities were introduced in the experimental IMAP2bis revisions to RFC-1176, and may be present in a server that does not support the CAPABILITY command: CREATE, DELETE, and RENAME commands To test whether these commands are present, try a CREATE INBOX command. If the response is NO, these commands are supported by the server. If the response is BAD, they are not. Older servers without the CREATE capability may sup- port implicit creation of a mailbox by a COPY command with a non-existant name as the destination. APPEND command To test whether this command is present, try to append a zero-length stream to a mailbox name that is known not to exist (or at least, highly unlikely to exist) on the remote system. SUBSCRIBE and UNSUBSCRIBE commands Try the form of these commands with the optional MAILBOX keyword. EXAMINE command Use the SELECT command instead. flags and internal date argument to APPEND command Try the APPEND without any flag list and internal date argu- ments. BODY, BODY[section], and FULL fetch data items Use RFC822.TEXT and ALL instead. Server does not support MIME. PARTIAL command Use the appropriate FETCH command and ignore the unwanted data. IMAP4 client implementations must accept all responses and data for- mats documented in the IMAP4 specification, including those labeledCrispin [Page 3] RFC 1732 IMAP4 - Compatibility December 1994 as obsolete. This includes the COPY and STORE unsolicited responses and the old format of dates and times. In particular, client imple- mentations must not treat a date/time as a fixed format string; nor may they assume that the time begins at a particular octet. IMAP4 client implementations must not depend upon the presence of any server extensions that are not in the base IMAP4 specification. The experimental IMAP2bis version specified that the TRYCREATE spe- cial information token is sent as a separate unsolicited OK response instead of inside the NO response. The FIND BBOARDS, FIND ALL.BBOARDS, and BBOARD commands of RFC 1176 are removed from IMAP4. There is no equivalent to the bboard com- mands, which provided a separate namespace with implicit restrictions on what may be done in that namespace. Older server implementations may automatically create the destination mailbox on COPY if that mailbox does not already exist. This was how a new mailbox was created in older specifications. If the server does not support the CREATE command (see above for how to test for this), it will probably create a mailbox on COPY. Older server implementations may not preserve flags or internal dates on COPY. Some server implementations may not permit the preservation of certain flags on COPY or their setting with APPEND as site policy.Crispin [Page 4] RFC 1732 IMAP4 - Compatibility December 1994IMAP4 server interoperability with old clients In general, there should be no interoperation problem between a server conforming to the IMAP4 specification and a well-written client that conforms to an earlier specification. Known problems are noted below: Poor wording in the description of the CHECK command in earlier specifications implied that a CHECK command is the way to get the current number of messages in the mailbox. This is incorrect. A CHECK command does not necessarily result in an EXISTS response. Clients must remember the most recent EXISTS value sent from the server, and should not generate unnecessary CHECK commands. An incompatibility exists with COPY in IMAP4. COPY in IMAP4 servers does not automatically create the destination mailbox if that mailbox does not already exist. This may cause problems with old clients that expect automatic mailbox creation in COPY. The PREAUTH unsolicited response is new in IMAP4. It is highly unlikely that an old client would ever see this response. The format of dates and times has changed due to the impending end of the century. Clients that fail to accept a four-digit year or a signed four-digit timezone value will not work properly with IMAP4. An incompatibility exists with the use of "\" in quoted strings. This is best avoided by using literals instead of quoted strings if "\" or <"> is embedded in the string.Security Considerations Security issues are not discussed in this memo.Author's Address: Mark R. Crispin Networks and Distributed Computing, JE-30 University of Washington Seattle, WA 98195 Phone: (206) 543-5762 EMail: MRC@CAC.Washington.EDUCrispin [Page 5] Html markup produced by rfcmarkup 1.69, available fromhttp://tools.ietf.org/tools/rfcmarkup/
 

IMAP4

Compatibility

with

IMAP2

and

IMAP2bis.

M.

Crispin.

December

1994.

http://tools.ietf.org/html/rfc1732

RFC 1732 2008 October

dvd rental

dvd


IMAP4 Compatibility with IMAP2 and IMAP2bis. M. Crispin. December 1994.

Rules

© 2008 Internet Explorer 5+ or Netscape 6+
Recommended Sites: 1. Arts - Business - Computers - Games - Health - Home - Kids and Teens - News - Recreation - Reference - Regional - Science - Shopping - Society - Sports - World Miss Gallery - Top Anime Hentai - DVD rental by mail - Fast Loans - Bad Credit Loan - Credit Card Consolidation - Wills - Credit Cards
2008-10-10 23:03:40

Copyright 2005, 2006 by Webmaster
Websites is cool :) 182Apartamenty Viva Maria - Torby Reklamowe - Zdjêcia Do Kalendarzy - Hotel Innsbruck - Poland Hotel