*** Provided by Tim Sellar <tim.sellar@dsvr.co.uk>
*** NOT FOR DISCLOSURE

The following files make up a portion of the Dsvr TrustedMail service:

dtm.schema - schema for the postgresql quarantine database dtmqd -
daemon running on mail scanners, spawns parallel processes to export
quarantined mails into db.  dtmdd - daemon running darabase server,
spawns parallel processes to deliver messages flagged for delivery.

Future Work: Implement a hash function to map a domain name to a unique
identifier. This identifier would be used to name the table held in
the database and would avoid clients having to initially access the
index table - wouldn't be a problem if Postgres supported longer table
names :(...

Allow access to quarantined mail via POP, or ideally IMAP.

On the scanner, each quarantined message is being parsed before being
stored within the database. The message is also separately parsed by
each filtering process: bogofilter, spamassassin. It would be more
efficient if mail could be parsed into a Mail::Box::Message have tests
applied to it and a decision be made as to whether quarantine should
take place. It could then be passed directly to the quarantine database
avoiding the current steps of reinjection to Exim, writing to Maildir and
then parsing again...  This would lead to a framework more like that used
by MailScanner - an incoming queue of messages which are batch processed
and placed in an outgoing queue (if they haven't been quarantined or
binned). Perhaps Mail::Box and Mail::Audit could be used for this...
