has Postfix new location of aliases.db?

[Miroslav Lachman]

Sahil Tandon wrote:
> On Thu, 04 Jun 2009, Miroslav Lachman wrote:
> 
> [...]
> 
> 
>>As you can see, file /etc/mail/aliases was modified (target of symlink)  
>>and then aliases.db was generated by `newaliases` command as 
>>/etc/aliases.db
>>
>>Above is with postfix-2.5.6,1 on FreeBSD 7.2-RELEASE #0: Fri May  1  
>>08:49:13 UTC 2009    GENERIC  i386
>>
>>This is with new postfix-2.6.1,1:
>># postconf -d | grep aliases
>>alias_database = hash:/etc/mail/aliases
>>alias_maps = hash:/etc/mail/aliases
> 
> 
> This was introduced with ports/134728, in which ALIAS_DB_MAP is compiled
> in as hash:/etc/mail/aliases.  I've rolled this back to the default value,
> which is system-dependent and chosen by ${WRKSRC}/src/util/sys_defs.h, which
> in turn relies on the ${WRKSRC}/makedefs script.
> 
> 
>>newaliases_path = /usr/local/bin/newaliases
> 
> 
> This is intentional and a good thing.  In mail/postfix prior to 2.6.x, the
> change was made in main.cf instead of being compiled in as a default; this
> is why you do not see it when viewing the *default* postconf output in 2.5.x;
> try postconf newaliases_path (i.e. without the -d flag).
> 
> 
>>And this is with older postfix-2.5.6,1:
>># postconf -d | grep aliases
>>alias_database = hash:/etc/aliases
>>alias_maps = hash:/etc/aliases
>>
>>There is definitely incompatible change in defaults :o(
> 
> 
> Indeed.  The attached patch (also filed as ports/135273) updates Postfix to
> 2.6.2 and makes the aforementioned changes.  As a result, I don't think we
> need to touch ports/UPDATING.

Thank you for fixing this issue.
It is always good to have it in UPDATING as some users still have 2.6.1 
in their ports tree.

Miroslav Lachman