forms of the
files contain binary
integers. As a consequence, those database files cannot be
shared via network-mounted file systems by machines of differing
architectures. This is not a problem for 4.4 BSD
file and database files can be used to circumvent
system security if they are writable by the wrong users.
Proper ownership and permissions are neither checked
for nor enforced by
that use the old-style
libraries can cause overly long alias lines (greater than 1024 bytes)
to be silently truncated. With the new databases,
(3), a warning is printed.
Note that V8
does not support old-style
for this very reason.
Recursive (circular self-referencing) aliases are detected only when
mail is being delivered. The
program does not look for
such alias loops when rebuilding its database.
Because of the way V8.8
locks the alias file for rebuilding,
it must be writable. If it is not,
prints the following and
and skips the rebuild:
warning: cannot lock
: Permission denied
This can be a problem if the master alias file is shared via NFS.