From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [69.252.207.41]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 4F7A67ABB3 for ; Sat, 11 Apr 2015 10:21:48 -0700 (PDT) Received: from resomta-ch2-07v.sys.comcast.net ([69.252.207.103]) by resqmta-ch2-09v.sys.comcast.net with comcast id EhKa1q0032EPM3101hKrVw; Sat, 11 Apr 2015 17:19:51 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:21e:4fff:fec2:a0f1]) by resomta-ch2-07v.sys.comcast.net with comcast id EhKq1q00H5LMg2101hKqRQ; Sat, 11 Apr 2015 17:19:51 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.3+ Date: Sat, 11 Apr 2015 13:19:50 -0400 Message-ID: <20150311131950.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=1428772791; bh=7i/j+LqYN19mZrpkjz/bHCCuV6SAW5KcxgVuxe+p7HE=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=FjGUAK/j+5PXDC8isoXm23U3nyINd3LtvDHwQGrMyuyhs13WOUHr7RuRnm5FseM1q mRdKoelgNUf/z1RL/fpLKf8tefXvaOrQJP+KkRnEmgi0cn2P3VqO/xMY3M0WzScI/m 1kohJ9zVT1rMCCwJxYKN28pX5PBNdIPy2BkVeUlSjqpU2K3llDFv1U5cnPRRZDFrxu PVklbGoExZ+wV9PFEaZa9UaUsctUBmVHL/Vtq4adsBgyEAaZY9FbKdZIHPQVJuTMUw vJHEktS80dieuHsD7qqN9aoY4wc1SIvXrpxkIVlvpy88jswOHkNssyW16csoLx4+4/ S55LGmid5v0pA== 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: Sat, 11 Apr 2015 17:21:48 -0000 Usually I refrain from commenting about other systems, other worlds, because I've never used them. Never touched windows, or gnome, or kde, or firefox, or speakup, or just about anything else; I live in my own little world. But aha, I did use mailx. It must have been nearly 30 years ago at bell labs. I liked it, and could still use it, but it entails a 2 pass process. I pulled mail down, and perhaps stored it, but then later I had to do more things with my emails. I wrote edbrowse to be an integrated system. Each email I can delete, or store, and put this attachment here, and throw that attachment away because it's just an image, and so on. One pass and I manage all the new emails and I'm done. That's why I typically have 6 emails pending, while my wife has 2000. As a side benefit, the rendered email looks just like it would if I edited the email later, in edbrowse, and browsed. This is more and more important as almost all emails are in html. So the first time I see it, when I'm wondering what to do with it, or even if I should keep it at all, it has the familiar braces and formatting of an edbrowse page, just like it will the next time I see it. All these points are small, and yet they're not small in that I fetch mail dozens of times a day and would like it to be ultra efficient and convenient. Even though I liked mailx, I will never go back to it. With that in mind, I think a simple version of imap could be done in a few hundred lines of code, with no structural changes and no negative immpact to edbrowse, if you never used imap it would never bother you, etc, and I could use it in a simple manner if I wished. The day may come when large mail servers only offer imap or exchange, no pop3 available. gmail for example still offers pop3 but I had to go into the settings section and set it up, because it is not available by default. So I may some day have to forget edbrowse as a mail client or support some level of imap, and this may be what others are seeing, and thus I would like a little bit of imap to work. Chris you said it looked a little more involved than you had hoped; if you don't want to mess with it I can look into it, but I would need to know where you get all this cool information about curl development. It's probably a thick manual, hopefully with examples. I'm thinking we should at least, as a first step, call the inner mail management routine that we already wrote, on the inbox folder, and get a feel for how that works. We could then build from there if we like it, or discard the effort if we don't. Karl Dahlke