Exim Email Control Specification
From Computer Tyme Support Wiki
This is a specification for an email control program I'd like to have written for Exim. I want to make this project public domain so that others can share in it. I want to keep it simple and flexable. Looking for some volunteers to work on it. I can trade significant web hosting for people who will make this happen.
Contents |
Overview
The idea behind this project is to create a PHP front end to text files on the back end that control Exim allowing users to have a high degree of personalization over feature that primarilly control spam. This would include personal white lists, personal black lists, forwarding, etc. The backend might also be a database but I'm leaning towards text files for simplicity and if done right should be very scalable. Once the structure is in place it should be easy to add a lot of customizations to give users every toy they ever dreamed of.
Authentication
The idea is yo use IMAP for authentication. All users and managers will use and email address and password to authenticate. It will attempt to log in to the email account and if successful, the user is considered logged in. Once loged in the user will be able to set all the features of their own account. If the user is a manager they well see additional choices to manage the things they are allowed to manage.
Control Files
Here is what I'm proposing for a control file structure. All of these files are test files. The directory structure is designed to be fast not having a lot of files in any one directory.
/etc/mailcontrol /etc/mailcontrol/config /etc/mailcontrol/managers /etc/mailcontrol/domains /etc/mailcontrol/domains/example.com /etc/mailcontrol/domains/example.com/passwd /etc/mailcontrol/domains/example.com/shadow /etc/mailcontrol/domains/example.com/alias /etc/mailcontrol/domains/example.com/config /etc/mailcontrol/domains/example.com/managers /etc/mailcontrol/domains/example.com/blocked-from /etc/mailcontrol/domains/example.com/blocked-hosts /etc/mailcontrol/domains/example.com/white-from /etc/mailcontrol/domains/example.com/white-hosts /etc/mailcontrol/domains/example.com/users /etc/mailcontrol/domains/example.com/users/joe /etc/mailcontrol/domains/example.com/users/joe/config /etc/mailcontrol/domains/example.com/users/joe/vacation /etc/mailcontrol/domains/example.com/users/joe/forward /etc/mailcontrol/domains/example.com/users/joe/blocked-from /etc/mailcontrol/domains/example.com/users/joe/blocked-hosts /etc/mailcontrol/domains/example.com/users/joe/white-from /etc/mailcontrol/domains/example.com/users/joe/white-hosts
The base director contains the master control files for the entire system. Booleans and settings in the config files. The managers file contains a list of email addresses of system managers.
Under each domain is the master files that control that entire domain. This includes the passwd, shadow, and alias files that mimick the unix passwd, shadow, and alias files. I've used a few examples of master white list and block lists but any number of files can be added for greater customization.
Each domain has a users folder which contains the user's accounts and personal settings. This allows the user to customize their own experience just the way they want. A few examples are given here but there's no limit to what you can add.
MySQL
Instead of the file structure it might be better to do it all with MySQL. I do however like the simplicity of these pure text files but I could be pursuaded by a good programmer and really clean code that makes it easy for people to add new features. I'd like to start with the text file interface and make database backends optional.
Administration
There are several levels of priveledges in this system. When the user is authenticated the system knows who they are and gives them the menus they should have access to. Three levels that need to be set up are Administrators, Domain Owners, and users.
Master Admins
Master admins control the system and can set anything else. They need to be able to create new domains, grant priveledges to other users, and config the system.
Domain Owners
Domain owners need dominion over their domain(s). Once they log in they can create and delete users, create aliases, manage block lists and white lists and any other settings that affect their domain. They would also have full control of all the users setting under their domains.
Email Users
Email Users would have control of their account. They can change their personal settings, vacation messages, forwarding, password, etc.
Feature Expansion
Once this structure is in place it should be easy to add new features. All you have to do to the front end is create a new text file to store the feature in and an Exim backend to run it. Both should be really easy. Menus can be created to allow users to block all 8 bit asian email, Block entire continents. Block words in subject lines. Personal blackhole (rather than bounce), forward email from specific users to server side imap folders, the sky is the limit. All we have to do is do it right in the first place, keep it simple, and we all win.
Exim Backend
Exim is very powerful. It's trivial to write a backend that runs off this structure. Dovecot can be easilly configured to access this structure as well. However I think if this were done right it should be generic enough to work with other MTAs and a variety of configurations. The backend assumes that if the files don't exist then nothing happens. If they do exist then they are read and processed.
So - who want's to make it happen?
A good programmer should be able to whip this up in a few days. I'm not much of a programmer anymore so I need someone to get it started and I can finish it. So - who wants to help get this going. The results will be GPL'd and everyone gets to share in the finished product. Email me if you want to do it. marc@perkel.com
