From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 9CAAB7AC4C for ; Sun, 12 Apr 2015 09:01:45 -0700 (PDT) Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-04v.sys.comcast.net with comcast id F40o1q0052GyhjZ0140oXo; Sun, 12 Apr 2015 16:00:48 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:21e:4fff:fec2:a0f1]) by resomta-ch2-09v.sys.comcast.net with comcast id F40n1q00Q5LMg210140oXS; Sun, 12 Apr 2015 16:00:48 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.3+ Date: Sun, 12 Apr 2015 12:00:47 -0400 Message-ID: <20150312120047.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1428854448; bh=m3RRrmxmfwxTvV7sPN+/IcK3E30yEO+ZPvOHIrwH8w4=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=XLoTtpou+zivibuh7hfEcJJTN63l3Qybfpf2VSPL63kKNTM4Q7/JVOozil2HudjiG aUbkvYG8+tla2OJQ2d3yDrhxnLxuhAmw1q91+wZF20ZC9qLWXcptEb8YBvKTldLP+M 7CKIZecpfBHMNb69LINYhjuVNaeCKrm1prU6kMTp3I2Ijv93BYW5O3n3gWHOs4n0+a p/oPYcm6YAU/M3zClpvtVsjxuzL2dVpvB0gdtrt/2eyz16cFiGW3IQ+XwRBeJ2v4Sb AGSziG/OixCPdYTx9aWtLMrMATo5/8DzdfwKaGuzoal+lg5sqauFhtvlBc4lF+2Ou/ McilPibi1yWJg== Subject: [Edbrowse-dev] mailx X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2015 16:01:46 -0000 > I think that the heirloom-mailx version can do all these things since it > supports every mail protocol I can think of. It's not the protocols, it's the user interface. > we need ... imap (with imaps and starttls support), Handled by curl, to some degree. > pop3 (with ssl and tls support), Already done, mostly by curl. > mbox and maildir support (for local mail), I wouldn't use this; keep mail on the server or put mails on your computer where they really belong. > Correct threading header support (currently it doesn't work correctly, It does, but you have to save email unformatted and browse and re. I need to make this mechanism more convenient from a user perspective, but it is implemented inside. I had to do this a few years ago because people on one of the linux lists yelled at me, each of my emails started a new thread and confused them and I really meant it to be a reply on a current thread so anyways yes I did some of this work. It wasn't hard. I think it's documented somewhere. > Other stuff ... Yes, not sure how vital the other stuff is. > but I wonder if it's time for an edmail program? We can certainly see the advantages of the separate eb js process, now that it's done, and ebmail ebspread etc could make a lot of sense, as long as it's all an integrated system. Bill Gates found this out a long time ago. Some web forms call up email client so you can send email, or even submit form by email, and from within email you can click on a link and go to your browser, and (not speaking of windows but of edbrowse) I can be in the editor and suddenly decide I want to send somebody email and just put subject at the top and type sm and out it flies. I really like that. I really like the integratedness of it all, but that certainly doesn't preclude modularizing the software more than it is today. Karl Dahlke