It passed the file requirements set out in require_files = require_files = $local_part:$home/.procmailrc
becuase it spawned a new process. "Child process of procmail_pipe transport returned 77".
The director was satisfied with the initial permission changes. Now its is having a hard time spawning a new
process.
I think its because of this line in the transport:
user = $local_part
effectivly setting user = root and trying to spawn a /usr/bin/procmail process as root.
Somewhere other than .procmailrc there is a security setting keeping exim from allowing root processes to run
inside as a child process.
> On Fri, 12 Oct 2001, Joseph Kezar wrote:
>
> > I did what you suggested. It did attempt to read the .procmailrc in /root
> > Now it quickly responds with this message.require_files
> > root@???
> > Child process of procmail_pipe transport returned 77 (could mean permission denied) from command:
> > /usr/bin/procmail
> >
> > Am I missing something in my transport? Is there a magical security setting to not allow incoming "root"
> > emails?
>
> Nope - it says permission denied.
>
> chgrp eximgroup /root/.procmailrc && chmod g+r /root/.procmailrc
>
> Chris
>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
--
Joseph Kezar
