I believe the better question to ask for is a concise API for interfacing to all Imail features/configuration parameters.
The limitation today on building alternate front-ends for IMail, whether it is a web interface in ASP or ASP.NET or application integration for mailing is the lack of an API for direct programmatic access of settings and control data. For example, an alternate WebMail needs to be able to change IMail filtering rules, user login password, alias settings, etc. if it is to be a full alternative without losing Imail-specific functionality. Although some of this can be done with sideways or under-the-hood tricks, a documented, supported "front-door" API is a right solution for Ipswitch to provide. I believe a good API is a more reasonable request of Ipswitch - it empowers any developer to go build what they want while not dragging Ipswitch into the "religious war" of IIS versus apache, ASP versus CF or PHP, etc. etc. To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
