Hey Dave,
The css-inliner is the key - so that's great that it may be suitable. The settings section sounds perfect.
With the CSS. I can include the CSS in the <styles> of the template itself, so no major issue really.
My other point was more based around the use of the templates and the default content. The system assumes that the "content" is going to be the same structure for any template that you use, whereas the default content needs to be different per template.
For instance, I may have a template for a "Alert" which is simple header | content | footer. Then another template which is for a "Newsletter" which has a header | issue number | Welcome text | Image & Story | Image & Story | Footer. The default content for "Alert" is simple, however the default content for the "Newsletter" is a fairly complex HTML table with images etc. Currently I cannot acheive this - I have to have the client "save and copy" a previous message that I set up for them.
If you are updating the newsletter plugin, maybe each template should have it's own default content rather than as a global setting?
Cheers,
Tim (toledoh.com.au)