Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 26 Aug 1998 10:51:53 -0600
From:      Lyndon Nerenberg <lyndon@esys.ca>
To:        Terry Lambert <tlambert@primenet.com>
Cc:        hackers@FreeBSD.ORG
Subject:   Re: Imap4
Message-ID:  <SIMEON.9808261053.E18812@warhol.esys.ca>
In-Reply-To: <199808260132.SAA29380@usr04.primenet.com>
References:  <199808260132.SAA29380@usr04.primenet.com> <Pine.GSO.3.95q.980825094938.394d-100000@elect8> from "Nick Hibma" at Aug 25, 98 09:51:27 am

next in thread | previous in thread | raw e-mail | index | archive | help

On Wed, 26 Aug 1998 01:32:09 +0000 (GMT) Terry Lambert <tlambert@primenet.com>
wrote:

> The wire protocol is similar to LISP: lots of silly parenthesis.

With lots of lists of things flowing around. What's wrong with parens? If it 
works for Lisp ... :-)

> Many ISPs dislike IMAP4 because it takes a lot of storage, and only
> gives back increased modem usage and wire traffic in return for
> the extra storage it consumes -- wait a minute, I get why they
> don't like it... ;-).

You mean your IMAP server doesn't implement quotas? Let me give you a URL to 
our sales page ... And with the push to thin clients and NC, where else are you going to store
that mail? Disk is cheap, and the security of having the mail backed up is a big win. 

> One of the most annoying this is that, without a full IMSP implementation,
> of which there is not one of, there is no provision for fanning out
> envelope information into sub-mailboxes (which would make IMAP4
> useful for virtual domain hosting, where POP3 fails to retain
> envelope information because of a stupid agrument between Eric Allman
> and Eric Raymond about "who is the MTA"), nor is there provision for
> client specification of server side filtering rules (which would make
> it otherwise more useful than POP3).

I'm not sure how IMSP helps with virtual domains. This belongs a lot closer to 
the MTA. IMSP isn't really useful until you've drilled down into the context 
of an authenticated (IMAP) user. As for filtering, SIEVE is getting close to 
being reality (there are three prototypes running that I'm aware of).

Also, what's a "full" IMSP implementation? There never was an RFC issued. The 
Cyrus and SMS IMSP servers are as "full" as it gets, being the only two 
released IMSP servers (that I'm aware of).

> Basically, it's an interesting "also ran" that won't displace POP3
> any time soon until its flaws are noted and corrected.

I'm going to take great pleasure in quoting that back to you in a couple of 
years :-)

My prediction is that IMAP is going to displace the majority of POP3 
implementations over the next 2-3 years. POP3 just can't handle the mobile 
community that represents more and more of the e-mail users out there today.

Now, to add something FreeBSD related, I've been pushing for ESYS to do a port 
of our servers to FreeBSD for a while now. We've had a couple of requests for 
it, but not enough to justify the cost of adding another platform. If there's 
anyone out there who would *buy* *a* *copy* of Simeon Message Server if we did 
a port, please e-mail me directly. (http://www.esys.ca for more info on the 
server product.)

--lyndon


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?SIMEON.9808261053.E18812>