From owner-freebsd-isp Fri Oct 17 09:52:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA22079 for isp-outgoing; Fri, 17 Oct 1997 09:52:23 -0700 (PDT) (envelope-from owner-freebsd-isp) Received: from cedb.dpcsys.com (cedb.dpcsys.com [206.16.184.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA22066 for ; Fri, 17 Oct 1997 09:52:12 -0700 (PDT) (envelope-from dan@dpcsys.com) Received: from localhost (dan@localhost) by cedb.dpcsys.com (8.8.5/8.8.2) with SMTP id QAA27617; Fri, 17 Oct 1997 16:43:44 GMT Date: Fri, 17 Oct 1997 09:43:44 -0700 (PDT) From: Dan Busarow To: Bradley Dunn cc: freebsd-isp@FreeBSD.ORG Subject: Re: in search of the ideal IMAP server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 16 Oct 1997, Bradley Dunn wrote: > Yes I have looked at imap.org. AFAIK, UW-IMAP does not store messages in > native MIME format, does it? Huh? MIME format is simply a few extra headers and optional boundary markers (over-simplification but essentially true). Of course uw-imap stores MIME messages in MIME format. They wouldn't be readable by a MIME capable MUA if it didn't. > messages in each folder. I have heard that native MIME message stores > really help in accomplishing this. Someone you have been talking to doesn't understand MIME. MIME addresses a lot of issues but storage efficiency isn't one of them unless you are refering to message/external-body. But that's a function of the sender's MUA, not the MTA or delivery agents like POP and IMAP. There's a list of RFC's for MIME at http://www.imc.org/rfcs.html#mime Dan -- Dan Busarow 714 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82