From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] imap
Date: Fri, 21 Mar 2014 09:27:21 -0400 [thread overview]
Message-ID: <20140221092721.eklhad@comcast.net> (raw)
This is perhaps more thinking ahead...
The most common request from users is:
why doesn't edbrowse work on this site,
and is usually an object or method that I haven't implemented yet.
The next request is:
what about imap?
I started looking at wikipedia imap and rfc3501.
There's a lot going on here.
I think there are three options for us.
1. Access an imap server much as we access a pop3 server today.
Use port 143 instead of 110.
Many of the commands are the same, at least functionally,
and of course there are many new commands.
We wouldn't have to use all the new commands.
2. Try to use a linux imap library to help us,
the way we use curl for http and ftp.
I don't even know if such exists and is easy to use.
It has now become a requirement that any libraries we use are
in linux and free bsd, since bsd is on board with us.
3. Ask the user to use a separate stand-alone program to pull
mail off an imap server and into a local mailbox file.
Edbrowse would then read the local mailbox file and pretend it was a mail server,
and present those mail messages to the user via the same interface as today.
Delete them (from the file rather than the mail server),
or same them to other files, or save attachments, etc, as we do today.
I would lean towards 3, but I might not understand what is going on here at all,
and I'm curious what others think.
Karl Dahlke
next reply other threads:[~2014-03-21 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 13:27 Karl Dahlke [this message]
2014-03-21 14:31 ` Chris Brannon
2014-03-21 17:11 ` Adam Thompson
2014-03-21 17:21 ` Adam Thompson
2014-03-21 18:26 ` Chris Brannon
2014-03-21 20:22 ` Adam Thompson
2014-03-22 10:04 Karl Dahlke
2014-03-22 21:28 ` Adam Thompson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140221092721.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).