I've got a question about how procmail determines what UID is supposed to own
an rcfile. I've poked around in the list archive, but don't see anything that
relates to this situation.. apologies if this has been covered before.
I'm using procmail to handle delivery to virtual domains on my system. Using
sendmail's 'mailertable' database, I direct the mail through the Mprocmail
mailer, using a procmailrc specific to the domain. The rc file is owned by
the domain's admin user.
With older versions of procmail, this presented no problem -- the various
mailboxen delivered to by procmail would end up being owned by the admin user
for the domain, and all was well. However, after testing an upgrade, I'm
running into problems with the "Suspicious rcfile" error. Here's my test
case:
mailertable entry:
test.com procmail:/usr/local/etc/conundrum/procmailrcs/test.com
the rcfile and containing directory:
drwxr-xr-x 2 root wheel 512 Dec 5 08:08 procmailrcs/
-r--r--r-- 1 test virtdom 404 Nov 18 17:26 procmailrcs/test.com
And the domain's admin user passwd entry:
test:*:2000:100:test.com:/depot/virtual/test.com/:/bin/false
GID 100 == "virtdom", so I know there isn't a secondary GID problem, which
I've spotted being mentioned on the list.
It would appear that procmail doesn't believe UID 2000 is the appropriate
owner for this rcfile. Am I missing something here? Is there some way to
convince procmail that I know what I'm talking aboout? :) If possible, I'd
like to avoid disabling this security check altogether.. knowing how procmail
determines who should own the rc file is probably all I need.
Thanks for any help,
Matt
----------------------------------------------------------------------
``Life moves pretty fast. If you don't stop and look around once in a while,
you could miss it.''
-- Ferris Bueller
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail