Opinionated email server
Find a file
2017-03-06 16:31:49 +02:00
config fixed broken imap 2017-03-06 16:13:40 +02:00
imap-core Initial preview 2017-03-05 23:45:50 +02:00
.eslintrc Initial preview 2017-03-05 23:45:50 +02:00
.gitignore Initial preview 2017-03-05 23:45:50 +02:00
api.js fixed broken imap 2017-03-06 16:13:40 +02:00
Gruntfile.js Initial preview 2017-03-05 23:45:50 +02:00
imap-notifier.js Initial preview 2017-03-05 23:45:50 +02:00
imap.js fixed broken imap 2017-03-06 16:13:40 +02:00
indexes.js Initial preview 2017-03-05 23:45:50 +02:00
LICENSE Initial preview 2017-03-05 23:45:50 +02:00
lmtp.js fixed broken imap 2017-03-06 16:13:40 +02:00
package.json fixed broken imap 2017-03-06 16:13:40 +02:00
README.md Updated README 2017-03-06 16:31:49 +02:00
server.js fixed broken imap 2017-03-06 16:13:40 +02:00

Wild Duck Mail Agent

This is a very early preview of an IMAP server built with Node.js and MongoDB.

Goals of the Project

  1. Build a scalable IMAP server that uses clustered database instead of single machine file system as mail store
  2. Push notifications. Your application (eg. a webmail client) should be able to request changes (new and deleted messages, flag changes) to be pushed to client instead of using IMAP to fetch stuff from the server

Todo

Does it work? Yes, it does. You can run the server and get a working IMAP server for mail store, LMTP server for pushing messages to the mail store and HTTP API server to create new users.

Is the server scalable? Not yet. These are some actions that must be done:

  1. Separate attachments from indexed mime tree and store these to GridFS. Currently entire message is loaded whenever a FETCH or SEARCH call is made (unless body needs not to be touched, for example if only FLAGs are checked)
  2. Optimize SEARCH queries to use MongoDB queries. Currently only simple stuff (flag, internaldate, not flag, modseq) is included in query and more complex comparisons are handled by the application but this means that too much data must be loaded from database (unless it is a very simple query like "SEARCH UNSEEN" that is already optimized)
  3. Optimize FETCH queries to load only partial data for BODY subparts
  4. Build a publish-subscribe solution to notify changes process-wide (and server-wide). Currently update notifications are propagated only inside the same process (journaled update data is available from DB for everybody but the notification that there is new data is not propagated outside current process).

Usage

Install dependencies

npm install --production

Modify config file

Run the index queries in MongoDB (optional, the app would work without it as indexes only become relevant once you have more than few messages stored)

Run the server

npm start

Create user

Users can be created with HTTP requests

POST /user/create

Arguments

  • username is an email address of the user
  • password is the password for the user

Example

curl -XPOST "http://localhost:8080/user/create" -H 'content-type: application/json' -d '{
    "username": "username@example.com",
    "password": "secretpass"
}'

The response for successful operation should look like this:

{
    "success": true,
    "id": "58bd6815dddb5ac5063d3590",
    "username": "username@example.com"
}

After you have created an user you can use these credentials to log in to the IMAP server. Additionally the LMTP server starts accepting mail for this email address.

License

Wild Duck Mail Agent is licensed under the European Union Public License 1.1.