clintwebb / mailsrvd Goto Github PK

The existing outgoing sender code tries to send the email, and if that
fails, it does not try again until the daemon is restarted, and then it
only tries on startup.   Need to be able to set a delivery date, and try
sending the email after that date.

The daemon currently used a mysql database to store all account config and
email data.  One of the main reasons for using mysql is because it offers
very easy and effective master/slave synchronization.  

The code (and config file) needs to provide the ability for a reading and
writing database connection.  When retrieving emails it will read the data
from one database, but when deleting the emails that were retrieved, it
will connect to the writing database and perform the operation there.

This will allow for the situation where we have a master database, and
multiple slave databases. Normally this would be the situation for improved
performance.

To take this a step further, we need to keep a reference of some sort to
indicate that an account is in use.  This is for cases where we have
multiple instances of the daemon running.  This would be accomplished by
connecting to the master database, locking the table, checking the value of
a field associated with the account, and if it is null, set the date.  Then
when other instances attempt to use that account before it is released, it
will return a message saying that the account is already in use.  

When the thread of a connection closes, it will first need to connect to
the master database and clear that field.  The field would contain a date,
and a cron job would fire every night that would make sure that any account
in-use fields that have a date older than 24 hours are cleared, because
surely we dont have any connections that are downloading messages for more
than 24 hours.

The mail server config is mostly done in the database, so changes can be
implemented fairly simply there.  However, we should probably provide a
very simple web-based interface to add domains, users, and addresses to the
system.  Simple web-server can be included in the daemon code.  

Webmail can be integrated into the daemon.  We could do this two ways.  We
can provide perl scripts that can be used as CGI from apache (or whatever).
 Or we can listen on a port and provide the webmail from the daemon
directly.  Since all the emails are in a database, it should be fairly easy
to integrate either solution.

If a sender system returns with a code that says delivery couldnt be made,
but to try again, it should reset the delivery date to the appropriate
time, and then try again.

Block lists use a DNS lookup to provide information on sender hosts and
whether we want to accept emails from them.  This is to stop spammers from
sending from known spammer-friendly hosts.   Should be configurable in the
database as to which DNS blockers we utilise.

What steps will reproduce the problem?
1. Segmentation problem
2.
3.

What is the expected output? What do you see instead?
running mail server. actual result : segmentation fault

What version of the product are you using? On what operating system?
latest version

Please provide any additional information below.
Is there any configuration document to configure the mail server

After the server has been running for a while, it will receive a connection
and attempt to open the database.  Database call returns a '14' error code.
 The server then causes an assert because it was expecting the database
call to return a result.

Need an init script that can be used to start and stop the daemon.

When a connection comes in from an IP address we have never seen before, we
will send a reply that indicates that the message cant be delivered at this
time and to try again later.  This stops a lot of spam that is being sent
by bulk as only real mail servers tend to respond to this correctly.

The path to the mail database should be in the config file.  It is
currently hard-coded into the source.

If the database connection is lost (ie, the database server is reset), then
the mail server should re-establish a connection.  Currently it only
connects on startup.

When the mail server daemon is installed, it needs to be able to connect to
the mysql database and add the database and all the tables, and possibly
add some entries.

The outgoing messages are not being sent, that code has not been converted
to use the mysql database and is currently disabled.