This document contains various ideas. They are either less useful
or need some more evaluation. Just to get started, here is a small
explanation about TLMP.

TLMP and bloated software

	In general, software grows and grows until they are consider bloated.
	They have zillions of features and most are barelly useful. One reason
	for this is that it is often far easier to add a functionality
	inside a program than outside of it. Programs are usually not built
	as libraries so they can't be commanded from outside.

	One solution is to add a macro langage to the program and allow
	various task to be perform there. This solves many problems but not
	all. Most of the time, a feature involves a change in the way the
	program	normally react. So the program must be changed. We are not
	just adding a feature.

	TLMP offers a solution. Programs are easily modified and visual.
	Most of the time, a single source, the main source, has to be
	modified. TLMP programs are generally engineered so most of the
	important areas are concentrated in the main source (periscope effect).

	One goal of TLMP is to supply programs as high level components easily
	enhanced and integrated. Tlmpmail is the first.

	The following ideas are not implemented in tlmpmail but maybe
	in the author version.


Some ideas....

	Deleted message are save in the deleted folder and this folder always
	keep either the last N message, or the last N days. We could enhance
	the filter to have a "deleted folder" entry. When deleting a mail
	we could walk the filter and any matching one with a filled
	"deleted folder" field would trigger a copy of the message in this
	folder. So we may end with one deleted folder per message type.

	Use the sent-mail folders to create the thread view. This is useful
	when a thread went on between to person outside of a mailing
	list. To recover the thread, you must know what you wrote.