Ordinarily,
sendmail requires a file to live in a safe directory path. A directory path is safe when all
components are writable only by root or the trusted user specified in the TrustedUser
option (?§24.9.122 on page 1112). If the ErrorHeader file is found in an unsafe directory
path, sendmail will silently skip using that file.
Site policy might require you to maintain that file in an unsafe directory path (perhaps on a
central disk served via NFS). If you cannot remedy this situation you can enable this item.
By specifying the ErrorHeaderInUnsafeDirPath item, you increase risk but allow the
ErrorHeader option??™s file to live in an unsafe directory path.
24.9.39.5 DontBlameSendmail=FileDeliveryToHardLink
Ordinarily, sendmail will not append mail to files that have more than one link. Such files
pose a problem because sendmail has no idea whether such links are to special files (such as
/etc/passwd), and so cannot check to see whether those other links live in safe directory
paths. If sendmail finds such a file when trying to deliver, it will bounce the message with
an error such as this:
/path
(reason: can't create (user) output file)
Here, path is the full pathname to the file that had more than one link. If you need to maintain
hard links for administrative reasons, you can enable this item. When you enable the
FileDeliveryToHardLink item you increase risk but allow sendmail to deliver to files that are
hard links.
Pages:
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801