Currently (v2.2.0a9 test build) there is an "asymmetry" in the mail attributes setup between file based repositories and db based repositories, that would be worth to fix in sqlResources.xml.
While, in the case of file based repositories, mail attributes are immediately available and fully functional simply by having james.sar v2.2.0a9 in place, in case of db based repositories some extra "manual" operations are needed, consisting in commenting and uncommenting appropriate entries in sqlResources.xml plus adding a "message_attributes" column to the "inbox" and "spool" tables if they already exist. If such operations are not done then mail attributes will exist and become nanipulatable by the APIs, but will not persist when a message is stored/spooled to disk. Such "manual" activity is unavoidable and quite acceptable when upgrading an existing server having existing messages in the db, but IMO they should and could be avoided when setting up a new server (or upgrading an existing one without messages in the db): this is achievable simply by having sqlResources.xml already configured *from the beginning* for mail attributes, not requiring any further modification after a clean install. This would also be consistent with having sqlResources.xml not changeable by users (unless there are problems to fix with a particular DBMS, fix that should be ported to CVS anyhow). I suggest then to modify sqlResources.xml accordingly in CVS to become "mail attributes enabled" by default. Some notes (in wiki? in the faq?) should be written to help administrators enable existing servers that have db based repositories (I can do that when back home). Any thoughts? (See also in this list under "Mail Attributes support added", and under "Mail attributes: backward and forward compatibility"). Vincenzo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
