2 on page 486) directive from inside an
aliases file must live in a safe directory path. A safe directory path is one in which all components
are writable only by root or the trusted user specified in the TrustedUser option
(?§24.9.122 on page 1112). But sometimes such :include: files must live in a directory in
which some component of its directory path is writable by root as well as others. When that
is the case, sendmail will log one of the following errors and will ignore those :include: files:
:include:/path... Cannot open /path: Group-writable directory
:include:/path... Cannot open /path: World-writable directory
If yours is such a site, and if you cannot correct the permissions, you can specify this item.
By enabling this IncludeFileInUnsafeDirPath item, you increase risk, but allow :include:
files to live in unsafe directory paths.
24.9.39.22 DontBlameSendmail=IncludeFileInUnsafeDirPathSafe
Even if you allow :include: files (?§13.2 on page 486) to live in unsafe directories, sendmail
will refuse to honor any references in them for delivery to files or programs. This behavior
is benign when only lists of addresses exist in those :include: files. But if you need to
further reference files and programs, you will also need to enable this item. With it enabled,
sendmail will run at greater risk, and will allow a :include: file that is in an unsafe directory
to include references to programs and files.
Pages:
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812