esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Koller" <>
Subject Re: ESMEMailet: send eMails to ESME - first user & Install guide published
Date Thu, 01 Jan 2009 10:00:08 GMT
Good morning,

the question regarding message contents and tags was not so much related to
the technical options, but more to the usability: where would the enduser
expect to put tags for an ESME message (when he sends an email message)?

Regarding the access for systems: I think it comes down to create a user
account and a valid token next to the regular registration/openid process.
This might be a topic for an ESME admin interface or the REST interface (a
method to be called by privileged users).

Kind regards,


On Thu, Jan 1, 2009 at 8:43 AM, Hirsch, Richard

> Looks very cool. I like the ability to register with your token.
> If you add the ability to examine the message contents then you would be
> able to add tags as well.
> What about the necessity of registering for other systems? How would that
> work? For example, how could I register for a CMS system that has the
> ability to send emails but might have difficulty in registering via a reply.
> D.
> -----Urspr√ľngliche Nachricht-----
> Von: Daniel Koller []
> Gesendet: Do 12/25/2008 17:03
> An:
> Betreff: ESMEMailet: send eMails to ESME - first user & Install guide
> published
> Hi all,
> I just published a first version of the ESMEMailet, which is the following:
> "...The ESME Mailet is a plugin for the Open source Mail Server Apache
> James<>,
> which allows users of an ESME infrastructure (both humans and technical
> systems) to send email messages to an ESME instance using their own
> identity. Messages sent through the mailet show up as personal messages
> from
> these end users, so people following you get them in the respective
> blogging
> timeline...."
> The install guide is available at
> Feedback, comments etc. are welcome!
> Kind regards,
> Daniel

Daniel Koller
Jahnstrasse 20
80469 M√ľnchen *

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message