Summary | Incoming email processor for generic email actions |
Queue | Horde Base |
Queue Version | HEAD |
Type | Enhancement |
State | Accepted |
Priority | 1. Low |
Owners | |
Requester | chuck (at) horde (dot) org |
Created | 10/07/2008 (6063 days ago) |
Due | |
Updated | 04/21/2014 (4041 days ago) |
Assigned | |
Resolved | |
Milestone | |
Patch | No |
http://www.readwriteweb.com/archives/akibot_an_enterprise_twitter_clone_infused_with_ai.php
http://webworkerdaily.com/2009/03/02/ccbetty-offers-your-own-personal-email-assistant/
email prompts for cost objects, which users could then reply to with
their hours.
New Attachment: Sandy your free personal email assistant.pdf
the user guide and here are some related links:
http://code.google.com/p/sandysback/
http://sandysback.blogspot.com/
http://getsatisfaction.com/iwantsandy/topics/what_is_an_alternate_service_to_i_want_sandy
This is another service that does NLP:
http://www.readwriteweb.com/archives/deadline_task_management.php
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Incoming email processor for generic email actions
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ No
State ⇒ Accepted
addresses for creating information. The address the message is sent to
should be inferred from the email so that a single alias can handle
messages for a whole Horde installation. Messages should be directed
to a specific application via keywords and probably a survey of API
methods to see what applications are available.
The address to send emails to should be configurable to some extent;
possibly with a random string for minimal privacy. In any case
destructive actions should not happen as a result of email processing.
Example use cases:
- send an email marked "note this" to create a note in mnemo
- send an email marked "schedule this" to create an event
- send an email with a vcard attachment to create a contact, or a
vevent attachment to create an event
- send an email with an image attachment to upload it to ansel
- send an email to jonah to create a blog post