to the users of mod_smtpd

[Rian Hunter <ri...@MIT.EDU>]

Hi,

To Plugin Writers:

Mod_smtpd is pretty heavily input filters based now. There were some  
sneaky bugs in the code that I got rid of (the ability to type a  
single '.' and not terminate the message) and some major cleanups in  
the data handler code. The biggest changes are that now there is a  
filter that translates a single '.' into an EOS bucket, and an '..'  
into an '.'. Also header parsing now goes into a filter too. This is  
all pretty sweet stuff.

To Users:
Stay tuned for a postfix plugin and an auto-built modules directory.

Housecleaning:
Mod_smtpd has been written as high-level as possible so as not to  
reinvent the wheel and deal with io security issues. Regardless it is  
in dire need of a code/security audit. Does anyone know of any  
protocol-level security tests or topics to keep in mind that can be  
used to "robustify" mod_smtpd.

Showstoppers:
The autobuild system still currently does not check for libapreq2 (a  
necessity of one of the filters). Since I hate Autoconf and Makefiles  
I've been punting this, even though it's high priority. Patches anyone?

Mod_smtpd is also in dire need of documentation and probably its own  
website, both are coming soon.

Thanks!
Rian Hunter

Re: to the users of mod_smtpd

[Jem Berkes <jb...@users.pc9.org>]

> To Plugin Writers:

If examining the source on svn, also remember to check out my completed 
RBL / DNSBL modules under modules/access. In particular, mod_dnsbl_lookup 
provides functionality that could easily be used to implement a 
spamassassin-style scoring filter. That particular module can also be used 
without mod_smtpd.