Re: Request for Procmail Plugin

[Nic B. <ni...@it...>]

On the other hand, procmail can be invoked with the name of the procmailrc
file to use.  So, it would not be too hard to establish a sitewide location
for procmailrc files, and give the web server rights to this location.  For
example, procmail could be told to find the user's procmailrc file in the
squirrelmail/data/ directory.  Just a thought.

Cheers,
	-nic

On Tue, June 19, 2001 8:20 am, Paul Joseph Thompson wrote:
>> Hi,
>>
>> i always thought that would be cool. like configuring .forward
>> via SM. But as long as you have a file based permission system, I
>> have no clue how to manage the permissions. I personally don't
>> want my webserver to write to all my users home directorys. If
>> there is a secure solution to it I will write a maildrop
>> interface. maildrop is (as far as I know) the cyrus filter stuff.
>> (this will force me to install it at my server. now i can't
>> filter at all ;( )
> 
> My best bet on permissions is that the plugin requires a
> person's .forward or .procmailrc file to be writable by the web
>server. I know that this is generally bad, but I am not sure of any
>other way to do this.
> 
> Of course, any vulnerablity in the web server and everyone's mail
> becomes immediately vulnerable.

-- 
Nic Bernstein                           ni...@it...
Knowledge is free but you must provide your own container