From: Tony Earnshaw (tonyebilly.demon.nl)
Date: Mon Aug 01 2005 - 04:50:07 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

man, 01.08.2005 kl. 03.22 skrev mouss:

> > 1544 [root:tru] /etc # cat /etc/aliases
> > grungefoo.nl tonnibilly.demon.nl
> >
> > 1545 [root:tru] /etc # postmap aliases
> > 1546 [root:tru] /etc #
> >
> > 1546 [root:tru] /etc # postmap -q grungefoo.nl hash:./aliases
> > tonnibilly.demon.nl
> >
>
> what about
> # cp .../postfix/access /etc/rc
> # postmap /etc/rc
> # postmap -q foobar /etc/rc
> ?

This is a ridiculous example.

> just because you give it a name doesn't mean it is what it should be.

Rubbish.

> we call aliases files those old unix style aliases files, the syntax of
> which is
> foo: bar
> and they are used via postalias or newaliases.
>
> what you are using is a standard "hash" file that you compile with postmap.

Having looked at the newaliases-style alias map, I understand that it's
differently formatted from other maps. I've never used such a formatted
map for aliases; apart from a brief excursion into a mailman alias saga,
which I left for Dax Kelson's postfix-to-mailman.py, I've never used
/etc/aliases.

All my alias maps and virtual alias maps are in LDAP, which uses
standard table lookups and "just works". If I do use an ordinarily
formatted hash map for /etc/aliases, that works too. In fact, I can do
more with such a map than with a newaliases-formatted map.

Neither are virtual alias maps, as detailed in VIRTUAL_README, formatted
in the newaliases (or as you put it "old unix style aliases files)
style.

--Tonni

--
mail: tonyebilly.demon.nl
http://www.billy.demon.nl

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]