Milter-greylist

> Here is 3.0rc1:
> 
> http://ftp.espci.fr/pub/milter-greylist/milter-greylist-3.0rc1.tgz
> MD5 (milter-greylist-3.0rc1.tgz) = b9bd8dc226ef54dc1ced49eeb6bd91b2
> 
> ChangeLog since 3.0alpha6:
> 3.0rc1
>         Warn about ignored ACL lines after acl default rule
> 	Small documentation fix (Leena Heino)
> 	Fix automatic config reload
> 

Should not we call it beta instead of release candidate?
In the series two we had beta, for example: 2.0b5.

About the systems with missing vsyslog() again.

The reference to the LINE_MAX comes from the man page of syslog(3) on Tru64 UNIX,
here is an extract:

> format [value...]
>            Similar to the printf fmt string, with the difference that %m is
>            replaced by the current error message obtained from errno.  A
>            trailing newline can be added to the message if needed. The value
>            parameters are the same as the value parameters of the printf()
>            function.  Callers of syslog() must ensure that the message is
>            not longer than LINE_MAX bytes. Results are unspecified if sys-
>            log() is called with a message larger than LINE_MAX bytes.

I do not know does the utilization of LINE_MAX as constant macro creates any
problem on other platform with missing vsyslog()? Is this constant used for
something else or have a weird value there?

On the other hand the "%s" format string is imperative. It may be replaced with
"%s\n" if really needed I guess, but I did not tested it on Tru64 UNIX. 

I attach now a patch hoping that it does not create any problem.

Bests,
Attila