[
https://issues.apache.org/jira/browse/WAVE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710924#comment-13710924
]
STenyaK commented on WAVE-70:
-----------------------------
I've done some work towards email integration for wiab.
The immediate goal I have is to have wiab become a fully usable alternative to
a traditional mailing list.
To do it, I'm adding a built-in agent bot to wiab source code. This bot can
currently:
- Take new blips/waves and send them via SMTP as emails (respecting the
message hierarchy, quoting correct text when inline-replying, etc), directed at
certain email address (supposedly, the mailing-list email address).
- Fetch new emails via IMAp from certain email account, search for emails
corresponding to the aforementioned mailing-list address which are new, and add
them as new waves (as of now, not respecting the message hierarchy, but it's
planned).
As you can see, it's a pretty limited integration. It also only supports one
mailing list per wiab server.
I'm not sure how far or where to go with this integration. As I say, short term
goal is mailing-list compatibility.
But, it could relatively easily be modified to support arbitrary emails (not
just those for certain mailing list). It could support per-user configuration
(so that the bot syncs the user email account with his waves, and viceversa).
Wiab could alternatively be modified to become a full-blown email server, or
rather, a wiab-email hybrid server.
What are your opinions on this?
> Integrating with email
> ----------------------
>
> Key: WAVE-70
> URL: https://issues.apache.org/jira/browse/WAVE-70
> Project: Wave
> Issue Type: Improvement
> Priority: Minor
>
> I do not know if main feature requests should be posted here, but I do
> think it is important.
> If you want the Wave protocol to slowly replace Email, it needs to be
> backward compatible!
> You should be able to send/receive emails from Google Wave (or any wave
> site). The system would basically send 2 version of the wave. A
> "wave"
> version, and an "email" version. The same way we do plain text /
> html
> currently for email. So we would add an email header including a reference
> to the current wave, so if the recipient is using a wave-compatible
> service, it would know to switch to wave. Otherwise, if it does not
> understand the wave header, it would just ignore it and use regular email.
> Something like that.
> Because seriously, I don't wave picking anytime unless you help people move
> gradually away from email.
> Right now I have a lot of friends with wave, but I don't use it because I
> know they check their emails wayy more often than their wave account.
> I do the same. So it all needs to be combined.
> ---
> Issue imported from http://code.google.com/p/wave-protocol/issues/detail?id=69
> Label: Type-Enhancement
> Label: Priority-Medium
> Stars: 6
> State: open
> Status: New
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
