Message Store messagetype and typequota options

The Message Store  option     enables Message Store message typing; by default, the standard MIME Content-type: header field is inspected, but optionally the   option   may be set, for sites that wish to inspect an alternate header field (the Message-context: header field, defined in RFC 3458 (Message Context for Internet Mail) can be a good choice); then under   the further integer-indexed   groups of options   and   specify the actual message types, and optionally a corresponding   may be set  for purposes of type-specific quotas. That is, with the  Message Store   option specifying what header field to inspect, then integer-indexed sets of   options define the types themselves, where an integer-indexed    option defines a value to recognize in that header  field, and then the correspondingly indexed   Message Store   option specifies the Message Store name to use for such messages; e.g.: msconfig&#x3e; set store.messagetype.enable 1 msconfig# set store.messagetype.header Message-context msconfig# set store.messagetype.mtindex:1.contenttype voice-message msconfig# set mtindex:1.flagname Voice msconfig# set mtindex:2.contenttype fax-message msconfig# set mtindex:2.flagname Fax msconfig# set mtindex:3.contenttype pager-message msconfig# set mtindex:3.flagname Pager msconfig# set mtindex:4.contenttype multimedia-message msconfig# set mtindex:4.flagname Multimedia msconfig# set mtindex:5.contenttype text-message msconfig# set mtindex:5.flagname Text Sites that wish to perform Message Store message typing that find they are receiving messages lacking the header line which the site wishes to use as a basis for message typing decisions, (e.g., receiving messages lacking Message-context:), may wish to consider configuring an MTA system level Sieve filter to add an appropriate header line based upon other message characteristics (e.g., an   action  based upon the message&#x27;s outermost MIME Content-type: header line) to provide a basis for the Message Store&#x27;s message typing.

Sites that wish to enforce per-message-type quotas would also set the   Message Store   option, and define per-message-type quotas using the    option under Message Store   with   appropriately indexed for each type. For instance, continuing the above example (that is, assuming that five message types have already been defined as above),  enabling use of user per-message-type quotas would involve: msconfig# set store.typequota.enable 1 msconfig# set store.messagetype.mtindex:1.quotaroot Voice msconfig# set mtindex:2.quotaroot Fax msconfig# set mtindex:3.quotaroot Pager msconfig# set mtindex:4.quotaroot Multimedia msconfig# set mtindex:5.quotaroot Text and then setting a user&#x27;s actual quotas would mean setting the user&#x27;s   LDAP attribute (quota on space) and/or   LDAP attribute (quota on number of messages) with  per-message-type value syntax; e.g.: mailQuota: 80M;#Voice%40M;#Fax%10M;#Pager%5M;#Multimedia%20M;#Text%10M mailMsgQuota: 10000;#Voice%300;#Fax%40;#Pager%300;#Multimedia%300;#Text%9000

See also:
 * enable Option
 * header Option
 * contenttype Option
 * flagname Option
 * quotaroot Option
 * Sieve editheader extension
 * Message Store options