At 2002-10-09 13:15 -0500, Philip Guenther wrote:
To quote the DIAGNOSTICS section of the procmail(1) manpage:
Oops!
Autoforwarding mailbox found
The system mailbox had its suid or
sgid bit set, procmail terminates
with EX_NOUSER assuming that this
mailbox must not be delivered to.
(*Every* message that procmail can log is documented in the DIAGNOSTICS
or EXTENDED DIAGNOSTICS section of the procmail(1) manpage.)
Thanks. The assumption seems mistaken, however (first para), and the
conduct in any event gratuitous (second para). Quote:
+ A file is marked as a candidate for mandatory locking by setting the
+ group-id bit in its file mode but removing the group-execute bit. This
+ is an otherwise meaningless combination, and was chosen by the System
+ V implementors so as not to break existing user programs.
+
+ Note that the group-id bit is usually automatically cleared by the
+ kernel when a setgid file is written to. This is a security
+ measure. The kernel has been modified to recognize the special case of
+ a mandatory lock candidate and to refrain from clearing this
+ bit. Similarly the kernel has been modified not to run mandatory lock
+ candidates with setgid privileges.
(Linux 2.4.19/Documentation/mandatory.txt. The file is datestamped
April 1998.)
Michael Talbot-Wilson
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail