From: Lincoln de Sousa <lincoln@comum.org>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] sup v2 progress report
Date: Mon, 28 Mar 2011 11:21:54 -0300 [thread overview]
Message-ID: <20110328142153.GA27479@lixeiro> (raw)
In-Reply-To: <1301257195-sup-9486@masanjin.net>
[-- Attachment #1.1: Type: text/plain, Size: 1443 bytes --]
On Sun, Mar 27, 2011 at 08:41:59PM +0000, William Morgan wrote:
> Hello all,
>
> I'm happy to report that Sup version 2 is well underway!
Hehe, believe me, you're not the only one happy with this news :)
> Sup version 2 features:
> - a client/server model that works over HTTP, allowing
> a) development of other clients, e.g. web-based and phone-based
> b) simultaneous access from multiple clients
> c) IMAP emulation, aka no more lock-in!
> - an improved console-based client
>
> Heliotrope, the server component, is close to ready for a version 1 release.
> You can find it at https://github.com/wmorgan/heliotrope/.
This is something that makes me think that this sup server could be used
as an MDA receiving mails directly from the MTA.
What currently have is the following env:
MTA
-> MDA (courier for me)
-> MDA Maildir (offlineimap in my case)
-> sup (heliotrope)
-> Mail reader
Why not doing something like this?!:
MTA -> sup (heliotrope) -> Mail reader
I've started to write a web app to read my mails and I'm not using an
IMAP, POP or any other of these protocols, it's based on a python
library I'm writting to be generict enough to connect with anything. But
I'd love to abandon this abstraction layer in favor of sup :D
Cheers,
--
Lincoln de Sousa <lincoln@comum.org>
xmpp:lincoln@comum.org
http://comum.org
http://culturadigital.br
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-03-28 15:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 20:41 [sup-devel] " William Morgan
2011-03-28 4:14 ` [sup-talk] " Matthieu Rakotojaona
2011-03-28 14:57 ` David J. Hamilton
2011-03-28 22:57 ` William Morgan
2011-03-28 12:52 ` [sup-devel] " Nicolas Pouillard
2011-03-29 3:11 ` [sup-talk] " William Morgan
2011-03-29 4:00 ` William Morgan
2011-03-29 21:19 ` [sup-talk] " Nicolas Pouillard
2011-03-29 21:31 ` William Morgan
2011-03-28 14:21 ` Lincoln de Sousa [this message]
2011-03-29 3:12 ` [sup-talk] " William Morgan
2011-04-14 7:39 ` [sup-talk] [sup-devel] " Ico Doornekamp
2011-04-14 7:51 ` Ico Doornekamp
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=20110328142153.GA27479@lixeiro \
--to=lincoln@comum.org \
--cc=sup-talk@rubyforge.org \
/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