Milter-greylist

Hi,

This is not a serious bug, but a confusing "misfeature" ...

When I updated from some 4.2.* version to 4.3.4, the following
error message started to appear when I check the configuration
file with "milter-greylist -c" (it's my habit to do that after
every change):

legacy configuration file '/etc/mail/greylist.conf' is used instead
of '/usr/local/etc/mail/greylist.conf'. IT SHOULD BE RENAMED!
config file "/etc/mail/greylist.conf" is okay

Well, /usr/local/etc/mail/greylist.conf is a Symlink to
/etc/mail/greylist.conf.  This is on purpose (we want all
mail-related configuration centralized in /etc/mail), and
I'm certainly not going to rename anything, as the error
message seems to require.

Is there a way to improve the logic behind that error message,
so it is less confusing or misleading?  For example, suppress
the message if *both* files exist, and one is a link to the
other?  Other suggestions?

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Gesch\ufffdftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M\ufffdn-
chen, HRB 125758,  Gesch\ufffdftsf\ufffdhrer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

Python is executable pseudocode.  Perl is executable line noise.

On Thu, May 20, 2010 at 02:34:36PM +0200, Oliver Fromme wrote:
> 
> When I updated from some 4.2.* version to 4.3.4, the following
> error message started to appear when I check the configuration
> file with "milter-greylist -c" (it's my habit to do that after
> every change):
> 
> legacy configuration file '/etc/mail/greylist.conf' is used instead
> of '/usr/local/etc/mail/greylist.conf'. IT SHOULD BE RENAMED!
> config file "/etc/mail/greylist.conf" is okay

I made the error message less aggressive in later version, as I still use
/etc/mail/greylist.conf, and I felt it a bit annoying.

-- 
Emmanuel Dreyfus
manu@...