You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by Reto Bachmann-Gmuer <re...@apache.org> on 2010/06/04 13:31:15 UTC
CLEREZZA-36: what mail functionality should be part of clerezza?
Looking at CLEREZZA-36 I'm wondering what email functionality should be part
of clerezza.
- I think that being able to send emails using the typerendering mechanism
makes sense
- I'm not sure if we need methods to provide methods to send mails to user
of the same clerezza instance using user-names are needed
- providing a generic email abstraction layer as façade to javax.mail imho
is clearly out of scope for clerezza
To the current API
- Its unclear how this permission work, why an action is needed and what
the public field SEND_MAIL is for (no documentation). Analysing the code I
understand:
SEND_FROM: needed to send an email from and to a user of the same
clerezza-instance using an email address associated to a user mentioned by
username in the target of the permission
SEND_MAIL: permission to send emails from any address and to any address
->I'd suggest to permit only sending user as the currently logged in user
and to distinguish between the permission to send to anybody or just to
other registered users.
- The methods takes a list of media-types but uses only one of them, I
don't see the need of giving a choice to the implementation but I think it
would be useful to be able to produce multi-part messages (like text and
html)
For CLEREZZA-36 I propose the following changes:
- deprecate methods that are unrelated to clerezza
- provide a service returning the javax.mail.Session, so that any
application sending email can benefit from the central configuration of
email settings
I created CLEREZZA-228 with the remaining issues.
Cheers,
reto