> Oh my. I think you misunderstood me. I'm *not* attempting to write iMail > templates in XML. I'm writing a web app that uses XML and XSL stylesheets, > which will then output regular iMail HTML files containing *no* XML. The
Ooops! My mistake. That is definitely easier/saner. I was thinking you wanted to allow customers to change look & feel "on-the-fly" through database lookups (or something similar). > Yeah, it's just a pet project. Unfortunatly, I have too much "real" work to > do right now, so this has been kinda put on the back burner. After redoing the HTML in many of the templates, I do have a great appreciation for the amount of work that went on in creating the HKSI templates. It's simple work. It just takes a while. > Wouldn't it just be easier to write a complete email app in ASP or .NET and > forget the iMail server alltogether? I thought about that option, but however hard it is to wrap IMail web messaging, it's even harder to do all of the web messaging functions from scratch. All I'm really doing by wrapping the web messaging portion is writing another UI-tier. I don't want to have to deal with the business or data-access layers to accomplish things like: - Authentication - Folders - User Administration (using IMail DB or External DB) - List Administration - Forwarding - Preferences - Etc, etc... -Norm Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Please visit the Knowledge Base for answers to frequently asked questions: http://www.ipswitch.com/support/IMail/
