home | O'Reilly's CD bookshelfs | FreeBSD | Linux | Cisco | Cisco Exam  


sendmailSearch this book
Previous: 24.6 Prevent Aliasing with -n Chapter 24
Next: 25. Mailing Lists and ~/.forward

24.7 Pitfalls

  • The dbm and ndbm forms of the aliases (5) database 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 db files.

  • The aliases 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 sendmail .

  • Versions of sendmail that use the old-style dbm (3) libraries can cause overly long alias lines (greater than 1024 bytes) to be silently truncated. With the new databases, such as ndbm (3), a warning is printed. Note that V8 sendmail does not support old-style dbm (3) for this very reason.

  • Recursive (circular self-referencing) aliases are detected only when mail is being delivered. The sendmail program does not look for such alias loops when rebuilding its database.

  • Because of the way V8.8 sendmail locks the alias file for rebuilding, it must be writable. If it is not, sendmail 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.

Previous: 24.6 Prevent Aliasing with -n sendmail Next: 25. Mailing Lists and ~/.forward
24.6 Prevent Aliasing with -n Book Index 25. Mailing Lists and ~/.forward