Milter-greylist

Hello,

I have recently tried to upgrade mg from version 4.3.2 to 4.3.4 on Tru64
UNIX.
I used the same configuration options and make as with the previous
version.

Now I got the following warning at the end of the configure stage:

config.status: WARNING:  'Makefile.in' seems to ignore the --datarootdir
setting

At startup time of the new binary I got the following message:

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

I got as well the following error soon after startup and the mg exits:

milter-greylist:
mkstemp("/usr/local/var/milter-greylist/greylist.db-HlnPA0pY") failed:
No such file or directory

Was there any incompatible changes which I am not aware of?
Or it should just work as before and there is a bug on that platform?

Bests,
Attila

Attila,

There was some discussion a while back about moving the configuration  
to "support normal user 'make install'" (search for this subject in  
the archives).

So the 'legacy configuration' notice should just be a warning.

As for the mkstemp issue, you should just be able to make those dirs  
and go.

btw, what were your config parameters?

Bill

Bill Levering
idbill@...
KFP: 0C38 4D7E 5B50 94FE 992D  406D 6C81 DE33 5459 A1AC

On Dec 10, 2009, at 2:21 AM, <attila.bruncsak@...> wrote:

> Hello,
>
> I have recently tried to upgrade mg from version 4.3.2 to 4.3.4 on  
> Tru64
> UNIX.
> I used the same configuration options and make as with the previous
> version.
>
> Now I got the following warning at the end of the configure stage:
>
> config.status: WARNING:  'Makefile.in' seems to ignore the -- 
> datarootdir
> setting
>
> At startup time of the new binary I got the following message:
>
> legacy configuration file '/etc/mail/greylist.conf' is used instead of
> '/usr/local/etc/mail/greylist.conf'. IT SHOULD BE RENAMED!
>
> I got as well the following error soon after startup and the mg exits:
>
> milter-greylist:
> mkstemp("/usr/local/var/milter-greylist/greylist.db-HlnPA0pY") failed:
> No such file or directory
>
> Was there any incompatible changes which I am not aware of?
> Or it should just work as before and there is a bug on that platform?
>
> Bests,
> Attila
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

<attila.bruncsak@...> wrote:

> Was there any incompatible changes which I am not aware of?
> Or it should just work as before and there is a bug on that platform?


A quick fix for you would be to configure --sysconfdir=/etc
--localstatedir=/var

Here is the long story:

The previous configure script forced --sysconfdir=/etc
--localstatedir=/var 

This oddity has been "fixed", with the result of a bare configure
producing a milter-greylist that look in /usr/local/etc/mail and
/usr/local/var/milter-greylist. 

There is a backward compatibility check for a config file in /etc, hence
the rough warning you get. The same test was forgotten for the dump
file, which should not be a problem, as loosing the database just cause
extra delay.

What is really surprising here is that make install did not create
/usr/local/var/milter-greylist (the install-db rule should do it). 

What does make install produces at yours?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

> There was some discussion a while back about moving the 
> configuration  
> to "support normal user 'make install'" (search for this subject in  
> the archives).
> 
> So the 'legacy configuration' notice should just be a warning.
> 
> As for the mkstemp issue, you should just be able to make those dirs  
> and go.

Thanks the info.
But I will rather try to change the config parameters
to match the current production directories.

> 
> btw, what were your config parameters?
> 

My site specific configure script is the following, and I am running it
as a non privileged user:

#! /usr/bin/ksh
CFLAGS="" ./configure --with-libmilter=/usr/local/src/sendmail/libmilter
make

Bests,
Attila

> > Was there any incompatible changes which I am not aware of?
> > Or it should just work as before and there is a bug on that 
> platform?
> 
> 
> A quick fix for you would be to configure --sysconfdir=/etc
> --localstatedir=/var
> 
> Here is the long story:
> 
> The previous configure script forced --sysconfdir=/etc
> --localstatedir=/var 

Thanks for the detailed information,
I will add this to my site specific configure script.

> 
> This oddity has been "fixed", with the result of a bare configure
> producing a milter-greylist that look in /usr/local/etc/mail and
> /usr/local/var/milter-greylist. 
> 
> There is a backward compatibility check for a config file in 
> /etc, hence
> the rough warning you get. The same test was forgotten for the dump
> file, which should not be a problem, as loosing the database 
> just cause
> extra delay.

Would be great to add the checking code.
The result is more than a simple extra delay,
milter-greylist is exiting with EX_OSERR.

> 
> What is really surprising here is that make install did not create
> /usr/local/var/milter-greylist (the install-db rule should do it). 
> 
> What does make install produces at yours?
> 

There is no surprise here, I am not running "make install" at all.
I am just copying the new milter-greylist binary through our firewall
from the internal development system to the external production
mail perimeter system.

Bests,
Attila

<attila.bruncsak@...> wrote:

> There is no surprise here, I am not running "make install" at all.
> I am just copying the new milter-greylist binary through our firewall
> from the internal development system to the external production
> mail perimeter system.

Right, that explains everything. Feel free to contribute the code that
create the dump directory before dropping root privileges.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...