On Sat, 13 Sep 1997, Philip Guenther wrote:
Howard Co Schls <hawks(_at_)clark(_dot_)net> writes:
I am running a list that uses the following script:
LOGFILE=$HOME/.procmail/log
:0
* ^From:(_dot_)*rivhillregister(_at_)lawlab(_dot_)com
{
:0fhw
| sed -e '/^#/d' -e '/^$/d' -e 's/^/Bcc: /' rivhillregister ; \
formail -I"From " -I"To: Unofficial Riverhill Mailing List" -ICc:
-IBcc:
:0
! -t
}
< snip >
/usr/lib/sendmail: /usr/lib/sendmail: cannot open
...
It appears that procmail has decided to try to write the messages to a
file called sendmail -t rather than call the application sendmail. What
could possibly cause this?
The problem is with sendmail, not procmail. The last of the log lines
that I quoted above was not generated by procmail: the word "cannot"
doesn't appear in the procmail sources except in comments, and it never
uses perror, strerror, or sys_errlist. Can you invoke /usr/lib/sendmail
by hand, and what exactly are the permissions of /usr/lib/sendmail?
The permissions for sendmail are:
-rwsr-xr-x 1 root mail 309020 Sep 13 18:39 /usr/lib/sendmail
I am not sure if this has changed recently, since my ISP is prone to
change things like this without warning or explanation. I can invoke
sendmail -q to flush the queue when I first log on, but I have not tried
-t manually, as I have no real need to do so.