Differences between revisions 7 and 8
Revision 7 as of 2005-06-15 09:36:11
Size: 2715
Editor: 165
Revision 8 as of 2009-09-20 22:58:23
Size: 2717
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Email: [[MailTo(sentialist AT SPAMFREE gmail DOT com)]] Email: <<MailTo(sentialist AT SPAMFREE gmail DOT com)>>
Line 29: Line 29:
Totally revamped drop-in replacement for the existing [http://james.apache.org/javadocs/org/apache/james/smtpserver/SMTPServer.html SMTPServer]. Possibly patches or pieces of coded targeted for ASF containers. Totally revamped drop-in replacement for the existing [[http://james.apache.org/javadocs/org/apache/james/smtpserver/SMTPServer.html|SMTPServer]]. Possibly patches or pieces of coded targeted for ASF containers.

Email: <sentialist AT SPAMFREE gmail DOT com>


My name is Le Dinh Bao Chau, Marcus. Currently I study at School of Computer Engineering, Nanyang Technological University, Singapore (http://www.ntu.edu.sg/sce/). I love programming and I have been programming for seven years. During such period, I have done many projects which are standalone and web-based applications using C,C++, Java and C#. My favourite languages are C++ and Java.

Though I have used Linux for more than 2 years, I am still new to open-source software development. I hope I would gain valuable experiences and knowledge about it during this summer. The project James Fast-fail implemetation caught my eyes quickly and I really get interested with it. However as I was acknowledged of this event quite lately, I have little time on investing the project. Still, I am confident I can catch up and finish it in time. Below is what I have obtained last few days. I will keep updating it as I find out more useful information.


One of the problem posed to James mail server developers is the degrade in performance when the server is hit heavy spam traffic and D.O.S attack. An approach to deal with this problem is extending the SMTP protocol which will allow the server to terminate the conversation before it wastes resource downloading spam, oversized, undeliverable or rules violated messages. The rule can be set and unset flexibly.

Another issue is that under the current design very little control is possible over a running instance of James mail server - the main configuration method is to edit configuration manually and then restart (which takes significant time).

Proposed solutions

Following FastFail proposal by DannyAngus and NoelBergman

Advantages for ASF

  • A solid foundation for implementing a feature heavily demanded by current internet realities - SMTP fast fail
  • Possible a new insight on the issue of reconfiguring components inside IoC containers


Totally revamped drop-in replacement for the existing SMTPServer. Possibly patches or pieces of coded targeted for ASF containers.


  • start active coding around June the 25nd, after I finish my internship. I will go thru the existing code before that to get the clear image of what should be done.
  • The draft version should be available around 15th July.
  • All changes to be made will be carried out from 16th to mid August.

After August 14 fix react to bug reports and requests for enhancements. If time permits look into integration with scripting languages.

ChauLe (last edited 2009-09-20 22:58:23 by localhost)