Carapace Message Store

A Carapace message store holds messages for a user. It is designed to support access by the standard protocols:

POP3 is the standard protocol for fetching messages from a message store. This allows common mail programs such as Microsoft Outlook or Outlook Express to retrieve messages from the Carapace message stores.
SMTP is the protocol for transferring Internet email. Carapace supports this protocol to allow messages to be sent and delivered into the Carapace message stores.

In addition, a message store can be configured to perform customised actions upon receipt of a message.

The MessageStore interface gives full access to message stores from other computer systems.

Access for administrators is via a Web-based UI running within the Carapace Hub. This makes use of the administrative functions offered by the Admin interface.

Each message store is owned by an individual user and access is password protected. All actions on a message store are audited within the Carapace audit.

Message Properties

Each message within a message store has the following properties:

sequenceNumber an Integer which uniquely identifies this message within the store -- number 1 indicates the oldest message within the store

status the status of message is takes of the following values:

new -- a newly-received message which has not yet been accessed by the message store owner
listed -- this message has appeared in a message store listing but has not yet been fetched
fetched -- the message has been fetched from the message store by the message store owner
deleted -- the message has been marked for deletion

sender the address of the sender of the message

subject the subject of the message

contentType a description of the type of content in the message -- for Internet email this is the MIME content type e.g. text/plain, multipart/alternative etc.

headers any headers for the message

content the full content of the message

Messaging Domains

Carapace holds messages for users within a domain. Both Internet email and the OSI X.400 mail use the concept of domains to signify a group of addresses. Examples of such domains are as follows:

mail system user address domain

Internet info@carapace.co.uk carapace.co.uk

X.400 G=Fred/S=Flintstone/P=CaveDwellers/A=StoneMail/C=US P=CaveDwellers/A=StoneMail/C=US

mail system	user address	domain
Internet	info@carapace.co.uk	carapace.co.uk
X.400	G=Fred/S=Flintstone/P=CaveDwellers/A=StoneMail/C=US	P=CaveDwellers/A=StoneMail/C=US

The domains which Carapace considers local are configured in the database using the Admin interface. Message stores can only be held for users having address within a local domain. Messages destined for users in other domains are passed on to the message transport system for remote delivery.

Contents Index Current topic: audit Related topics: databases

`sequenceNumber`	an Integer which uniquely identifies this message within the store -- number 1 indicates the oldest message within the store
`status`	the status of message is takes of the following values: `new` -- a newly-received message which has not yet been accessed by the message store owner `listed` -- this message has appeared in a message store listing but has not yet been fetched `fetched` -- the message has been fetched from the message store by the message store owner `deleted` -- the message has been marked for deletion
`sender`	the address of the sender of the message
`subject`	the subject of the message
`contentType`	a description of the type of content in the message -- for Internet email this is the MIME content type e.g. `text/plain`, `multipart/alternative` etc.
`headers`	any headers for the message
`content`	the full content of the message