Lack of documentation is becoming a problem for acceptance.


However, writing software without defects is not sufficient. In my experience, it is at least as difficult to write software that is safe - that is, software that behaves reasonably under adverse conditions.

The challenge with Postfix, or with any piece of software, is to update software without introducing problems.

Writing software that's safe even in the presence of bugs makes the challenge even more interesting.

Coming back to the topic of computer security, the TCP Wrapper is an example of such a safety net. I wrote it when my systems were under attack by someone who appeared to walk through walls.

In a previous life I wrote the software that controlled my physics experiments. That software had to deal with all kinds of possible failures in equipment. That is probably where I learned to rely on multiple safety nets inside and around my systems.

Adding functionality is not just a matter of adding code.

This will surprise some of your readers, but my primary interest is not with computer security. I am primarily interested in writing software that works as intended.

I was going to visit IBM for six months as a visiting scientist. Now, six months is a lot of time, so I came with a whole list of projects that I might want to work on.

I want to avoid locking people into solutions that work only with Postfix. People should have a choice in what software they want to use with Postfix, be it anti-virus or otherwise.