http://www.manitou-mail.org/wiki/ 2010-09-07T06:41:14+02:00 http://www.manitou-mail.org/wiki/ http://www.manitou-mail.org/wiki/lib/images/favicon.ico text/html 2010-07-23T19:56:01+02:00 http://www.manitou-mail.org/wiki/doku.php/mdx_debian_package?rev=1279907761&do=diff We start from a fresh source tree for manitou-mdx, as obtained by un-tarring a manitou-mdx-<version>.tar.gz source archive. We'll use 0.9.11 as an example. The commands we need to create the package are available through the dpkg-dev (or fakeroot) and dh-make packages. text/html 2009-07-09T19:43:34+02:00 http://www.manitou-mail.org/wiki/doku.php/mdx_filters?rev=1247161414&do=diff Filters are normally edited in the user interface, in the window that appears when the File->Filters command is run. Once defined, they are applied server-side by manitou-mdx to messages that enter the database. A filter is defined to apply to incoming or outgoing mail or both. Applying a filter consists of evaluating its condition, and if the result is true, doing the actions that are associated to it. If a filter has no action, it can be considered inactive. A condition is basically an expr… text/html 2009-08-15T14:49:21+02:00 http://www.manitou-mail.org/wiki/doku.php/mdx_plugins?rev=1250340561&do=diff Plugins overview Plugins reference documentation spamc - Calls spamassassin to score messages and tag them spam or not. html_indexer - Extracts the text from HTML parts and pass it to the full text indexer to allow subsequent searches inside HTML-only contents. text/html 2009-09-07T21:01:17+02:00 http://www.manitou-mail.org/wiki/doku.php/nsis_script?rev=1252350077&do=diff NSIS (<http://nsis.sourceforge.net>) is used to create the install program for the Windows version of the Manitou-Mail user interface. It assumes the existence of a c:\manitou\nsis-installer directory, and that this directory contains manitou.exe, the Qt DLLs, and help/ xpm/ translations/ sub-directories, as well as assistant_adp.exe, which is the program for the Qt help system. text/html 2008-11-02T23:30:33+02:00 http://www.manitou-mail.org/wiki/doku.php/schema_0_9_10?rev=1225665033&do=diff Below is the SQL script for PostgreSQL that creates from scratch all the database objects. Before running it through psql, those preconditions should be met: * The database should exist and have UTF8 encoding (createdb -E UTF8 name_of_database in shell or CREATE DATABASE name_of_database ENCODING 'UTF8' under psql) * The plpgsql language should be enabled (createlang -d name_of_database plpgsql external command or CREATE LANGUAGE plpgsql under psql) * The current directory should contain … text/html 2008-11-09T02:19:02+02:00 http://www.manitou-mail.org/wiki/doku.php/schema_0_9_10_functions?rev=1226193542&do=diff These functions are called by the UI or manitou-mdx trash_msg CREATE OR REPLACE FUNCTION trash_msg(in_mail_id integer, in_op integer) RETURNS integer AS $$ DECLARE new_status int; BEGIN UPDATE mail SET status=status|16,operator=in_op WHERE mail_id=in_mail_id; SELECT INTO new_status status FROM mail WHERE mail_id=in_mail_id; RETURN new_status; END; $$ LANGUAGE 'plpgsql'; text/html 2008-11-08T18:55:59+02:00 http://www.manitou-mail.org/wiki/doku.php/schema_0_9_10_grants?rev=1226166959&do=diff Access rights management is left to the administrator by way of self-written SQL commands, as is the creation of database users. This page gives some basic guidelines on how to manage a database with multiple users in a typical scenario: * One dedicated database user is the owner of the database and all its objects. This is the user that runs the initial creation script. * One or several roles (=groups) are created with CREATE ROLE commands. * Access rights are assigned to each role for … text/html 2008-11-02T23:12:31+02:00 http://www.manitou-mail.org/wiki/doku.php/schema_0_9_10_upgrade?rev=1225663951&do=diff Below is the SQL script for PostgreSQL that upgrades the schema from 0.9.9 to 0.9.10. The changes fall mostly in two categories: * removing the trashed_mail table, the trashcan being merged into the mail table * setting referential integrity constraints text/html 2008-11-04T00:18:57+02:00 http://www.manitou-mail.org/wiki/doku.php/schema_0_9_10_upgrade_notes?rev=1225754337&do=diff Referential integrity constraints Before 0.9.10, there were no referential integrity constraints in the schema. The reason was mainly that most RI constraints refer to a message and messages were split between the mail and trashed_mail tables (as opposed to one table only), thus making simple RI constraints impractical. In 0.9.10, those tables are unified so RI constraints are enabled. text/html 2009-06-13T22:45:06+02:00 http://www.manitou-mail.org/wiki/doku.php/schema_0_9_11?rev=1244925906&do=diff Below is the SQL script for PostgreSQL that creates from scratch all the database objects. Before running it through psql, the database should exist and have UTF8 encoding (createdb -E UTF8 name_of_database in shell or CREATE DATABASE name_of_database ENCODING 'UTF8' under psql). Also, the current directory should contain the SQL files that are referenced at the end of the script; they contain the definitions of plpgsql functions. text/html 2009-06-13T22:57:57+02:00 http://www.manitou-mail.org/wiki/doku.php/schema_0_9_11_grants?rev=1244926677&do=diff Access rights management is left to the administrator by way of self-written SQL commands, as is the creation of database users. This page gives some basic guidelines on how to manage a database with multiple users in a typical scenario: * One dedicated database user is the owner of the database and all its objects. This is the user that runs the initial creation script. * One or several roles (=groups) are created with CREATE ROLE commands. * Access rights are assigned to each role for … text/html 2009-08-08T13:43:31+02:00 http://www.manitou-mail.org/wiki/doku.php/schema_0_9_11_upgrade?rev=1249731811&do=diff Below is the SQL script for PostgreSQL that upgrades the schema from 0.9.10 to 0.9.11. This script as well as all the SQL files are available in <http://www.manitou-mail.org/source/manitou-sql-0.9.11.tar.gz> -- This SQL script upgrades the database schema for manitou-mail -- from 0.9.10 to 0.9.11 version \set ON_ERROR_STOP 1 BEGIN; CREATE TABLE filter_log ( expr_id int, -- No reference to filter_expr, we don't want any constraint here mail_id int, -- No reference to mail to be able t… text/html 2009-08-08T13:44:47+02:00 http://www.manitou-mail.org/wiki/doku.php/schema_0_9_13_upgrade?rev=1249731887&do=diff Below is the SQL script for PostgreSQL that upgrades the schema from 0.9.12 to 0.9.13. This script as well as all the SQL files are available in <http://www.manitou-mail.org/source/manitou-sql-0.9.13.tar.gz> -- This SQL script upgrades the database schema for manitou-mail -- from 0.9.12 to 0.9.13 version \set ON_ERROR_STOP 1 BEGIN; ALTER TABLE body DROP COLUMN textsize; ALTER TABLE body ADD bodyhtml TEXT; UPDATE runtime_info SET rt_value='0.9.13' WHERE rt_key='schema_version'; END; text/html 2010-07-20T22:12:15+02:00 http://www.manitou-mail.org/wiki/doku.php/schema_1_0_0_grants?rev=1279656735&do=diff Access rights management is left to the administrator by way of self-written SQL commands, as is the creation of database users. This page gives some basic guidelines on how to manage a database with multiple users in a typical scenario: * One dedicated database user is the owner of the database and all its objects. This is the user that runs the initial creation script. * One or several roles (=groups) are created with CREATE ROLE commands. * Access rights are assigned to each role for … text/html 2010-07-20T21:37:32+02:00 http://www.manitou-mail.org/wiki/doku.php/schema_1_0_0_upgrade?rev=1279654652&do=diff Below is the SQL script for PostgreSQL that upgrades the schema from 0.9.12 to 1.0.0 -- This SQL script upgrades the database schema for manitou-mail -- from 0.9.12 to 1.0.0 version \set ON_ERROR_STOP 1 BEGIN; ALTER TABLE body DROP COLUMN textsize; ALTER TABLE body ADD bodyhtml TEXT; ALTER TABLE header DROP COLUMN header_size; ALTER TABLE mail DROP COLUMN msg_day; ALTER TABLE mail RENAME attachments TO flags; UPDATE mail SET flags=1 WHERE flags!=0; UPDATE mail SET flags=flags|2 WHERE mail… text/html 2010-08-22T01:45:42+02:00 http://www.manitou-mail.org/wiki/doku.php/sql_analysis?rev=1282434342&do=diff This query extracts, for each of the header fields from a fixed list, the number of occurrences of all distinct values of the field. SELECT split_part(substr(lines, 1+position(E'\n'||field in lines), 200), E'\n', 1) as ct, count(*) FROM header, (values ('X-Priority'), ('Importance'), ('Precedence'), ('Priority'), ('X-MSMail-Priority'), ('X-MS-Priority')) as h(field) WHERE position(E'\n'||field IN lines)>0 group by split_part(substr(lines, 1+position(E'\n'||field in lines), 200), E'\n', 1) text/html 2010-08-20T10:22:15+02:00 http://www.manitou-mail.org/wiki/doku.php/start?rev=1282292535&do=diff Welcome to the Wiki for Manitou-Mail, a database-driven mail user agent. manitou-mdx manitou-mdx is a Perl program that is responsible for importing incoming mail into the database, and exporting outgoing mail to a Mail Transfert Agent. MDX stands for Mail Database eXchanger. It is supposed to run as a daemon (always running in background) although it can also be invoked as a normal command to import existing mailboxes. Its functionalities can be vastly extended by user-contributed plugins wr…