Added support for SMFIC_UNKNOWN
Added support for SMFIC_DATA
Avoid infinite loop: signal handler modifies errno

The postfork_dispatcher relies on errno being EINTR when accept() gets interrupted by a signal (namely, sigchld here). However, the sigchld handler calls waitpid() which sets errno to ECHLD when no more child processes exist.
When the last child exits while the master is in accept(), accept() fails and errno is very likely to be ECHLD when checked. Previously, the handler proceeded as it does for real connections, forked a child process. That is likely to be the only child existing, terminating very soon (as there is no connection in fact), being reaped. The parent is likely accept()ing new connections, which brings us back to the beginning of the loop. This continues eating up a good part of the cpu, until one of the conditions named "likely" fails, which can take some minutes.
Proposed quick fix (this patch): do not rely on errno being EINTR, but simply go back to accept() in the parent when accept() did not return a socket.
Bump to 1.00
milter-protocol: add clarifying commentary for BODY and REPLBODY messages

The existing writeup did not explain that the strings sent in
SMFIC_BODY and SMFIR_REPLBODY messages are not NUL-terminated,
that multiple SMFIR_REPLBODY messages could be sent, or that
the body should have CRLF line endings.
Merge pull request #4 from siebenmann/docsupdate

milter-protocol: add clarifying commentary for BODY and REPLBODY messages
Merge branch 'master' of github.com:dwery/sendmail-pmilter