7 through V8.9, sendmail made this check only if PICKY_QF_NAME_
CHECK was defined when building sendmail. This was introduced because some
sites allow legitimate programs (other than sendmail) to write into sendmail??™s queue.
To fix this problem, either undefine PICKY_QF_NAME_CHECK when you build
sendmail (if your site allows other programs to write into the queue directory), or
trace down the process that is placing badly formed qf names in your queue and fix it.
11.5.2 Bad qf Owner or Permissions
Each qf file must be owned by the effective user ID under which sendmail runs (usually
root). A qf file must not be group- or world-writable. If a qf file fails either test, it
is considered bogus and is renamed to a Qf file. Then sendmail logs these messages:
id: bogus queue file, uid=owner, mode=perms
Losing qffile: bogus file uid in mqueue
Here, id is the identifier portion of the qf filename, owner is the uid of the user that
owns the qf file, and perms are the file permissions of the qf file, printed in octal.
This problem might point to bad queue directory permissions that allow anyone (or
some group) to place files there. Or it might indicate that some process other than
sendmail is writing to your queue.
11.5.3 Extra Data at End of qf File
One form of attack against sendmail is to append additional control lines to the end
of an existing qf file.
Pages:
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756