From owner-freebsd-chat Wed Feb 12 19:38:55 2003 Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7740737B401 for ; Wed, 12 Feb 2003 19:38:53 -0800 (PST) Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net [207.217.120.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9D0243F85 for ; Wed, 12 Feb 2003 19:38:52 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0418.cvx22-bradley.dialup.earthlink.net ([209.179.199.163] helo=mindspring.com) by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18jAD3-0002es-00; Wed, 12 Feb 2003 19:38:50 -0800 Message-ID: <3E4B12F5.2608BBB@mindspring.com> Date: Wed, 12 Feb 2003 19:37:25 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Brad Knowles Cc: Rahul Siddharthan , freebsd-chat@freebsd.org Subject: Re: Email push and pull (was Re: matthew dillon) References: <20030211032932.GA1253@papagena.rockefeller.edu> <3E498175.295FC389@mindspring.com> <3E49C434.D8D497EE@mindspring.com> <3E4A83BC.8A15E7C3@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4dfa0e541153ecfc1f03f714904123f29a8438e0f32a48e08350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Brad Knowles wrote: > At 9:26 AM -0800 2003/02/12, Terry Lambert wrote: > >> In what way does IMAP4 need to be changed? > > > > Add domain support. > > Certainly, you could pass pretty much whatever you want. The > issue is whether or not the IMAP server understands the @domain > portion. > > This problem is already solved -- check out Perdition. The problem is *not* solved by Perdition. Perdition does not even *begin* to solve the problem. > > Well, the "OP" in this case is actually a reference to a DJB > > document, and what we're interested in here is solving the > > problem. We don't have to accept both the data store and the > > "don't send messages" parts of the document, all or nothing. > > Well, if we're interested in solving the problem and not > necessarily accepting the entire document as specified, then we might > as well throw the whole thing away. I agree. It is a poor specification. > > No, you'd direct-send notices. You'd flood-fill the messages > > the notices referred to, to address the scalability and availability > > problems, and to partially address the "revisionist history" and > > "delete before receipt" problems. > > You can do this today. Send an e-mail and tell people to go read > a specific USENET news message. Doesn't work too well. Doesn't address any privacy issues. Even encrypted, your data is out there for anyone to perform traffic analysis upon. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message