Re: tlug: IMAP daemon

["Stephen J. Turnbull" <turnbull@example.com>]

>>>>> "Totoro" == Totoro  <riley@example.com> writes:

    Totoro> I've been diddling with IMAP lately, and so far it does
    Totoro> seem to be a tad underdocumented.

Thanks for the confirmation.

Yo, Craig!

    Totoro> RH's package included a little bit of info, but not much
    Totoro> more than what you have. For a protocol that is being
    Totoro> touted as the replacement for POP, it seems like time to
    Totoro> get more information together...

Well, here's a list available at any RFC repository.  Typically
they're in text files with names like `rfc####.txt', although often
they're compressed.  ftp://ftp.lab.kdd.co.jp/rfc is what I use.

2060 defines the protocol; it's pretty heavy going and probably only
worth reading the first few sections if you're not an implementer.
1733 and 2180 talk a little bit about applications.

2060 INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1. M. Crispin.
     December 1996. (Format: TXT=166513 bytes) (Obsoletes RFC1730)
     (Status: PROPOSED STANDARD)
1733 DISTRIBUTED ELECTRONIC MAIL MODELS IN IMAP4. M. Crispin. December
     1994. (Format: TXT=6205 bytes) (Status: INFORMATIONAL)
2180 IMAP4 Multi-Accessed Mailbox Practice. M. Gahrns. July 1997.
     (Format: TXT=24750 bytes) (Status: INFORMATIONAL)

The rest of these are probably not interesting, but they came for
"free" with the grep ;-)  On second thought, the content is not very
interesting, but some of the titles are food for thought.

2244 ACAP -- Application Configuration Access Protocol. C. Newman, J.
     G. Myers. November 1997. (Format: TXT=154610 bytes) (Status: PROPOSED
     STANDARD)
2222 Simple Authentication and Security Layer (SASL). J. Myers.
     October 1997. (Format: TXT=35010 bytes) (Status: PROPOSED STANDARD)
2221 IMAP4 Login Referrals. M. Gahrns. October 1997. (Format: TXT=9251
     bytes) (Status: PROPOSED STANDARD)
2195 IMAP/POP AUTHorize Extension for Simple Challenge/Response. J.
     Klensin, R. Catoe, P. Krumviede. September 1997. (Format: TXT=10468
     bytes) (Obsoletes RFC2095) (Status: PROPOSED STANDARD)
2193 IMAP4 Mailbox Referrals. M. Gahrns. September 1997. (Format:
     TXT=16248 bytes) (Status: PROPOSED STANDARD)
2192 IMAP URL Scheme. C. Newman. September 1997. (Format: TXT=31426
     bytes) (Status: PROPOSED STANDARD)
2177 IMAP4 IDLE command. B. Leiba. June 1997. (Format: TXT=6770 bytes)
     (Status: PROPOSED STANDARD)
2095 IMAP/POP AUTHorize Extension for Simple Challenge/Response. J.
     Klensin, R. Catoe, P. Krumviede. January 1997. (Format: TXT=10446
     bytes) (Obsoleted by RFC2195) (Status: PROPOSED STANDARD)
2088 IMAP4 non-synchronizing literals. J. Myers. January 1997.
     (Format: TXT=4052 bytes) (Status: PROPOSED STANDARD)
2087 IMAP4 QUOTA extension. J. Myers. January 1997. (Format: TXT=8542
     bytes) (Status: PROPOSED STANDARD)
2086 IMAP4 ACL extension. J. Myers. January 1997. (Format: TXT=13925
     bytes) (Status: PROPOSED STANDARD)
2061 IMAP4 COMPATIBILITY WITH IMAP2BIS. M. Crispin. December 1996.
     (Format: TXT=5867 bytes) (Obsoletes RFC1730) (Status: INFORMATIONAL)
1732 IMAP4 COMPATIBILITY WITH IMAP2 AND IMAP2BIS. M. Crispin. December
     1994. (Format: TXT=9276 bytes) (Status: INFORMATIONAL)
1731 IMAP4 Authentication Mechanisms. J. Myers. December 1994.
     (Format: TXT=11433 bytes) (Status: PROPOSED STANDARD)
1730 INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4. M. Crispin.
     December 1994. (Format: TXT=156660 bytes) (Obsoleted by RFC2060,
     RFC2061) (Status: PROPOSED STANDARD)

---------------------------------------------------------------
Next TLUG Nomikai: 14 January 1998 19:15  Tokyo station
Yaesu Chuo ticket gate.  Or go directly to Tengu TokyoEkiMae 19:30
Chuo-ku, Kyobashi 1-1-6, EchiZenYa Bld. B1/B2 03-3275-3691
Next Saturday Meeting: 14 February 1998 12:30 Tokyo Station
Yaesu Chuo ticket gate.
---------------------------------------------------------------
a word from the sponsor:
TWICS - Japan's First Public-Access Internet System
www.twics.com  info@example.com  Tel:03-3351-5977  Fax:03-3353-6096