Posted by drob on May 8, 2006 at 11:12pm
In a meeting today discussing the next generation of the Events systems we recognized that mail issues were a pretty big deal. We'll be working and posting specific use cases shortly. In the meantime there was a stong feeling from those present that we should coordinate all mail issues with this group.
There are two broad issues - the UI and the back-end services.
UI
- The ability to compose and deliver HTML and text emails
- A well designed UI for non-technical end-users
- Ability to drop in merge codes for personalization and common text
API
- abstracted mail delivery services
- ability to create unique tokens
- auto-generation of reply addresses
I'm sure this is an incomplete (if not mis-informed) list - but you get the idea :). Our initial question is what level of coordination do we need to have? Our assumption is that send.module does much of what we need already. What else should we be thinking about?

Comments
The mimemail module has good
The mimemail module has good html email handling.
--
bradlis7.com | churchofchristnet.net
bradlis7.com | churchofchristnet.net
yup
My understanding is that mimemail is used by send.module - I think most of our work would leverage (extend??) send.