procmail
[Top] [All Lists]

Re: rc compatibility?

1999-12-17 11:03:27
On Dec 17, 11:44am, Philip Guenther wrote:

I do have a followup question.  Multiple permission changes to the rcfile
didn't seem to have an effect.  I tried 755, 600, 777; but when I changed
the home directory to 755 that did the trick.  With the home directory at
755, the permissions of the rcfile didn't matter; it worked whether the
rcfile was group writeable or not.  We're running Solaris 2.6 and we call

Hmm, how exactly are you invoking procmail?  Procmail only checks group
permissions when no rcfile was specified on the command line, causing it
to use the default rcfile.

And perhaps when -m is specified on the command line?

This is the description from the manpage:

      -m   Turns procmail into a general purpose mail filter.   In
           this  mode  one rcfile must be specified on the command
           line.   After  the  rcfile,  procmail  will  accept  an
           unlimited  number  of  arguments.   If the rcfile is an
           absolute path starting with  /etc/procmailrcs/  without
           backward  references  (i.e. the parent directory cannot
           be  mentioned)  procmail  will,  only  if  no  security
           violations are found, take on the identity of the owner
           of the rcfile (or symbolic link).   For  some  advanced
           usage  of  this  option you should look in the EXAMPLES
           section below.

I don't know if it was the presence/lack of -m, but I know that when I
switched to 3.14, that a shell script which had been working, that
built a temporary procmail .rc file was failing with permission
checks, because the .rc file was written into /tmp, which is obviously
world writeable.  When I changed the script to create the temp. .rc
file under my home dir, the complaint went away.  Personally, I would
have liked to see a switch that let me disable the permission checks.

Philip, separate question - the blurb on the updated FAQ said it would
recommend that folks not upgrade to 3.14, but the only thing that I saw
was the prob. with home dir. permissions, and Red Hat's config.  Is
that the only prob.  to woory about?

<Prev in Thread] Current Thread [Next in Thread>